In
some cases, you must reapply a customization to an object that has been
patched.
•
ODI’s version-compare utility identifies the changes introduced by the patch.
• You only need to reapply customizations to
mappings that have been changed by the patch.
In some cases, you must
reapply a customization to an object that has been patched. For example, if you
installan Oracle Business Intelligence Applications patch that modifies the
Supply Chain and Order Management application,you might need to manuallyreapply
customizationsthat you have made to the Supply Chain and Order Management
application.
As part of customizing an ETL
task (including interfaces and package under a specifictask folder),you copy
the task folder to be customized, version the original,and version the copy.
Any patches are applied to the current version of the originaltask. Leverage
ODI’s version-compare utilityto identify the changes introduced by the patch.
The copy is also versioned so
that any changes introducedcan be isolated. After a patch, compare any changes
with those introducedby the patch and verify that there is no conflict, and
then manuallyapply the same changes introduced by the patch to the customized
ETL tasks.
A patch only installschanged
repository objects, not the entire ODI WorkRepository. Therefore, you only need
to reapply customizations to mappings that have been changed by the patch.
For
example, if a patch only modifies the Supply Chain and Order Management
application, you only need to manually reapply customizations that you have
made to the Supply Chain and Order Management application.Customizations in
other applications would not be affected by the patch.
No comments:
Post a Comment