Siebel Financial Services Connector for ACORD P&C and Surety Guide > Overview > Siebel Connector for ACORD XML Architectural Overview >

Outbound Data Flow

Figure 2 illustrates an outbound data flow as well as an inbound data flow. During an outbound data flow:

  1. When the workflow is initiated, the FINS ACORD XML Transaction Manager extracts data from the Siebel database

    The transaction manager takes as input all the ROW_IDs of the objects. This data is then used to instantiate the internal integration objects based on the Siebel business objects.

    The transaction manager returns all the 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.

  2. The internal integration object instances are then passed to the FINS ACORD XML Data Transformation Engine (DTE) to transform the internal integration object instances into external integration object instances.

    The DTE also adds all necessary ACORD-specific command layer attributes into the instances transformed.

  3. The FINS ACORD XML Converter converts all external integration object instances into proper XML integration object instances. It also adds the envelope, header, and other sections to the newly converted instance.
  4. Lastly, the XML Hierarchy Converter converts the XML integration object instance from a property set format into a text format.
  5. The message is then sent to external systems using any transport mechanism supported by Siebel eAI.

NOTE:  Figure 2 depicts the connector process using the MQ Series transport adapter. However, the transport mechanism can be HTTP, MSMQ, or any other transport mechanisms supported by Siebel eAI.

Siebel Financial Services Connector for ACORD P&C and Surety Guide