IBM Enterprise Records, Version 5.1.+              

Installing IBM Enterprise Records in a high availability environment

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

To install IBM Enterprise Records in a high availability environment:

  1. Install IBM Enterprise Records on each node of the application server cluster.
    • If IBM 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 Enterprise Records 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 IBM 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 IBM Enterprise Records nodes with different bootstrap.properties files.
  2. Run IBM Enterprise Records Configuration Manager to configure and deploy IBM Enterprise Records and Application Engine or Workplace XT. You can run an instance of the configuration manager on a single node and deploy it to all the other nodes of the application server cluster by changing the server or node you are targeting.
    • If the configuration files, for example Actions.xml, for IBM Enterprise Records are shared among all the nodes, specify a shared directory in Configure Web Application task for the Web Deployment profile. By using a shared directory, you should only perform the configuration steps (run the Configure Web Application task) on a single node, but deploy the web applications to every node in the group in the HA environment.
    • If the configuration files are not shared, you will need to run the Configure Web Application task on each node in the HA environment.
      Attention: When you make a change to one of the configuration files, there might be inconsistent behavior if the change is not made to all of them. It is possible to create a shared folder for the configuration file to keep the user interface consistent across all nodes.
    • For JBoss Application Server, you will need to configure and deploy on every server node.
  3. Deploy IBM Enterprise Records.
    Server Instructions

    WebSphere® Application Server

    In the "Web application deployment" profile settings for IBM WebSphere Application Server, change the application server host, SOAP port and cell to the correct values for your application server. In the settings for the Deploy Web Application task, select the appropriate server node where IBM Enterprise Records Configuration Manager will be deploying.

    Deploy the IBM Enterprise Records web application on theIBM WebSphere Application Server 6.x or 7.x, after you create the cluster and load balancer instances by using the administrative console. By using these steps, you can deploy IBM Enterprise Records on the cluster and proxy server instances.

    WebLogic Server

    In the Web application deployment profile settings for WebLogic Server, change the application server host and SOAP port to the correct application server. Select the appropriate target name where IBM Enterprise Records Configuration Manager will be deploying.

    Deploy the WebLogic Server 9.x, or 10.x, after you create the WebLogic domain, administration server and cluster. Use these steps to deploy IBM Enterprise Records on the cluster.

    JBoss Application Server

    On the JBoss Application Server you configure and deploy the IBM 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.

  4. Run the RMAccessRole tool on the IBM Enterprise Records server node.

    To successfully set up the Classified Records Security Personnel Access Role for a highly available IBM Enterprise Records, you must run the RMAccessRole tool on only one IBM Enterprise Records installation 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 IBM 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 IBM Enterprise Records URL is: http://proxy_url:proxyport/EnterpriseRecords. Use this URL when you complete the installation steps for IBM Enterprise Records.

    Attention:
    • You must perform the Transfer Workflow Definitions task from the command prompt by running the Transfer Workflows task. 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 IBM Enterprise Records Sweep applications. Perform these steps on each node in the group of application servers.


Feedback

Last updated: August 2011


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