Prepare for Release Management
Create Security Roles
Security plays an important role in the Release Management process. The Security Manager will need to set security levels for configurors and managers who are involved in the Release Management process. Several sample security roles are provided below to demonstrate a typical security breakdown but this can be modified to meet specific business needs. The Release Management folders in the Rules Palette are not visible to users unless they have received a security role with release management privileges.
Sample Security Roles
Configuration Analyst: This role is responsible for creating Configuration Packages. Typical security privileges would include:
- ConfigPackage-Add
- ConfigPackage-ReadyToMigrate
- ConfigPackage-Remove
- ConfigPackage-ViewOwned
- BusinessRules- All Non-Administration Rules-Check-In/Check-Out
- Administration- All Non-Security Administration-Check-In/Check-Out
- Administration- All Non-Security-View
Configuration Lead: This role is responsible for reviewing all Configuration Packages and resolving any rule conflicts. The Orphan Rules Configuration Package must also be reviewed by this role to ensure that any deleted rules are not needed in any other Configuration Package. Typical security privileges would include:
- ConfigPackage-ViewAll
- ConfigPackage-PutOnHold
- ConfigPackage-TakeOffHold
- MigrationSet-ViewAll
Build Manager: This role is responsible for reviewing Migration Sets and creating and building Release Packages. Typical security privileges would include:
- ConfigPackage-ViewAll
- MigrationSet-ViewAll
- ReleasePackage-Build
- ReleasePackage-Create
- ReleasePackage-ViewAll
- Administration- All Non-Security-View
Rules Architect: This role is responsible for managing a high level view of the complete Release Management process and tracking the progress at the various stages. Typical security privileges would include:
- ConfigPackage-ViewAll
- MigrationSet-Create
- MigrationSet-ViewAll
- ReleasePackage-ViewAll
- Administration- All Non-Security-View
Release Manager: This role is responsible for finalizing the Release Package and deploying it to the target environment. Typical security privileges would include:
- MigrationSet-ViewAll
- ReleasePackage-Deploy
- ReleasePackage-ViewAll
- Administration- All Non-Security-View
Prepare for Versioning
This process should be performed according to the status of the configuration in the affected environments. If active configuration has not yet taken place, then follow the steps outlined in the Pre-Configuration IVS Initialization Process for Versioning. If active configuration has already begun in the environments, then follow the steps outline in the Post-Configuration IVS Initialization Process for Versioning.
Pre-Configuration IVS Initialization Process for Versioning
This process assumes active configuration has not begun against the affected environments. If configuration has begun and this process was not run beforehand, then please use the Post-Configuration IVS Initialization Process for Versioning.
- Make sure all active environments are set up and properly aligned with your migration strategy in their corresponding Web Application Utility.
- Stop all Rules Palette configuration and any OIPA applications running against the databases where you are planning to implement Versioning and Release Management.
- Execute the ClearIVS.sql script against the IVS database. These scripts will leave current security intact. The scripts are provided in Appendix A of this document.
- Choose a baseline OIPA database that all other OIPA databases will be based upon.
- Take a full backup of the baseline OIPA database.
- Restore the baseline OIPA backup to all remaining OIPA databases that will be a part of the IVS/RM ecosystem.
- Restart all Web Application Utilities.
- Start the newest version of the Rules Palette and create new environments for each of the OIPA applications/databases.
- Run the Version Generator in "Generate New Versions" mode against the baseline environment.
- Run the Version Generator in "Generate Reference Versions" mode against all remaining environments (one environment at a time), choosing the baseline environment as the reference.
- Restart all OIPA applications.
- Login to all OIPA application environments to assure that the environment is up and running. Login to all Rules Palette environments to make sure the Rule Palette environments are set up correctly. Verify in all environments that one of each rule type is present and has the correct version associated with it (at this point, all versions will be 1).
- There is also an optional step to use the Diff Report tool in the Rules Palette to confirm that the same information exists in both databases. This tool and the process for using it are documented in the Rules Palette help system within the application.
Post-Configuration IVS Initialization Process for Versioning
This process assumes active configuration has already begun against the affected environments. If configuration has not yet begun, then please use the Pre-Configuration IVS Initialization Process for Versioning.
- Make sure all active environments are set up and properly aligned with your migration strategy in their corresponding Web Application Utility.
- Notify ALL configurors/testers to stop work on affected environments.
- Stop all Web Application Utilities and OIPA applications running against the databases where you are planning to implement Versioning and Release Management.
- If you want to retain your current Versioning/Release Management system for audit purposes, take a backup of the IVS database.
- Execute the ClearIVS.sql script against the IVS database. These scripts will leave current security intact. The scripts are provided in Appendix A of this document.
- Choose a baseline OIPA database that all other OIPA databases will be based upon.
- Take a full backup of the baseline OIPA database.
- Restore the baseline OIPA backup to all remaining OIPA databases that will be a part of the IVS/RM ecosystem.
- Restart all Web Application Utilities.
- Start the newest version of the Rules Palette and create new environments for each of the OIPA applications/databases.
- Run the Version Generator in "Generate New Versions" mode against the baseline environment.
- Run the Version Generator in "Generate Reference Versions" mode against all remaining environments (one environment at a time), choosing the baseline environment as the reference.
- Restart all OIPA applications.
- Login to all OIPA application environments to assure that the environment is up and running. Login to all Rules Palette environments to make sure the Rules Palette environments are set up correctly. Verify in all environments that one of each rule type is present and has the correct version associated with it (at this point, all versions will be 1).