Defining a data domain profile

To define a new data domain profile in the Endeca Server, use the endeca-cmd put-dd-profile command, or the putDataDomainProfile request of the Cluster Web Service. The domain profile must exist before you create data domains, otherwise, the default data domain profile is used.

A data domain profile defines the resources available to a data domain. It serves as a template for the Endeca Server when it creates data domains on provisioned Endeca Server nodes in the Endeca Server cluster.

A data domain profile is used by the Endeca Server only for the initial data domain creation. When you create a data domain in the Endeca Server cluster, it is configured based on either a default data domain profile or a custom data domain profile (if you specify it). After the data domain has been created, the profile is not associated with this data domain. That is, you can later change the characteristics of the data domain. You can also delete this data domain profile without affecting any data domains.

Note: Be careful when creating a data domain profile to ensure the Endeca Server has enough capacity to host a data domain created based on this profile. For example, the setting for compute-cache-size in the data domain profile is larger than the ramSizeMB that you specified in the node profile for the instances of Endeca Server nodes, then no data domain using this profile can be created.

To define a data domain profile:

Use the endeca-cmd put-dd-profile command, specifying the domain profile parameters. For information, see Data Domain profile parameters.
For example, the following command specifies the data domain profile named MyProfile:
endeca-cmd put-dd-profile MyProfile
         --description "To be used in development environment"
         --query-leader true
         --read-only false
         --num-followers 2
         --oversubscribe true
         --num-compute-threads 4
         --compute-cache-size 4
         --startup-timeout 600
         --shutdown-timeout 30
         --session-id-type header
         --session-id-key X-Endeca-Session-ID
         --autoIdle true
         --idleTimeoutMinutes 30

Alternatively, you can specify the data domain profile with a request to the Cluster Web Service, using the putDataDomainProfile operation, specifying the values in the request.

After creating this new profile, you can create data domains with it.