Step 2: Installing on Managed Servers

As a second step in the cluster deployment, install WebLogic Server, ADF Runtime, 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.

Before you start the installation, ensure that you:
  • Install the Java 6 SDK (you will need to point to its location).
  • Provide write access to the shared file system on which the indexes for the data domains will be stored.

For a full list of software requirements, see Required Oracle products.

This procedure describes how to use the orchestration script in non-configuration mode. It assumes that you have already installed the required packages on the first server in your cluster deployment, and that the WebLogic domain for the Endeca Server has been created, with the Admin Server started.

If, for any reason, you prefer not to use the script and to install all the components manually on these two nodes, you can do so. See Installing WebLogic Server and Application Developer Framework and Manually Installing Endeca Server on a Single Machine. (You do not need to create and start the WebLogic domain for the Endeca Server, as it has already been created.)

Important: On host2 and host3, the installation of the WebLogic Server, ADF Runtime, and Endeca Server should follow the same directory structure (the same path), as on host1.

To install the required software on the Managed Servers, using the orchestration script in the non-configuration mode:

  1. Edit the configuration script as follows and save it:
    Configuration parameter What to specify for the installation on the Managed Servers, in the Endeca Server cluster
    INSTALL_MODE Select INSTALL_ALL. This installs the required packages, but does not do any other tasks (this is the non-configuration mode).
    START_MODE Select PROD to start WebLogic Server in production mode. This is the default.
    JAVA_HOME Specify the absolute path to the installed Java SDK. Although default Linux and Windows locations are provided, you should set the location for your specific use.
    ORACLE_HOME Specify the absolute path of the Oracle Middleware directory in which the components will be installed (for example, C:\Oracle\Middleware on Windows). Note that the Middleware directory must not exist because the script will create it. Although default Linux and Windows locations are provided, you should set the location for your specific use.
    ORACLE_INV_PTR Linux only. Provide the Oracle Installer Inventory Pointer file location. Default is the /etc/oraInst.loc location.
    INSTALLER_LOCATION Specify the absolute path of the directory that contains the installation files. Although default Linux and Windows locations are provided, you should set the location for your specific use.
    ENDECA_SERVER_DOMAIN_NAME Specify the name of the WebLogic domain for Endeca Server. endeca_server_domain is the default domain name. Note that the script in the non-configuration mode will not use this information.
    ENDECA_SERVER_PORT Select 7001, which is the default HTTP port. This is the HTTP port on which Endeca Server listens for requests (if Endeca Server is installed in non-secure mode). Note that the script in the non-configuration mode will not use this information.
    DEPLOY_ENDECA_SERVER_IN_SECURE_MODE Select TRUE (the default). This specifies that Endeca Server should be installed in secure mode (Endeca Server will use the HTTPS port).
    ENDECA_SERVER_SECURE_PORT Select 7002. This is the default HTTPS port on which Endeca Server listens for requests (if Endeca Server is installed in secure mode). Note that the script in the non-configuration mode will not use this information.
  2. On the two machines in your cluster deployment that are going to serve as Managed Servers, run the orchestration script in non-configuration mode, using the options you specified in the configuration file. For information, see Installing in non-configuration mode.

    The script in the non-configuration mode installs the required software, but does not perform other tasks.

As a result of this task, you should have the required software installed on these machines. The next step is to configure these machines as Managed Servers in the WebLogic domain for the Endeca Server.