Before running the orchestration script in
configuration mode, you must have already done the following:
- Installed the Java 6 SDK
on the machine.
- Created an installation
source directory and placed the WebLogic, ADF, and Endeca Server installers
into it.
- Unpacked the orchestration
script ZIP file (for Windows) or TAR file (for Linux).
- Edited the script
configuration file with the settings that the script will use for your
environment. In particular, make sure the
INSTALL_MODE parameter has the
INSTALL_ALL setting.
Also keep the following requirements in mind:
- On Windows, the
orchestration script must be run with administrator rights.
- On Linux, the
orchestration script must be run as a non-root user. In addition, if the
--temp-directory flag is not used, the user
must have access to the default OS
/tmp directory (otherwise, the install will fail
as it tries to delete files from
/tmp).
- If you use the optional
--temp-directory flag, make certain that you specify
the absolute path of the temporary directory to use. A relative path will cause
the script to fail.
Because a WebLogic domain will not be created, the script will not
prompt for any user input.
To run the orchestration script in non-configuration mode:
Note that if the orchestration script fails, it prints an error
message telling you that the
ORACLE_HOME directory specified in the configuration
file exists. At this point, you must either delete the directory or provide a
new location (in the configuration file) before you can re-run the script.
The non-configuration mode installation does not perform the tasks of
creating a WebLogic domain, generating SSL certificates, and registering the
Data Enrichment plugins. If you want to manually perform these tasks, refer to
the following links:
Keep in mind that you must create the WebLogic domain for Endeca
Server before you can generate SSL certificates and register the Data
Enrichment plugins.
After the entire installation is finished, you can verify the
installation in one of two ways: