Corigo Vietnam, LLC Logo

Enterprise Software at Small Business Prices

SUPPORT SYSADMIN FAQS
Support >> SysAdmin FAQs
 

Installation Instructions

Table of Contents

Overview
System Requirements
Installation Preparation
Installing Prerequisite Applications
       1) Installing Java JDK
       2) Installing Apache Tomcat
       3) Installing Macromedia JRun
Installing Workplace Enterprise®
       1) Run Setup Executable
       2) License Configuration
       3) License File
       4) Java Application Server
       5) Destination Configuration
       6) Database Configuratin
Finishing Up
       1) Configure Tomcat to Execute all Servlets
       2) Configure ODBC
       3) Share Document Folders
       4) How to Run Workplace Enterprise®
       5) Trouble Shooting

Overview

Workplace Enterprise® is an enterprise solution built upon Java application server and database technology. Therefore, the Java application server and the database server must be pre-installed before the installation of Workplace Enterprise® can occur.

During the installation process the Workplace Enterprise® setup program shall request the name of the server, director location of the Java application server (such as Apache Tomcat 4.x or Macromedia JRun 4.x), the web application name to use, the name of the database server, database name and login details, the location of the document management files, and an ODBC data source name for linking to the database.

There are not any installs required for the client computers, as Workplace Enterprise® is accessed via a standard web browser.

System Requirements

The following programs are required to have been installed before Corveum Workplace Enterprise® can be setup. If any of these programs are not installed the installation process will exit.

  • Database Server: Microsoft SQL Server 7.0 or 2000
  • Java JDK: 1.3 or greater
A complete list of System Requirements is available below.

Installation Preparation

Before installing Workplace Enterprise® you'll need to consider the following installation details.

Host Server

  • Which server to install Corveum Workplace Enterprise® on to

Java Application Server

  • Java Application Server home directory location
  • Web application name to use for Workplace Enterprise®

Document Management Storage Location
  • Where to store the files that Workplace Enterprise® will manage

Database Server

  • Server name housing Microsoft SQL Server
  • Where to store the MS SQL Server data files
  • Workplace Enterprise® database name
  • Database login username and password
  • ODBC data source name for connecting to the database

Installing Prerequisite Applications

Installing Java SDK

The Java SDK is located on the install CD in the directory called Java. Double-click on the executable and install it where ever desired.

Installing Apache Tomcat Server

Once Java has been installed, next you must install the Java application server Apache Tomcat. It's located on the CD in the directory called Apache Tomcat and can be installed anywhere.

Note: The directory path for Tomcat cannot contain any spaces.

c:\ApacheGroup\Tomcat4.1 (correct)
c:\Apache Group\Tomcat 4.1 (not correct)

Remember to configure Tomcat for all JSP pages (see Finishing Up) before running the Corigo Action Workplace Enterprise®.

Installing Macromedia JRun

Macromedia JRun4 only supports Java SDK 1.3. If the installer detects JDK 1.4 then the option for JRun on the Java Application Server screen will be disabled.

Installing Workplace Enterprise®


1) Run Setup Executable

From the installation CD, run the Workplace Enterprise® executable (such as, Workplace Enterprise.exe) in the root directory.

2) License Confirmation

Please read the terms of the license before proceeding.

License Confirmation Screen


Confirm the license next by clicking the I Agree button.

3) License File

If you have a license file then it can be input here. If you do not have a license file, then Workplace Enterprise® will be installed with a 30 Day Evaluation license. For information about how to obtain a license file please click here.

License File Screen


4) Java Application Server

Choose your Java Application Server. Workplace Enterprise® supports either Apache Tomcat 4.x (JDK 1.3 and JDK 1.4) or Macromedia JRun 4.x.(JDK 1.3 only).

The Macromedia JRun 4.x option shall be disabled if the installer detects JDK 1.4.

Java Application Server Screen


5) Destination Configuration

Next, the name of the host server, the Java Application Server details, and the location of the Corveum Workplace Enterprise® document management storage location.

