Siebel Database Upgrade Guide > Preparing Siebel Application Data for Upgrade >

Preparing Siebel Mobile User Data for Upgrade

Environments: Development, production test, production.

Platforms: Windows, UNIX, IBM z/OS.

This topic applies primarily to developers running the Siebel Mobile Web Client in the development environment and to end users in the production environment. This topic applies to the production test environment only if it has Siebel Mobile Web Client users.

After synchronizing, mobile users must make no further changes to their local databases until the upgrade has been completed. Any changes made during the upgrade are lost when they are reinitialized following the upgrade.

Complete the following steps before beginning the upgrade of either a development environment or a production environment. For additional information on these steps, see Siebel Remote and Replication Manager Administration Guide and Siebel System Administration Guide.

To prepare Siebel Mobile Web client users for the database upgrade

1. Perform a partial synchronization for mobile users, sending all transactions to the server database.
2. Verify that Siebel Mobile Web Clients have synchronized and that all changes have been merged into the server database as follows:
   1. Check that no transaction files remain in the synchronization inbox and outbox for any mobile user. The synchronization inbox for each user is on the Siebel Server:

      Windows: SIEBEL_ROOT\docking\MOBILEUSERNAME

      UNIX: $SIEBEL_ROOT/docking/MOBILEUSERNAME

      Transaction files are in the format number.dx; for example, 00000023.dx.

   2. Check the mobile users Remote Status view and resolve any insert conflicts.
   3. Log onto a Siebel Business Application, such as Call Center, as the Siebel administrator. Use the Tasks view from the Administration-Server Management screen to make sure that each Transaction Merger task has successfully completed.
   4. Verify that Workflow Monitor and Workflow Action agents have processed all pending requests. If Workflow Manager has completed successfully, then the S_ESCL_REQ table must not have any rows.
3. To prevent synchronization of Siebel Mobile Web Clients with the database server, stop or disable all Siebel Remote components on all Siebel Servers.
4. Disconnect all Siebel Web Clients from the Siebel Server by stopping the appropriate Application Object Managers, as described in Siebel System Administration Guide.