Repository Manager Guide

10.3

Back Next

Applying a Change List to the Target Repository

To apply changes to the target repository:

Click the

Apply

button.

Repository Manager

prompts you to select a rollback strategy in the event of a failure during the import process.

Select one of the following options:

Strategy	Description
Full rollback	Rolls back all of the changes attempted during the promote process.
Rollback to last change	Rolls back to the last successful change prior to the interruption of the promotion application process. For example, if changes in base object columns A and B were successfully applied to the target repository, but the promotion application process failed before changes in column C were successfully applied to the target repository, then changes are rolled back to column B. Use this option if you are promoting many changes and want to keep successfully-applied changes in the event of a failure.

Strategy

Description

Full rollback

Rolls back all of the changes attempted during the promote process.

Rollback to last change

Rolls back to the last successful change prior to the interruption of the promotion application process. For example, if changes in base object columns A and B were successfully applied to the target repository, but the promotion application process failed before changes in column C were successfully applied to the target repository, then changes are rolled back to column B.

Use this option if you are promoting many changes and want to keep successfully-applied changes in the event of a failure.

Rollbacks for each design object involve rolling back two changes: the physical change in the repository (for example, removing a physical column), as well as the metadata about the design object (the metadata descriptor of the column).

Choose OK
.

If the target repository is currently registered with a proxy user,

Repository Manager

prompts you to enter the owner password for this repository.

If prompted, enter the password of the ORS schema owner.

Data integrity validation is performed based on the user choice. A dialog box asks the user to select if the data integrity validation is to be performed before promoting the changes (either in promote ChangeList or Visual).

Repository Manager

displays a progress bar.

When finished,

Repository Manager

displays a message indicating whether the promote process succeeded.

Promoting Changes Using Change Lists

Repositories Currently Registered with a Proxy User

Monitoring the Results of Changes

Download Guide

Watch

Comments

Communities