Provisioning the data store

To provision the data store, use the provisionMdex operation in the Data Ingest Web Service. This operation creates the primordial records (such as PDRs and DDRs), and resets these records to their default values.

It is assumed that you run this operation after running clearMdex. It is also assumed that you have previously exported your configuration defined in the schema records and will import it after you run the provisionMdex operation.

To provision the data store and create PDRs and DDRs with their default values, use the provisionMdex element in a Data Ingest Web Service request. The request should use this format:
<ingest:provisionMdex/>
Note: If you submit the provision request after a Transaction Web Service request that starts a an outer transaction, the provision request must specify the outer transaction ID as the first element. If no outer transactions have been started, the ID element must be omitted in the request, or its value must be empty.

To provision the data store:

Create a provisionMdex request, similar to the example below and send the request to the Data Ingest Web Service:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:ingest="http://www.endeca.com/MDEX/ingest/1/0">
 <soapenv:Header/>
     <soapenv:Body>
        <ingest:provisionMdex>
           <ingest:OuterTransactionId>txId</ingest:OuterTransactionId>
        </ingest:provisionMdex>
      </soapenv:Body>
   </soapenv:Envelope>                                                        
This request adds the primordial schema records in the data store and sets these schema records to their defaults.
A successful provisionMdexResponse returned from the above sample request should look similar to this example:
<ingest:provisionMdexResponse>
            <ingest:OuterTransactionId>txId</ingest:OuterTransactionId>
            <ingest:numPropertiesCreated>2</ingest:numPropertiesCreated>
            <ingest:numRecordsAffected>2</ingest:numRecordsAffected>
            <ingest:numRecordsDeleted>0</ingest:numRecordsDeleted>
</ingest:provisionMdexResponse>

After you have run the provisionMdex operation, you can import your configuration and run admin/<DataStore>?op=updateaspell to update the spelling dictionary.

If you use Reset Data Store for running clearMDEX and provisionMDEX operations, then this connector also updates the spelling dictionary.