An Introduction to Customization Manager
As I mentioned in the introductory article, one of the marquee features of ACP is the Customization Manager.
Customization Manager provides a solution to the age-old question of how to manage files associated with custom applications, custom reports, and custom extensions. The result is a dramatic reduction in the amount of time and energy associated with moving, building, and managing these artifacts through the instances in your environment.
The way it works is that we take the files that comprise the custom report or applications, and then we bundle them up into what is, for all intents and purposes, and Oracle patch. We can then utilize the standard EBS tools (i.e, AD Utilities, to be specific) to propagate and apply that patch into downstream instances.
Some of the other key features of Customization Manager are:
- Support for over 200 file types (e.g., forms, bi publisher, OAF, etc.)
- The "Custom Patches" can be applied using Patch Manager (i.e., another component of ACP)
- Central console for all custom patches
- Build or compile Java or Form libraries
- Validate custom files to ensure adherence to a set of standards
- Native support for prominent Source Control systems (e.g., CVS, Subversion)
- Built-in standard and comparison reports
We're in the process of finalizing some Customer Advisory webcasts on Customization Manager, as well as the other components of ACP. These webcasts should give you a better idea on the look, feel, and functionality of Customization Manager. Stay tuned!