Bookshelf v7.5: Configuring the Data Transformation Maps

Siebel Financial Services Connector for IAA-XML Guide > Configuration Roadmap >

Configuring the Data Transformation Maps

One of the step in configuring the integration objects for your integration process is to map the components and fields in your internal integration object to the message elements in the external integration object. These maps will be used by the FINS IAA-XML Data Transformation Engine to move the data from one integration object to another. For each integration process you need to configure two maps for inbound and two maps for outbound process. These map names are in the user properties entry of the dispatcher map integration object. The map names are created by the FINS IAA Wizard when it creates the integration objects.

Following four maps are the maps we need to configure for our illustration:

AddPartyRequest_ERqIRqMapIn (server receiving a request)

AddPartyRequest_IRsERsMapOut (server sending out response)

AddPartyResponse_IRqERqMapOut (client sending out a request)

AddPartyResponse_ERsIRsMapIn (client receiving response)

If you wish, you can change the map name in the user properties of the dispatcher map after configuring the data transformation map.

Following procedure walks you through configuring the AddPartyRequest_ERqIRqMapIn data transformation map which is used for receiving an inbound request.

To configure the DTE map

Start Siebel Client.

From the Application-level menu, choose View>Site Map>Integration Administration Screen > Data Map Editor.

The Integration Object Map applet appears.

Create a new record in this applet.

Name. This name must be the same as the data transformation map name created by the wizard and stored in the dispatcher map list. For example, AddPartyRequest_ERqIRqMapIn where ERq indicates external request integration object and IRq indicates internal integration object.

Select the source integration object and the target integration objects for the mapping. Keep the following definitions in mind:

Source Object. For an outbound request or inbound response message, the source object is the internal integration object. For an outbound response or inbound request message, the source object is the external integration object. For example, AddPartyReq is the source object for inbound request.

Target Object. For an outbound request or inbound response message, the target object is the external integration object. For an outbound response or inbound request message, the target object is the internal integration object. Fro example, IAAPartyContact is the target object for inbound request.

Map the source components and the target components.

Map fields to fields.

NOTE: For details on creating data maps, see Business Processes and Rules: Siebel eBusiness Application Integration Volume IV.