Use this procedure to install and configure IBM FileNet Content Search Engine, an optional component based on the Autonomy K2 product, in your highly available IBM FileNet P8 environment.
To install a highly available Content Search Engine:
1. Verify that you have performed the required preparation tasks as shown in
“Performing required preparation tasks” on page 35.
2. Verify that your cluster is running.
3. (Windows 2008 MSCS) Create an empty Service or Application resource.
4. (Windows 2008 MSCS) Add a client access point to the Service or Application resource (Use the virtual name and IP during installation).
5. Verify that the shared directories are mounted on each node.
v Binary Share (UNIX, optional) v Temp Directory Share
For information, see “Creating required shared directories” on page 38.
6. (Windows 2008 MSCS) Add the highly available storage locations to the Service or Application resource.
7. Install Content Search Engine on all cluster nodes. In a highly available environment, you must run the Content Search Engine installer on each node, selecting the shared directory as the Content Search Engine installation path.
a. Install Content Search Engine on a cluster node.
Follow the instructions in the IBM FileNet P8 Platform Installation and Upgrade Guide for installing and configuring Content Search Engine with the following additional information:
v Use the shared binary location as installation location (verity_install_path).
UNIX This might either be a local shared cluster disk or a highly available shared storage location.
Windows
This must be a local shared cluster disk.
v In the Select Autonomy K2 Server Type screen, select Master Administration Server.
v In the Specify Master Administration Server Information screen, use the host name of the cluster rather than the host name of the local cluster node.
Important: For Windows 2008 MSCS, use the virtual name defined for the Service or Application resource when specifying the Master
Administration Server Information.
v When the installer has finished, K2 will be running. Stop the application before failing to another node.
UNIX Issue: k2adminstop Windows
Stop the Verity K2 Administration Server and the Verity K2 Administration Web Server services.
b. Fail over to another node and repeat the install process with the same parameters.
8. Configure local files to point to cluster address.
After the installation has been completed on all nodes, the following files will contain local host names and must be edited to have the local node names changed to the cluster virtual host name:
v verity_install_path/_cseuninst/installvariables.properties v verity_install_path/config.vcnf
v verity_install_path/data/docs/WEB-INF/web.xml v verity_install_path/k2/common/base.xml
v verity_install_path/k2/common/verity.cfg v verity_install_path/data/host/admin/adminN.xml
Where the value of N is stored in verity_install_path/data/admin/
admin.dat.
9. Configure Veritas or Microsoft Cluster Server (MSCS) CSE Resource Group.
After installing Content Search Engine on your cluster, you must configure the following cluster resources. These should all be placed in the same Resource or Service group so that they fail over together:
v Network name (Windows) / IP Address (UNIX)
v Binary File Share (if local to the cluster rather than mounted from a remote highly-available storage location)
v Temporary File Share (if local to the cluster rather than mounted from a remote highly-available storage location)
v Collections File Share
Follow the instructions in the IBM FileNet P8 Platform Installation and Upgrade Guide on collections directory requirements to create a temporary directory and to create a collections directory.
v Content Search Engine services
Table 27. Content Search Engine services configuration procedures
Operating system Procedure
UNIX Configure the Veritas Application Agent as
follows:
User k2_os_user StartProgram
verity_install_path/_platform/
bin/k2adminstart StopProgram
verity_install_path/k2/
_platform/bin/k2adminstop PidFiles
verity_install_path/data/host/
k2admin.pid/opt/verity/data/
host/catalina.pid
It is possible to start and stop the K2 Administration Server and K2
Administration Web Server separately on UNIX, but doing so requires custom scripting. See the IBM FileNet P8 High Availability Solutions Redbook for more information.
Windows v Verity K2 Administration Server (required)
v Verity K2 Administration Web Server (optional)
10. Add the following resource dependencies:
Collections File Share
IP Address (UNIX)/Network name (Windows) Collections mount point
K2 Administration Server / Administration Web Server
Binary and temporary file shares (if these are clustered resources. If they are mounted from a remote highly available location, this is not necessary)
Collections File Share
IP Address (UNIX)/Network Name (Windows)
11. Configure Content Search Engine per install guide instructions, for your cluster.
Follow the instructions in the IBM FileNet P8 Platform Installation and Upgrade Guide for configuring Content Search Engine, using the cluster name for the K2 Dashboard URL entry.
12. Create a Content Search Engine collections directory.
Follow the instructions in the IBM FileNet P8 Platform Installation and Upgrade Guide for creating a Content Search Engine collections directory.
13. Configure Content Engine for content-based retrieval.
Follow the instructions in the IBM FileNet P8 Platform Installation and Upgrade Guide for configuring Content Engine for content-based retrieval, using the cluster host name when configuring the Verity Domain.
Related tasks
Installing and configuring Content Search Engine
Use the information in the IBM FileNet P8 Platform Installation and Upgrade Guide to install and configure Content Search Engine.
Collections directory requirements
Create a temporary directory and create a collections directory when creating your cluster resources.
Configuring Content Search Engine
Use this procedure to configure services required on the K2 Master Administration Server, and on additional Administration Servers you might install for IBM FileNet P8 Content Search Engine. All servers are configured through the Master
Administration Server Dashboard.
Creating a Content Search Engine collections directory
Use this procedure to configure the storage location and related security for your K2 collections.
Configuring Content Engine for content-based retrieval
You must use Enterprise Manager to configure an index area and enable the content-based retrieval (CBR) feature provided by the IBM FileNet P8 Content Search Engine.