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

Inbound Data Flow


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

Inbound business data flows start with a receiver server component such as the MQSeries, HTTP, or MSQM.

The receiver runs in the background continuously, waiting for data from external ACORD-based applications. When the receiver receives an ACORD message, it invokes the workflow process configured to handle and process the data. The workflow typically dictates the whole Siebel Connector for ACORD XML business logic.

  1. The raw XML text string is passed through the XML Hierarchy Converter to be converted into an XML integration object instance.
  2. The FINS ACORD XML Dispatcher then takes in the XML instance, parses it and identifies the messages received according to the rules set forth in the dispatcher map. The FINS ACORD XML 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 ACORD Wizard.

  3. The FINS ACORD XML Converter then takes the XML instance, and processes individual sections of the instance while converting each sub-tree into external integration object instances.
  4. The FINS ACORD XML DTE transforms the external integration object instances into internal integration object instances.
  5. The internal integration object instances are passed to the FINS ACORD XML Transaction Manager which performs the operation specified in the instance (such as insert/update/delete) through the invocation of other business services configured in its user properties.
Siebel Financial Services Connector for ACORD P&C and Surety Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.