Oracle Customer Hub (UCM) Master Data Management Reference > Configuring the MDM Foundation and Workflows > Configuring Siebel Master Data Integration Objects >

Modifying the Map Property of Siebel Master Data Application Integration Objects


This topic describes the task of modifying the map property of Siebel Master Data Application dispatcher map integration objects. For background information on Siebel Master Data Application integration objects, see About Siebel Master Data Application Integration Objects.

To modify the dispatcher map user properties

  1. From Siebel Tools, choose Object Explorer, then Integration Object.
  2. Query for the dispatcher map name, for example, CIFDispMap.
  3. Navigate to the user properties of the dispatcher map to see its user properties, and modify the properties as appropriate.

    The name of the user property represents the rule the dispatcher tries to match, for example:

    CRMML/PartyPackage/DeleteAccount

The dispatcher tries to find the user property name in the message received. If it finds the match, it then uses the information in the value column to determine the values it requires. The value for the previous example name follows:

CRMML/PartyPackage/DeleteAccount;a;b;CIFAccountDelete;CIFAccountDeleteRs;IXMLOperation_DELETE

Each value is made up of six tokens that are separated by a semicolon (;), and each token represents specific information as outlined in Table 119.

Table 119. Dispatcher Map Value User Property
Token
Description
Example

1st

Indicates the location to insert the remaining five tokens at run time.

NOTE:  The message must start with the CRMML/ PartyPackage because the UCM Dispatcher uses it to inspect the incoming XML data; that is, the first token is an XML Path Language search expression.

CRMML/PartyPackage/DeleteAccount

2nd

System reserved token

a

3rd

System reserved token

b

4th

The request integration object

CIFAccountDelete

5th

The response integration object

CIFAccountDeleteRs

6th

The operation corresponding to the DeleteContact business process. This is configured in the user property of the UCM Transaction Manager.

 

IXMLOperation_DELETE

The name column of the map user property must be unique and represents the business process name that you want to support. You must modify the dispatcher map entries to reflect the new business process name. The same principle applies to all the tokens.

NOTE:  Compile the integration objects and the dispatcher map created by the wizard into your Siebel Repository file (.srf). Make sure you migrate your new integration objects to the same database used by your client. You also must copy your newly compiled Siebel Repository file to the correct object directory that your servers use.

Oracle Customer Hub (UCM) Master Data Management Reference Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.