Overview: Siebel eBusiness Application Integration Volume I > Custom Business Scenarios > Data Access and Replication >

Contact Information

Consider a scenario in which you want to send changes to contact information in the Siebel Database to an external mainframe system through the EAI MQSeries transport mechanism. Your first step is to define and configure the message that needs to be exchanged. In the Siebel Database, the Contact business object contains several business components, and each business component has several fields. You do not want to send all of this information to the external system. You want to choose only a subset of this information.

Use Siebel Tools to define the integration object for the contact message you want to exchange. Siebel Tools provides an Integration Object Builder that walks you through the process of defining your integration object. Once you have defined the message, define what to do with this message. The contact message needs to be sent to the external system using EAI MQSeries AMI Transport. You can use the Siebel Workflow Process Manager to model this integration message flow and to send the message. An integration message flow is a sequence of business services that are connected. Table 3 details the requirements for exporting contact information from Siebel applications to a mainframe system.

Table 3. Customer Data Export Integration Requirements
Business Requirement
Technological Requirement
Siebel's eAI Solution
To access the Siebel Database
Business service to query the integration object
EAI Siebel Adapter
To convert an internal Siebel message format into XML
Siebel message-to-XML conversion technology
EAI XML Converter
To place the converted XML document in the destination queue
IBM MQSeries compatibility
EAI MQSeries AMI Transport


 Overview: Siebel eBusiness Application Integration Volume I 
 Published: 18 April 2003