Orchestration script syntax

This topic describes the syntax of the Endeca Server orchestration script.

The orchestration windows and linux directories also contain the Endeca Server orchestration script for your operating system.

The orchestration script is named run_endecaserver_install.sh for Linux and run_endecaserver_install.bat for Windows. The syntax to run the script is: 
run_endecaserver_install.bat|sh config_file [--temp-directory temp_dir]
where:
  • config_file is the name of the script configuration file (such as config_linux.prop). If the file is not in the same directory as the orchestration script, then the name must include the absolute path of its location.
  • --temp-directory is an optional flag that specifies the absolute path of the temporary directory to use. The script extracts and executes the installers in this directory. If this flag is not used, then the default behavior is to use the operating system's configured temporary directory. Note that the contents of the directory are first deleted before the script unpacks the installer files.
A sample use on Linux is: 
./run_endecaserver_install.sh config_linux.prop --temp-directory /tmp

Note that a path is not needed for the configuration file because it is in the same directory as the script.

Orchestration script directory contents

The orchestration script and its resources are shipped in a ZIP file for Windows and a TAR file for Linux. When you unpack these files, a directory (named windows or linux) is created.

Both directories contain these items:
  • orchestration script (run_endecaserver_install.sh or run_endecaserver_install.bat)
  • script configuration file (config_linux.prop or config_win.prop)
  • utils directory, which contains utilities used during the installation
  • rsp.template directory, which contains the response files used for the WebLogic and Endeca Server silent installations

You can unpack the ZIP/TAR files in any directory, such as your installer source directory.

Script log directory

When the orchestration script runs, it creates a log directory (in the temporary directory) in which it writes the various log files for the installation. For example, the ENDECA_INSTALL.log contains information on the Endeca Server installation.