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

Note The hardware and software requirements for the machine where you will install a CS client application may change over the period that Content Services 5.5 is supported. So that these requirements can be quickly updated as needed, they are maintained in the "CS Client Library Files" section of the Content Services Platform Requirements documents at the FileNet Worldwide Customer Support web site.

Hardware Requirements

* If you do not use at least the minimum display settings indicated, some windows will not fully display and you may experience flashing of color adjustments when switching between windows.

Software Requirements

Installation Notes

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

• The CS User Admin API does not include a setup program and must be installed on a machine that also contains an installation of the FileNet Content Services Client Library Files. However, the CS User Admin API should not be installed on a system where the CS Admin Tools or Web Admin Tools are already present. Potential conflicts may arise when the CS User Admin API is installed on a system where the CS Admin Tools or Web Admin Tools are already present.

• 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, click the ODBC Data Sources icon

     • Using Windows 2000 or Windows XP, 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.5 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 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.

   Note You need to make the user USR_CS_WEBADMIN member of 'Administrators' group of the local machine when prompted by setup.

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 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.

Note After the successful installation of CS WebAdmin tools perform the following steps while working on Windows 2003 server –

1. Go to "Control Panel" -> "Administrative Tools"  ->  "Internet Information Services(IIS) Manager"  ->  "Web Services Extension" and make the status of  "Active Server Pages" to "Allowed".

2. Un-check the "Enforce access checks for this application" option which can be done by:

   • Launching "Component Services" ("Control Panel" -> "Administrative Tools" -> "Component Services").

   • Right click COM+ application named "Content Services Web Administration Tools" and select "Properties".

   • Click on "Security" tab on property sheet.

   • Un-check "Enforce access checks for this application" checkbox and click on OK.

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.