Upgrade Guide for DB2 UDB for z/OS > Performing the Siebel Tools Repository Merge >

Running the Repository Preparation Wizard on Release 6.2.1 Repository

6.x upgrades only. This topic applies to upgrades from Release 6.2.1.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform the Upgrade.

Before you run the repository merge on an ASCII database, you must run the Repository Preparation Wizard on the Prior Customer Repository. This utility is invoked from Siebel Tools and is used to perform the following procedures:

• Migrate strings. Release 7.x supports locale strings in object-specific tables. In order to move the S_MSG data in your environment to the new locale table structure in Release 7.x, you need to run the Migrate Strings utility.

  Migrate strings for each language that was supported in your prior repository.

• Merge labels and fields. Release 7.x merges labels with controls so that the label is now recognized as the caption property of the control. Before you run the repository merge, you need to run the Repository Preparation Wizard to merge labels, controls and fields from the previous version based upon form applet layout.

  NOTE:  If you are upgrading to a Siebel Financial Services 7.x application, do not use the default input file to merge labels and fields. See the Caution note in Step 3.

• Merge Web templates. Release 7.x merges Web templates in Siebel Tools to only use Base and Edit/Query/New for the majority of the preconfigured applets. Previous releases of Siebel used four separate templates to deliver the same functionality. Before you run the repository merge, you need to run the Merge Templates utility to merge your applet web templates.

The Repository Preparation Wizard prompts you to confirm that you completed the following steps before it proceeds with the repository merge.

NOTE:  If your upgrade fails while you are preparing the prior customer repository for merge, you need to restore your database to the most recent backup and complete repository preparation procedures. If your upgrade fails after you successfully completed the "Merge labels and fields" part of repository preparation, you must restore your database to the point after which you merged labels and fields.

To migrate strings, merge labels and fields, and merge applet Web templates

1. In Siebel Tools, navigate to the Tools menu, and then choose Tools > Upgrade > Prepare Repository.

   Choose Prior Customer Repository as the repository that you wish to prepare.

   The String Migration window appears.

2. In the String Migration window:
   1. Select the language for which you wish to migrate strings.
   2. To log migrated strings, click in the check box beside Log migrated strings, then click Browse to specify the log file.

      If you have a single-language implementation and your base language is not English (ENU), you need to perform extra steps to upgrade labels of custom applets. See 476642.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Alert 426.

      To continue, click Next. The Merge Labels and Fields window appears.

3. In the Merge Labels and Fields window:
   1. Specify the input file by clicking the Browse button.

      The utility operates on every form applet except those specified in the input file. The default input file is applets.txt. Modify the input file only if you have additional applets that should not be merged.

      CAUTION:  If you are upgrading to a Siebel Financial Services 7.x application, you should not use the default input file, applets.txt, because the repository preparation utility operates on every form applet except those specified by the input file, and Siebel Financial Services applications contain additional applets that should not be merged. Instead, you should browse to the \Tools\Bin directory and select the input file named fins_applets.txt.

   2. Specify the location of Web templates.

      To continue, click Next. The Merge Applet Web Templates window appears.

4. In the Merge Applet Web Templates window, click the Browse button to specify the same input file that you used in Step 3, then click Next.

   NOTE:  The utility operates on every form applet except those specified in the input file. The default input file is applets.txt. Modify the input file only if you have additional applets that should not be merged.

   The Merge Applet Web Templates window appears. Click OK to confirm that you want to proceed.

   The wizard prepares your Prior Customer Repository for the merge.

   The Repository Preparation Wizard records the results of the labels and fields merge and the template merge into the labelmerge.txt file and the templatemerge.txt file, respectively. If you want to view information about how the Repository Preparation wizard prepared your repository for merge, you can check these files, located in the Siebel_Tools\temp directory. More information about these log files is provided in the table below.

The following errors in the templatemerge.txt file are acceptable if they are against standard applets, because there were no Edit or New applet web templates associated with standard applets in the previous version.

• Upgrading APPLET_NAME.
• Using Edit as source template.
• Could not find source template.