Bookshelf v7.5: IAA Dispatcher Map

Siebel Financial Services Connector for IAA-XML Guide > Configuration Roadmap > Creating Integration Objects in Siebel Tools >

IAA Dispatcher Map

The IAA dispatcher map is an integration object that contains the rule sets used by the FINS IAA-XML Dispatcher. The default IAA dispatcher map is IAADispMap. If you have the correct project locked, the wizard updates the user properties of the default IAA dispatcher map. Otherwise, the wizard creates a new IAA dispatcher map with the following name format and updates its user properties.:

IAADispMap_<currently locked project name>

To view the Dispatcher Map user properties

From Siebel Tools, choose Object Explorer>Integration Object.

Query for the dispatcher map name. For example. IAADispMap.

Navigate to the user properties of the dispatcher map to see its user properties

The first two rows in the User Properties applet are the rule sets created by the wizard for AddParty scenario.

The name of the user property represents the rule the dispatcher tries to match and the value represents the value the dispatcher needs to insert. For example, the name, Message/COMMAND/AddPartyRequest/Person, is the path the dispatcher try to locate in the message received and if it finds the match then it uses the information in the value column, Message/COMMAND/AddPartyRequest;AddPartyRequest_ERqIRqMapIn;AddPartyRequest_IRsERsMapOut;AddPartyReq;IAAPartyContact;IXMLOperation_ADD, to determine the values it needs to insert as follow:

Each value is made up of six tokens that are separated by ";" and each token represents a specific information.

First token is the location to insert the remaining 5 tokens at runtime. For example, Message/COMMAND/AddPartyRequest.

Second token is the name of data transformation map for mapping external request integration object indicated by ERq to internal request integration object indicated by IRq. For example, AddPartyRequest_ERqIRqMapIn.

Third token is the name of data transformation map for mapping internal response integration object IRs to external response integration object ERs. For example, AddPartyRequest_IRsERsMapOut.

Forth token is the external request integration object. For example, AddPartyReq.

Fifth token is the internal response integration object. For example, IAAPartyContact.

Sixth token is the operation corresponding to <AddPartyRequest> command. For example, IXMLOperation_ADD Which is configured in FINS IAA Wizard user properties. This token will be used as key to operation for FINS IAA-XML Transaction Manager.

The data transformation map names must be used when configuring the transformation maps. For details, see Configuring the Data Transformation Maps. The map names have to be unique and you need to modify the dispatcher map entries to reflect the new name. The same principle applies to all the tokens.

NOTE: Compile all the integration objects and the dispatcher map created by the wizard into your .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 clients.