Bookshelf v8.0: Integration Objects

Integration objects are logical representations of Siebel business objects or of external application data, such as SAP Business Application Programming Interfaces (BAPIs) or externally-defined XML documents. An integration object is metadata stored in the Siebel repository. One integration object can be mapped to another integration object. Instances of integration objects are used in integration processes for data exchange.

NOTE: For more information on integration objects, see Integration Platform Technologies: Siebel Enterprise Application Integration.

Integration objects are made up of three distinct data sections: the canonical, the external, and the XML, as shown in Figure 3.

The integration object schema in the Siebel repository is composed of the three data sections shown in Table 4.

Table 4. Integration Object Data Type
Name	Purpose
Canonical section	Stores information about an object in a common representation. The names used for objects, components, and fields are the names that the designer wishes to be visible in Siebel systems. The data types are the Siebel business component field types that are used by the Object Manager.
External section	Stores information about how the object, component, or field is represented in the external system. For integration objects based on business objects, this may include the business object names, component names, and field names and data types. For integration objects based on a SAP IDOC, this may include the names used within SAP as well as information needed by the IDOC adapter to parse and generate IDOCs, such as the field offsets.
XML section	Stores the mapping between an integration object definition and its XML representation. This allows any integration object to be represented as XML.