1. Web Services On Demand Guide
  2. Preparing the Integration Event WSDL File and Schema Files

Preparing the Integration Event WSDL File and Schema Files

You can use the methods of the Integration Events service to track changes for the supported record types. You must download the integrationevent.wsdl file and the XSD Schema file for each record type that you require to track. You can download XSD files for all objects for the Web Services v1.0 API and for the Web Services v2.0 API. The integration event WSDL file imports the XSD files for each record type.

In addition, to get integration events generated for merge operations, you must download a Merge schema file and integrate this and the integration event WSDL file with your application. Existing customers must download the latest integrationevent.wsdl file, if they wish to use the Merge schema file.

Note: The Merge schema file is only applicable to integration events processing and cannot be used for other purposes.

The integrationevent.wsdl file is dynamically generated based on which objects have an active workflow rule with an integration event action configured.

For each object with an integration event action configured, a child element of <SiebelMessage> is added to the WSDL files, for example, <ListOfAccount>.

For child objects, an element is added for the parent object, for example, an entry for the Account parent object is added for the Account Team child. For child objects with multiple parents, an element is added for each possibe parent, for example, Account, Contact, and Opportunity parent entries would be added for a Revenue child.

Also, for each object, one or more <import> elements are added to the WSDL file with attributes for the namespace and schema location of an XSD file. The attribute values depend on whether Web Services v1.0 or Web Services v2.0 Schema have been selected for the integration events for the object. The following is an example of an <import> element for an object with an integration event for which the Web Services v1.0 Schema is selected:

<xsd:import namespace="urn:/crmondemand/xml/account" schemaLocation="Account.xsd" />

The following is an example of an <import> element for an object with an integration event for which the Web Services v2.0 Schema is selected:

<xsd:import namespace="urn:/crmondemand/xml/Account/Data" schemaLocation="Account.xsd" />

For more information about specifying the schema version when creating integration event actions, see Oracle CRM On Demand Online Help.

To prepare the WSDL

  1. Go to the Web Services Administration page in the Oracle CRM On Demand application.

  2. Download the Integration Events WSDL.

  3. Download the Generic Schema files for objects for which you wish to generate integration events and copy these to the folder where you downloaded the WSDL file.

  4. If you have created custom fields or renamed fields for an object, download the Custom XSD file for the object.

  5. If you require to access events resulting from merge operations, download the generic schema file for the Merge Service API.

  6. In the integrationevent.wsdl file, remove references to any Schema files for objects you will not be using.

  7. Add the integrationevent.wsdl file to your development environment.

Note: You must repeat steps 3 through 7 each time a new custom field is added that will be tracked through integration events, or when you begin tracking a new object type. Otherwise, the client application cannot process events containing these newly added fields or objects.