This topic lists the operations of the Entity Configuration Web Service.
Operation | Description |
---|---|
listEntities | List entities that already exist in the
data store. Note that even if you have not created any custom entities, this
operation lists the base entity created automatically on top of PDRs for your
record attributes.
You can use this operation to export the existing entities, for example during an upgrade procedure, in order to later import them to the Endeca Server with the putEntities operation. |
validateEntity | Validate an entity with the specified key and definition before it has been added. |
validateEntities | Validate multiple entities with specified definitions. |
putEntity | Add an entity with the specified key and
definition to the data store.
The key must be valid according to the NCName format. The NCName format is defined in the W3C document Namespaces in XML 1.0 (Second Edition), located at this URL: http://www.w3.org/TR/REC-xml-names/#NT-NCName For an entity to be created, its building blocks — the physical records and attributes — must already exist in the data store. If an entity with the specified key already exists in the corpus, it is replaced by the new entity with the same key (if the EQL statements defining the entity are valid). If an entity does not exist, and if its EQL definition is valid, the entity is created. You cannot modify or create the base entity using this command. The base entity is created by the Oracle Endeca Server on top of PDRs for existing physical attributes on your records. |
putEntities | Add multiple entities with the specified
keys and definitions to the data store. The keys must be valid according to the
NCName format.
You cannot use this command to create or replace the base entity. |
deleteEntities | Delete multiple entities for which keys are specified. You cannot delete the base entity. |
deleteAllEntities | Delete all custom entities that exist in the corpus without specifying any of their keys. You cannot delete the base entity. |