Creating a data domain in the Endeca Server cluster

This task describes how to create an Endeca data domain after you have deployed an Endeca Server cluster.

Before you start, verify the status of the Endeca Server cluster by going to the Admin Server on host1, navigating to $DOMAIN_HOME/EndecaServer/bin (if you installed the Endeca Server in a secure mode), and running:

endeca-cmd list-nodes --password <sslPassphrase>

where <sslPassphrase> is the password you specified when running the script to generate SSL certificates for the Endeca Server. The command should return a list of host names for all Managed Servers on which the Endeca Server application is running as an Endeca Server cluster.

Important: The endeca-cmd command exists in the $DOMAIN_HOME/EndecaServer/bin directory only on host1 which is the Admin Server, so it is important to access this command in this directory only if you are on the machine that is running the Admin Server for the WebLogic domain for Endeca Server (host1 according to the cluster deployment diagram in this guide). This is the recommended way of accessing endeca-cmd if you are running the Endeca Server cluster in a secure mode. Alternatively, if you want to access endeca-cmd on any of the Managed Servers in the Endeca Server cluster, go to the directory $ORACLE_HOME/Middleware/EndecaServer<version>/endeca-cmd. If you run this command from that directory and have installed the Endeca Server in a secure mode, be sure to specify all the SSL options on the command line. For full information on running the endeca-cmd command, see the Oracle Endeca Server Administrator's Guide.

This procedure assumes you have installed the Endeca Server cluster in a secure mode (SSL-enabled).

To create an Endeca data domain in an Endeca Server cluster:

On host1 (this is the machine on which the Admin Server of the WebLogic Server created for Endeca Server is running), go to $DOMAIN_HOME/EndecaServer/bin.
Create a new data domain profile for the Endeca data domain, which will include a total of two nodes. (Each will be allocated to run on a separate Endeca Server instance.) Run the following command:
```
endeca-cmd put-dd-profile my_two_node_dd_profile --num-followers 1 --password <sslPassphrase>
```
where my_two_node_dd_profile is the name of the data domain profile, and sslPassphrase is the password that you specified with the --sslPassphrase flag of the generate_ssl_keys utility.
This command creates the data domain profile in which there is one leader node and one follower node in the data domain.
Create a data domain using this profile. Run:
```
endeca-cmd create-dd test --dd-profile-name my_two_node_dd_profile --password <sslPassphrase>
```
This command creates an Endeca data domain test, based on the previously configured data domain profile. In this data domain, two nodes (Dgraph processes) are running, each on its own Endeca Server instance.
Verify the state of the data domain. Run:
```
endeca-cmd get-dd-health test --password <sslPassphrase>
```
The command returns the following information:
```
Data domain: test
Leader node health:
Hostname: host1
Port: 7004
Protocol: HTTPS
Is available
Follower nodes health:
Hostname: host2
Port: 7004
Protocol: HTTPS
Is available
```
This output indicates that the data domain test runs on two nodes, both of which are available. Note that even though you created this data domain from one machine, it is configured to run two nodes on different Endeca Server instances. You can now access this data domain from any Endeca Server instance machine.