|Bookshelf Home | Contents | Index | PDF|
The following scenarios concern an IT developer named Chris Conway, who works for a computing company, PCS Computing. One of his responsibilities is creating and maintaining the data mappings between Siebel and the other applications in use at PCS. He is assigned to create mapping between Siebel applications and the external application they need to integrate with.
After weighing various options, Chris decides to use the Siebel Data Mapper instead of scripts to perform the data mapping. He creates the internal integration object using the Siebel Integration Object Wizard in Siebel Tools. He also creates an external integration object using the external application's DTD.
When Chris is ready to map the two integration objects, he navigates to the Data Mapper and creates a new entry by supplying the name of the map and associating the internal integration object with the external integration object, as explained in Creating New Data Maps. He then uses the Map Editor form to create object, component, and field maps, as explained in Creating Integration Component Maps.
When he finishes creating the map, Chris navigates to the Siebel Workflow Process Designer form to define the integration flow. For one of the workflow steps, he defines an invocation of the Siebel Data Mapper. He supplies the appropriate parameters, including the name of the map, and saves his work.
|Business Processes and Rules: Siebel eBusiness Application Integration Volume IV|