Changes to creating data domains and the treatment of the Dgraph processes

Due to the changes that occurred for the Endeca Server cluster, the way you create an Endeca data domain (known in the previous release as an "Endeca data store") has changed. Similarly, the administration of the Dgraph process has changed.

These statements summarize the changes:

In the previous release, system administrators could directly manage a particular Dgraph, as there was a direct correlation between the Dgraph host and port and the Endeca Server host and port.
In this release, two types of system administrators may be involved — first, those system administrators that administer the Endeca Server cluster, start one or more Endeca Server instances, and create data domain profiles that could be used to create data domains.

Next, those administrators that manage data domains, create data domains, utilizing the Endeca Server nodes, and the data domain profiles that have been created for them.

Note: Depending on the deployment scenario, the same system administrators can be responsible both for the provisioning of the Endeca Server instances and the creation and management of the data domains.
In the previous release, the data store was created by running endeca-cmd after installing and starting the Endeca Server.
To create a data domain in this release, after installing and starting the Endeca Server, use the endeca-cmd command to first create the data domain profile (or use the default data domain profile), and then use this profile to create a data domain.
In the previous release, the data store's index (known as "data files"), could be configured to reside on a different directory than the installation of the Endeca Server, by using the endeca-cmd command.
In this release, this setting is controlled by the EndecaServer.properties file. It is strongly recommended not to change this setting.

Note that if the data domain is deployed in the Endeca Server cluster, the configuration of this file must be exactly the same on all Endeca Server instances supporting this data domain in a cluster. Additionally, the index must reside on the same directory on a shared file system that is accessible by all Endeca Server instances. If you have created more than one data domain, all of their index files will reside in the same directory.

For information about EndecaServer.properties, see the Oracle Endeca Server Administrator's Guide.

For more information on the management of data domains in this release, see Cluster changes in this guide, and the Oracle Endeca Server Cluster Guide.