Siebel Financial Services Enterprise Application Integration Guide > Overview of Siebel Financial Services Enterprise Application Integration > Details of Siebel Financial Services EAI >

Declarative Integration

Siebel integration objects allow you to represent integration metadata for Siebel business objects, XML, SAP IDOCs, and SAP BAPIs as common structures that the EAI infrastructure can understand. Because these integration objects adhere to a set of structural conventions, they can be traversed and transformed programmatically, using Oracle's Siebel eScript objects, methods, and functions, or transformed declaratively using Siebel Data Mapper. There are three types of integration object used within Siebel Financial Services EAI, Envelope Integration Object, Internal Integration Object, and External Integration Object.

Envelope Integration Object. This object presents the hierarchy of the envelope and header section of any industry XML standards.

Internal Integration Object. This object defines the Siebel data hierarchy for an external application. The internal integration object has the hierarchy of Siebel business object and business components as well as the fields. It maps to the objects in the Siebel Financial Services application and is created using Integration Object Builder in Siebel Tools. The internal integration object is required to facilitate the Industry XML Transaction Manager to package the gathered data. This service gathers the data needed for a particular message and packages it into the hierarchy defined in the internal integration object.

External Integration Object. This object defines the XML hierarchy. The external integration object maps the internal integration object components and fields to external application aggregations and fields. The Data Transformation Engine and Converter use this object to construct the external format structures.