Bookshelf Home | Contents | Index | Search | PDF |
Siebel Universal Customer Master Applications Reference for Industry Applications > Siebel UCM Applications Administration > Integration Objects >
CIF Dispatcher Map Integration Objects
The CIF dispatcher map is an integration object that contains the rule sets used by the FINS CIF Dispatcher. The default CIF dispatcher map is CIFDispMap. Siebel UCM 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
Deactivate business processes that you are not supporting in a production environment for performance reasons. 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
- From Siebel Tools, choose Object Explorer>Integration Object. For more information on using Siebel Tools, see Siebel Tools Reference.
- Query for the dispatcher map name. For example, CIFDispMap.
- 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;IXMLOperat ion_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:
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.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Universal Customer Master Applications Reference for Industry Applications Published: 18 April 2003 |