Siebel Application Integration for Oracle Fusion Middleware Guide > Working with Web Services Using SAI for Oracle Fusion Middleware > About Working with Web Services Using SAI for Oracle Fusion Middleware >

About Base Integration Objects

Traditionally, Siebel EAI integrations specify an integration object as the input, the output, or both. With SAI for Oracle Fusion Middleware, the core requirement for an integration object is extended to accommodate a logical one-to-one relationship between a business object and an integration object. Each integration object in SAI for Oracle Fusion Middleware provides a representation of an underlying business object and its relationships, hiding the Siebel-specific ID fields and displaying the constituent fields of the underlying key to maintain the relationship. Such integration objects are called base integration objects.

There is a one-to-one mapping between business object and integration object; for each business object, there is one base integration object. XSDs are generated from the base integration object. You enforce the one-to-one mapping with a column in the business object repository that contains the base integration object name.

NOTE:  Base integration objects are seed integration objects that are provided and maintained by Oracle.

There is one base integration object for each business object that contains all the fields that are exposed in that business object. These base integration objects are the primary integration tool, and the required subset of fields demanded by the business requirements are specified by the use of XSD (XML Schema Definition) files. At run time, these XSD files are correlated back to the base integration object and a dynamic integration object is created that the underlying Siebel infrastructure can use transparently. These dynamic integration object definitions are then cached in order to avoid any performance overhead.

Alternatively, you can continue to use your existing integration object definitions by explicitly selecting to Query Integration Objects in the SAI for Oracle Fusion Middleware deployment wizard for inbound Web services in Oracle JDeveloper, and then entering a search term. For information about using this feature, see Creating Inbound Web Services Based on Siebel Business Services.