InfoSphere Enterprise Records, Version 4.5.1.3+              

Installing InfoSphere Enterprise Records in a high availability environment

You can install IBM® InfoSphere™ Enterprise Records in a IBM FileNet® P8 high availability environment.

To install InfoSphere Enterprise Records in a high availability environment:

  1. Install InfoSphere Enterprise Records on each node of the application server cluster.
    • If InfoSphere Enterprise Records is to be installed on an existing Application Engine or Workplace XT cluster, the site preferences object in the Content Engine's object store must be checked out with IBM FileNet Enterprise Manager to verify the correct URL for Application Engine or Workplace XT. The XML element <setting key="workplaceBaseURL"> must be set to the URL of the load-balancer or proxy server in the Application Engine or Workplace XT farm. If the <workplaceBaseURL> element is not set, check out the XML document, correct the setting, and check it back in.
    • In the "Installing IBM InfoSphere Enterprise Manager software" task you are required to specify the server name of Content Engine. If Content Engine is clustered, specify the cluster host name or IP address of the service group that the API Listener belongs to. This is to ensure that all InfoSphere Enterprise Records cluster nodes can connect to the active node of the Content Engine cluster.
    • This task also requires the path to the bootstrap.properties file. Select the location that was created to host the Application Engine or Workplace XT configuration data here (likely a Windows shared server or NFS export location).
      Restriction: Do not install InfoSphere Enterprise Records nodes with different bootstrap.properties files.
  2. Configure the application server cluster and deploy Application Engine or Workplace XT according to the IBM FileNet P8 Platform Installation and Upgrade Guide or IBM FileNet Workplace XT Installation and Upgrade Guide.
  3. Start of changeDeploy InfoSphere Enterprise Records.
    Server Instructions

    WebSphere® Application Server

    Before you deploy the application on the IBM WebSphere Application Server, select the cluster or managed nodes, or both that will be running the application when you map modules to servers. See "Configuring and deploying Application Engine or Workplace XT."

    To deploy InfoSphere Enterprise Records, see "Deploying the IBM InfoSphere Enterprise Records web application," IBM WebSphere Application Server 5.x, 6.x, or 7.x procedures after you create the cluster and load balancer instances by using the administrative console. By using these steps, you can deploy InfoSphere Enterprise Records on the cluster and proxy server instances.

    WebLogic Server

    Before you deploy the application on WebLogic Server, make sure the targets for the application include the WebLogic Server cluster or the managed nodes, or both that will be running the application. See Configuring and deploying Application Engine or Workplace XT.

    To deploy InfoSphere Enterprise Records, see IBM InfoSphere Enterprise Records web application, WebLogic Server 8.1.x, 9.x, or 10.x procedures after you create the WebLogic domain, administration server and cluster. Use these steps to deploy InfoSphere Enterprise Records on the cluster.

    JBoss Application Server

    On JBoss Application Server you configure and deploy the InfoSphere Enterprise Records web application in a group of independent application server instances.

    In this configuration, because there is no central administration server, every server acts as a separate server instance and must be configured separately.

    When you install in a group of independent application server instances the steps shown in the "Deploying on JBoss Application Server" task must be performed on every node.

    End of change
  4. Run the RMCreationTool and RMAccessRole tool on the InfoSphere Enterprise Records server node.

    To successfully add marking sets and addons to the FileNet P8 domain and set up the Classified Records Security Personnel Access Role for a highly available InfoSphere Enterprise Records, you must run the RMCreationTool and the RMAccessRole tool on only one InfoSphere Enterprise Records in the highly available environment.

    Follow the instructions in the “Adding marking sets and addons to the FileNet P8 domain“ or “(DoD Classified only) Creating the classified records security personnel access role” task.

  5. If a load-balancer or proxy server is used in this configuration, ensure that you use this URL for the remaining InfoSphere Enterprise Records installation steps that require an application URL.

    If the application is deployed to a group of application servers, and a load-balancer is configured for this group, then a URL for Application Engine might be http://proxy_url:proxyport/Workplace.

    An example of the InfoSphere Enterprise Records URL is: http://proxy_url:proxyport/RecordsManager. Use this URL when you complete the installation steps for InfoSphere Enterprise Records.

    Attention: Start of change
    • You must perform configuration steps that use the InfoSphere Enterprise Records, or Application Engine or Workplace XT web applications. Perform these steps on one node per HA environment only, and not on every node in the group.
    • You must perform the Transfer Workflow Definitions task from the command prompt by using WorkflowTransfer.bat/.sh. You must do this on one node per HA environment only, and not on every node in the group.
    • You must perform configuration steps that use the Process Task Manager (to make configuration changes to the Component Manager) or the InfoSphere Enterprise Records Sweep applications. Perform these steps on each node in the group of application servers.
    End of change


Feedback

Last updated: November 2010


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