Configuring after upgrading
Starting with version 5.0.03, BMC has replaced the BMC Release Lifecycle Management common installer with standalone installers for BMC Release Process Management (BRPM) and BMC Release Package Deployment (BRPD) applications.
To successfully use BMC Release Lifecycle Management after you upgrade to version 5.0.03, perform the following configurations.
Adding CORS_ORIGINS property for cross-domain access
The cross-domain access from the RLM Requester UI to the RPM server is ensured by the cross-origin resource sharing (CORS) mechanism. While upgrading from version 4.8 to 5.0.03, the CORS_ORIGINS property is not added to the production.rb file. You must manually add the property and specify the value that matches your requirement.
To add the new property, perform the following steps:
- Go to RLMhome/releases/productVersion/RPM/config/environments, and then open the production.rb file.
Add a CORS_ORIGINS property and specify the value that matches your requirement.
You can specify multiple origin servers, for example, if you are running the RLM Requester UI on two or more servers.- Save the changes.
- Restart the RPM service. For more information, see Starting-or-stopping-product-services.
Restoring embedded PostgreSQL database
If you have installed BRPD and BRPM with an embedded PostgreSQL database by using a common installer, starting version 5.0.03, you must use the standalone installers to upgrade to each product. If you upgrade to BRPM first, the PostgreSQL database version for BRPM is upgraded too, the database for BRPD is no longer available after the upgrade. Before upgrading BRPM, you must back up the PostgreSQL database for BRPD which you can restore later to continue using BRPD.
For example, if you are upgrading BRPM using the standalone installer, back up the PostgreSQL database for BRPD before upgrading the BRPM server. After the upgrade is complete, you can restore the database backup.
Related topics