Adding Endeca Server instances to the cluster

To add another Endeca Server instance to an already deployed Endeca Server cluster, provision an additional WebLogic Managed Server and deploy the Endeca Server domain to this server.

The instructions in this topic assume that you have already deployed an Endeca Server cluster with three Endeca Server instances running on three Managed Servers in the WebLogic domain created for the Endeca Server.

To add another Endeca Server instance to the Endeca Server cluster:

  1. Install the required software on an additional machine. For instructions, see Installing WebLogic Server and Application Developer Runtime and Installing Endeca Server on a Single Machine.
  2. Ensure that this machine has write access to the same shared file system to which existing Endeca Server machines have access.
  3. In the WebLogic domain for the Endeca Server, create another Managed Server. For instructions, see Step 2: Creating Admin Server, generating SSL certificates, and cloning Managed Servers. Do not generate SSL certificates (as it is assumed you have already generated them).
  4. Create a WebLogic domain template and deploy it on machine that will host the additional Managed Server.

    For instructions, see Step 4: Packing the WebLogic domain and Step 5: Unpacking the WebLogic domain on Managed Servers.

  5. (Optional.) Add the host name of this node to the list of host names on which the Cluster Coordinator service must be running, in the EndecaServer.properties file.

    If you are adding the fourth Endeca Server node, skip this step. If you are adding the fifth Endeca Server node, you can optionally perform this step. This step is needed to ensure that an odd number (that is equal to or greater than three) of the Endeca Server nodes are also running the Cluster Coordinator service. For instructions, see Changing settings in EndecaServer.properties.

  6. Specify the directories on the shared file system in the EndecaServer.properties. For instructions, see Changing settings in EndecaServer.properties.
  7. Start the Managed Server and change the WebLogic domain's deployment targets to include this Managed Server. See Step 6: Changing the deployment targets and starting servers.

Once the additional Managed Server is deployed, the Endeca Server application is started in it. Now you can create data domain profiles that require a greater number of Endeca Server instances; the Endeca data domains that you create using these profiles will be allocated to this additional Endeca Server instance.

Note: Existing data domains will not be dynamically adjusted to take advantage of the additional Endeca Server cluster capacity. In other words, to take advantage of the increased capacity, create new data domain profiles, and use them to create new data domains.