Testing Upgrade Kits

This topic describes how to test upgrade kits. This task is a step in Process of Retrieving, Installing, and Testing Upgrade Kits.

The recommended method for testing upgrade kits is to create and distribute an upgrade kit to a limited and controlled number of users. In this method, you can assign specific testing users to the Siebel Test Client configuration so your regular subscribers will not be allowed to install any upgrade kits in the testing phase. Distribute the upgrade kit only to the Siebel Test Client configuration. See Using the Siebel Test Client Configuration for Testing.

Caution: When testing new upgrade kits, it is strongly recommended that you perform tests using both Developer and Mobile Web Clients. If for any reason Mobile Web Client users experience problems installing or downloading the new upgrade kit, then the problems will be significant.

After an upgrade kit has been thoroughly tested under the Siebel Test Client configuration, you can then distribute it to the appropriate production configurations.

To optimize the setup process for new users, it is recommended that you create a master installation image for each configuration your Siebel Anywhere subscribers use, and keep these images up to date. If all current upgrade kits are installed to create a current image, then you can use the image to set up new subscribers, so each new subscriber will not need to download and install many upgrade kits. This method also makes it safer to deactivate old upgrade kits, since new subscribers will receive the necessary software by means of installation images, rather than being required to install old upgrade kits.

Note: Siebel Anywhere does not deliver Siebel Database Schema upgrade kits to individual Developer Web Client users, because they connect to shared databases. Test database extensions in the development environment.