InfoSphere Enterprise Records, Version 4.5.1.3+              

Preparing for the high availability InfoSphere Enterprise Records installation

You must perform some pre-installation tasks before you install IBM® InfoSphere™ Enterprise Records for high availability.

The application server must have a cluster instance configured and it must be ready for applications to be deployed. Aside from the configuration data (bootstrap.properties), the remainder of the InfoSphere Enterprise Records software does not require network or clustered storage resources. The InfoSphere Enterprise Records software can be installed onto local storage for each machine in the cluster. When installing IBM InfoSphere Enterprise Records, the installer will create a number of directory structures, and install the InfoSphere Enterprise Records files into these directories. Verify that the user who will be performing the installation has the correct access requirements. Do this on all InfoSphere Enterprise Records nodes where you will be installing software.

To prepare for the InfoSphere Enterprise Records installation in a high availability environment:

  1. Install Content Engine, Process Engine, and Application Engine. Follow the instructions in the IBM FileNet P8 Platform Installation and Upgrade Guide, and for high availability installation of these components, see the following topics in the P8 Information Center.
    • FileNet P8 High Availability Technical Notice > Installing and configuring for high availability > Installing a highly available Content Engine
    • FileNet P8 High Availability Technical Notice > Installing and configuring for high availability > Installing a highly available Process Engine
    • FileNet P8 High Availability Technical Notice > Installing and configuring for high availability > Installing a highly available Application Engine/Workplace XT
  2. Verify that you have performed the required preparation tasks. This is shown in FileNet P8 High Availability Technical Notice > Planning and preparing for high availability > Performing required preparation tasks in the P8 Information Center.
  3. Verify that the cluster nodes and load balancers are started if the application server that is used to cluster InfoSphere Enterprise Records is WebLogic Server or WebSphere® Application Server.
  4. Mount the location of the bootstrap.properties file on each server in the cluster.

    This location should be mounted to the same path on every server. For example, if the bootstrap.properties file is mounted to /opt/FileNet/bootstrap on one node then it should be mounted to the same directory on each subsequent node.

    A location for the bootstrap.properties file should already exist as part of the Application Engine or Workplace XT high availability configuration. To ensure that each InfoSphere Enterprise Records instance functions identically in the cluster, it is important that each instance uses the same bootstrap.properties file. The InfoSphere Enterprise Records installer allows you to select the location of the bootstrap.properties file during installation.

    Restriction: Start of change Do not host the bootstrap.properties file on an application server cluster node. Although you can install the bootstrap.properties file locally with its location shared or the NFS exported for other nodes to access, if the node hosting the file fails, then the remainder of the cluster nodes will fail. Host this file on a highly available server that is not connected to the Application Engine or Workplace XT and the InfoSphere Enterprise Records cluster.End of change


Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)