Configuring the application on multiple servers

To configure an application on multiple servers run the Deployment Template deploy script.

Before running the Deployment Template, verify that:

On the Tools server, you have installed Endeca Workbench and the EAC Agent.
On the Data Processing (ITL) server, you have installed the Platform Services (this includes the EAC Central Server and EAC Agent) and the MDEX Engine. The data is typically hosted on this server as well.
On the Data Processing (ITL) server, you have downloaded the Deployment Template and set up a directory for your deployment, such as C:\Endeca\apps on Windows, or localdisk/apps on UNIX.
On the MDEX Engine server, you have installed the MDEX Engine and the EAC Agent. (You can have multiple physical servers each running the MDEX Engine, or more than one MDEX Engine running on the same machine.)
On all servers, the Endeca HTTP service is running. This starts the EAC.

To configure the application on multiple servers:

Go to the C:\Endeca\Solutions\deploymentTemplate-<version>\bin directory on Windows or /usr/local/Endeca/Solutions/deploymentTemplate-<version>/bin on UNIX and run the deploy.bat or deploy.sh script. This script creates the project directories and configuration files.
Confirm the correct version of the Platform Services installation package (the template verifies the ENDECA_ROOT variable), and answer Yes to proceed.
Select the deployment type, Dgraph.
Specify the name of the application: MyApp and the location of the application directory: C:\Endeca\apps on Windows or /localdisk/apps on UNIX.

Note: In this guide, the directory for each of your applications is referred to by the [appDir] abbreviation. With the paths above, this is equal to C:\Endeca\apps\MyApp on Windows and /localdisk/apps/MyApp on UNIX.
Specify the EAC port (the Endeca HTTP service port) or accept the default port: 8888
For Enable IAP Workbench integration, specify Yes.

Note: This configuration also applies to any Endeca Workbench edition.
Specify the Endeca IAP Workbench port (this is the Endeca Tools Service port for your Endeca Workbench edition) or accept the default port: 8006.
Specify other necessary ports:
1. For the Dgraph1, specify the Dgraph1 user query port or accept the default: 15000
2. For the Dgraph2, specify the Dgraph2 user query port or accept the default: 15001
3. For the Endeca Logging and Reporting Server, specify the server port or accept the default: 15010
  Note: The Logging Server port number can be no larger than 32767. If you plan to use the reference implementation and verify the Logging Server, you can set the Logging Server to run on port 15002 (for Dgraph1) or on port 15003 (for Dgraph2), and the reference implementation will work by default when connected to an MDEX Engine running on ports 15000 and 15001, respectively. These settings assume that the Logging Server runs on the same machine as the MDEX Engines. If you are using a different port for your Dgraph with the JSP reference implementation, specify a port equal to Dgraph_port_number + 2. This is because the Logging Server for the JSP reference implementation submits log entries to a port 2 above the Dgraph port.