Siebel Financial Services Connector for VCML Guide > Overview > Architectural Overview >

Inbound Data Flow

As shown in Figure 2, the following occurs during an inbound data flow:

  1. Inbound business data flows start with a receiver server component such as the MQSeries, HTTP, or MSMQ.
  2. The receiver runs in the background continuously, waiting for data from external VCML-based applications. When the receiver receives a VCML message, it invokes the workflow process configured to handle and process the data. This workflow manages the business logic for the connector.
  3. The raw XML text string is passed through the XML Hierarchy Converter business service to be converted into an XML integration object instance.
  4. The FINS VCML XML Dispatcher business service takes in the XML instance, parses it, and identifies the messages received according to the rule sets in the VCML Dispatcher Map. The VCML dispatcher identifies the envelope, header, and body sections. The dispatcher then associates the appropriate internal and external integration objects to the message so that it can be processed by the converter. The Dispatcher map is an integration object created by the FINS VCML Wizard Service.
  5. The FINS VCML XML Converter business service takes the XML instance, and processes individual sections of the instance while converting each subtree into external integration object instances.
  6. The FINS VCML XML DTE business service transforms the external integration object instances into internal integration object instances.
  7. The internal integration object instances are passed to the FINS VCML XML Transaction Manager business service, which performs the operation specified in the instance through the invocation of other business services configured in its user properties.

 Siebel Financial Services Connector for VCML Guide 
 Published: 18 April 2003