The Configuration Web Service lets you create and change the records schema and configuration, for the data domain.
<host>:<port>/endeca-server/ws/config/<dataDomain>?wsdlwhere the host and port represent the Oracle Endeca Server, and the dataDomain is the name of the data domain created on the server.
A request to the Configuration Web Service consists of a configTransaction element, which contains a series of operations that read the configuration and schema and also update it. Operations can be combined arbitrarily in a single service request; each of the operations can appear at most once. The operations perform actions on PDRs (Property Description Records), DDRs (Dimension Description Records), groups, the GCR (Global Configuration Record), and on XML configuration documents.
The input to the Configuration Web Service depends on the operation used. It can include attribute schema records (PDRs and DDRs), Global Configuration Record, groups, and a set of XML configuration documents.
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 Configuration Web Service return data.
If the operation returns data, the response to the 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 Configuration Web Service.
<config:configTransaction> xmlns:config="http://www.endeca.com/MDEX/config/services/types/3/0" xmlns:mdex="http://www.endeca.com/MDEX/config/XQuery/2009/09"> <config:listGroups/> </config:configTransaction>