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

Migrating Repository Objects to the Standard UI

Upgrades: All upgrades. Perform this task if you selected Incorporate Custom Layout (ICL) on your previous upgrade.

Environments: Development environment only.

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

If you selected the Incorporate Custom Layout (ICL) feature for your previous upgrade, you must migrate UI repository objects to the standard UI before doing the repository merge for your next upgrade. The migration does not affect customized objects in the Prior Customer Repository. Customized objects are preserved and are included in the repository merge.

Migrating to the standard UI uses defined logic to select objects and then modifies these objects as follows:

• ICL UI objects: Inactivates and deletes the Web templates and certain child objects. These are the objects that preserved the layouts of the previous release.
• Standard UI objects. Activates the UI Web templates and child objects that provide the standard UI look and feel for the release you are upgrading from. These objects have -UPG appended to the name.

For a full description of how ICL works during an upgrade, see About the Incorporate Custom Layout (ICL) Upgrade Option.

How Customizations Are Handled

ICL UI objects you have customized after the previous upgrade are not affected by the migration to the standard UI. These changes are preserved and are included in the repository merge for the new release.

Siebel Tools identifies these customizations by comparing the modification time of ICL UI objects with their corresponding standard UI objects. If the modification times differ by more than a specified lag time, Siebel Tools does not change the ICL UI object, and it is treated as a customized object in the upcoming repository merge.

For example, your previous ICL repository merge required about three days to complete. This means the modification time of an ICL UI Web template and its corresponding standard UI Web template did not differ by more than three days when the repository merge completed. You later modified the ICL UI Web template. Its modification time now differs by more than three days from the corresponding standard UI Web Template.

You then use Siebel Tools to migrate the repository to the standard UI and use a lag time of three days. Since the modification time comparison for the ICL UI Web template is greater than the lag time, the ICL UI Web template is not replaced by the corresponding standard UI Web template. The ICL UI Web template is treated as a customized object in the upcoming repository merge.

The default lag time is 72 hours. You can specify a lag time between 24 and 120 hours. Observe the following guidelines:

• Avoid setting a lag time that is shorter than the time required to complete the previous repository merge. This can cause objects that were not customized after the merge to be treated as customized.
• Do not set a lag time that is significantly larger than the length of the previous repository merge. This increases the risk that customizations were made before the lag time expired. These customizations will be lost during the upcoming repository merge.

How Repository Objects Are Changed

The migration process locates both standard UI objects and ICL UI objects in the repository. The process then determines whether to modify the standard UI object or the corresponding ICL UI object:

• Deleting the ICL UI object and activating the corresponding standard UI object migrates the UI to standard.
• Deleting a standard UI object and retaining the corresponding ICL UI object preserves the customized ICL UI object.

Table 21 shows the logic used to modify these objects. Interpret the table columns as follows:

• ICL UI Object Found? Yes means Siebel Tools has located a standard UI object, and it has a corresponding ICL UI object. No means that a corresponding ICL UI object is not in the repository. In most cases, this is because the object was inactive in the Prior Customer Repository during the previous merge. When this occurs, the object is appended with -UPG. No ICL UI object that preserves look and feel is created.
• Within Lag Time? Yes means that the modification time comparison is within the specified lag time. No means the comparison is not within the specified lag time. No indicates that you have modified the ICL UI object after the repository merge.
• Status in Prior Standard Repository. Siebel Tools checks the Active/Inactive status in the Prior Standard Repository to prevent activating an object that is inactive in the Prior Standard Repository.

In the table, Prior Customer Repository refers to your current Siebel Repository, which you renamed in preparation for the upcoming repository merge.

How Logging Is Done

The migration process logs the changes to the repository in the following log file:

SIEBEL_ROOT\log\iclmigration.log

The beginning of the log lists top-level objects that were affected by the ICL feature. For each object, the log then iteratively lists the operations performed on all child objects.

Specifying a Lag Time

The default lag time is 72 hours. You can revise this by editing the Siebel Tools .cfg file. The minimum is 24 hours, and the maximum is 120 hours.

Prerequisite: Your Siebel Tools installation must be release 7.7 or later.

To specify a lag time

1. In the Siebel Tools installation directory, navigate to the \bin\lang directory, where lang is the installed language, for example ENU.
2. Using a text editor, open tool.cfg, and locate the [Siebel] section.
3. Add the following variable at the end of the section:

   PriorICLMergeTimeLag = time

   where time is an integer greater than or equal to 24 and less than or equal to 120.

4. Save the file.
5. Restart Siebel Tools.

Migrating to the Standard UI

A menu option in Siebel Tools migrates the repository Web templates and child objects to the standard UI. Upgrading the UI requires a minimum of three hours to complete.

Prerequisites:

• Your Siebel Tools installation must be release 7.7
• Set the lag time as desired. The default is 72 hours
• Verify that you have backed up the upgraded database

To migrate to the standard UI

1. Start Siebel Tools.
2. In the Tools menu, choose Upgrade. Then select Migrate ICL Objects to Standard.
3. In the ICL Migration dialog, make the following selections and click Continue:
   • Prior Customer Repository: Select Prior Customer Repository. This is the Siebel Repository in your current release, which you have renamed in preparation for the upgrade.
   • Prior Standard Repository: Select Prior V7.X Siebel Repository. This is the Prior Standard Repository for your currently installed release. This repository was loaded when you performed the database upgrep for the new release.
4. In the ICL Migration Warning dialog, click Yes to confirm you have backed up the Prior Customer Repository.

   The ICL Migration Status dialog box appears. It displays log entries during the migration.

   During the migration, you cannot perform other operations in Siebel Tools. You also cannot close Siebel Tools.

   A pop-up message displays when the migration is complete.

5. To cancel the migration after it has begun, do the following:
   1. In the ICL Migration Status dialog box, click Cancel.
   2. In the dialog box that asks you to confirm you want to cancel, click Yes.

If you cancel the migration after it has begun, you must restore the saved Prior Customer Repository from backup and begin the migration again.