Cluster installation and deployment tasks

This section includes a diagram of the cluster deployment, outlines a high-level cluster installation and deployment procedure, and provides detailed tasks for the installation and deployment of an Endeca Server cluster.

Cluster deployment diagram
The following diagram illustrates a WebLogic domain with one Admin Server and three Managed Servers, in which an Endeca Server cluster is deployed on its Managed Servers.
High-level installation and deployment procedure
This topic lists high-level tasks required for the installation and deployment of the Endeca Server cluster.
Step 1: Installing on the Admin Server
As a first step in the cluster deployment, install WebLogic Server and Endeca Server on the first of the three machines on which you will be initially deploying an Endeca Server Cluster.
Step 2: Installing on Managed Servers
As a second step in the cluster deployment, install WebLogic Server and Endeca Server on the remaining two machines on which you are deploying an Endeca Server Cluster (these machines will become Managed Servers), but do not create the WebLogic domain.
Step 3: Cloning Managed Servers
In this step, on the machine known in the diagram as host1, you create three Managed Servers.
Step 4: Adjusting the cluster configuration
In order for the Endeca Server cluster to run, two of its configuration files should be configured to list the Managed Servers, the location of the shared file system, and the listen ports for the Managed Servers on which the Endeca Server instances will be running.
Step 5: Packing the WebLogic domain
To pack the WebLogic domain, use the pack.* and unpack.* scripts of the WebLogic Server.
Step 6: Unpacking WebLogic domain on Managed Servers
Before you can start the Managed Servers, unpack the WebLogic domain template on the machines that do not yet contain the WebLogic domain's configuration.
Step 7: Changing deployment targets and starting servers
In this step, you change the deployment targets from the Admin Server to Managed Servers and start all servers in the WebLogic domain for the Endeca Server.
Step 8: Registering the Data Enrichment plugins in the Endeca Server cluster
This topic describes how to run a command-line script that registers the Endeca Server Data Enrichment plugins, if you are installing in the cluster.
Step 9: Configuring JMS settings
In this step, on each of the managed servers, you configure JMS (Java Messaging Service) settings. JMS in WebLogic is used by the Data Enrichment plugins and must be configured in the Endeca Server cluster if you will use Data Enrichment plugins (known as Enrichments in Studio).