Applying hotfix

Do the following:

1. Log in as an administrator to the server that hosts the database and save a backup of the database before performing the upgrade.

2. Stop the BMC Release Process Management service for the current version.

   Note

   If you run several instances of BMC Release Process Management connected to the same database for load balancing and clustering purposes, also stop the BMC Release Process Management service for these instances.

3. From the command line, run the following command: 

   • (Windows) dir RLMhome\releases
   • (Linux or Solaris ) cd RLMhome/releases
     

   Note

   Complete steps 3 through 13 on all the other hosts that are part of the cluster.

4. Create a directory with the following name: newProductVersion\RPM. For example, 5003004-HF1\RPM.
5. Copy the downloaded brpm.war file to the RLMhome\releases\newProductVersion\RPM folder.
6. Extract the brpm.war file by using Java Archive Tool, UnZip, 7-Zip, or any other file extractor.
   For example, for Java Archive tool, use the following command:
   %JAVA_HOME%\bin\jar.exe -xvf <RLM_HOME>\releases\<new_product_version>\RPM\brpm.war
7. Copy the following configuration files from RLMhome\releases\previousProductVersion\RPM\config to RLMhome\releases\newProductVersion\RPM\portal.war\WEB-INF\config:
   
   • database.yml
   • automation_settings.rb
   • smtp_settings.rb
   • wicked_pdf_config.rb
   • carrierwave_settings.rb
8. Navigate to the RLMhome\bin directory and update the start file as follows:
   
   • (Windows) Set the value of the CURRENT_RPM_PATH parameter to the directory that you created in step 4.
     set CURRENT_RPM_PATH="RLMHome\releases\newProductVersion\RPM"
   • (Linux) Set the value of the CURRENT_RPM_PATH parameter to the directory that you created in step 4.
     export CURRENT_RPM_PATH="RLMHome\releases\newProductVersion\RPM"
9. On the command line, navigate to RLMhome\bin and run the following command:
   • (Windows) setenv.bat
   • (Linux). ./setenv.sh

10. In the same command line window as the previous step, navigate to RLMhome\releases\newProductVersion\RPM\portal.war\WEB-INF and run the following rake task:

    jruby -S rake --verbose db:migrate RAILS_ENV=production
    

    
    

11. Start the BMC Release Process Management service.

Do the following:

1. Log in as an administrator to the server that hosts the database and save a backup of the database before performing the upgrade.

2. Stop the BMC Release Process Management service for the current version.

   Note

   If you run several instances of BMC Release Process Management connected to the same database for load balancing and clustering purposes, also stop the BMC Release Process Management service for these instances.

3. From the command line, run the following command: 

   • (Windows) dir RLMhome\releases
   • (Linux or Solaris ) cd RLMhome/releases
     

   Note

   Complete steps 3 through 13 on all the other hosts that are part of the cluster.

4. Create a directory with the following name: newProductVersion\RPM. For example, 5003003-HF1\RPM.
5. Copy the downloaded brpm.war file to the RLMhome\releases\newProductVersion\RPM folder.
6. Extract the brpm.war file by using Java Archive Tool, UnZip, 7-Zip, or any other file extractor.
   For example, for Java Archive tool, use the following command:
   %JAVA_HOME%\bin\jar.exe -xvf <RLM_HOME>\releases\<new_product_version>\RPM\brpm.war
7. Copy the following configuration files from RLMhome\releases\previousProductVersion\RPM\config to RLMhome\releases\newProductVersion\RPM\config:
   
   • database.yml
   • automation_settings.rb
   • smtp_settings.rb
   • wicked_pdf_config.rb
   • carrierwave_settings.rb
8. Update the stomp parameter:
   
   1. Go to RLMhome\releases\newProductVersion\RPM\config, and then open the torquebox.yml file in a text editor.

   2. For the stomp parameter, change the host value from localhost to the server IP address or the domain name of your current BMC Release Process Management server.

      Note

      You can copy the valid host value from the torquebox.yml file located in RLMhome\releases\previousProductVersion\RPM\config.

   3. Save your changes to the file.
9. Update the RPM-knob.yml file, as follows:
   
   1. Go to RLMhome\server\jboss\standalone\deployments and then open the RPM-knob.yml file in a text editor.
   2. Change the application root from RLMhome\releases\previousProductVersion\RPM to RLMhome\releases\newProductVersion\RPM.
   3. Save your changes to the RPM-knob.yml file.
10. Navigate to the RLMhome\bin directory and update the start file as follows:
    
    • (Windows) Set the value of the CURRENT_RPM_PATH parameter to the directory that you created in step 4.
      set CURRENT_RPM_PATH="RLMHome\releases\newProductVersion\RPM"
    • (Linux) Set the value of the CURRENT_RPM_PATH parameter to the directory that you created in step 4.
      export CURRENT_RPM_PATH="RLMHome\releases\newProductVersion\RPM"
11. On the command line, navigate to RLMhome\bin and run the following command:
    • (Windows) setenv.bat
    • (Linux). ./setenv.sh

12. In the same command line window as the previous step, navigate to RLMhome\releases\newProductVersion\RPM and run the following rake task:

    jruby -S rake --verbose db:migrate RAILS_ENV=production
    

    
    

13. Start the BMC Release Process Management service.