Thursday, December 27, 2012
Agile Adoption Roadmap: The Importance (or not) of Agile Terminology for an agile culture
Agile Adoption Roadmap: The Importance (or not) of Agile Terminology for a...: I have noticed in my experience in helping teams transition toward an Agile culture that moving away from the traditional terminology and a...
Wednesday, April 7, 2010
Application Release Management for the Oracle E-Business Suite
The Oracle E-Business Suite is a comprehensive application that helps many businesses succeed.
However, it has proven to be a nightmare to development and IT teams, especially when some updates are done to the existing environment, as well as when patching needs to be done. The challenge lies in the way organizations manage the process of changing the application.
Very often, is process is manual. Some organizations have an enterprise change management solution, that they try to manually link (or integrate) with the Oracle E-Business Suite. What does this mean?
Here, the change management process is external to the E-Business Suite, meaning the change control system depends on manual confirmation of external migration activities. This could potentially mean running scripts or executing batch commands to actually perform activities in the Oracle EBS system. Here, the change control system cannot execute the Oracle migration process, thereby introducing a manual layer where an approval is got externally, and the migration process is done through scripts or through a "bubble gum and wire" method.
The challenges lead to a situation where auditing and reporting of change management activity requiring integration of manually obtained information from multiple sources. Sometimes, this means creating manual reports where data does not exist. Auditing and reporting must be timely and accurate. Often, the management does not have hours to wait for such a report.
Automation is a definite benefit here. Integrating the change control system from within the Oracle migration process helps streamline the change management process. Automated interface simplifies and increases control and manageability over the process. This process sits inside the Oracle EBS, and automates and simplifies the migration process, thereby reducing errors and reducing the time-to-deploy. An added benefit is the automated documentation of the migrated objects and the process.
Most commercial offering sit outside of the E-Business Suite, and try to bring automation through interfacing with the Oracle E-Business Suite. One interesting solution that I've seen is the Unitask Object Migration Manager. When integrated with Serena TeamTrack, the entire migration process is initiated and managed by the Change Management process. PVCS provides the version management layer. This helps automate the functioning of recording the migration activity, and provides a single point from which to audit all migration and change management activity.
See "http://community.serena.com/files/9b863cec9a/Unitask_Object_Migration_Manager_Battlecard.pdf" for details.
However, it has proven to be a nightmare to development and IT teams, especially when some updates are done to the existing environment, as well as when patching needs to be done. The challenge lies in the way organizations manage the process of changing the application.
Very often, is process is manual. Some organizations have an enterprise change management solution, that they try to manually link (or integrate) with the Oracle E-Business Suite. What does this mean?
Here, the change management process is external to the E-Business Suite, meaning the change control system depends on manual confirmation of external migration activities. This could potentially mean running scripts or executing batch commands to actually perform activities in the Oracle EBS system. Here, the change control system cannot execute the Oracle migration process, thereby introducing a manual layer where an approval is got externally, and the migration process is done through scripts or through a "bubble gum and wire" method.
The challenges lead to a situation where auditing and reporting of change management activity requiring integration of manually obtained information from multiple sources. Sometimes, this means creating manual reports where data does not exist. Auditing and reporting must be timely and accurate. Often, the management does not have hours to wait for such a report.
Automation is a definite benefit here. Integrating the change control system from within the Oracle migration process helps streamline the change management process. Automated interface simplifies and increases control and manageability over the process. This process sits inside the Oracle EBS, and automates and simplifies the migration process, thereby reducing errors and reducing the time-to-deploy. An added benefit is the automated documentation of the migrated objects and the process.
Most commercial offering sit outside of the E-Business Suite, and try to bring automation through interfacing with the Oracle E-Business Suite. One interesting solution that I've seen is the Unitask Object Migration Manager. When integrated with Serena TeamTrack, the entire migration process is initiated and managed by the Change Management process. PVCS provides the version management layer. This helps automate the functioning of recording the migration activity, and provides a single point from which to audit all migration and change management activity.
See "http://community.serena.com/files/9b863cec9a/Unitask_Object_Migration_Manager_Battlecard.pdf" for details.
Subscribe to:
Posts (Atom)
