Tuning the Siebel Mobile Web Client in a Siebel Remote Deployment

This topic discusses how you can optimize the performance of a Siebel Mobile Web Client in a Siebel Remote deployment. It contains the following information:

"Optimizing Application Configuration File Parameters"
"Guidelines for Optimizing Data Synchronization Between Siebel Mobile Web Client and Siebel Remote"
"Choosing an Appropriate Routing Model"

For more information about performance tuning for Siebel Mobile Web Clients, see Chapter 5, "Tuning Siebel Web Client for Performance."

Optimizing Application Configuration File Parameters

This topic is part of "Tuning the Siebel Mobile Web Client in a Siebel Remote Deployment". It discusses how you can modify values for the parameters specified in your Siebel application configuration file to optimize the performance of a Siebel Mobile Web Client.

DockTxnsPerCommit

The value of this parameter specifies the number of transactions that Siebel Remote applies to the local database before performing a commit. If you have an environment where a large number of transactions are constantly being created, then adjusting the value of DockTxnsPerCommit upwards might decrease the amount of time taken for initialization and synchronization tasks for large quantities of data. In such a scenario, test a variety of values (for example, 1000, 2000, 3000) and determine which value is best for your environment.

The DockTxnsPerCommit parameter appears in the [Local] section of your application configuration file. The default value is 500.

Guidelines for Optimizing Data Synchronization Between Siebel Mobile Web Client and Siebel Remote

This topic is part of "Tuning the Siebel Mobile Web Client in a Siebel Remote Deployment". It lists some points that can help you to optimize data synchronization between your Siebel Mobile Web Client and Siebel Remote Server. Note the following:

Synchronize frequently

Synchronizing frequently reduces the number of transactions to transmit and commit for each synchronization session. The longer that a user waits between synchronization sessions, the more data there is to send.
Enable TrickleSync on the Siebel Mobile Web Client

Each time that a Siebel Mobile Web Client connects to your Siebel Enterprise network, TrickleSync performs database synchronization. For more information, see Siebel Remote and Replication Manager Administration Guide.
Use time-based filters to prevent sending data from server to client that is older than a specific date.

Choosing an Appropriate Routing Model

This topic is part of "Tuning the Siebel Mobile Web Client in a Siebel Remote Deployment".

One way to increase performance is to reduce the volume of data transmitted to the remote users. This can be best achieved by choosing the appropriate routing model.

Routing model choices provide a useful level of granularity in setting the size of a local database. In general, using appropriate routing models improves overall performance of a remote environment and helps decrease Database Extract times and increase Transaction Router throughput.

If none of the supplied routing models are appropriate, then contact Oracle Advanced Customer Services, who can help you to develop a routing model that is appropriate to your environment. Contact your Oracle sales representative to request assistance from Oracles Application Expert Services.