High-level installation and deployment procedure

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

This procedure (and the subsequent topics that discuss each task in detail) are based on the following assumptions:
  • The procedures are described for Linux. For Windows, the procedures are similar, with path names that use backward slashes and scripts that end with .cmd.
  • The procedures use the $DOMAIN_HOME variable to indicate 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: 
    Oracle/Middleware/user_projects/domains/endeca_server_domain
  • The procedures use the port numbers, host names, and server names as 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.
  • The procedures assume secure installation (with SSL) of the Oracle Endeca Server. Options for the unsecured installation are included in parenthesis.
Note: This procedure provides a high-level overview of all tasks. The topics that follow this procedure include detailed steps for each task. Therefore, read this procedure first to understand the entire deployment process, and then use the subsequent topics to perform the required steps.

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

  1. On three separate machines (host1, host2, host3 in the diagram), install WebLogic Server 10.3.6, ADF Runtime, and Endeca Server. On host1, deploy a WebLogic domain with the Endeca Server application in it.

    For instructions, see Step1: Installing required software on multiple machines. As a result of this step, you should have the required software installed on three machines, and an Admin Server configured in the WebLogic domain that is created for the Endeca Server application.

  2. On the Admin Server running on host1, generate SSL certificates for the Endeca Server and create three Managed Servers.

    For instructions, see Step 2: Creating Admin Server, generating SSL certificates, and cloning Managed Servers.

  3. Modify EndecaServer.properties and EndecaCmd.properties.

    For instructions, see Step 3: Adjusting the cluster configuration.

  4. Stop the Admin Server and pack the WebLogic domain, using the pack.* script.

    This creates the WebLogic domain template. For instructions, see Step 4: Packing the WebLogic domain.

  5. On the Managed Server machines host2 and host3, unpack the WebLogic domain using the template you have created.

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

  6. Restart the Admin Server and change the targets for the Endeca Server application's deployment from the Admin Server to three Managed Servers. On the Managed Server machines host1, host2 and host3, start the Managed Server.

    For instructions, see Step 6: Changing the deployment targets and starting servers.

  7. Verify the deployment. For instructions, see Verifying a cluster installation and deployment.