Overview: Siebel eBusiness Application Integration Volume l > Siebel eAI Architecture >

About Integration Requirements and Siebel eAI

Table 3 maps real-world data and application integration requirements with their corresponding Siebel eAI features.

Table 3.  Integration Requirements and How They Relate to Siebel eAI Features
Integration Requirements
Siebel eAI Features or Components

Metadata Definition

XML Metadata

External application metadata (from SAP applications, Oracle applications, and so on)

  • Integration objects based on Siebel business objects
  • Integration objects based on external metadata
  • Integration Object Wizard

In any integration project, you need a way to supply data about data, called metadata. Siebel applications provide XML as the common format for representing external application data. In addition, Siebel applications provide an object type in Siebel Tools called the Integration Object, as well as an Integration Object Wizard, which automates the task of creating integration objects.

Data Transformation

Declarative data transformation mapping

High-performance transformation engine

  • Siebel Data Mapper

Siebel eAI allows you to define what type of data to be exchanged, and allows you to export an XSD or a DTD for a Siebel integration object.

Business Process Coordination

  • Siebel Business Process Designer
  • Workflow Process Manager

See About Business Process Coordination Using Workflows.

Transport Mechanisms (for interfacing with other technologies)

Transport Adapters:

  • IBM MQSeries
  • Microsoft MSMQ
  • HTTP
  • Java Message Service

See About Transport Mechanisms.

High Volume Data Exchange

  • EIM (Enterprise Integration Manager)

See About High-Volume Data Exchange.

Standards-based Integration Mechanisms

  • XML as a format for data exchange
  • COM, CORBA and Java-based programmatic interfaces
  • HTTP as a transport protocol


Overview: Siebel eBusiness Application Integration Volume l