Important usage note

This topic discusses operations in the data domain you can perform using the Data Ingest Web Service. It also lists several operations that are not recommended.

Supported data domain operations

You can use the Data Ingest Web Service to perform the following actions in the data domain:
  • Add new individual records to the data domain
  • Add managed attribute values
  • Add key-value assignments on the existing records in the data domain
  • Delete or replace specified record assignments
  • Delete individual records, or replace them
  • Change the name of a standard attribute in the running data domain
  • Remove all data records and the schema records from the data domain
  • Provision the data domain (by creating the schema records, such as PDRs and DDRs, and resetting these records to their default values).

Operations that are not recommended

While the actions listed below can be done with the Data Ingest Web Service, it is not recommended to use the Data Ingest Web Service for them.

The Data Ingest Web Service does not perform reference checks, so it is possible to render your data domain invalid or unusable by performing certain operations using this Web service. Here is a list of operations to use with caution:
  • Removal of system records — these are records that define your schema (such as PDR, DDR, or other system records). For example, removing a PDR may invalidate a group to which the attribute defined by this PDR belongs. As a workaround, you can remove all records and schema and then provision the data domain using the Reset Data Store connector in Integrator. For more information on custom connectors available in Integrator, see the Oracle Endeca Information Discovery Integrator User's Guide.
  • Creation of records that define groups or entities (used for views in Studio). It is recommended to use either the Configuration Web Service or Studio for these actions. For information on the Configuration Web Service, see the Oracle Endeca Server Developer's Guide. For information on Studio, see the Oracle Endeca Information Discovery Studio User's Guide.
  • Renaming of individual standard attributes that belong to groups or entities (used for views in Studio). If you rename the attribute without removing it from groups or entities, you will invalidate them. Remove the standard attribute from groups or entities before renaming it.