Frequently Asked Questions

Product: Content Services

Subject: Setting up Filenet Content Services in a Microsoft Windows Cluster Server, Oracle Fail Safe
environment.

Question: How do I setup up Filenet Content Services in a Microsoft Windows Cluster Server, Oracle Fail
Safe environment?

Resolution: Use the following procedure in conjunction with Oracle FailSafe documentation, Microsoft
Cluster Server documentation and the instructions for installing Content Services in a cluster environment
found in the Installation Guide, Content Services, Windows Oracle edition.

Installing Microsoft Cluster Server

1. Install Windows 2000 Advanced Server on each node of the cluster, accepting default values for
settings.

2. Read the Planning for Windows Clustering Requirements for server clusters topic of the online
Windows Clustering help to be sure that you have the proper hardware required for clustering.

3. From a command prompt, type comclust.exe.

4. Repeat step 3 at each node of the cluster.

Cluster Setup

1. Verify that each node in your cluster is in compliance with Microsofts Cluster Hardware Requirements
and the Cluster Software Requirements.

2. If you have not already done so, install Microsoft Cluster Service and Cluster Administrator on a local
drive of each node in your cluster. Refer to Installing Microsoft Cluster Server or the Microsoft Windows
Clustering documentation for additional information.

3. Verify that all the nodes in your cluster are in the same Windows 2000 domain. If you did not add the
nodes to a Windows 2000 domain during step 2, add them now:
Open the Windows 2000 Control Panel and start the System tool.
Go to the Network Identification tab and click Properties.
Select the Domain option button and enter your domain name. For example, to join the
MYDOM.LOCAL domain, type MYDOM and click OK.
Reboot the server.

4. Add a user who is a member of the Domain Admins group to the local Administrators group of each
node in your cluster.

5. Using Cluster Administrator, add each node to the cluster you are configuring. Refer to Windows
Clustering documentation for additional information. Continue at Installing Oracle Fail Safe.

Installing the Windows Oracle Database Engine

The following procedure provides minimal instructions for installing Oracle8i Release 3 (8.1.7) on a
property server for a new library system installation. Details are given only where the library system has
specific requirements pertaining to the Oracle installation and configuration. For complete information on
Oracle, including Advanced Oracle features such as Parallel Server, refer to the Oracle documentation
(available via the Browse Documentation button on the Oracle8i CD autorun main menu).

Install Oracle binaries on each node. Install on NODE1 and NODE2 simultaneously (to save time).

Note It is strongly recommended that if you install Content Services co-resident with the Database
Engine, that only one database (instance) be installed on that machine to reduce client connection
complexity.

To install Oracle8i on a property server:

1. Verify that your server is in compliance with all system requirements.

2. Verify that your computer's host name meets requirements.

3. Turn off any virus protection software.

4. Insert the Oracle8i CD into your CD drive to access the autorun main menu. If you do not have direct
access to the Oracle8i CD, you can view this menu by executing Win32 \Autorun \autorun.exe on the
installation media.

Caution The Oracle Universal Installer will not install the Oracle database server software on a Pentium 4
system unless you perform the following workaround:
Copy the Oracle8i CD to your hard disk.
Delete or rename the file symcjit.dll, located in the installation directory.
Run setup.exe from the root of the copied tree (or from the install\win32 directory).

5. On the autorun main menu, click the Install/Deinstall Products button.

6. On the Welcome dialog box, click Installed Products to verify that no Oracle products are currently
installed on this server. Click Close to close the Inventory dialog box. Click Next.
Note If you are installing from the network, you can get to the Welcome dialog box by double-clicking
setup.exe, located on the Oracle 8.1.6/8.1.7 root.

7. On the File Locations dialog box, accept the source and destination defaults or edit as necessary for
your configuration. Make note of the destination (Oracle Home) settings for future reference. Click Next.
All locations = C: local node

8. On the Available Products dialog box, select Oracle8i Standard Edition or Enterprise Edition
8.1.6.0.0/8.1.7.0.0. Click Next.

9. On the Installation Types dialog box, select Custom. Click Next.

