This topic provides instructions on upgrading BMC Release Process Management (BRPM) to 5.0.x. In addition, it provides instructions on applying a hotfix.
If you are using BRPM, you can upgrade these components in any sequence.
| |
---|
| |
| Performing the upgrade (You are here) |
| |
Before you begin
Before you begin the upgrade process, perform the following tasks:
- Extract the downloaded BRPM zip files in a temporary directory.
- BMC recommends that you stop the BRPM service before you upgrade the product database to the new version.
During the upgrade, make sure that you meet the following requirements:
- For HTTP/HTTPS and messaging system ports, use different port numbers for 5.0.x and your current product version.
- All passwords must be at least six characters long and contain at least one letter, one number, and one non-alphanumeric symbol.
Upgrading BMC Release Process Management
You can upgrade from an earlier version of the product to the new BRPM version in one of the following ways:
- By migrating the database from the earlier to new version.
- By using a fresh database for the latest version.
In addition, the upgrade can be performed either to a new installation folder or to the same one as your current version.
Important
The database.yml file contains the following sections:
- Development
- Test
- Production
Before upgrading, you must make sure that the configurations in each of these sections match with each other. You must also make sure that these configurations match with the parameters in the BRPMInstalledConfiguration.xml file present in the location /opt/bmc/RLMhome/.
Upgrading to version 5.0.04 or later
To upgrade to version 5.0.04 or later in a new installation folder
Do the following:
Start the installation program.
Windows:
- To install the product with the administrator privileges, go to RLMinstallationDirectory\RLM\Disk1 and run the setup.cmd command.
- To install the product as a normal user, double-click setup.cmd.
Linux:
- Log in as a root user.
- Navigate to RLMinstallation Directory/RLM/Disk1.
- To make the installation file executable, run the chmod -R +x . command.
- To start the installation program, run the ./setup.sh command.
- On the welcome page of the BMC Release Lifecycle Management 5.0.x Installer wizard, click Next.
- On the license agreement page, select I agree to the terms of the license agreement, and then click Next.
- On the Directory Selection page, specify a new installation directory for BRPM 5.0.x, and then click Next.
- On the Installation Type page, do one of the following, and then click Next.
- If you started the installation program with Administrator or root privileges, select Installer is started with root privileges so perform full installation.
- If you started the installation program without Administrator or root privileges, select Install solution files and configurations. Do not perform tasks that require special rights.
- On the Select features page, select the products and components that you want to upgrade, and then click Next.
- On the BRPM data migration page, in the Copy data from list, do one of the following:
- To skip the database migration, ensure that No migration required is selected, and then click Next.
- To migrate the data from your previous product version, select your current BRPM version, and then specify the following details for migrating your database:
In Existing installation location, specify the directory path to your current product version from which you want to migrate the data.
Tip
The default directory path to your current product version is the following:
- Windows: C:\Program Files\BMC Software\RLM\releases\releaseVersion\RPM
- Linux/Solaris: /opt/bmc/RLM/releases/releaseVersion/RPM
- In Database migration:
- To save your data from the existing database and update the database to the 5.0.x version, select Update database.
- To delete your data from the existing database and update the database to the 5.0.x version, select Clean database (Reset data contents).
- (Optional) Select Copy SMTP configuration settings.
- (Optional) Select Copy automation results.
(Optional) In the Cluster installation section, ensure that the Skip database modification (remote database only) check box is selected if you are installing the product application files and are not making changes to the database.
Note
You can use the Skip database modification option if you install the BRPM product to a node in a cluster and you already have installed the same version of the application and database on another node of the same cluster. For more information, see High-availability-deployment.
- Click Next.
- On the BMC RPM Server Instance type page, select the deployment mode for BRPM, enter the details and click Next:
- To run BRPM as a single instance, select Standalone, and do the following:
- In the Node name box, enter the name of the standalone node.
- In the Node IP box, enter the IP address of the standalone node.
- To run BRPM as a node in the cluster, select Cluster, and do the following:
- In the Node name box, enter the name of the cluster node.
- In the Node IP box, enter the IP address of the cluster node.
- On the JRE Information page:
- To Use the bundled JRE (version <version>), click Next.
- To use any other JRE, clear the Use the bundled JRE (version <version>) check box, click Browse, set the path to the JRE on your computer, and then click Next.
- (This page appears only when you are using http protocol in your existing installation) On the Server HTTPS Port Information page, do one of the following, and click Next:
- Select the Generate Self-Signed Certificate option, and enter the following information if you want to use the self-signed certificate generated by the installer:
- In the HTTPS Port box, enter the HTTPS port number. Default is 8443.
- In the Passphrase box, create a passphrase for your certificate.
- In the Common Name (CN) box, specify the name that represents the server protected by the certificate. For example, SAT.co.in.
- In the Organization Unit (OU) box, specify the name of the name of your organization unit. For example, Accounting.
- In the Organization Name (O) box, specify the name of your organization. For example, SAT Pvt. Ltd.
- In the Locality Name (L) box, specify your city or other locality. For example, Brooklyn.
- In the State Name (S) box, specify the name of your state, province, or other political subdivision. For example, New York.
- In the Country Code (C) box, specify the name of your country. For example, US. You can enter only upto 2 characters.
- Enter the following information if you want to use a third-party SSL certificate:
- In the HTTPS Port box, enter the port number for the SSL connection.
- In the Private Key box, specify the directory path to the private key for SSL encryption.
- In the Certificate File box, specify the directory path to the certificate for SSL connection.
- In the Passphrase box, enter the passphrase for your certificate.
For more information about how to obtain SSL private key, certificate file, and passphrase, see Obtaining-test-SSL-certificates.
On the Super User Details page, provide the superuser credentials, and then click Next.
Notes
- The Super User Details page is not available if you selected to update your database on the BRPM data migration page.
- The superuser is the first user who has administrator access permissions to use BRPM.
- On the JBoss Super User Details page, enter the following details, and then click Next:
- Login: Username for the superuser required to log on to the JBoss server.
- Password: Password for the JBoss superuser
- On the Messaging System Details page, specify the following details to connect to the messaging system server of BRPM, and then click Next.
- Port: Port for the messaging system server that is different from the one used for the previous version.
- User: User name for the messaging system server.
- Password: Password of the messaging system server.
- On the Database details page, specify the relevant details for the database, and then click Next.
On the Email Notification details page, do one of the following, and then click Next.
Note
The Email Notification details page is not available if you selected to copy your SMTP settings from the previous BMC Release Process Management on the BRPM data migration page.
Not to configure email notifications, click Next.
To configure email notification settings, select Use SMTP, and then specify the following SMTP server details:
- SMTP Server: The fully qualified name of the SMTP server used for sending emails.
- SMTP Port: (Default 25) The SMTP server port.
- SMTP Domain: The part of the user name after "xyz@" in your email address. For example, if your user name is redmine@example.net, then your domain name is example.net.
- SMTP Authentication: The authentication mechanism used for your SMTP service. You can select from one of the options in the list displayed.
- SMTP User: The user name used to connect to the SMTP server. For example, redmine@example.net.
- SMTP Password: The password used to connect to the SMTP server.
- TLS: Select this check box if your SMTP server requires a secure connection and is using TLS.
To learn more about email notifications and how to change notification configurations manually, see Changing email notification configuration manually.
Click Next.
- On the Installation Preview page, view the installation details, and then click Install.
To upgrade version 5.0.04 or later in the same installation folder as your current version
Do the following:
Start the installation program:
Windows :
- To install the product with the administrator privileges, go to RLMInstallationDirectory\RLM\Disk1 and run the setup.cmd command.
- To install the product as a normal user, double-click setup.cmd.
Linux:
- Log in as a root user.
- In terminal, go to RLMInstallationDirectory/RLM/Disk1.
- Enter the chmod -R +x . command.
- Enter the ./setup.sh command.
- On the welcome page of the BMC Release Lifecycle Management 5.0.x Installer wizard, click Next.
- On the license agreement page, select I agree to the terms of the license agreement, and then click Next.
On the Directory Selection page, specify your current installation directory for BRPM, and then click Next.
Example
If you installed the previous version of BRPM to /opt/bmc/RLM, then the same path must be specified on the Directory Selection page when upgrading.
- On the Destination Warning page, click Next.
- On the Installation Type page, do one of the following, and then click Next.
- If you started the installation program with administrator or root privileges, select Installer is started with root privileges so perform full installation.
- If you started the installation program without administrator or root privileges, select Install solution files and configurations. Do not perform tasks that require special rights.
- On the feature selection page, view the products and components that will be upgraded, and then click Next.
- On the BRPM data migration page, in the Copy data from list, do one of the following:
- To skip the database migration, ensure that No migration required is selected, and then click Next.
- To migrate the data from your previous product version, select your current BRPM version, and then specify the following details for migrating your database:
In Existing installation location, specify the directory path to your current product version from which you want to migrate the data.
Tip
The default directory path to your current product version is the following:
- Windows: C:\Program Files\BMC Software\RLM\releases\releaseVersion\RPM
- Linux/Solaris: /opt/bmc/RLM/releases/releaseVersion/RPM
- In Database migration:
- To save your data from the existing database and update the database to the 5.0.x version, select Update database.
- To delete your data from the existing database and update the database to the 5.0.x version, select Clean database (Reset data contents).
- (Optional) Select Copy SMTP configuration settings.
(Optional) In the Cluster installation section, ensure that the Skip database modification (remote database only) check box is selected if you are installing the product application files and are not making changes to the database.
Note
You can use the Skip database modification option if you install the BRPM product to a node in a cluster and you already have installed the same version of the application and database on another node of the same cluster. For more information, see High-availability-deployment.
- Click Next.
- On the JRE information page:
- To Use the bundled JRE (version <version>), click Next.
- To use any other JRE, clear the Use the bundled JRE (version <version>) check box, click Browse, set the path to the JRE on your computer, and then click Next.
- (This page appears only when you are using http protocol in your existing installation) On the Server HTTPS Port Information page, do one of the following, and click Next:
- Select the Generate Self-Signed Certificate option, and enter the following information if you want to use the self-signed certificate generated by the installer:
- In the HTTPS Port box, enter the HTTPS port number. Default is 8443.
- In the Passphrase box, create a passphrase for your certificate.
- In the Common Name (CN) box, specify the name that represents the server protected by the certificate. For example, SAT.co.in.
- In the Organization Unit (OU) box, specify the name of the name of your organization unit. For example, Accounting.
- In the Organization Name (O) box, specify the name of your organization. For example, SAT Pvt. Ltd.
- In the Locality Name (L) box, specify your city or other locality. For example, Brooklyn.
- In the State Name (S) box, specify the name of your state, province, or other political subdivision. For example, New York.
- In the Country Code (C) box, specify the name of your country. For example, US. You can enter only upto 2 characters.
- Enter the following information if you want to use a third-party SSL certificate:
- In the HTTPS Port box, enter the port number for the SSL connection.
- In the Private Key box, specify the directory path to the private key for SSL encryption.
- In the Certificate File box, specify the directory path to the certificate for SSL connection.
- In the Passphrase box, enter the passphrase for your certificate.
For more information about how to obtain SSL private key, certificate file, and passphrase, see Obtaining-test-SSL-certificates.
- On the JBoss Super User Details page, enter the following details, and then click Next:
- Login: Username for the superuser required to log on to the JBoss server.
- Password: Password for the JBoss superuser.
On the Messaging system details page, specify the following details to connect to the messaging system server, and then click Next.
Note
The Messaging system details page displays only if your current messaging system password does not match the following pattern:
- At least one letter
- At least one number
- At least one non-alphanumeric symbol
- The Port and Host boxes are dimmed since they use information from your previous installed versions.
- User: User name for the messaging system server.
- Password: Password of the messaging system server.
- On the Database details page, specify the following details to connect to the database server, and then click Next.
- Database: Select your database type, either POSTGRESQL, ORACLE, or SQL_SERVER.
- Host: Host address for the database system server. The Host field is disabled. By default, the installation program detects the IP address of the host computer on which you are installing this product.
- Port: Port for the database system server. The default port value is 5432 (PostgreSql), 1521 (Oracle), and 1433 (SQL_Server).
- RPM Database/SID Name: Specify a database name or identifier (for example, bmc_rpm_db).
- RPM Database User:User name for the database system server.
- RPM Database Password: Password of the database system server.
- On the Installation Preview page, view the installation details, and then click Next.
Post-upgrade tasks
After you complete the upgrade, you might need to perform the following tasks:
- To verify that the upgrade was completed successfully, access the product interface. For more information, see Accessing-the-interface.
- If you cannot access the product from Google Chrome or Mozilla Firefox, clear the browser cache, cookies, and temporary files.
- To fix the SSH and NSH automation scripts after an upgrade to BRPM 5.0.01.00 (for the details, see DRZXB-16048), do the following:
- Go to RLMhome/releases/5.0.01.00/RPM/lib/script_support and open the dispatch_script_header.rb file in a text editor.
- In line 468, value_str = "#{value}".gsub!('"', '\"'), delete ! after the gsub method.
Result: value_str = "#{value}".gsub('"', '\"'). - Save the file, and then restart the services.
- To remove groups and teams automatically created during database migration, see Using a rake task to remove groups and teams.
- To remove manual group assignments for LDAP users, see Using a rake task to remove manual group assignments for LDAP users.
- During upgrade to 5.0.03, 5.0.03.001, 5.0.03.002, or 5.0.03.003, the torquebox.yml file (located at RLMhome\releases\productVersion\RPM\config) is retained from the previous version and it does not get refreshed with the latest version. As a result, live updates fail for requests and the Requester UI does not get refreshed automatically. To fix the issue, do the following:
- Stop the BRPM service.
- Navigate to the RLMhome\releases\productVersion\RPM\config directory for the version to which you have upgraded.
- Copy the attached torquebox.yml file in the config directory.
- Search for the stomp section and update the value of the host parameter.
- Search for the messaging section and update the value of the concurrency parameter.
- Save and close the file.
- Start the BRPM service.
For more information, see Additional-actions-after-the-upgrade.
Where to go from here
Additional-actions-after-the-upgrade