Content Services Web Explorer Setup

See the Readme.htm file on the Installation CD for information on new features, known issues and other reference information on the CS Web Explorer.

Hardware and Software Requirements

Hardware Requirements

CPU Pentium-compatible

Disk Space 25 Mb

Memory 64 Mb

Software Requirements

Operating System Windows 2000, Service Pack 1 or Windows NT 4.0 Server, Service Pack 6a

System software

• Internet Information Services (IIS) 4 (with NT) or 5 (with Windows 2000)
• Internet Explorer 5.0 or higher
• Microsoft ADSI 2.0 or greater for NT4

  Note ADSI needs to be installed prior to installing CS Web Admin

Installation Notes

• We recommend that you do not install CS Web Admin on the CS Server.

• Do not install CS Web Admin Tools on a client machine that has CS Admin Tools (thick client) installed.

• Web Admin Tools cannot be installed via Terminal Services.

• For Oracle databases, library names are case-sensitive.

• You must exclude the global.asa file from any virus protection scanning program you might be using. To do this (using McAfee Virus Shield as an example), go to the properties dialog box of the Virus Protection service, choose the Exclusion tab, browse to the global.asa file (located in the C:\Program Files\FileNET\CSWebAdmin directory) and exclude it from virus scanning.

• To make a CS library available for use with CS Web Explorer, complete the following steps:
  

  For Microsoft SQL Server Database Servers

  Configure ODBC System DSN entries as follows:

  1. From the Control Panel, access the ODBC Data Source Administrator by using one of the following methods:

     • Using NT or Win 9x, click the ODBC Data Sources icon

     • Using Windows 2000, double-click the Administrative Tools icon, then the Data Source (ODBC) icon

  2. Choose the System DSN tab.

  3. Click Add.

  4. Scroll to the SQL Server entry, then double-click it to bring up the Create a New Data Source to SQL Server dialog box.

  5. Enter the name of your database server as your data source name, enter a description, and enter the name of your database server as the location.

  6. Click Next.

  7. Configure the data source connection.

     • Select With SQL Server authentication

     • Click Client Configuration. Make sure that TCP/IP is selected. You can use dynamic port allocation, or you can enter the specific port number that is used when SQL Server 2000 was installed. Click OK

     • Select "Connect to SQL Server to obtain..." only if you have a valid SQL account that connects directly to SQL Server. You will need to verify your password.

     • Click Next

  8. Accept the default database setting.

  9. Click Next.

  10. Test the database connection by clicking Test Data Source. You should get the TESTS COMPLETED SUCCESSFULLY! test result if you have a valid SQL Server account from Step "g". If you do not, you will get a login failure message "Not associated with a trusted SQL Server connection." This is an acceptable message as you will still have connectivity to the database.

  11. Click OK to close the ODBC Administrator dialog box.

  
  Note It is only necessary to complete this step once for each server you are accessing, even if there are multiple libraries on that server.
  

For Oracle Database Servers

1. Configure ODBC System DSN entries as follows:

   1. From the Control Panel, double-click the Data Sources icon to open the ODBC Data Source Administrator dialog.

   2. Click the System DSN tab in the ODBC Data Source Administrator.

   3. Click Add.

   4. Double-click Microsoft ODBC for Oracle to bring up the Oracle8 ODBC Driver Setup dialog box.

   5. Click Options to expand the dialog box.

   6. Enter the Data Source Name (use the database server name), the Server name, and check the SQLDescribeCol always returns a value for precision check box.

   7. Click OK.

   8. If you wish, you can test the ODBC connection using the Oracle ODBC Test utility. Be sure to select the Data Source Name for the machine you just created. You must also have a valid Oracle database user account and password to test with, for example: james/famous

2. Configure the Net Service Names using the Net8 Assistant or the Net8 Configuration Assistant for all CS 5.x database servers you are accessing
   Note You need to complete this step only once for each Oracle server you are accessing, even if there are multiple libraries on that server. Detailed installation instructions are provided in the FileNET CS 5.2 Windows Oracle documentation located in the \Documentation directory on the CS Admin Tools CD. You can also find the latest updates to this documentation on the FileNET Website at: http://www.css.filenet.com

Installation Procedure

To install CS Web Explorer :

1. Verify the system requirements listed above and be sure to complete the steps in the "Installation Notes" topic.

2. Use one of the following methods to run the Setup program from the Panagon CS Admin Tools CD:

   • To run a silent install: \Admin\setup.exe /s /v/qn - note the space after the "s"

   • To run a Minimal User Interface install: \Admin\setup.exe /v/qb

   • To run a GUI Install: Setup.exe Setup will launch the msi file.

3. To run the Web-based System Administration Tools go to: http:\\<server name>\cswebadmin. This path can be set by the administrator during the installation. Consequently, it may be different than the example shown here.

4. Go to Start\Programs\FileNET Panagon IDM and run the CS Web Admin Configure dialog to add CS Libraries running on the database server. At least one library must be configured.

5. Verify that you can log on to a configured library on the PC where you want to install and run CS Web Explorer.

Uninstalling CS Web Admin

1. Go to: Start\Settings\Control Panel\"Add/Remove Programs" or run Setup again.

2. Select FileNET Content Services Web Admin.

3. Click Remove.