10. The Available Products dialog box lists all components available for installation. These items are the
minimum requirements for Content Services. You may want to install other components for added
flexibility or administration, such as Advanced Replication, Oracle Partitioning, or Enterprise Manager
Products. Oracle ODBC Driver is not used by Content Services but you may want to install it anyway
since it contains ODBC Test, a useful troubleshooting tool for testing ODBC connectivity. Except where
noted, the following items are the minimum components that you must choose to install:

Oracle8i Server 8.1.6.0.0/8.1.7.0.0

Oracle Database Configuration Assistant 8.1.6.0.0 only
Generic Connectivity Using ODBC 8.1.6.0.0 only
Net8 Products 8.1.6.0.0/8.1.7.0.0
 Net8 Client 8.1.6.0.0/8.1.7.0.0
Net8 Server 8.1.6.0.0/8.1.7.0.0
Oracle Protocol Support 8.1.6.0.0/8.1.7.0.0
Oracle Utilities 8.1.6.0.0/8.1.7.0.0
Oracle Database Utilities 8.1.6.0.0/8.1.7.0.0
SQL*Plus 8.1.6.0.0/8.1.7.0.0
Oracle Configuration Assistants 8.1.6.0.0/8.1.7.0.0
Oracle Database Configuration Assistant 8.1.6.0.0/8.1.7.0.0
Development Tools 8.1.6.0.0 only
Oracle Call Interface (OCI) 8.1.6.0.0/8.1.7.0.0
Oracle ODBC Driver 8.1.6.0.0/8.1.7.0.0 (optional)
Oracle Installation Products 8.1.6.0.0/8.1.7.0.0
Oracle Universal Installer 1.7.0.19.0 (for Oracle 8.1.6)
Oracle Universal Installer 1.7.1.9.0 (for Oracle 8.1.7)

11. On the Component Location dialog box, select the locations where you want to install the
components. Click Next. All locations = C: local node

12. On the Create Database dialog box, choose No to create a database. FileNET recommends that you
create and configure a database later after the Oracle component installation.

13. On the Oracle Protocol Support dialog box, click Next.

14. On the Summary dialog box, review the choices you have made for installation. Click Install to begin
installing the files.

15. At the end of the installation, the Net8 Configuration Assistant will automatically launch. Do not
Perform typical configuration. Click Next.

16. On the Directory Service Access dialog box, choose No to complete directory service access
configuration. If you have a directory service, you can complete this at another time. Click Next.

17. On the Listener Configuration, Listener Name dialog box, choose a name for the listener. Click Next.
Chose LISTENER (must be identical for both nodes)

18. On the Select Protocols dialog box, ensure that TCP is a selected protocol. Click Next.

19. On the TCP/IP Protocol dialog box, you may use the standard port number, or choose your own. Take
note of this port number, as this is the number that all the CS Servers (including web servers) and CS
clients will need to use. Click Next.

20. On the More Listener? dialog box, choose No to configure another listener. Only one listener is
required for the database Content Services will use. Click Next.

21. On the Listener Configuration Done dialog box, Click Next.

22. On the Naming Methods Configuration dialog box, choose No to change naming methods. You will
create a Net Service Name later. Click Next.

23. NET8 CONFIG STEPS

Local Net Service Name Configuration
Add
Second selection: Oracle8 release 8.0 or Oracle7 DB service (allows for use of SID vs.
Service_Name in tnsnames.ora)
Enter SID
 Protocol = TCP
Host Name = (use the Oracle DB Virtual Server Name)
Standard port = 1521
NOdo not perform testcan test later
Net Service Name = wacswinora (virtual server name of the Oracle DB created on the Domain
Controller)
No to configuring another, Next
Then you can go back and test the newly created NSN.

