Overview: Siebel Enterprise Application Integration > Scenarios for Using Siebel EAI > Overview of Architecture for Siebel EAI >

Scenarios for Data that is Accessed, Exported or Replicated

This topic describes scenarios where a business process requires access to specific data in order to accomplish a process goal.

Export Customer Data to an External System

In this scenario, a change to contact information in the Siebel Database must be sent to an external mainframe system through IBM WebSphere MQ. Work you can perform in this situation can include:

1. Define and configure the message that must be exchanged. In the Siebel Database, the Contact business object contains several business components, and each business component includes several fields. It is not desirable to send all of this information to the external system. You must choose only a subset of this information.
2. Use Siebel Tools to define the integration object for the contact message you must exchange. Siebel Tools provides an Integration Object Builder that assists you to define an integration object.
3. Define how the message is handled. The contact message must be sent to the external system by using EAI MQSeries Server Transport. You can use the Siebel Workflow Process Manager to model the message flow for this integration, and to send the message. The flow for an integration message is a sequence of business services that are connected.

Table 3 describes the requirements to export customer data from a Siebel application to an external system.

Access a Company Catalog through Replication

In this scenario, salespeople must be provided access to a product catalog while they are on the road. Therefore, you import the catalog information into a Siebel application so that Siebel Remote can handle the mobile replication. Siebel Enterprise Integration Manager (EIM) imports this information.

Table 4 describes the requirements to provide access to a company catalog through replication.

Access Customer History Information Without Replication

In this scenario, a company is in the financial industry. Because a financial service institution is typically cautious when handling customer data, the company must provide access to data while replicating as few times as possible, if at all. However, the customer service agent must access the transaction history for your customer in order to provide the best service. This information is typically stored in Customer Information Files (CIF) on a mainframe computer.

The Siebel Virtual Business Component (VBC) can handle this business requirement. A VBC abstracts external data and presents it to a Siebel application as part of the Siebel data model. Siebel business logic and user interface components process a VBC in the same way that they process a standard business component.

Table 5 describes the requirements to integrate customer transaction history information into a Siebel application.

Access to Java Data

In this scenario, a customer service Web application is written with JavaServer Pages (JSP). To pass this data into a Siebel application so that the account record is updated, you call Siebel Java Data Beans in the Siebel Object Interface. This way, a customer service representative can use the information from the Web application JSP while serving the customer.

Table 6 describes the requirements to access Java data.