Connecting an Endeca Server connection to an Endeca Server cluster

The Endeca Server can use a clustered configuration. When configuring an Endeca Server cluster to use with Studio, you should always have a load balancer in front of the cluster. For details on Endeca Server clustering, including how to set up a load balancer in front of the cluster, see the Oracle Endeca Server Clustering Guide.

Endeca Server connection definition settings for connecting to a cluster

When configuring the definition for an Endeca Server connection that is connecting to an Oracle Endeca Server cluster, the relevant settings are:

Endeca Server Connection Setting Description
server Required. The server for the load balancer.
port Required. The port number for the load balancer.
dataDomainName Required. The name of the data domain.
sslConfig Optional. If applicable, the SSL settings for connecting to the load balancer. Includes the following settings:
  • caFile - The truststore file.
  • caPassword - The truststore password.

    Note that on the Data Source Definition dialog, once you save the Endeca Server connection, the value of caPassword is masked as ************. The value also is encrypted in the Studio database.

  • certFile - The name of the keystore file.
  • certPassword - The keystore password.

    Note that on the Data Source Definition dialog, once you save the Endeca Server connection, the value of certPassword is masked as ************. The value also is encrypted in the Studio database.

Example of an Endeca Server connection connected to an Endeca Server cluster

The following Endeca Server connection is configured to connect to a cluster. 
{
 "server":"loadbalancer1.acme.com",
 "port":"7002",
 "dataDomainName":"acmeDB",
 "sslConfig": {
        "caFile":"truststore.ks",
        "caPassword":"************",
        "certFile":"keystore.ks",
        "certPassword":"************"
        },
  "name":"Sales Data"
}