Running a silent installation on UNIX

The silent installer for UNIX reads the necessary input from a response file.

Silent installations are installations that use the --silent flag to run without a user interface. The responses to the UNIX installer prompts are supplied in a response file and provide the same answers that an interactive user would provide. The silent installer is useful if you want to add the installation of Platform Services to your own install script, or push out the installation on multiple machines.

To launch the silent installer on UNIX:

Create a new text file. In this procedure, the file is named silent.txt.

In the file, specify the response value for each prompt on its own line, in the order in which they appear in the interactive installer. For example:

Y
8888
8090
8088
Y
/usr/local/endeca/MDEX/6.1.5
Y

Each line answers a question that the installer asks:

Response	Description
Y	Accepts the Endeca End-User License Agreement.
8888	The port on which the Endeca HTTP Service listens.
8090	The shutdown port for the Endeca HTTP Service.
8088	The port number of the Endeca Control System JCD.
Y	Indicates that you want to install EAC Central Server and Agent.
/usr/local/endeca/MDEX/6.1.5	The absolute path to the MDEX Engine root directory. If the MDEX Engine is not installed, use a newline or carriage-return to indicate that there is no MDEX Engine installed.
Y	Indicates that you want to install the reference implementations.

Note: You must specify a value for each prompt. Even if you want to use the default, you must specify that value to the installer.

From a command prompt, navigate to the directory where you downloaded the installer.
Run the install script with the --silent flag (which indicates silent mode), the --target flag (which specifies the absolute path of the target installation directory), and the response file as an input. For example:
```
./platformservices_601_x86_64pc-linux.sh --silent --target /usr/local < silent.txt
```
The installation is complete when the screen displays a reminder message about setting the environment variables.

After the installation is finished, you should run a script that sets the Platform Services environment variables (such as ENDECA_ROOT), as well as some additional ones that are used internally. The two environment variable scripts are located in the endeca/PlatformServices/workspace/setup directory and are named as follows:

installer_csh.ini (for csh and tcsh shells)
installer_sh.ini (for Bourne, Bash, and Korn shells)

The following example shows how to run the sh version:

source /usr/local/endeca/workspace/setup/installer_sh.ini

Generally this command should be placed in a script run at the startup of the shell so the variables are set for future use.

To start the Endeca HTTP Service, change to the endeca/PlatformServices/6.0.3/tools/server/bin directory and run the startup.sh script. (You can also run the script from another directory by using the absolute path to the script). For information on controlling this service, see the Endeca Application Controller Guide.

If you did not specify the MDEX Engine root directory in the response file, the com.endeca.mdexRoot setting (in the EAC eac.properties configuration file) will have a blank value. The file is located in the $ENDECA_CONF/conf directory. If you later install the MDEX Engine on your system, you must edit the file and add the absolute path of the MDEX Engine root directory in the setting. For more information on this file, see the Endeca Application Controller Guide.