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

Scenarios for Data that is Transformed

When performing data transformation within the Siebel environment, you use two types of integration objects:

• An Internal integration object mirrors the data structure of a Siebel business object and contains a subset of business components and fields.
• An external integration object mirrors the data structure of an external system.

The EAI Siebel Adapter performs the same function whether the data transformation is performed inside or outside the Siebel environment. The XML Converter and the transports also perform the same function, whether they are used within the Siebel environment or outside the Siebel environment.

The only difference is that, if used outside the Siebel environment, then both of these business services perform an operation on an external integration object instance, as opposed to performing an operation on an internal integration object instance when used within the Siebel environment.

You use business services to define data mapping and data transformation rules. Siebel EAI provides many mappings and transformation rules in the prebuilt external adapters. You define internal and external integration objects in Siebel Tools.

NOTE:  Business services provide a flexible scripting environment to map data from the Siebel data structure to an external data structure. Within a business service, a Siebel application provides a set of methods that allow you to perform an operation on an instance for an integration object.

Pass Data to an External Application

In this scenario, an order is created in a Siebel Business Application, and is then passed to an external application. The external application returns the order status and an order number. Work you can perform in this situation can include:

1. Identify the Siebel business object to update. For that business object, identify the components and fields to update.
2. Identify the object in the external system with which you must integrate.
3. Determine the mapping between the Siebel business object and the external object.
4. In Siebel Tools, use the Integration Object Wizard to create a new internal integration object. Choose only the components and fields that must be updated.
5. In Siebel Tools, create a new external integration object.
6. In either Siebel Tools or in the Siebel client, use business services to define the data mapping and data transformation.
7. In Siebel Tools, define an integration workflow process and add exception handling to it.
8. Test the workflow process using the process simulator.
9. Add a mechanism to call the workflow process from Oracle's Siebel applications.

Table 9 details the requirements for data transformation integration.