Upgrade Guide > Preparing Siebel Application Data for Upgrade >

Preparing Siebel Mobile User Data for Upgrade

Upgrades: All Siebel upgrades.

Environments: Development, production test, production.

This topic applies primarily to developers running the 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 Mobile Web Client users.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

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 mobile users for the database upgrade

1. Perform a partial synchronization for mobile users, sending all transactions to the server database.
2. Verify that 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 Administration-Server Management > Tasks 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, the S_ESCL_REQ table should not have any rows.
3. To prevent synchronization of Mobile Web Clients with the database server, stop or disable all Siebel Remote components on all Siebel Servers.
4. Disconnect all Web Clients from the Siebel Server by stopping the appropriate Application Object Managers, as described in Siebel System Administration Guide.
5. Upgrades from Siebel 7.5x and earlier. Make sure that Dedicated Web Clients have disconnected from the Siebel Database Server.

   The method you use to do this depends on your database. For example, with an Oracle RDBMS, you would stop the primary listener. However, all RDBMS types require starting the database in restricted mode. Refer to the documentation that you received from your RDBMS vendor for more information.