Siebel Remote and Replication Manager Administration Guide > Setting Up Mobile Web Clients > Routing Rules and Dock Objects >

Dock Objects

A Dock Object is a logical grouping of tables with a special schema structure to synchronize data between a server database and a mobile database in a coherent manner. Routing rules belong to dock objects.

Generally, there are three types of dock objects in the Siebel architecture:

Enterprise dock objects are those objects that are visible to all users within the application. Examples include currency and catalog.

Private dock objects are those objects that will not be routed to mobile users. If data is created on Mobile Web Clients, it will be sent up to the server. However, updates to them will not be returned to the client. Data visibility of private dock objects to users is not used in the routing consideration.

CAUTION:  After making any change to the database schema, run the Generate New Database Template component and reextract all mobile clients, or use Siebel Anywhere kits to distribute the change to all mobile clients. It is strongly recommended that you do this even if the schema change only affects private dock objects, because individual tables in a private dock object may become visible to mobile clients at a later time, and problems can occur if server and local database structures do not match.

Limited dock objects are those objects whose data may or may not be visible to a particular user—most user data is of this type. These objects have routing rules, as described earlier, that determine which records are routed to a particular mobile user.

Routing rules are SQL statements that determine whether a given piece of data should be routed to a given user. Routing rules embody the data visibility and data access built into Siebel eBusiness applications. Any transactions in the system are associated with a set of routing rules that may cause the transactions to be routed to a mobile user.

A routing model is a collection of routing rules. The next section includes a detailed description of the routing models available. A mobile user can now be defined as associated with any of the routing models. Thus, transaction routing will behave differently for each mobile user, depending on the routing model the user is associated with.


 Siebel Remote and Replication Manager Administration Guide 
 Published: 19 November 2003