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

Outbound Data Flow

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

  1. When the workflow is initiated, the FINS VCML XML Transaction Manager business service extracts data from the Siebel Database. It takes as input the current Row Id of the primary business component in the current business object and an integration object name. The FINS VCML XML Transaction Manager business service calls the underlying EAI Siebel Adapter to instantiate the integration object based on the Siebel business components.
  2. The FINS VCML XML Transaction Manager business service returns all instances retrieved as Siebel property sets. A property set is a representation of data in memory in the Siebel internal format. It is used widely by the business services that constitute the connector components.
  3. The internal integration object instances are then passed to the FINS VCML DTE business service to transform into external integration object instances.
  4. The FINS VCML XML Converter business service converts all external integration object instances into proper XML integration object instances. It adds the envelope, header, and other sections to the newly converted instance.
  5. Lastly, the XML Hierarchy Converter business service converts the XML integration object instance from a property set format into a text format.
  6. The message is then sent to external systems using any transport mechanism supported by Siebel eAI.

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