The Entity Configuration Web Service lets you create, replace, delete and update entities.
The Entity Configuration Web Service is a WS-I compliant SOAP/HTTP Web service that also supports the wrapped-document/literal pattern of binding. The service is declared in sconfig.wsdl. The service supports creation and management of entities, as well as validation of statements in them.
http://localhost:<port>/ws/sconfig/<DataStore>?wsdlwhere the host and port represent the Oracle Endeca Server, and DataStore is the name of the data store created on the server.
xmlns:v1_0="http://www.endeca.com/endeca-server/sconfig/1/0"In this example, 1 is the major version; 0 is the minor version. If more than one minor version is supported, it is listed in its own namespace in the WSDL document.
For reference information on the Entity Configuration Web Service operations and for schema elements, see the Oracle Endeca Server API Reference.
A request to the Entity Configuration Web Service depends on the operation. The operations perform actions on entities, listing them, adding and removing them, and validating them.
After creation, each entity is represented as a single logical record in the Endeca data store. The on-disk storage of these records means that they persist across restarts of the Endeca data store, as they are loaded into the Dgraph process at start-up time.
The input to the Entity Configuration Web Service depends on the operation used. It can include a key and an EQL statement that defines an entity, for put operations; it can include the key only, for deleteEntities operation; or it can include the definition of the entity, for validate operations.
It is incorrect to specify an outer transaction ID when an outer transaction is not in progress. All configuration requests with incorrectly specified outer transaction IDs fail with a SOAP fault.
Not all operations in the Entity Configuration Web Service return data.
If the operation returns data, the response to the Entity Configuration Web Service is a results element, within which each of the submitted operations produces an element showing its own results.
If any operation does not succeed, the whole web service transaction returns a SOAP fault and none of the operations are applied. An operation may not succeed if an outer transaction has been started by a Transaction Web Service, but an incorrect ID has been specified within a request sent to the Entity Configuration Web Service.