Siebel Anywhere Administration Guide > Upgrade Planning and Preliminary Tasks > Determining Upgrade Requirements >

Other Preliminary Upgrade Tasks for Specific Upgrade Kit Types

The following paragraphs describe additional preliminary tasks to perform for specific upgrade kit types.

Preliminary Tasks for Siebel Database Schema Upgrade Kits

Perform the following tasks before creating a Siebel Database Schema upgrade kit:

• Make sure the ODBC data source correctly points to the server database that has the modified database definition.
• Determine the values to use for the following settings. For brief descriptions of these settings, see Table 18.
  • User Name (for DBA)
  • User Password (for DBA)
  • Schema Qualifier
  • Privileged User ID
  • Privileged User Password
  • Table Space
  • Index Space
• Use SQL queries on your server database to obtain values for the following parameters specific to your database platform:
  • 16K Table Space
  • 32K Table Space
  • Table Group File
• If you are operating in a DB2 environment, drop all customized views and triggers before you run the Upgrade Kit Wizard to define a database schema upgrade kit. Otherwise, the attempt to create the kit will fail.

For more information about the overall process of deploying a database schema upgrade, see Performing Database Schema Updates.

Preliminary Tasks for Siebel Repository File Upgrade Kits

Perform the following tasks before creating either a Siebel Client Repository File upgrade kit or a Siebel Server Repository File upgrade kit:

• Obtain or create the new repository (.srf) file.
• Place the new repository file in a network location that is accessible to the Siebel Server where the Upgrade Kit Builder will be running.
• Make a note of the UNC path to the network location where you placed the .srf file.

Preliminary Tasks for Third-Party Software Upgrade Kits

Perform the following tasks before creating a Third-Party upgrade kit:

• Locate or prepare the executable file or script that will be executed on the subscriber's machine when the upgrade kit is installed. Make a note of any input parameters required by the executable file or script.
• Place the executable file on the Siebel Server where the Upgrade Kit Builder is enabled, or in a network location that is accessible to that server.
• Make a note of the UNC path to the network location where you placed the executable file.
• Determine the location where the third-party software should be installed on the subscriber's machine.

Preliminary Tasks for Siebel Customer Revisions Upgrade Kits

Perform the following tasks before creating a Siebel Customer Revisions upgrade kit:

• Locate or prepare the executable file or script that will be executed on the subscriber's machine when the upgrade kit is installed. (For example, this might be a reset.bat script file that resets browser security settings to the values that allow the Mobile Web Client to function properly.) Make a note of any input parameters required by the executable file or script.
• Locate any other files to be included in the upgrade kit, and make a note of the locations to which they should be installed on the subscriber's machine.