Configuring silent installation on Windows

The silent installer for Windows reads the necessary input from command-line properties.

Silent installations are installations that use the /s switch to run without a user interface. The responses to the Windows installer prompts are supplied with command-line properties and provide the same answers that an interactive user would provide.

The basic syntax for a silent installation on Windows is: 
platformservices_603_x86_64pc-win32.exe /s /v" /qn endeca_properties"
The Endeca properties are described below. Note that this is the asynchronous version. To run the command synchronously, preface the installer executable with the start /wait command (especially useful in automated scripts).
If you want the installer to create a log, use the /l switch as part of the /v arguments; for example: 
/s /v"/l* install.log /qn endeca_properties"

Note that the Endeca HTTP Service, when installed, does not start automatically, though it is set to automatically start on system startup (it will be started upon the next reboot).

Endeca Properties

The following properties, when passed to the silent installer, provide configuration information for the installation.

Endeca Property Name Meaning
INSTALLDIR Required. Specifies the absolute path to the directory to install Platform Services (e.g., C:\Endeca\PlatformServices). The path should be in escaped quotes. Keep in mind that you cannot install the Endeca software in a directory with spaces in its name.
Note: If you do not use the default location, and you are installing more than one Endeca product on the same machine, ensure that you install each product to a separate location.
ENDECA_USER_NAME Required for features that install the HTTP Service. The user name to use when launching the Endeca HTTP Service. Note that the user must already exist and the name should be specified in escaped quotes.
ENDECA_USER_PASSWORD Required if the user name is specified. The password for the Endeca HTTP Service user. Note that the password should be in escaped quotes.
ENDECA_PASSWORD_CONFIRM Required if the user name is specified. Confirms the password for the Endeca HTTP Service user. Note that the password should be in escaped quotes.
_USERDOMAIN Optional. The Windows domain for the Endeca HTTP Service user. Note that the domain name should be in escaped quotes. The default is the domain the current user is logged in to.
ETOOLS_HTTP_PORT Optional. The port on which the Endeca HTTP Service listens. The default is 8888.
ETOOLS_SERVER_PORT Optional. The shutdown port for the Endeca HTTP Service. The default is 8090.
JCD_PORT Optional. The port on which the Endeca JCD Service listens. This service is not installed by default. The default is 8088.
ADDLOCAL Optional. Specifies which features to install (see the next section for the feature names). If omitted, all features (except the Endeca Control System) are installed.

Endeca Installable Features

The ADDLOCAL property specifies which Endeca features to install. The features correspond to the list on the Custom Setup screen in the interactive installer. If the ADDLOCAL property is omitted, all features are installed, except for the Endeca Control System. You can specify multiple features by using a comma-delimited list.

Property Value Meaning
Endeca_Platform_Services
  • IAP_X64_Bin
  • IAP_X86_Bin
Data Foundry directories and components, including Forge and the CADK. Use IAP_X64_Bin for the 64-bit version of the binaries and IAP_X86_Bin for the 32-bit version. Note that Forge is a 32-bit program regardless of the specified feature.
Endeca_Application_Controller_Server EAC Central Server and Agent
Endeca_Application_Controller_Agent EAC Agent only
Endeca_Application_Controller_Utility EAC command-line utility (eaccmd)
Endeca_Logging_and_Report Endeca Log Server and Report Generator
Endeca_Presentation_and_Logging_APIs
  • Java_APIs
  • NET_APIs
APIs for Endeca MDEX Engine and Log Server. Use Java_APIs for the Java version of the APIs and/or NET_APIs for the .NET version.
Endeca_Reference_Implementation
  • Sample_data
  • JAVA_jsp_Implementation
  • ASP.NET_Implementation
Sample references, consisting of the sample wine project with source data and JSP and .NET UI front-end references.
Endeca_Control_System
  • JCD_X64_Bin
  • JCD_X86_Bin
Endeca Control Interpreter. Use JCD_X64_Bin for the 64-bit version of the binaries and JCD_X86_Bin for the 32-bit versions.
Endeca_Documentation This guide, Migration Guide, Licensing Guide

Common Configurations

The following are some configurations for building specific types of servers. Note that the command examples are wrapped for ease of reading.

Development Server:
  • Installs the entire Platform Services package (except for the Endeca Control System)
The command line would be similar to this example, which omits the ADDLOCAL property: 
platformservices_601_x86_64pc-win32.exe /s /v" 
  /qn INSTALLDIR=\"C:\Endeca\PlatformServices\" 
  ENDECA_USER_NAME=\"endeca\" ENDECA_USER_PASSWORD=\"endeca\"
  ENDECA_PASSWORD_CONFIRM=\"endeca\" 
  ETOOLS_HTTP_PORT=8888 ETOOLS_SERVER_PORT=8090"
MDEX Engine Server:
  • EAC Agent
  • EAC Utility
  • Presentation and Logging APIs
The command line is identical as the Development Server, with the addition of this ADDLOCAL property: 
ADDLOCAL=Endeca_Application_Controller_Agent,
Endeca_Application_Controller_Utility,
Endeca_Presentation_and_Logging_APIs,Java_APIs,NET_APIs
ITL Server:
  • EAC Server
  • EAC Utility
  • Forge (including the CADK)
  • Reference implementations
  • Log Server and Report Generator
The command line is identical as the Development Server, with the addition of this ADDLOCAL property: 
ADDLOCAL=Endeca_Application_Controller_Server,
Endeca_Application_Controller_Utility,
Endeca_Platform_Services,IAP_X64_Bin,
Endeca_Reference_Implementation,Sample_data,
JAVA_jsp_Implementation,ASP.NET_Implementation,
Endeca_Presentation_and_Logging_APIs,
Java_APIs,NET_APIs
This example is for a 64-bit Windows server. Replace IAP_X64_Bin with IAP_X86_Bin for a 32-bit Windows server.
Tools Server:
  • EAC Agent
  • EAC Utility
  • Presentation and Logging APIs
  • Reference implementations
  • Log Server and Report Generator
The command line is identical as the Development Server, with the addition of this ADDLOCAL property: 
ADDLOCAL=Endeca_Application_Controller_Agent,
Endeca_Application_Controller_Utility,
Endeca_Presentation_and_Logging_APIs,Java_APIs,NET_APIs,
Endeca_Reference_Implementation,Sample_data,JAVA_jsp_Implementation,
ASP.NET_Implementation,Endeca_Logging_and_Report