Destination Configuration Screen


  • Computer Name: Is the name of the host server where the Java Application Server resides
  • Java App Server Home: Is the root directory where the Java Application Server is installed. Note: If your server is Tomcat, the path to the Tomcat home cannot include any spaces in the directory path as this will not work.
  • Server Name (JRun Only): Is the name of the server under which the enterprise application resides.
  •                         For example,
            c:\Macromedia\JRun4\default
  • Enterprise Application Name (JRun Only): Is the name of the enterprise application under which the web application resides.
  •                         For example,
            c:\Macromedia\JRun4\default\default-ear
  • Web Application Name: Is the name of the web application where Workplace Enterprise® will be installed.
  •                         For example Tomcat,
            c:\ApacheGroup\Tomcat4.1\webapps\cew
                        For example JRun,
        c:\Macromedia\JRun4\default\default-ear\cew-war
  • Document Storage Location: Is the root location where documents managed by Workplace Enterprise® will be managed from. Beneath this directory additional directories will be created where files will be stored, and temporary directories used for file check out and viewing. Stored files are managed and organized by the web application name; thus, a directory will be created that has the same name and beneath it will be three additional subdirectories.
    • docs: Location where files are physically stored
    • <web app name >_shared_read: Location where files are temporarily stored while being viewed (read only) by a user. Later this directory will need to be sharedso all users can have access to the directory via the network.
    • <web app name >_shared_modify: Location where files are temporarily stored when being edited by a user. Later this directory will need to be shared so all users can have access to the directory via the network.

        For example,
            c:\corigodocs\cwe\
            c:\corigodocs\cwe\docs\
            c:\corigodocs\cwe\cwe_shared_read\
            c:\corigodocs\cwe\cwe_shared_modify\

    6) Database Configuration
    Finally, is the database configuration screen where values will be entered about the database server, database name and storage location, username and password, and the ODBC data source name.

    Database Configuration Screen


    • SQL Server Name: The name of the server hosting Microsoft SQL Server
    • SQL Server Data Home: Location of where to place the Microsoft SQL Server data files
    • Database Name: Name of the database
    • Database Username: Database login user name
    • Database Password: Database login password,
    • Windows Authentication: If checked, the current Windows login shall be used to connect to the database. If not checked, then the Database Username and Database Password values shall be used. Whether to check the box or not is dependent on how SQL Server was installed.
    7) ODBC/JDBC
    For connecting to the database, there are two options:
    1) The name of the ODBC name used to access the database
    2) Or, "." if you are using the JNetDirect JDBC driver.

    If you are using ODBC, later on the ODBC DSN will need to be configured manually.
    ODBC/JDBC configuration


    Clicking the Install button to begin installation. Once the installation process has completed please continue on to the Finishing Up section.

    Finishing Up

    1) Configure Tomcat to Execute all Servlets

    If you are using Tomcat, in order for Workplace Enterprise® to operate you'll need to be enabled Tomcat to execute all servlets. This can be accomplished by editing the web.xml file located in the /conf directory of the Tomcat root. Uncomment the lines for servlet mapping so it is the same shown as below.

    Tomcat Enable All JSP
    Once completed, Tomcat will need to be restarted in order to enact the change.

    2) Configure ODBC

    If you are using the JNetDirect JDBC driver you do not need to do this step. The installation process will configure Workplace Enterprise® to use the JDBC driver automatically. Be sure to place the JNetDirect JDBC driver file (JSQLConnect.jar) in the common directory where the Java Application Server can find it. For example for Tomcat c:\Apache\Tomcat4.1\common\lib; and, for JRun c:\Macromedia\JRun4\servers\lib.

    Setup an ODBC data source name with the same name as already specified on the Database Configuration screen.

    i) Click the System DSN tab and then the Add button.

    ODBC Configuration Screen


    ii) Select SQL Server as the driver type.

    ODBC Configuration Screen


    iii) Enter the data source name (ODBC Data Source Name) and select the server (SQL Server Name) to connect with. If the server is on the local machine then (local) can be selected. Otherwise, select the server from the drop down list.

    ODBC Configuration Screen


    iv) Windows NT authentication is acceptable or a specific SQL login ID and password can be entered. When Workplace Enterprise® accesses the database, the setting for username (Database Username) and password (Database Password) shall be utilized.

    ODBC Configuration Screen


    v) Check the checkbox for Change the database to: and select the SQL Server database name just installed (Database Name)

    ODBC Configuration Screen


    vi) Click the Finish button to make the DSN.

    ODBC Configuration Screen


    vii) Click the Test Data Source... button to make sure the driver is operating correctly.

    ODBC Configuration Screen


    viii) If the driver setup went well you should see the message below. If not, go back and confirm all the settings were entered properly.

    ODBC Configuration Screen


    ix) Remember to restart your java server after completing the ODBC connection.

    3) Share Document Folders

    For document management, in order for files to be shared the temporary folder under the specified must be visible to others on the network. As described in Destination Configuration Section, beneath the location specified (Document Storage Location) and the web application name (Web Application Name) sub-directory, use Explorer navigate to these folders.

    Document Management Storage Location


    Right mouse click over the directory folder and set the folder to be shared while retaining the same name as the folder.

    Document Management Storage Location


    The resulting folders should be like this.

    Document Management Storage Location


    4) How to Run Workplace Enterprise®

    To run Workplace Enterprise® open your web browser and type in the following URL:

        http://<server name>:<port>/<web application name>/

    Where,
        <server name> = host server name of the Java Application Server
        <port> = the port used to connect to the Java Application Server
        <web application name> = web application name

        For example Tomcat,
            http://win2kserver:8080/cew/
        For example JRun,
            http://win2kserver:8100/cew/

    You should see a startup screen for Workplace Enterprise® if everything is working properly.

    5) Trouble Shooting

    If you are unable to run Workplace Enterprise®, please try the following.

    • Restart the Java Application Server to make sure it was properly intialized. If you have installed it as service, stop and restart the service. Once started, give it a moment to settle and finish loading into memory all the web applications under its control.
    • Confirm the Java Application Server Port number is correct. If not then you'll not be able to access the server. Attempt to run the Java Application Server directly without accessing a web application (For Tomcat - http://localhost:8080) to make sure it's operating. If it is not, then you'll need to reconfigure it until it does. Once operating properly, you can then attempt to access a web application, such as Workplace Enterprise® (For Tomcat - http://localhost:8080/cew).
    • If no JSP pages are displayed and you are using Tomcat 4.x confirm that it has been configured to display all servlets requested. Click here for configuration instructions.
    • Confirm the Web Application Name is correct. The web application name must match the one used during install (For Tomcat - http://localhost:8080/cew) otherwise it will not work.
    • If you are using the JNetDirect JDBC driver and it is not working, you'll receive a database error upon trying to login. Confirm that the JNetDriver JAR file JSQLConnect.jar is located in the Java Application Server's directory where the server can find it.
      For Tomcat, the directory c:\Apache\Tomcat4.1\common\lib can be used.
      For JRun, the c:\Macromedia\JRun4\servers\lib
    • If you are using ODBC DSN confirm that it matches the installed settings. If they are not the same you will not be able to log in.
    • ODBC has been known to have problems handling high intensity transactions causing a degradation in performance by either not working at all or by queries taking a very long time to execute (many seconds or even minutes). If this is occurring, consider switching to the JNetDirect JDBC driver. Please contact Corigo for more information.
    • Users cannot check out or view document files. Make sure that all users have permission to access the shared directories (cew_share_readonly and cew_share_modify) and that they match the installed settings. The permissions can be set clicking the Security tab on the folders' properties dialog box.
    • If you have linked your Java Application Server to a web server, such as Apache or IIS, make sure the connector is working properly. Test the web server first by accessing it directly (http://localhost). If it's not working you'll need to reconfigure it until it's operating. Next make sure you can access the Java Application Server through the port directly first (as described above). Then you can try accessing a web application using the connector by accessing it through the web server (http://localhost/cew).
    • Restart SQL Server. This is rarely needed but might be helpful.
  • How to Obtain a License



    If Workplace Enterprise® was installed without a Corigo license file being provided, it was then configured for a 30 Day Evaluation license. If you applied a valid license file during the installation, then your system has already been configured for the license.

    To upgrade the license Corigo, you'll need to send to Corigo the activation code from the server on which Workplace Enterprise® was installed. This is done with a program that was installed with Workplace Enterprise® (instructions are below). Upon receiving the code, Corigo shall generate a license file and send it to your company by email. In order to update Workplace Enterprise® with the new license it must be applied using a program installed with Workplace Enterprise® (Corigo Update License).

    Please follow these instructions to obtain an activation code:

    1) Run Corigo Activate License

    Please run the activation code generation program. It was installed with Workplace Enterprise® and can be found in the Windows Program Menu.

    Windows Program Menu-->Corigo-->Workplace Enterprise®-->Corigo Activate License
    2) Copy Activation Code from Screen

    Highlight the generated activation code from the screen as shown and press CTL-C to copy it. Be sure to highlight the

    entire code to the end of the string.

    License Activation Screen
    3) Make an Email with Activation Code

    Make an email and paste (CTL-V) the code into the body of the mail along with the following details.

  • Your Name
  • Your Contact Phone Number
  • Your Email Address
  • Along with details about the company to be licensed.
  • Company Name
  • Address
  • Phone Number
  • Fax Number
  • Email Address
  • 4) Send Email to Corigo
    Please send the email to sales@corigo.com.

    Please click here for additional Corigo contact information.
    5) What Corigo will do
    Upon Corigo receipt of the email will contact you to discuss pricing, number of users and other details necessary for the license.

    Once a license file has been generated it will be sent to you by email. Follow the instructions included to update Workplace Enterprise®.

    How do I update my license?


    Updating your Workplace Enterprise® license is done from the Workplace Enterprise® server. Pull up the Start menu to Programs, select the Corigo folder, then the Workplace Enterprise® folder and select Corigo Update License. This will launch the license update application.
    Browse to the new license file or type in the path directly and click Install.


    When the license has been updated you will see the following window. Click Ok to complete the update then restart the Java server to complete the process.

     

    Thank you in advance for purchasing Workplace Enterprise®!

    Contact Information



    Corigo contact information:
    Corigo Vietnam, Llc.
    391B Ly Thuong Kiet Street
    Tan Binh District, HCMC
    Viet Nam
    +84-8-909-6064 (phone)
    +84-8-835-1124 (fax)
    http://www.corigo.com/
    For Sales:

    Please send an email to the Sales Department to request additional information about Workplace Enterprise® and the other products Corigo sells.

    sales@corigo.com
    For Technical Support:

    Please contact Corigo Vietnam by either phone or fax at the numbers above, or by sending an email to this address.

    support@corigo.com

    If you are having problems with Workplace Enterprise® installation, configuration or system operations, please provide the following information about your system's configuration.

    1. Computer hardware
    2. Operating System and service patches installed
    3. Java Application Server
    4. Java JDK version
    5. Database server and service patches installed
    6. Which database driver being used - ODBC or JNetDirect JDBC driver

    If you are reporting a bug please write down the steps taken that exposed the bug and any information written to the Java Application Server's system log file. There you'll find entries written to the log file by Workplace Enterprise® that describes where in the system a problem had occurred.

    System Requirements

    Server

    Microsoft Windows 2000 Server, 2003 Server
    MS SQL Server 7-2000
    Apache Tomcat 4.x
    Macromedia JRun 4.x
    Java JDK 1.3 (Apache Tomcat 4.x or Macromedia JRun 4.x)
    Java JDK 1.4 (Apache Tomcat 4.x)
    Pentium IV or equivalent
    512Mb RAM
    Client

    Microsoft Windows 98, ME, NT, 2000, XP
    Apple OS 7-9, OS X, LINUX, or UNIX
    Internet Explorer 5.0-6.x (preferred), Opera 7, or Netscape 7.x
    Pentium II or equivalent
    128Mb RAM

     

     
    www.corigo.com