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

About Inheriting Upgrade Behavior


Upgrades: All upgrades.

Environments: Development environment only.

You can link objects together so that one object inherits the upgrade behavior of another. You do this by specifying an upgrade ancestor for an object.

Use standard objects as upgrade ancestors. A standard object is an uncustomized repository object provided by Siebel Systems. Objects in the Prior Siebel Repository and the New Siebel Repository are standard objects.

Typically, you create customized objects by making a copy of a standard object and then modifying the copy, called the descendent.

You can specify upgrade ancestors for the following object types:

  • Applets
  • Business Components
  • Integration Objects
  • Reports

You specify the upgrade ancestor in the descendent's Upgrade Ancestor field in Siebel Tools. During the repository merge, the descendent is upgraded in the same way as the upgrade ancestor.

For example, you copy the standard object Applet A and name the descendent Applet B. In the New Siebel Repository, Applet A has been modified to include several new list columns.

Here is what happens to Applet B (the descendent) during the repository merge:

  • If you specified Applet A as the upgrade ancestor, then Applet B is upgraded to include the two new list columns.
  • If you did not specify Applet A as the upgrade ancestor, then Applet B does not receive the two new list columns.

Limitations on the Upgrade Ancestor Property

The Upgrade Ancestor property is considered only during repository merges as part of application upgrades under these conditions:

  • If an upgrade ancestor is not present in the New Siebel Repository, it is obsolete, and its upgrade behavior is not propagated to descendents. If an ancestor object is obsolete in the New Siebel Repository, descendents are not also obsolete. They are copied to the New Customer Repository.
  • If an upgrade ancestor is not present in the New Siebel Repository, error messages display during the repository merge and are written to the merge log file. These errors are acceptable and do not mean the merge has failed.
  • The Upgrade Ancestor property is not considered during repository imports. However, imported objects can specify an upgrade ancestor. When the next application upgrade is done, the Upgrade Ancestor property is taken into account.
  • The setting of the Upgrade Ancestor property is not considered when applying application patches. If the upgrade ancestor is modified by the patch, descendents are not modified.
  • The Upgrade Ancestor Property is not used by the postmerge utilities. The postmerge utilities revise layout objects without regard to how ancestor objects were revised.
  • Specifying an upgrade ancestor for objects slows the repository merge.

Upgrade Ancestor Picklist

When you click in the Upgrade Ancestor field, a picklist displays. The following criteria are used to populate the picklist:

Applets
  • Table is the same as the current applet buscomp
  • Class is the same as the current applet class
  • Upgrade Ancestor is null
  • Applet is a standard object
Reports
  • Buscomp is the same as the current report buscomp
  • Class is the same as the current report class
  • Upgrade Ancestor is null
  • Report is a standard object
Business Components
  • Bus Comp is the same as the current business component
  • Class is the same as the current business component
  • Upgrade Ancestor is null
  • Business component is a standard object
Integration Objects
  • Base Object Type is the same as the current Base Object Type
  • Business Object is the same as the current business object
  • Upgrade Ancestor is null
  • Integration object is a standard object

Propagating Changes to Objects After the Merge

If you do not select an upgrade ancestor for an object, changes to the upgrade ancestor are not propagated to the descendent during the repository merge.

You can manually propagate changes to descendents after the merge by using the Siebel Tools object comparison and synchronization features. These features enable you to compare any two objects and propagate differences to one or both of the objects. For more information, see Configuring Siebel Business Applications.

Related Topic

About the Postmerge Utilities

Upgrade Guide for DB2 UDB for z/OS