The following table lists the concepts and terms that have changed in this Endeca Server release compared with the previous release.
New term | Description |
---|---|
Endeca Server Java application | In the previous release, the Endeca Server software included the Endeca Server Java application (as in this release). However, in this release, the Endeca Server Java application is installed and deployed in the Oracle WebLogic Server. This term is also known as the Endeca Server, the Endeca Server instance, or the Endeca Server node. |
Endeca Server domain | In the previous release, this term did not
exist. In this release, before you deploy the Endeca Server application in the
WebLogic Server, a dedicated WebLogic domain must be configured for it. This
domain is known as the Endeca Server domain. (This process is described in
detail in the
Oracle Endeca Server Installation Guide.) This term
is also known as the
WebLogic domain for the Endeca Server application.
Important: Do not confuse the term
Endeca Server domain with the term
Endeca data domain. The Endeca Server domain
refers to the domain created in the WebLogic Server. The term data domain, or
Endeca data domain, refers to the logical collection of data and metadata
managed by the Endeca Server application running in the WebLogic Server domain.
|
data domain, or Endeca data domain | In the previous release, this term was known
as the
data store. In this release, data domain is a
logical collection of data and metadata managed by the Endeca Server. Through
its interfaces, the Endeca Server allows for the data loading, configuration,
and querying of a data domain. A data domain may impose order on subsets of its
data through entities (known in Studio as views).
A data domain is the largest unit of data over which the Endeca Server allows queries to be expressed. It represents a discrete set of data and includes indexed data records and system records. (Applications wishing to correlate, join, or display data from multiple data domains must do so themselves.) Each data domain runs one or more Dgraph processes. Each of the Dgraph processes runs on the Oracle Endeca Server node; depending on the number of Dgraph processes configured for the data domain, it can be hosted by more than one Endeca Server nodes. To create a data domain hosted in the Oracle Endeca Server, you first create a data domain profile, using either the Endeca Server Web service interfaces or the endeca-cmd utility. You can then use this profile to create a new data domain. The Dgraph processes for this data domain will then be allocated and started on the available Endeca Server nodes. If the data domain runs multiple Dgraph processes hosted by more than one Endeca Server instances, it is also referred to as the data domain cluster that runs in the Endeca Server cluster. |
Endeca Server cluster | In the previous release, the Endeca Server
cluster was represented by a set of Endeca Server instances each running a
single Dgraph process. The cluster was managed at the Dgraph level.
In this release, the Endeca Server cluster is a deployment of multiple Endeca Server instances that host and manage multiple clustered data domains. The Endeca Server cluster is managed at the Endeca Server instance level. For a complete description of a cluster, including a diagram, see the Oracle Endeca Server Cluster Guide. |