1. Anywhere Administration Guide
  2. Other Preliminary Tasks for Upgrade Kits

Other Preliminary Tasks for Upgrade Kits

This topic describes additional preliminary tasks to perform for upgrade kits, based on their specific component types.

This topic is part of Determining Your Upgrade Requirements.

Preliminary Tasks for Siebel Database Schema Upgrade Kits

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

  • Make sure that the changes to your Siebel database schema can be distributed by this type of upgrade kit.

  • Make sure that the ODBC data source correctly points to the server database that has the modified database definition.

  • Use SQL queries on your server database to obtain values for the following parameters, as they apply to your database platform:

    • 16K Table Space

    • 32K Table Space

    • Table Group File

  • If you are operating in an IBM DB2 environment, then drop all customized views and triggers before you run the Upgrade Kit Wizard to define a Siebel Database Schema upgrade kit. Otherwise, the attempt to create the upgrade kit will fail.

For more information about the overall process of deploying a Siebel Database Schema upgrade kit, see Process of Updating the Siebel Database Schema.

Preliminary Tasks for Siebel Repository Export Import Upgrade Kits

Perform the following tasks before creating a Siebel Repository Export Import upgrade kit:

  • Using the Siebel Migration application, complete a full runtime repository migration operation.

  • Set up the Siebel Mobile Web Client.

  • Create a new workspace, make the repository changes, and deliver the updates.

  • Using the Siebel Migration application, complete an incremental runtime repository migration operation.

  • Make sure that the repository changes are available in the runtime environment to which clients are pointing.

  • Make sure that the ODBC data source correctly points to the server database that has the modified database definition.

  • If you are running the dataexp.exe directly in the developer environment instead of using the Siebel Migration application, then make sure the workspace is in a check-pointed state.

For more information about planning for a database migration using Siebel Application Interface, preparing data for a migration using Siebel Application Interface, and migrating database data from a source environment to a target environment using Siebel Application Interface, see Siebel Database Upgrade Guide.

Preliminary Tasks for Third Party Software Upgrade Kits

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

  • Locate or prepare the executable file or script that will be executed on the subscriber's computer when the upgrade kit is installed. Make a note of any input parameters required by the executable file or script for the third-party software.

  • Place the executable file in a network location that is accessible to the Siebel Server where the Upgrade Kit Builder is enabled.

  • 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 will be installed on the subscriber's computer.

Preliminary Tasks for Siebel Client Customer Revisions Upgrade Kits

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

  • Locate or prepare the executable file or script that will be executed on the subscriber's computer when the upgrade kit is installed. 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 where they will be installed on the subscriber's computer.