NOTE: Sometimes if the first line in the sqlnet.ora file is not commented out the net8 config assistant will
append the fully qualified domain name to the Net Service Name. For a production environment, this may
be necessary, but for our setup, it is not. Go to your sqlnet.ora file and comment out (add the # signs)
the first two lines (C:\oracle\ora81\network\ADMIN\sqlnet.ora)
#NAMES.DEFAULT_DOMAIN = BLACKFORESTDOM.LOCAL
#SQLNET.AUTHENTICATION_SERVICES= (NTS)

23. On the Done dialog box, click Finish.

24. On the End of Installation dialog box, you may exit the installer and create a database instance later,
either manually or via the Oracle Database Configuration Assistant. If you wish to create and configure an
Oracle database instance now, using the Configuration Assistant, click on Configuration Tools and
highlight it and press the space bar. Click Done and Exit.

Continue with Creating and Configuring a Windows Oracle Database as per the Content services
documentation. Continue with installing Oracle Fail Safe below after completing the above steps on both
nodes.

Installing Oracle Fail Safe

Install FailSafe on both nodes:

Install Microsoft Cluster Server and Cluster Administrator on a local drive of each node that will be
in your cluster. (see Installing Microsoft Cluster Server in the Installation Guide for Content
Services or the Microsoft Windows Clustering documentation)
Add the nodes to the cluster and make sure the cluster is up and running on each node.
Uninstall any previous version of Oracle Fail Safe from each cluster node.
Install the Oracle database server on a local drive of each node in the cluster but do not create
your database yet.
Log in to each cluster node as the same user, who is a member of the Domain Admins group for
the domain to which the nodes belong.
Stop Microsoft Cluster Administrator on each node before you start installing Oracle Fail Safe on
that node. To install Oracle Fail Safe follow the instructions included in the online documentation
found in the Oracle Fail Safe CD. The following constraints apply:
Finish installing Fail Safe Server on one cluster node before you start installing it on the other
cluster node.
Optionally, install Fail Safe Manager on a cluster node when you are installing Fail Safe Server on
that node.
You will need to install Fail Safe Manager on at least one cluster node or on a client node outside
the cluster in order to verify the success of the Fail Safe installation (see Verifying Oracle Fail
Safe)
Install Fail Safe Server (and Manager) only on a local drive, not on a shared cluster drive.
Choose Typical as the Installation Type.
Specify the same Oracle Home for Fail Safe Server (and Manager) on each node in the cluster,
and make sure that no other Oracle products are installed in the Oracle Home.
 When prompted for the Oracle Fail Safe domain, specify the domain to which the cluster nodes
belong. When prompted for the account and password, specify the same user (a member of the
Domain Admins group) who logged in to each node of the cluster.
Reboot the node when you have finished installing Fail Safe Server (and Manager) if this is the
first time you have installed them in the Oracle Home location. Be sure to wait until the reboot
process is complete (when you see the login prompt) before you start installing Fail Safe on the
other cluster node.

When you have completed the installation of Oracle Fail Safe on each node of the cluster, continue at
Verifying Oracle Fail Safe in the Content Services documentation.

Creating and Verifying the Database

When an Oracle database resides in a cluster environment, it must be installed on the drives shared by
the cluster, and it must be a resource in a group. If you have not already done so, create the group for the
database (see Creating and Verifying a Group in the Content Services documentation).

Create the database by following the instructions in Creating and Configuring a Windows Oracle
Database in the Installation Guide for Content Services. Be sure to specify a shared cluster drive for the
location of the database files. (This includes the control files, data files, log files and the locations
determined by the LOG_ARCHIVE_DEST parameters.)

The INIT.ORA file can be either on the shared drives or on the local drives of the cluster nodes. If it is on
the local drives, it must have the same local path on each drive.
Do not create any property repositories yet; you will do that after the database has been added to its
resource group.

Creating and Configuring a Windows Oracle Database

The following instructions utilize the Oracle Configuration Assistant for creating an Oracle Database
Instance. For creating an instance manually, please refer to Oracle 8i Documentation. Also, many dialog
boxes will prompt you for specific values or parameters that can affect Oracle performance. It is strongly
recommended that you Consult your Oracle documentation before creating a database to help you
determine the best configuration for how you will use Content Services.

Note It is strongly recommended that you use a dedicated instance for Content Services. Other
applications using the same instance Content Services is using can have potential conflicts and/or
performance problems with Content Services, the other application(s), or both.

To create and configure an Oracle database:

1. On the first screen of the Oracle Database Configuration Assistant, choose to Create a database. Click
Next.
Path=c: Drive
Oracle8i Enterprise Edition

2. Choose Custom. If you are initially using the Oracle Database and Content Services for development
and/or testing purposes, Typical is probably sufficient. Otherwise, it is strongly recommended to choose
Custom to custom tailor your database to your specific needs. Click Next.

3. You will be given a choice in what type of application will be using the Oracle database. Choose the
option that applies most to how you will use Content Services. For simplicity sake, the following
instructions will assume Multipurpose. Click Next.

4. Enter the number of users that will be simultaneously connecting to the database using Content
Services. Click Next.
5. Enter the mode in which the database will operate. FileNET recommends Dedicated Server mode for
better performance. Click Next.

6. Choose the options you require. Content Services does not require any. Click Next.

7. On the Database Identification screen, enter a Global Database Name (GDN) and Oracle System
Identifier (SID). Caution Do not enter cluster as the Global Database Name, whether or not you have
installed the database engine in a cluster environment. If you do, your database installation will fail.
Specify the path and name for the initialization filename and choose 8.1.0 for the Compatible Parameter.
If your Content Services system does not need to support the Euro character, accept the default character
set (code page) WE8ISO8859P1. If your Content Services system does need to support the Euro
character, read the readme for hotfix pack CS-5.2.0-003 (or later) before installing your CS system. Make
note of your choices in this step for future reference, such as for configuring Content Services servers and
clients. Click Next.
GDN = ORCL
SID = ORCL
Path for all = H: (shared drive)
Compatible Parameter = 8.1.0
Code Page = WE8ISO8859P1

Enter password and click next

8. Review the control file parameter information and make changes where appropriate. Again, Consult
your Oracle documentation for further information on these parameters. Click Next.

9. On the dialog box used to configure tablespaces, review the settings, paths, and filenames of the all
the default tablespaces. The following are minimum requirements for Content Services:
SYSTEM : 100 MB
ROLLBACK : 250 MB
INDEX : 58 MB
TEMPORARY : 250 MB

See the Oracle documentation for further information. Click Next.

NOTE: Make sure to click on each tab, and change the location of each tablespace: System, Tools, User,
Rollback, Index, and Temporary

10. Review Redo Log file and file size information and make changes as necessary. Click Next.

11. Review Checkpoint and Checkpoint Timeout information and make changes as necessary. Enable
Archive Log and Format/Destination if necessary. Consult your Oracle documentation for further
information. Click Next.

12. Review the SGA parameter information and make changes as necessary. For optimal performance,
we recommend the following:
Shared Pool Size : 35000000
Block Buffers : 8192
Log Buffer Size : 163840
Processes : 150, or the maximum number of connections + 10%, whichever is greater
Block Size : 8192
Consult your Oracle documentation for further information. Click Next.

13. Review the path and filenames for User and Background Processes for trace files. Consult your
Oracle documentation for further information. Click Next.
14. Decide whether to create the database now or save information into a batch file. We recommend
saving to a batch file. If a failure in the database creation will result, the batch file can help in debugging
problems. Click Finish.

15. Save the batch file to a location where you will be able to locate it at a later time. Save the file as a
.bat file. Any associated scripts will automatically be installed in this location as well.

16. After the database is created, DO NOT CREATE a tablespace for the library system. Oracle Fail Safe
will create the tablespace.

Creating and Verifying the Database continued

Oracle Fail Safe Manager will display an icon in the Standalone Resources folder of the tree view for the
database you just created. To verify this database, select the icon and choose Troubleshooting > Verify
Standalone Database.

In the Verify Standalone Database, you should see a value in each field. Type and confirm the password,
and then click OK. A status message will appear when the verification is complete.

Add the verified standalone database to its resource group by dragging the database icon in the tree view
from the Standalone Resources folder to the resource-group folder.

At this point, you should have a fully operational database that is aware of both Oracle Fail Safe and its
cluster environment. To finish preparing the database for use by Content Services components refer to
the Installation Guide, Content Services, Windows Oracle edition.

2004 FileNET Corporation USA. All rights reserved.