Important

   

Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

BSA 8.9.01 Rolling Update 3 (RU3)

This topic contains instructions for downloading and installing Rolling Update 3 on BMC Server Automation (BSA) 8.9 SP1. A Rolling Update provides product fixes by updating specific files in existing BSA components, thus delivering the latest product fixes without having to upgrade the entire product. Rolling Updates are installed on top of a service pack without affecting the product version or build number.

Important

The Rolling Updates discussed in this page can only be installed on BMC Server Automation 8.9 SP1. Do not install the updates on any other release of BMC Server Automation.

Rolling Updates available for 8.9 SP1

The following table lists the Rolling Updates provided for BMC Server Automation 8.9 SP1 along with their release dates.

Base ReleaseBuild numberRolling UpdateRelease date


Service Pack 1 for BMC Server Automation 8.9


8.9.01.68

Rolling Update (RU) 3November 9, 2017
Rolling Update (RU) 2September 11, 2017
Rolling Update (RU) 1July 28, 2017

Note

You can install a newer Rolling Update on top of a previously installed Rolling Update as long as the base release is the same. For example, you can install RU 3 over RU 1 or RU 2, as long as the base release has not been upgraded to a higher version.

Preparing for installation

Before you begin installing the Rolling Update, check the following prerequisites:

  • BMC recommends that you to go through the list of product fixes mentioned here.
  • (Optional) You have an Integrated Development Environment (IDE) or DB client command line tool, such as SQL *Plus or sqlcmd, set up to run the RU 3 DB update scripts on your database.

Download the latest available Rolling Update

You can access and download the installation files for RU 3 from the following FTP location:

Note

You must be logged on to this page to view the FTP URL.

 Click here to expand the MD5 and checksum related infromation for the files

Verify the downloaded content by using the following check sums:

Linux Application Server files

File Name

MD5SUM

BSAAPPSERVER-89SP1-RU3-68-LIN64.zip
c38634313bc0e8efbefeaec4c083c5b6

Linux Console (RCP) files



BBSACONSOLE89-SP1- RU3-112-LIN64.zip
6a08de82cd1a0d0c0a65649cb078f001
BBSACONSOLE89-SP1- RU3-112-LIN32.zip
631c5559977f771fd539097494e5c9ff


Windows Application Server files

File Path and Name

MD5SUM

BSAAPPSERVER-89SP1-RU3-68-WIN64.zip

02bcff3b5924062fc34bbdb7520c3096

Windows BSA Console (RCP) files

File Name

MD5SUM

BBSACONSOLE89-SP1- RU3-112-WIN64.zip
df1d76fd0cba0c973b30a6edd194f495
BBSACONSOLE89-SP1- RU3-112-WIN32.zip
a82ee5d21b30e8072a7fedd8c22942eb

Download and extract the required zip packages on your Application Servers, host running the database client software, and BSA console servers as described below:

  • Downloading the files on your Application Servers
    1. Depending on the type of operating system running on your Application Servers, download either of the following zip packages from the FTP location.

      Windows

      89SP1_RU3\BSAAPPSERVER-89SP1-RU3-68-WIN64.zip

      Linux

      89SP1_RU3\BSAAPPSERVER-89SP1-RU3-68-LIN64.zip

    2. Copy and extract the zip package to temporary folder (for example /tmp on Linux or C:\temp on Windows) on your Application Servers.

  • Downloading the files on your database server

    1. Depending on the type of operating system running on your host running the database client software, download either of the following zip packages from the FTP location.

      Windows

      89SP1_RU3\BSAAPPSERVER-89SP1-RU3-68-WIN64.zip

      Linux

      89SP1_RU3\BSAAPPSERVER-89SP1-RU3-68-LIN64.zip

    2. Copy and extract the zip package to temporary folder (for example /tmp on Linux or C:\temp on Windows) on your host running the database client software.

  • Downloading the files on your BSA Console servers

    1. Depending on the type of operating system running on your BSA Console server, download either of the following zip packages from the FTP location.

      Windows

      89SP1_RU3\BSACONSOLE_89SP1-RU3\BBSACONSOLE_WINDOWS_89SP1-RU3

      Linux

      89SP1_RU3\BSACONSOLE_89SP1-RU3\BBSACONSOLE_LINUX_89SP1-RU3

    2. Copy and extract the zip package to temporary folder (for example /tmp on Linux or C:\temp on Windows) on your BSA console server.

Step 1: Installing on all Application Servers in your environment

Perform the following steps on all Application Servers in your BMC Server Automation environment:

  1. Log on to your Application Server with a user having root or Administrator privileges.

  2. Navigate to the temporary location where you have extracted the installation files, as described in this step.
  3. Execute the rollingUpdateInstaller.nsh script using the following command in cmd or shell terminal:
    nsh rollingUpdateInstaller.nsh

    Tip

    The Application Server will restart twice for the installation to complete successfully.

  4. The following message is displayed:
    #### Rolling Updatation Completed Successfully ####
    Repeat the above steps on all other Application Servers in your environment.

    Warning

    Wait for the installation process to complete successfully on one Application Server, before beginning the installation process on another Application Server. Running installations on different Application Servers simultaneously will result in errors during installation.

  5. Verify whether all Application Servers have been updated successfully by running the following SQL query in your database:
    Select ID, RU_VERSION, STATUS, APPSERVER_NAME, EXECUTION_TIME from ROLLING_UPDATE;

    Expected output
    ID RU_VERSION      STATUS  APPSERVER_NAME                              EXECUTION_TIME
    ---------- ---------------- -----------------------------------------------------------------
    1 8.9.01.68-RU3    success bsaappserverhost01                    27-OCT-17 04.10.53.634000 PM

