Siebel Financial Services Connector for IAA-XML Guide > Overview > Architectural Overview >

Inbound Data Flow

As illustrated in Figure 2, an inbound business data flow starts with a Receiver Server Component such as the MQSeries, HTTP, or MSMQ Receiver. The Receiver runs in the background continuously waiting for message to arrive from external IAA-XML based applications. Upon receiving an IAA-XML message, it then invokes the workflow process configured to handle and process the data further. The workflow dictates the business logic behind the Siebel Connector for IAA-XML as follow:

  1. The raw XML text string is passed through XML Hierarchy Converter to be converted into an XML integration object instance.
  2. The FINS IAA-XML Dispatcher then traverses the XML instance and identifies the messages received according to the rule sets of the IAA Dispatcher Map and then identifies the envelope, header and body sections among the hierarchy nodes and sends it to the FINS IAA-XML Converter.

    3. NOTE:  The Dispatcher Map is created by the FINS IAA Wizard. For details, see FINS IAA Wizard

  3. The FINS IAA-XML Converter then takes the XML instance, and process individual sections of the instance while converting each sub-tree into external integration object instances before sending it to the FINS IAA-XML DTE.
  4. The FINS IAA-XML DTE transforms the external integration object instances into internal integration object instances and passes it to the FINS IAA-XML Transaction Manager,
  5. The FINS IAA-XML Transaction Manger then performs operation specified in the instance by invoking the services configured in its user properties.

 Siebel Financial Services Connector for IAA-XML Guide  
 Published: 18 April 2003