Siebel Master Data Applications Reference for Industry Applications > Siebel Master Data Applications Administration > About Siebel Master Data Application Integration Objects >

UCM Dispatcher Map Integration Objects


The UCM dispatcher map is an integration object that contains the rule sets used by the UCM Dispatcher. The default UCM dispatcher map is CIFDispMap. Siebel Master Data Applications use the following predefined dispatcher maps:

  • CIFDispMap—Default dispatcher map used
  • CIFDispMapAccount—Dispatcher map containing only CIFAccount messages
  • CIFDispMapContact—Dispatcher map containing only CIFContact messages
  • CIFDispMapHHMisc—Dispatcher map containing the CIFHousehold, CIFFINCORP Account, and CIFPersonal Address messages
  • CIFDispMapPerf—Dispatcher map containing a subset of CIFContact messages for improving performance

For performance reasons in a production environment, deactivate business processes that you are not supporting. You can do so by deactivating the user property name corresponding to the business processes that are not applicable.

To view the dispatcher map user properties

  1. From Siebel Tools, choose Object Explorer>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.

The name of the user property represents the rule the dispatcher tries to match. An example name follows:

CRMML/CIFPartyPackage/DeleteAccount

The dispatcher tries to locate 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 needs to insert. The value for the previous example name follows:

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

Each value is made up of six tokens that are separated by a semi-colon (;), and each token represents a specific information as outlined in the following table:

Table 25.  Dispatcher Map Value User Property
Token
Description
Example

1st

The location to insert the remaining five tokens at runtime

CRMML/CIFPartyPackage/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 <DeleteContact> business process, which is configured in the user property of the UCM Transaction Manager as key to operation

IXMLOperation_DELETE

The name column of the map user property must be unique and represents the business process name you want to support. You need to 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 need to copy your newly compiled .srf to the correct object directory of the same server used by your servers.

Siebel Master Data Applications Reference for Industry Applications