How Siebel Anywhere Component Versions Are Used

After Siebel Anywhere has stored an upgrade kit's version information in the database and the Siebel administrator has distributed the upgrade kit, eligible subscribers have access to the upgrade kit. Siebel Anywhere compares the subscriber's current component version with the version information in the database under conditions that depend on both the type of subscriber and certain settings. For detailed information about when these version checks are done, see the following table.

Subscriber Type	When Version Check Occurs
Mobile Web Client and Developer Web Client users	Mobile and Developer Web Clients perform the version check when the client starts up and connects to either the server or local database. Mobile Web Clients also perform a version check during each synchronization session.
Regional Node Servers	Performed as the Regional Node Server starts up, dependent upon the version check flag on the Regional Node Server. The Replication Agent on a Regional Node Server also performs a version check for each synchronization session, dependent upon the same Version Check parameter.

Multiple factors affect what happens after Siebel Anywhere performs a version check. These factors include the subscriber type, the state the Siebel application is in when the versions are compared, and the relative version numbers.

In general, if a version check reveals that a subscriber is required to upgrade, then that subscriber is prompted to do so and has limited or no access to the affected application until the upgrade is complete. For detailed information about responses to the version check process when the upgrade is required, see About Specifying the Versions That Can Use the Upgrade Kit.

However, if a version check reveals that a subscriber is not required to upgrade, then that subscriber generally is not prompted to upgrade, but can voluntarily navigate to the Component Upgrades view in the User Preferences screen to discover whether an upgrade is available and to request the upgrade. For more information about displaying optional upgrade kits and requesting optional upgrades, see the following table.

Client or Server	Status of Application: Running	Status of Application: Startup
Mobile Web Client	During synchronization, if a version check discovers a required upgrade kit, then a prompt appears asking if the user wants to download the upgrade kit now. The choices are: Yes. The upgrade takes place. No. Synchronization does not occur. If you restart synchronization prior to exiting from the application, then you will be prompted again.	If a version check discovers a required upgrade at application startup, then a message such as the following appears: Client is being started in read-only mode. Please start a Siebel Remote session to retrieve the upgrade kit required to upgrade your system.
Developer Web Client	Not applicable.	If version check discovers a required upgrade at application startup, then a prompt appears asking if the user wants to download the upgrade kit now. The choices are: Yes. The upgrade takes place. No. The application starts in read-only mode.
Regional Node Server	If Version Check is TRUE, then Replication Agent automatically downloads the upgrade kit and shuts down the Regional Node Server. If Version Check is FALSE, then Replication Agent stops merging but does not shut down the Regional Node Server.	If Version Check is set to TRUE, then the Regional Node Server downloads the upgrade kit and shuts down. The Siebel administrator must invoke the Upgrade Wizard manually, from the command line, to perform the upgrade. If Version Check is FALSE, then the Regional Node Server starts up.