Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Additional actions after the patch upgrade

The following defects require additional actions if you upgrade from the provided or earlier versions of BMC Release Process Management:

Defect

Description

Upgrade from version

DE87154

In BMC Release Process Management version 4.3.01.07 and earlier, during automation execution, passwords for integration servers are saved without encryption in automation log files.

In BMC Release Process Management version 4.3.01.08 and later, use the SS_integration_password_enc constant to store the encrypted value of the automation server password in automation scripts.

After you upgrade from BMC Release Process Management version 4.3.01.07 or earlier version 4.3.01.08 and later:

  • If you use the imported jira_add_request_issue.rb script, reimport this script.

  • In your custom automation scripts,  use the following function to decrypt the server password:

    decrypt_string_with_prefix(SS_integration_password_enc)

 4.3.01.07

US182803

For the integration with BMC VaraLogix Q Deployment Automation, you can now select channels for deployment. For more information, see Automation scripts for BMC VaraLogix Q Deployment Automation.

To use channels in your automation scripts, update the automation scripts for BMC Application Automation and BMC Release Package and Deployment.

4.3.01.08

DE88874

In database, there are duplicated records for the same version tag.

4.3.01.09

DE82434

When you use LDAP for authorization, users cannot access the assigned requests and steps until you update their user roles.

4.3.01.09

DE88790

When you use integration with BMC Release Package and Deployment for managing NSH server and use NSHuser nameand password in BMC Release Process Management automation steps, the NSH user password is saved as not encrypted text in BMC Release Package and Deployment logs.

Warning: The updated automation scripts work only if you integrate BMC Release Process Management version 4.3.01.12 with BMC Release Package and Deployment version 4.3.01.12. After you install version 4.3.01.12 for both BMC Release Process Management and BMC Release Package and Deployment, update the automation scripts for BMC Release Package and Deployment.

4.3.01.11

To apply updates

To apply the appropriate updates for after the patch installation, complete the following steps:

  1. Depending on your operating system, choose one of the following methods to stop the BMC Release Process Management service for the current version:

      • (Windows) Stop the BMC Release Process Management service through the Services dialog box by navigating to Start > Run > services.msc.
      • (Unix) On the command line, run the /etc/init.d/bmcrpm-4.3.01.11<or your product version> stop command.
  2. Navigate to <RLM_HOME>\bin and run the following executable file:

      • (Windows) setenv.bat
      • (UNIX) setenv.sh

  3. Navigate to <RLM_HOME>\releases\<your current version>\BRPM\WEB-INF and perform the following actions: 

    • To remove duplicated records for the version tag, run the following rake task:

      jruby –S rake version_tags:clear_duplicates

    • To fix the access for requests and steps for the LDAP users, run the following rake task:

      jruby -S rake user:assigned_apps:update_roles RAILS_ENV=production

    • To update automation scripts for BMC Release Package and Deployment, enter the following:

      Note

      If you made changes to the default automation scripts, and then you apply an automatic update for these scripts, your changes are not saved during the automatic scripts update.


      jruby -S rake --verbose scripts:automation:rlm_update

    • To update automation scripts for BMC Application Automation, enter the following:

      Note

      If you made changes to the default automation scripts, and then you apply an automatic update for these scripts, your changes are not saved during the automatic scripts update.


      jruby -S rake --verbose scripts:automation:baa_update

       

  4. Use the appropriate method to start the BMC Release Process Management service based on your operating system:
    • (Windows) Start the BMC Release Process Management service through the Services dialog box by navigating to Start > Run > services.msc.
    • (UNIX) In the command line, run the /etc/init.d/bmcrpm-<your patch varsion> start command.
  5. Start the BMC Release Process Management service.

Related topics

Known-and-corrected-issues

Patch-8-for-Service-Pack-1-version-4-3-01-08

Patch-9-for-Service-Pack-1-version-4-3-01-09

Patch-10-for-Service-Pack-1-version-4-3-01-10

Patch-11-for-Service-Pack-1-version-4-3-01-11

Patch-12-for-Service-Pack-1-version-4-3-01-12

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*