2.3 Clustering LiveCycle

If you install a LiveCycle component on an application server cluster, here are some things you must know:

  • Each application server in the cluster on which you deploy LiveCycle must have a homogeneous topology (that is, all nodes in the cluster must be configured identically). You can ensure that all modules are configured identically by configuring run-time properties in the single-installation staging area.

  • The configuration is deployed by using the single entity approach; all nodes in a cluster are deployed as if deploying to a single node.

Setting up a clustered environment for LiveCycle involves the tasks that follow.

    2.3.1 Clustering LiveCycle on JBoss

    You must perform the following tasks to deploy LiveCycle on a JBoss Application Server cluster:

    1. Prepare the hardware as per your requirements.

    2. Install the operating system and update it with all necessary patches and service packs.

    3. Install and configure the database server.

    4. Install and configure the application server cluster.

    5. Install LiveCycle modules and configure LiveCycle for deployment.

    6. Deploy LiveCycle to JBoss Application Server.

    2.3.2 Clustering LiveCycle on WebLogic

    You must perform the following tasks to deploy LiveCycle on a WebLogic Server cluster:

    1. Prepare the hardware as per your requirements.

    2. Install the operating system and update it with all necessary patches and service packs.

    3. Install and configure the database server.

    4. Install and configure the application server cluster.

    5. Install LiveCycle modules and configure LiveCycle for deployment.

    6. Deploy LiveCycle to WebLogic Server.

    2.3.3 Clustering LiveCycle on WebSphere

    You must perform the following tasks to deploy LiveCycle on a WebSphere Application Server cluster:

    1. Prepare the hardware as per your requirement.

    2. Install WebSphere Application Server Network Deployment software on the server that will manage the cluster
      Note: Select default environment(Cell), if you want to install deployment manager and an application server profile on the same machine.
    3. Install WebSphere Application Server Network Deployment software on any other server that will be used as a cluster node.
      Note: In steps 2 and 3, you can also select None and create Deployment Manager or Application Server profiles later using command line utility.
      Note: For cluster, use Network Deployment software only. Base software version is only for standalone application server. As per IBM EULA, user are not allowed to use Base software with Network Deployment software.

    4. Install the HTTP Server (IBM HTTP Server) and start Webserver.

    5. Install WebSphere Update Installer on each server/node and deploy the required Fixpack.

      Before you deploy LiveCycle, you must update to the supported version of WebSphere as specified in Adobe LiveCycle ES4 Supported Platforms. See the WebSphere Support Website for Fix Pack installation instructions and to access the WebSphere updates.

    6. Install Websphere Installation Manager on each server/node and deploy the JPA 2.0 (if not already installed on your WebSphere).

      Youmust install WebSphere Feature Pack for JPA 2.0. See, WebSphere Support Website and search Installing and uninstalling the feature pack to download and install Feature Pack.

    7. Set up the cluster:

      • Start the Deployment Manager.

      • Start all servers on all nodes.

      • Federate nodes to the Deployment Manager.

      • Create the cluster using existing application server profiles or create member using application server template.

      • Start the cluster.

    8. Configure cluster resources.

    9. (For manual deployment) Deploy applications to both the cluster and HTTP Server.

    10. Generate the WebSphere HTTP plug-in and propagate it.

    // Ethnio survey code removed