Step 2: Applying the RU 3 update to the BSA Database

Ensure that you perform the RU 3 database update steps only after you have installed the update on all Application Servers in your environment.

  1. Stop all Application Servers running in your environment (see Starting and stopping BMC Server Automation components).
  2. Navigate to the temporary location where you have extracted the installation files, as described in this step.

  3. Depending on which database you are using, navigate to either of the following paths in the temporary location:

    Oracle<temporary_location>\postinstall\db\oracle
    MS SQL<temporary_location>\postinstall\db\sqlserver
  4. Extract the QM002315851_Remediation and QM002245450_Remediation zip packages and move the contents to a location on the host running the database client software, from where you can use SQL *Plus or sqlcmd (or any IDE) to connect to the BMC Server Automation database schema.

    Note

    If you are using BMC Decision Support for Server Automation (BDSSA), you must apply the hotfix related to QM002245450. For information about the hotfix, see https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA21O000000oVulSAE&type=Solution.

  5. Navigate to the location on the host running the database client software where you have moved the extracted scripts.

  6. Depending on whether you are using an MS SQL server or an Oracle database server, select the appropriate tab below and perform the steps on your database. Although you can execute the scripts using any IDE, the below examples provide steps that are specific to SQL *Plus and sqlcmd.

      1. Open command prompt or shell, and navigate to the temporary location on the host running the database client software where the files are copied.
      2. Connect to SQL *Plus using the following command:
        sqlplus <username>/<password>@tnsentryforbsadb
      3. Run the scripts provided in the temporary location using the following commands:

        Location of the script inside the zip package Command
        /QM002245450_Remediation/oracle start QM002245450_Remediation.sql

        /QM002315851_Remediation/oracle

        start QM002315851_Remediation.sql
      1. Open command prompt or shell terminal and navigate to to the temporary location on the host running the database client software where the files are copied.

      2. Use the sqlcmd utility to execute the extracted scripts. Enter the following commands:

        • sqlcmd -S <DB-Server-Name> -d <database-name> -U <user-name> -i QM002315851_Remediation.sql

          Replace the variables with the values described in the table below:

          Variable Value
          <DB-Server-Name> Name of the MS SQL server
          <database-name> Name of Bladelogic database
          <user-name> User name of to log in to the database

          Location of the script inside the zip package: \QM002245450_Remediation\sqlserver


        • sqlcmd -S <DB-Server-Name> -d <database-name> -U <user-name> -i QM002245450_remediation.sql

          Replace the variables with the values described in the table below:



          <DB-Server-Name> Name of the MS SQL server
          <database-name> Name of Bladelogic database
          <user-name> User name of to log in to the database

          Location of the script inside the zip package: \QM002315851_Remediation\sqlserver

    • Start all the Application Servers in your environment (see Starting and stopping BMC Server Automation components).

    Step 3: Upgrading the BSA Console server

    (This is an optional step and can be skipped if you do not want to install BSA Console-related product fixes.)
    To install BSA Console-related fixes you must upgrade all BSA Console servers in your environment as described in the steps below:

    Important

    If you have a BSA console installed on the same server as your BSA Application Server, do not perform this procedure. You can only upgrade BSA Consoles in your environment, which are not installed on the same server as the BSA Application Server.

    1. Ensure that you have exited from all BSA Console (RCP) instances on the server.
    2. Navigate to the temporary location where you have extracted the installation files, as described in this step.

    3. Depending on whether your BSA Console is running on a 32-bit or 64-bit server, copy and extract either of the following zip packages:

      32-bit Windows server

      BBSACONSOLE89-SP1- RU3-112-WIN32.zip

      64-bit Windows server

      BBSACONSOLE89-SP1- RU3-112-WIN64.zip

      32-bit Linux server

      BBSACONSOLE89-SP1- RU3-112-LIN32.zip

      64-bit Linux server

      BBSACONSOLE89-SP1- RU3-112-LIN64.zip

    4. Run the installer file provided inside the zip package (BBSACONSOLE89-SP1- RU3-112-WIN32.exe, BBSACONSOLE89-SP1- RU3-112-WIN64.exe, BBSACONSOLE89-SP1- RU3-112-LIN32.bin, or BBSACONSOLE89-SP1- RU3-112-LIN64.bin ) to upgrade your BSA Console.
    5. Launch the upgraded BSA Console and connect to the BSA Application Server.

    6. Click the Help menu and select About BMC Server Automation Console.

    7. Verify that the BSA Console version is updated to 8.9.01.112.

    Product fixes

    BSA Rolling Updates are cumulative type of updates. When you install a particular Rolling Update, product fixes from earlier updates are also added to the product. For example, when you install RU 3, all product fixes added in RU 1 and RU 2 will also be installed along with RU 3 product fixes. See the below table for a list of product fixes and the Rolling Update that they were corrected in.

    Tip

    Depending on which component fixes you wish to install you can perform either of the following:

    • To install only Application Server-related fixes:
      Perform Step 1: Installing on all Application Servers in your environment and Step 2: Applying the RU 3 update to the BSA Database.
    • To install Console- and Application Server-related fixes:
      Perform Step 1: Installing on all Application Servers in your environment, Step 2: Applying the RU 3 update to the BSA Database, and Step 3: Upgrading the BSA Console server.


    Start adding filters for your table either in the macro settings or on the filtration pane.

    Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

    The table is being loaded. Please wait for a bit ...
    Defect IDCategoryDescriptionCorrected in
    QM002307545Application ServerNSH_Proxy.Connect authorization is required by roles running NSH script jobs.RU 1

    QM002146157


    Application Server

    OCSP validation during PKI authentication does not work as expected on BSA 8.7.

    RU 1

    QM002208472


    Application Server

    objects created in nsh job via blcli server do not have the correct permissions

    RU 1

    QM002270287


    Application Server

    The BLCLI command BlPackage.importDepotObjectToPackage ignores the rebootMode argument.

    RU 1

    QM002277813


    Application Server

    Blcli_connect and blcli_disconnect services must be manually stopped when BLCLI server service is started.

    RU 1

    QM002316960


    Application Server

    The following error is encountered when remediating on a Solaris target server, if the Solaris Live upgrade property is set to true.
    Error: null when creating remediation artifacts

    RU 1

    QM002283980


    Application Server

    The BLCLI command Delete cleanupAgent deleted the tx_config.cfg file from the location: /usr/nsh/NSH/Transactions/

    RU 2

    QM002289074


    Application Server

    Patch remdiation on AIX 7.1 hangs if remediation involves moving files.

    RU 2

    QM002309878


    Application Server

    NSH proxy service appears as it is down even though it is still running.

    Workaround: Restart the Application Server to reflect the correct status of the NSH proxy service.

    RU 2

    QM002321714


    Application Server

    Unable to connect to standalone NSH proxy, even with a role assigned with NSH_Proxy.Connect.

    RU 2

    DRBLG-108282

    Application Server

    Added ACI switch support.

    RU 2

    QM002331683

    Application Server

    Even after applying BMC Server Automation 8.9.01 Hotfix 2, the versions number appears as 8.9.01.00.

    RU 2

    QM002248162

    Application Server

    Clicking on Maintenance Window throws an error, because RBAC Cleanup deletes all ACLs associated with Maintenance Windows.

    RU 2

    QM002264788

    Application Server

    NSH Proxy/Job servers causing stale nsh ssue

    RU 2

    QM002268236

    Application Server

    Smart job group creation is fails in job group through blcli in 8.9 SP1.

    RU 2

    QM002265299

    Application Server

    DBM offline "-state" command shows invalid modules progress and deletes improper data on customer db.

    RU 2

    QM002315851

    Application Server

    Extended property is blank in SUSE Linux patching jobs.

    RU 2

    QM002296014
    QM002301780

    Application Server

    To create a Red Hat PAJ using the blcli and set the "Specify Package Name Options for Analysis"

    RU 3

    QM002336530

    Application Server

    Auto-remediation generated deploy job does not consider Single job mode option.

    RU 3

    QM002344170

    Application Server

    Windows 2016 template in CSM_Virtual_Guest_Packages is displayed as Novell Open Enterprise Server.

    RU 3

    QM002245450

    Application Server

    All CVEs for a Microsoft Bulletin are not associated with the Microsoft Bulletin in the BSA patch catalog. This prevents the Portal from mapping all CVE items present in the Microsoft Bulletin.

    If you are using BMC Decision Support for Server Automation (BDSSA), you must apply the hotfix related to QM002245450. For information about the hotfix, see https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA21O000000oVulSAE&type=Solution.

    RU 3

    QM002347135

    Application Server

    BLCLI Email sendMail with multiple lines in the body generates error.

    Workaround: Disable BLCLI server and use blcli_execute.

    RU 3

    QM002347540

    Application Server

    BLCLI utility getCurrentUserName throws an error.

    Workaround: Disable BLCLI server and use blcli_execute.

    RU 3

    QM002349767

    Application Server

    BLCLI Email sendMailWithAttachment does not work with Scandinavian characters in subject.

    RU 3

    QM002327113

    Console

    Update Server Properties populates OS_VERSION property as "UNKNOWN" for targets running RHEL ComputeNode release”

    RU 1

    QM002297941

    Console

    Key combination does not work as expected in 8.9.01.68 BSA console, after opening Depot Script by double-clicking.

    RU 1

    QM002307443

    Console

    8.9.01.68 32-bit client is broken.

    RU 1

    QM002268236

    Console

    Smart job group creation fails for job group through blcli in 8.9SP1.

    RU 2
    Was this page helpful? Yes No Submitting... Thank you

    Comments