Bookshelf Home | Contents | Index | PDF |
Siebel Deployment Planning Guide > Siebel Infrastructure Planning > Defining Data Flows and Integration RequirementsThis topic is a step in Process of Infrastructure Planning. This infrastructure planning step identifies how data will flow to and from the Siebel deployment. An example of a key data flow would be customer contact updates that originate at several call centers and flow to the master customer contact database at a headquarters location. This step identifies where the master copy of data records will reside. It also identifies the data interchange requirements for applications. To identify data flows and transaction volumes
Figure 4 shows an example of a model of a data flow. The example shows a call center running the Siebel Communications application. The company maintains an ERP database and a phone number database separately from the Siebel Database, which contains customer information. Siebel Communications sends XML messages containing customer orders to the order fulfillment application, and receives order fulfillment status through an inbound HTTP adapter. Siebel Communications also queries the phone number database for available phone numbers in real time. The phone number database then receives assigned phone numbers from the Siebel Database using Siebel EIM. |
Siebel Deployment Planning Guide | Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |