Bookshelf Home | Contents | Index | PDF |
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 ObjectsThis 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
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. 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: Deploy the integration objects and the dispatcher map created by the wizard into your Siebel Runtime Repository. Make sure you migrate your new integration objects to the same database used by your client. You also must deploy Siebel Runtime Repository to the correct servers in use. |
Oracle Customer Hub (UCM) Master Data Management Reference | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |