|
Oracle® Rules Palette Release 9.1.0.0.0 E15811-01 |
You can create configuration packages by checking-out rules, transactions or segments and assigning them to a configuration package or you can create configuration packages right from the Main Explorer. Just right-click on the Configuration Package node and select New Configuration Package.

Your security level will determine if you can view all configuration packages or only the ones you create. Configuration packages display under the Configuration Package node. Each package contains folders for the items that can be included in the package. You will see the items you add to the configuration package in the respective folder. Business rules added to the package will display under the business rule folder. Stored Procedures added to the package will display under the Stored Procedures folder and so forth.

Note: In the 9.1.0.0.0 release of the Rules Palette, release management does not support Inquiry, Batch or File. You will not be able to add these types of screens to a configuration package.
Steps to Create Configuration Package
Check-out the .xml file for the first item in your configuration package. The Add to Configuration window will open.
Select a configuration package from the drop down list or select New Configuration Package and enter the new package name.
Click OK. If the item is already locked in another configuration package, then you will receive a Configuration Package Lock message. You can contact the package owner or the system administrator to gain access.

Make any necessary updates to the item and save the changes.
Continue adding all necessary business rules and transactions.
Open the Main Explorer tab.
Open the configuration packages folder. You should only see the configuration packages that you have created.
Right-click on the configuration package you are building and select Add non-palette items.
Enter the stored procedure information and click Attach.
Right-click on the configuration package you are building and select Ready to Migrate. Your configuration package will disappear from the configuration packages node because it has been moved up to the migration set level. Only users with security permissions to view migration sets will be able to view the package.
You can also create an empty configuration package from the Release Management node in the Admin Explorer. Click the Admin Explorer tab and open the Release Management folder under Administration.
You are now ready to add your configuration package to a migration set.