|
Oracle® Rules Palette Release 9.1.0.0.0 E15811-01 |
The Release Management process allows you to control the flow of database information from a source environment to a target environment. You can create configuration packages containing business rules, transactions, stored procedures, DML scripts and DDL scripts. These configuration packages are then bundled into a migration set, which can be released and deployed to the target environment.
There are two steps that must be completed in order to set-up Release Management:
Identify the source and target environments by modifying the asenv.properties file for both environments. This turns on the release management functionality and identifies the database source information.
Create security roles so that users can view release management functionality.
Process Overview
There are several steps that must be completed to move through the release process. First you must create a configuration package. Once it is complete, you will mark it ready to migrate and then a migration set will be created. A release package is then created. You will build the package and promote the package. After all these steps have been completed, a release manager will deploy and promote the package in the target environment.
Note: Before making any changes and migrations, make sure all environments in the development track are in sync with respect to their rules configuration.
Once Release Management has been set-up in your source environment, you can begin creating configuration packages. You should see a node for configuration packages under your environment name in Main Explorer. If the node is not present, contact your Security Manager to receive the proper security role.
The configuration packages node on the Main Explorer holds the configuration packages that you have created. You will not be able to see the packages created by other users. When you first begin the release management process, this folder will be empty until you create your first package. Packages are removed from this folder once they have been labeled Ready to Migrate.
Configuration Package right-click menu
Ready to Migrate: select this option when you are done creating your configuration package. The rules and transactions associated with your package will unlock and be available for use.
Put on Hold: select this option when you are not ready to migrate but you want to release the rules and transactions associated with your package so that they are available for other users.
Add Non-Palette Items: select this option to attach stored procedures, DDL scripts, or SQL scripts to your configuration package.
After a configuration package is marked Ready to Migrate, the package is moved to the Migration Sets folder in Release Management, which is located on the Admin Explorer tab. The Build Manager (or BA with administrative privileges) will create a migration set that includes the configuration package as well as any other packages that are relevant.
Release Management Folder Hierarchy
Migration Sets: right-click to create a migration set. You will select configuration packages to add to the migration set.
Release Packages: right-click to create release package. You will select one migration set for the release package.
Name of Release Package you created: right-click on the name of the release package to build the package. Right-click again to promote the package. You will only see the right-click option for the stage that the release package is currently in. For example, if it has already been built, you will only be able to promote.
Once you promote the migration set, it will move from the Built folder to the Promote folder. The package will continue to move through the folder structure as it advances through the release process.
After the migration set is created, you will need to create a release package. The migration set will remain in the Migration Set folder.
After the release package is created, the Build Manager will need to go back to the Release Management folder in Admin Explorer. From that folder the release package can be built by right-clicking the package and selecting Build Release Package. Once the package is built, the right-click menu option will change to Promote.
After you promote the package, you need to log-out of your source environment and log-in to your target environment. From the Admin Explorer, you will see the Release Management node. Open the folder and look for Release Packages. Your release package should be listed under the Release Package node. First you will deploy the package and then you will promote the package. After you have completed these two actions, you will no longer have a right-click action menu for the release package. The migration is complete.
