Print      Open PDF Version of Online Help


Previous Topic

Next Topic

About Integration Events

An integration event is a mechanism for triggering external processes based on specific changes (create, update, delete, associate, dissociate) to the records in Oracle CRM On Demand. Integration events contain information about the data that was changed by the user. This information is stored in one or more integration event queues as an XML file, which allows the details of events in Oracle CRM On Demand to be accessed by external applications. For example, an external application might need to track Account changes in Oracle CRM On Demand and trigger local updates accordingly.

For customers who require multiple applications to integrate with Oracle CRM On Demand independently, the company administrator can define multiple integration event queues. Using the integration event functionality, the same event can be generated for multiple queues, and the external applications are guaranteed queue integrity, because the external applications can be configured to request only the events from a specific queue.

About Setting Up Integration Event Administration

If you are a new customer, then the integration event functionality is automatically enabled. However, if you are an existing customer, then the Oracle CRM On Demand integration event functionality must be configured by Oracle CRM On Demand Customer Care and by your company administrator. Contact Oracle CRM On Demand Customer Care to request support for Integration Event Administration and to specify the maximum total size of the integration event queues.

Note: The maximum size of the integration queues is not displayed on your Company Profile page.

When Oracle CRM On Demand Customer Care has set up the integration event functionality, the Integration Event Administration link is visible in the Data Management Tools section of the Admin Homepage. Also, the Administrator user role has the Enable Integration Event Access privilege enabled. For more information about user roles, see Adding Roles.

About Creating, Storing, and Accessing Integration Events

To trigger the creation of integration events, you must create workflow rules with Create Integration Event actions. For each such action, you can specify which fields on a record are to be tracked. When the value changes in a tracked field, the change is recorded in an integration event. You can also specify to which queues the integration events are written. For more information about workflow rules, see About Workflow Rules.

Integration events are stored in one or more queues, the maximum total size of which is specified for your company by the Customer Care representative. A default integration event queue is provided, and you can create additional queues.

When a queue is full, any new integration events are not stored. When the number of integration events in the queue is again below the maximum, new events will once again be added to the queue.

On the Integration Event Settings page, you can delete integration events from a queue. You can also configure Oracle CRM On Demand to send a warning email to a specified address when the queue is full, or when the number of integration events in the queue exceeds a number that you specify.

You can disable integration event queues, including the default queue, but you cannot delete a queue.

External applications access the integration event queues by using the Integration Events Web service, which has two methods:

  • GetEvents. Retrieves integration events from a queue.
  • DeleteEvents. Deletes integration events from a queue.

For information about downloading the Web Services Description Language (WSDL) file for the Integration Events Web service, see Web Services Integration. For more information about the Integration Events Web service, see Oracle Web Services On Demand Guide.

Sometimes an integration event queue can contain events that a client application cannot process. For information about how to handle such bad events, see Oracle Web Services On Demand Guide.


Published 1/9/2017 Copyright © 2005, 2017, Oracle. All rights reserved. Legal Notices.