Changing settings in EndecaServer.properties

Change the configuration of this file to include the listen port of all three Managed Servers, their host names (for the Cluster Coordinator), and the location of the shared file system.

1. Go to $DOMAIN_HOME/config, and open the EndecaServer.properties file in a text editor.
2. Modify the file as follows:
   • endeca-cluster-coordinator-hosts must contain comma-separated host names of all three Managed Servers: host1, host2, and host3, in this example. (Always use the top-level portion of the domain names, for this field. Do not use the Fully Qualified Domain Names).
     Note: If you will later expand the Endeca Server cluster, by adding machines to the WebLogic domain, you should include their host names in this list based on the following requirement—the total number of these machines should be an odd number that is equal to or greater than three. For example, if you will be adding a fourth machine, its host name should not be added to this list. If you will be adding a fifth machine, you can optionally leave the list to contain three host names, or include all five host names — both configurations will satisfy the Cluster Coordinator requirement for the Endeca Server cluster.
   • endeca-data-dir and endeca-offline-dir should point to the directories on a shared file system to which all three hosts have write access. The file paths should use forward slashes (even if you are installing on Windows).
   • endeca-cluster-coordinator-dataDir should point to the directory on the shared file system. The file path should use forward slashes (even if you are installing on Windows).
   • endeca-data-enrichment-pluginsDir and endeca-data-enrichment-resourcesDir should point to their directories on the shared file system. The file paths should use forward slashes (even if you are installing on Windows).
   • endeca-webserver-port should be 7004 (this assumes that you installed the Endeca Server in a secure mode). For a non-secure installation, this port should be 7003. (You can use another port number, as long as the port is either the same as an SSL-enabled port configured for the Managed Servers, or their Listen Port, and as long as the port number is not in the endeca-ds-port range as shown in the example in this topic.)
3. Leave the other settings unchanged and save the file.

endeca-require-https=true
endeca-runtime-basedir=C:/Oracle/Middleware/EndecaServer<version>/endeca-server
endeca-data-dir=Q:/data_dir
endeca-offline-dir=Q:/offline_data_dir
endeca-logs-dir=C:/Oracle/Middleware/user_projects/domains/endeca_server_domain/EndecaServer/logs
endeca-dgraph-install=C:/Oracle/Middleware/EndecaServer<version>/endeca-server/dgraph
endeca-webserver-port=7004
endeca-ds-port-min=7011
endeca-ds-port-max=8011
...
endeca-ds-cert-file=C:/Oracle/Middleware/user_projects/domains/endeca_server_domain/config/ssl/dgraphCert.pem
endeca-ds-ca-file=C:/Oracle/Middleware/user_projects/domains/endeca_server_domain/config/ssl/dgraphCA.pem
endeca-secure-mode=true
endeca-cluster-coordinator-dir=C:/Oracle/Middleware/EndecaServer<version>/endeca-server/cluster-coordinator
endeca-cluster-coordinator-hosts=host1,host2,host3
endeca-cluster-coordinator-clientPort=2181
...
endeca-cluster-coordinator-dataDir=Q:/cc_data_dir
endeca-cluster-coordinator-dataLogDir=C:/Oracle/Middleware/user_projects/domains/endeca_server_domain/EndecaServer/data
endeca-cluster-coordinator-serverPort=3181
endeca-cluster-coordinator-leaderPort=4181
endeca-cluster-coordinator-maxClientCnxns=0
endeca-cluster-coordinator-minSessionTimeout=4000
endeca-cluster-coordinator-maxSessionTimeout=180000
...
endeca-data-enrichment-pluginsDir=Q:/DataEnrichment/plugins
endeca-data-enrichment-resourcesDir=Q:/DataEnrichment/resources