Bookshelf Home | Contents | Index | PDF |
Deployment Planning Guide > Siebel Infrastructure Planning > Defining Data Flows and Integration RequirementsThis 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. This topic is a step in Process of Infrastructure Planning. To identify data flows and transaction volumes
Figure 3 shows an example of a model of a data flow. The example shows a call center running Siebel eCommunications. The company maintains an ERP database and a phone number database separately from the Siebel database, which contains customer information. Siebel eCommunications sends XML messages containing customer orders to the order fulfillment application, and receives order fulfillment status through an inbound HTTP adaptor. Siebel eCommunications also queries the Phone Number Management System for available phone numbers in real-time. The Phone Number Database then receives assigned phone numbers from the Siebel Database using Siebel EIM. |
Deployment Planning Guide |