Siebel Remote and Replication Manager Administration Guide > Architecture of Siebel Remote > How Siebel Remote Manages the Amount of Data It Synchronizes >

How Siebel Remote Filters the Data It Synchronizes

Siebel Remote uses routing rules and routing models to filter the data that it synchronizes. For example, the data that a field sales representative requires might be different from the data that a field service representative requires. The sales representative might require detailed information about opportunities while the service representative requires detailed information about service requests. Routing rules provide the logic for the Database Extract and the Transaction Router server components. These rules reflect the data visibility and data access policies that exist in the Siebel application. For more information, see the following items:

• Controlling the Data That Siebel Remote Routes to Clients
• Modifications to Dock Objects
• Configuring Siebel Business Applications

Dock Objects

A dock object is a logical grouping of tables that include schema structures that Siebel Remote uses to synchronize data between a server database and a local database. A routing rule belongs to a dock object.

Table 6 describes the types of dock objects that Siebel Remote uses.

Routing Rules

A routing rule is an SQL (Structured Query Language) statement that the Transaction Router and the Database Extract server components use to determine the records that Siebel Remote must route to each user. They provide the following benefits:

• Protects data integrity
• Allows the user to view the same data that the user can view when the user connects to the Siebel Server
• Facilitates access control
• Maintains application logic and functionality

A transaction in Siebel CRM is associated with a set of routing rules that might cause Siebel Remote to route the transaction to a user. A Siebel release can include more than a thousand active routing rules. For more information, see Modifying a Routing Model.

Routing Models

A routing model is a collection of routing rules. It identifies the data that Siebel Remote extracts to the user and the subsequent transactions that it routes to this user. You can associate a user with any routing model. Transaction routing behaves differently for each user depending on the routing model that you associate with the user. One of the following routing models is adequate for most users:

• MOBILE CLIENT - STANDARD
• MOBILE CLIENT - EXTRACT ONLY
• Executive Management

You must carefully apply docking rules to reduce the size of the local database. A smaller local database can reduce synchronization times and transaction application times. Docking visibility rules identify the records that Siebel Remote synchronizes from the server database to each user. For more information, see Predefined Routing Models for Siebel Remote.

A routing model also affects the data that Siebel Remote extracts to regional servers and the subsequent transactions that it routes to regional nodes. For more information, see Comparison Between Siebel Remote and Siebel Replication Manager.

Displaying Views for Data That Routing Models Route

You can configure Siebel Remote so that a Siebel application displays only the views that display data that the routing model routes. You can use this configuration for a user who is assigned to one of the following predefined routing models:

• Sales Rep Standard
• Sales Mgr Standard
• Field Technician
• Analyst
• Sr. Field Engineer
• Field Engineer

Each user is associated with one routing model. The combination of the routing model and the routing rules determine if Siebel Remote routes a record to a remote client. For more information, see Predefined Routing Models for Siebel Remote.

Specialized Routing Models

It might be necessary to use a specialized routing model to help minimize the size of the local database. It is strongly recommended that you get help from Oracle before you deploy Siebel Remote with a specialized routing model. For more information, see Getting Help from Oracle.

Selective Retrieval Routing Model

The Selective Retrieval routing model can reduce the amount of data that Siebel Remote synchronizes, reduce synchronization time, and reduce the size of the local database. This routing model is appropriate for the user who uses connected and disconnected versions of a Siebel application. It might not be appropriate for a user who only uses the remote client or who requires access to some features, such as quotes or forecasting because Selective Retrieval limits the functionality of the Siebel application in some areas. Enabling records for synchronization also requires a direct connection to a Siebel Enterprise Server or to a regional server if the regional server contains the records that are enabled for synchronization. For more information, see Using Selective Retrieval to Route Data, and About the Siebel Enterprise and the Siebel Enterprise Server.

How Selective Retrieval Works

A user can enable or disable records for synchronization at any time. If you assign a user to the Selective Retrieval routing model, and if this user enables a record for synchronization, then Siebel Remote synchronizes this record to the remote client that is associated with the enabling User ID. It also synchronizes any records that are related to the enabled record to maintain data integrity. For example, if the user enables an account record, then Siebel Remote synchronize the records for the contacts and addresses that are associated with this account.

If the user enables records for synchronization before Siebel Remote extracts the server database for the remote client, then the Transaction Router server component handles fewer items on the subsequent synchronization.

If you assign a user to the Selective Retrieval routing model, and if this user disables a record for synchronization, then Siebel Remote removes this record and any associated records from the local database during the next synchronization.