Oracle Customer Hub (UCM) Master Data Management Reference > Configuring Source Data History and Cross-Reference Functionality > Configuring Source Data History and Cross-Reference Functionality for Oracle Customer Hub >

About System Publish and Subscribe Modes

Oracle Master Data Management Applications use one of three modes to publish or update data: real-time mode, batch mode, and event mode. For information on configuring these modes, see Configuring System Publish and Subscribe for Oracle Master Data Management Applications.

Real-Time Mode

When configured, the real-time mode of the publish and subscribe functionality runs when another process or business service explicitly calls the UCM Publish/Subscribe Service business service. The calling process sends this business service a record to publish. The following workflow processes provide examples of real-time publishing: the UCM Customer Profile Integration Process, UCM Account Batch Data Management Workflow, UCM Contact Batch Data Management Workflow, UCM (Organization, Person, Financial Asset, or Group) Customer Profile Integration SOAP Process, and UCM Batch Process.

Batch Mode

During a batch mode operation, the UCMBatchPubSub server component calls the UCM Daily Publish workflow process. This workflow process calls the UCM Publish/Subscribe Service business service, and this business service checks if the business service is being run on a server component. If the service is being run on a server component, it retrieves the server parameters for UCM Batch Object Type (alias UCMBatchObjectType), UCM Batch Size (alias UCMBatchSize), and UCM Sleep Time (alias UCMSleepTime). Then the business service iteratively runs through the following steps until the server component stops:

1. Creates an internal search specification for the business component. This step is based on the following format:

   '(([Last Update - SDQ] <= 'mm/dd/yyyy hh:mm:ss') AND ([Last Update - SDQ] > 'mm/dd/yyyy hh:mm:ss'))'

   where:

   • mm/dd/yyyy hh:mm:ss arguments indicates the current time and the current time less the UCMSleepTime parameter value (default value of 60 seconds).
   • [Last Update - SDQ] indicates the business component field name of the integration component field name specified by the SearchFieldName user property configured in the UCMBatchObjectType integration object. By default, the IO CIFContact has the IC property SearchFieldName = Last Update, which maps to the BC Contact's field Last Update - SDQ component field value [Last Update - SDQ].
2. The search specification is passed to the EAI Siebel Adapter, and it uses the method QueryPage with the SearchSpec against the UCMBatchObjectType to find the records that have changed or are new. The UCMBatchSize parameter value is used to determine how many records are returned in the query page's result set.
3. For each record returned in the query page's result set, it is published according to the registered systems that meet the following conditions:
   • They have the object defined in the Publish/Subscribe view.
   • They have a publish frequency set to Batch.
   • They have not expired.

Event Mode

Any system configured for real-time mode or batch mode can also subscribe to event mode if that system requires the message to be published when an event occurs. Events refer to Oracle Customer Hub (UCM) operations, such as Merge or Unmerge, or Link and Update, or Create New, and so on. These events are preconfigured by default, but are not published. However, Oracle Customer Hub (UCM) can be customized to prepare the outbound message (resulting from such operations) by using Oracle Customer Hub (UCM) Publish/Subscribe Service-EventPublishMethod.

NOTE:  You must customize the UCM application before you can publish Unmerge events. This is not part of standard UCM functionality and is not within the scope of Oracle Support Services. You must contact Oracle Consulting Services for help in implementing this customization.