Siebel applications define a data abstraction layer that removes dependencies on the underlying databases. To access a database, Siebel applications must interact with the Siebel Object Manager. The Object Manager presents database table data in the form of business component records that represent database structures.

A business component typically represents a table in a database. Business components contain records and fields similar to those in relational database tables. For example, the Contact business object might contain the business components Customer Contact, Supplier Contact, and so on. The Customer Contact business component might contain such fields as Name and Last Contact Date.

A business object is a group of related business components. Each business component can have relationships with other business components. A relationship can be a parent/child relationship that has a one-to-many relationship (a Multi-Valued Link field) or a many-to-many relationship (an Association). The Siebel Adapter supports both kinds of relationships.

Siebel applications store the definitions of their business objects and business components in repositories. Different repositories can define different sets of (and properties for) business objects and business components. A Siebel application can access only the repositories associated with its Object Manager. The repository that defines a business object and business component provides the object's and component's repository context.

With the Siebel Adapter, you can configure adapter services that Query, Insert, Update, and Delete business component records. In addition, you can configure services that attach files to business component records, and services that invoke Siebel business services or Siebel business component methods on your Siebel Server. For details, see webMethods-To-Siebel Communication.

For information about Siebel business objects and business components, see the Tools Guides on the Siebel Bookshelf.