Loading configuration documents

You can use the Configuration Web Service to load the XML configuration documents to the data domain's configuration.

If you load your configuration documents before loading your source records, you can modify them as needed. After they have been configured as desired, you can then use the Data Ingest Web Service to load your source records.

You can load the following configuration documents:
  • dimsearch_config
  • recsearch_config
  • relrank_strategies
  • stop_words
  • thesaurus

For more information on the syntax of these documents, see the section Dgraph Configuration Reference.

The operations for managing the XML configuration documents are the following:
Operation Description
listConfigDocuments Return the names of the Dgraph process configuration documents.
getConfigDocuments Return the requested Dgraph process configuration documents.
putConfigDocuments Add or replace each of the specified Dgraph process configuration documents.
The following example illustrates the use of the putConfigDocuments operation to load the RECSEARCH_CONFIG configuration document. The RECSEARCH_CONFIG document creates one search interface (named All) that consists of the ProductType, Region, and Description attributes: 
<soap:Envelope>
<soap:Body>
<config:configTransaction>
<config:putConfigDocuments>
    <mdex:configDocument name="recsearch_config">
      <RECSEARCH_CONFIG>
        <SEARCH_INTERFACE CROSS_FIELD_BOUNDARY="ALWAYS" NAME="All">
          <MEMBER_NAME RELEVANCE_RANK="3">ProductType</MEMBER_NAME>
          <MEMBER_NAME RELEVANCE_RANK="2">Region</MEMBER_NAME>
          <MEMBER_NAME RELEVANCE_RANK="1">Description</MEMBER_NAME>
        </SEARCH_INTERFACE>
      </RECSEARCH_CONFIG>
    </mdex:configDocument>
  </config:putConfigDocuments>
</config:configTransaction>
</soap:Body>
</soap:Envelope>

To load the XML configuration documents into the data domain of the Oracle Endeca Server:

  1. Make sure that the Oracle Endeca Server and the data domain are running. Access the Configuration Web Service for the data domain as in this example: http://<host>:<port>/ws/config/<DataDomain>?wsdl.
  2. Make a SOAP request to the Configuration Web Service as shown above.
If the request is successful, the response contains a SOAP success message, similar to the following: 
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
 <soapenv:Header/>
 <soapenv:Body>
   <config-types:results xmlns:config-types="http://www.endeca.com/MDEX/config/services/types/3/0"/>
 </soapenv:Body>
</soapenv:Envelope>