Bookshelf v7.5: Viewing the Dispatcher Map

Siebel Financial Services Connector for ACORD P&C and Surety Guide > Configuration Roadmap > Creating Integration Objects in Siebel Tools >

Viewing the Dispatcher Map

When it creates the paired external and internal integration objects, the FINS ACORD Wizard creates a pair of new or updated entries in the dispatcher map.

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

ACORDDispMap_<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 ACORDDispMap.

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

The table below shows the rule sets created by the wizard for the Add Policy scenario.


Name	Value
ACORD/InsuranceSvcRq/PersAutoPolicyAddRq	ACORD/InsuranceSvcRq/PersAutoPolicyAddRq;PersAutoPolicyAddRq_ERqIRqMapIn;PersAutoPolicyAddRq_IRsERsMapOut;PersAutoPolicyAddRq;AcordPolicy;SAUpsert
ACORD/InsuranceSvcRs/PersAutoPolicyAddRs	ACORD/InsuranceSvcRs/PersAutoPolicyAddRs;PersAutoPolicyAddRs_ERsIRsMapIn;PersAutoPolicyAddRs_IRqERqMapOut;PersAutoPolicyAddRs;AcordPolicy;SAUpsert

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 ACORD/InsuranceSvcRq/PersAutoPolicyAddRq is the path the dispatcher uses to locate the message received, and if it finds the match then it uses the information in the value column, ACORD/InsuranceSvcRq/PersAutoPolicyAddRq;PersAutoPolicyAddRq_ERqIRqMapIn;PersAutoPolicyAddRq_IRsERsMapOut;PersAutoPolicyAddRq;AcordPolicy;SAUpsert, to determine the action it needs to take. Following is a description of the meaning of each of the parts of the information in the value column.

Each value is made up of six tokens that are separated by semicolons (;), and each token represents specific information.

The first token is the location to insert the remaining five tokens at runtime. For example, ACORD/InsuranceSvcRq/PersAutoPolicyAddRq.

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

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

The fourth token is the external request integration object. For example, PersAutoPolicyAddRq.

The fifth token is the internal response integration object. For example, AcordPolicy.

The sixth token is the operation corresponding to the <PersAutoPolicyAddRq> message, for example SAUpsert. This token will be used as the key to operation for FINS ACORD 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.