How to do implementation/migration plans reduce migration time in OBIEE

 

Web Catalog Migration Plan

PlanDevelopers must remember to track their Web Catalog changes as they are developing and NOT after they have completed development. It is much too easy to forget to migrate an object if you do not keep track of the change as you were making the change. For example, the above columns can be used by Excel to track Web Catalog changes. Not all columns are necessary for tracking your changes but they can be removed before sending your migration request to the person responsible for migrations.

Repository Migration Plan

Keeping track of individual changes helps the team to determine if all layers of a repository should be migrated or manually recreate the changes in the next environment. In addition, this type of document will help track what changes have been made and have not.

Sound familiar? Developers must remember to track their Repository changes as they are developing and NOT after they have completed development. It is much too easy to forget to migrate an object if you do not keep track of the change as you were making the change.

Code Review & Separation of Duties

Code Review:

• Before implementing changes a code review should be completed by your peers. This will ensure everyone is following „best practices‟ and your design meets expectations.

• Having peer reviews at project milestones helps keep the project on track and allows for time to make adjustments. 

Separation of Duties:

• When implementing into production a „best practice‟ is to have a designated "production implementer‟ carry out the implementation plan. This will help prevent malicious or poorly tested code from going into production since this implementer will request sign off from the end users who tested and own the changes.

• If the implementer was the developer who made the change in a lower instance then a backup implementer should be utilized.

• SOX Compliance.

Do not overlook these steps as a stepping stone to a successful implementation and project. While these extra steps may take time to complete they prevent major surprises and force team members to adhere to strong development principles that produce a consistent, quality product.