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.