Upgrade Guide for Microsoft Windows > Upgrading the Siebel eBusiness Application > Preparing the Prior Customer Repository for the Merge >

Migrate Strings, Merge Labels and Fields, and Merge Templates


CAUTION:  The repository merge procedures only apply to development environment upgrades. If you are performing a production environment upgrade, skip to Upgrading the Custom Database Schema.

Before you run the repository merge, you need to run the Repository Preparation Wizard from Siebel Tools to perform the following operations:

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. For example, if your upgrade fails after you successfully completed the Merge Labels and Fields part of repository preparation, you would 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 the browse button to specify the log file.

      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.

      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 (those developed for Handheld or Wireless applications).

      CAUTION:  If you are upgrading to Siebel Financial Services 7.x, 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 SIEBEL_ROOT\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 you have additional applets that should not be merged (those developed for Handheld or Wireless applications).

    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.

File Name
Description
labelmerge.txt
Generated by label and field merge. Lists all applets that are being modified. For each applet modified, displays whether the label and field merge was successful. If a control already has a caption, the old caption is logged for that control.
templatemerge.txt
Generated by the template merge. Lists all applets that are being modified and displays whether the merge was successful. For each applet, displays the following:
  • The template being used as the source (other templates are merged into this template.)
  • The Applet Web Templates being inactivated.
  • Controls whose types are changed to ensure that they only appear in the correct modes.

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.


 Upgrade Guide for Microsoft Windows
 Published: 20 October 2003