High-level installation and deployment procedure

This topic lists high-level tasks required for the installation and deployment of the Endeca Server cluster.

Note: This procedure provides a high-level overview of all tasks. The topics that follow this procedure include detailed steps for each task. Read this procedure first to understand the entire deployment process, and use the subsequent topics to perform the required steps.

This procedure (and the subsequent topics that discuss each task in detail) are based on the following assumptions:

The commands and path names are described for Linux. For Windows, path names should use backward slashes and scripts should end with .cmd.
The $DOMAIN_HOME variable indicates the location of the WebLogic domain created for the Endeca Server. For example, if endeca_server_domain is the name of your WebLogic domain for the Endeca Server, then the default path to it on Linux is:
```
$MW_HOME/user_projects/domains/endeca_server_domain
```
The port numbers, host names, and server names are the ones that are displayed in the cluster deployment diagram. See Cluster deployment diagram. You can use your own port numbers and host and server names, as long as port numbers satisfy the deployment requirements for the Endeca Server cluster. These requirements are included in the tasks in this section.
A secure installation (with SSL) of the Oracle Endeca Server is assumed. Options for the unsecured installation are included in parenthesis.
The orchestration script in non-configuration mode is used for installing the required software packages. You can choose to not use the orchestration script and install all packages manually.
The procedures assume that, along with the Endeca Server application, you plan to use Data Enrichment plugins in Studio. If you are not planning to use data enrichment plugins, you can skip all steps related to the Data Enrichment plugins in this section.
If you are performing a manul installation on Linux, you must use the same user ID when installing on each node to ensure that it will be able to access directories located on other nodes.
Finally, it is assumed that, as a result of installing and deploying the Endeca Server cluster, you will be running WebLogic in production mode.

To install and deploy an Endeca Server cluster, perform the following high-level tasks:

On the first of the three machines, (host1 in the diagram), use the orchestration script in the non-configuration mode to install WebLogic Server, ADF Runtime, and Endeca Server. On this node, you also manually configure the WebLogic domain and generate SSL certificates.

For instructions, see Step 1: Installing on the Admin Server.
On the two remaining machines (host2 and host3 in the diagram), also use the orchestration script in the non-configuration mode, to install WebLogic Server, ADF Runtime, and Endeca Server. If you installed securely on the Admin Server, be sure to use DEPLOY_ENDECA_SERVER_IN_SECURE_MODE set to TRUE on these machines.

For instructions, see Step 2: Installing on Managed Servers.

After this step, you are ready to create Managed Servers in the WebLogic domain.
On the Admin Server running on host1, create three Managed Servers.

For instructions, see Step 3: Cloning Managed Servers.
On host1, modify EndecaServer.properties and EndecaCmd.properties.

For instructions, see Step 4: Adjusting the cluster configuration.
On host1, stop the Admin Server and pack the WebLogic domain, using the pack.* script.

This creates the WebLogic domain template. For instructions, see Step 5: Packing the WebLogic domain.
On the Managed Server machines, host2 and host3, unpack the WebLogic domain using the template you have created.

For instructions, see Step 6: Unpacking WebLogic domain on Managed Servers.
On host1, restart the Admin Server and change the targets for the Endeca Server application's deployment and for the Data Enrichment Framework Java application's deployment from the Admin Server to the three Managed Servers. On the Managed Server machines host1, host2 and host3, start the Managed Server.

For instructions, see Step 7: Changing deployment targets and starting servers.
On host1, register the Data Enrichment plugins. For instructions, see Step 8: Registering the Data Enrichment plugins in the Endeca Server cluster.
On each of the Managed Servers, configure JMS settings. For instructions, see Step 9: Configuring JMS settings.
Verify the deployment. For instructions, see Verifying a cluster installation and deployment.