Step 1: Installing on the Admin Server

As a first step in the cluster deployment, install WebLogic Server, ADF Runtime, and Endeca Server on the first of the three machines on which you will be initially deploying an Endeca Server Cluster.

Before you start the installation, ensure that you:
  • Install the Java 6 SDK (you will need to point to its location). For a full list of software requirements, see Required Oracle products.
  • Provide write access to the shared file system on which the indexes for the data domains (and resources needed by the Data Enrichment plugins) will be stored.
  • Create an installation source directory, place the three installation files into it, and unpack the orchestration script ZIP file (for Windows) or TAR file (for Linux). For information, see Orchestration Script Installation.

This procedure describes how to use the orchestration script in non-configuration mode. If, for any reason, you prefer not to use the script and to install all the components manually, you can do so. See Installing WebLogic Server and Application Developer Framework and Manually Installing Endeca Server on a Single Machine. In this case, you will also need to manually configure the WebLogic domain, generate the SSL certificates, and register the Data Enrichment plugins.

To install the required software on the Admin Server using the orchestration script in non-configuration mode:

  1. On host1, which is the first machine in your cluster deployment, open a command prompt and navigate to the directory that contains the orchestration script.

    Note that you must edit and then run the script with administrator rights.

  2. Edit the configuration script as follows and save it:
    Configuration parameter What to specify for the installation on the Admin Server, in the Endeca Server cluster
    INSTALL_MODE Select INSTALL_ALL to set the non-configuration installation mode. In this mode, the script installs WebLogic, ADF, and Endeca Server, but does not perform configuration tasks (that is, does not create a WebLogic domain, does not create SSL certificates, and does not register the Data Enrichment plugins).
    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.
    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).
    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).
  3. On host1, 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 installs the required components on this machine.

    The non-configuration mode installation does not perform the tasks of creating a WebLogic domain, generating SSL certificates, and registering the Data Enrichment plugins. Therefore, you must manually configure the WebLogic domain for Endeca Server, and then generate SSL certificates. (Data Enrichment plugins should be registered too, but this is done after you create Managed Servers.)

  4. Create a WebLogic domain for Endeca Server. See Creating the WebLogic domain for Endeca Server.
  5. Generate SSL keys. See Creating SSL certificates.

As a result of this task, you should have the first machine in your cluster on which the required software is installed, the WebLogic domain for hosting the Endeca Server cluster configured, and SSL certificates generated. Note that the Data Enrichment plugins are not yet registered. The Admin Server of the WebLogic domain should also be started.