Cheat sheet for upgrading individual BMC Server Automation components

This topic provides a list of the steps required to upgrade BMC Server Automation, versions 8.6 and later. This topic is targeted to experienced BMC Server Automation users, and does not include relevant planning and prerequisite information.  

BDSSA upgrade requirement


If your BMC Server Automation environment includes BMC BladeLogic Decision Support for Server Automation, upgrade BMC BladeLogic Decision Support for Server Automation before upgrading BMC Server Automation. For more information, see the following topic in the Decision Support for Server Automation online technical documentation:

 Upgrading


Use this method for upgrading the product if you are upgrading from an x86 32-bit environment, if you have a mixture of 32-bit and 64-bit Application Servers or you have -local installed Application Servers (that is a self-contained application server install)

Tip

Prior to upgrading your production environment, it is best practice to test the upgrade in a duplicated environment.

If you are not an experienced user, see the related topics listed in the table to review the required planning information for upgrading the product.


StepDescription
1Prepare the environment for upgrade

To prepare the environment for upgrade:

    Perform these tasks in order. Many steps are prerequisites for other steps that occur later in the process.

    1. Back up the BMC Server Automation database. The data upgrade occurs in place. If, for any reason, it should become impossible to complete the upgrade, the only way to restore the database to its pre-upgrade state is from the backups.
    2. Ensure that your connection to Microsoft SQL database is not encrypted. BMC Server Automation does not support using an encrypted Microsoft SQL database connection at the time of upgrade. However, after the product is upgraded successfully, BMC Server Automation can use an encrypted connection to communicate with the Microsoft SQL database.
    3. Shut down the BMC Server Automation environment:
      1. Stop the Application Server
      2. Stop the PXE server. See Starting and stopping a PXE server.
    4. Back up the installation directories for all Application Servers and PXE servers. Note that the user who installed the earlier version of the product might have changed the installation directory from the default location, so ensure that you have the right location. If your current installation is already an upgrade from a previous version, the paths might be different, due to differences in these locations in earlier versions of BMC Server Automation. If you do not know the installation location for BMC Server Automation components view the contents of the %WINDIR%\rsc\HOME file.

      The default installation locations are:

      • Application Server: C:\Program Files\BMC Software\BladeLogic\NSH
      • PXE Server: C:\Program Files\BMC Software\BladeLogic\PXE
        If you are upgrading the PXE server, follow the upgrade instructions for Windows or UNIX, to prevent loss of configuration settings.

      Important

      Ensure that all files and folders in the installation directory and its sub-directories do not have the read-only attribute enabled. The upgrade might fail, if the read-only attribute is enabled on any file.

       

    5. Ensure that there is an RSCD agent installed on each Application Server to avoid potential errors in the upgrade process.

    6. Ensure that there is an RSCD agent and NSH are installed on the PXE server.

    7. Make sure that you have 4 GB on disk with temp space and 4 GB on disk with installation directory.
    8. Ensure that you have disabled the NSH proxy on all Application Servers in the environment to avoid failure during upgrade. To disable the NSH proxy, run the following command on the NSH client:

    9. secadmin -m default -p 5 -T encryption_only -e tls -appserver_protocol clear
      This command temporarily removes the appserver_protocol=ssoproxy entry from the default line in the secure file (in the rsc folder).

      Note: After the upgrade completes, remember to add this entry back into the secure file. You can use the following command:
      secadmin -m default -p 5 -appserver_protocol ssoproxy

      10. Ensure that MicrosoftVisual C++ 2015 Redistributable Update 3 is installed on the server. For more information, see Installing an RSCD agent (Windows).

      Note

      As a prerequisite to install Microsoft Visual C++ 2015 Redistributable Update 3 on Windows 2012 R2, you must have the following patches installed on your server:

      • KB2919442 - This patch is required for KB2919355.
      • KB2919355 - This patch requires several other patches (clearcompressionflag.exe, KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018). These are available on download KB2919355 page.

      For more information about the prerequisites for Microsoft Visual C++ 2015 Redistributable Update 3, refer to the Microsoft documentation here.



    Perform these tasks in order. Many steps are prerequisites for other steps that occur later in the process.

    1. Back up the BMC Server Automation database. The data upgrade occurs in place. If, for any reason, it should become impossible to complete the upgrade, the only way to restore the database to its pre-upgrade state is from the backups.
    2. Shut down the BMC Server Automation environment:
      1. Stop the Application Server.
      2. Stop the PXE server. See Starting and stopping a PXE server.
    3. Back up the installation directories for all Application Servers and PXE servers. Note that the user who installed the earlier version of the product might have changed the installation directory from the default location, so ensure that you have the right location. If your current installation is already an upgrade from a previous version, the paths might be different, due to differences in these locations in earlier versions of BMC Server Automation. If you do not know the installation location for BMC Server Automation components view the contents of the /usr/lib/rsc/HOME file (on Linux or UNIX) or the %WINDIR%\rsc\HOME file (on Windows).

      The default installation locations are:

      • Application Server: /opt/bmc/bladelogic/NSH
      • PXE Server: /opt/bmc/bladelogic/NSH
        If you are upgrading the PXE server, follow the upgrade instructions for Windows or UNIX, to prevent loss of configuration settings.
    4. Ensure that there is an agent installed on the Application Server. For agent installation on Linux or UNIX, use the -local option (as discussed in Installing components in non-default installation paths using the local flag). Similarly, if an RSCD agent and NSH are not already installed on the PXE server, install them now.

    5. Ensure that you have 4 GB on disk with temp space and 4 GB on disk with installation directory.
    6. Ensure that you have disabled the NSH proxy on all Application Servers in the environment to avoid failure during upgrade. To disable the NSH proxy, run the following command on the NSH client:
      secadmin -m default -p 5 -T encryption_only -e tls -appserver_protocol clear
      This command temporarily removes the appserver_protocol=ssoproxy entry from the default line in the secure file (in the rsc folder).

      Note: After the upgrade completes, remember to add this entry back into the secure file. You can use the following command:
      secadmin -m default -p 5 -appserver_protocol ssoproxy




    Note: For performance reasons, close down any open BMC Server Automation Consoles prior to upgrading. Open consoles do not affect the upgrade, but can cause performance issues post-upgrade.

    Related topics:

    Preparing to upgrade individual components on UNIX and Linux

    Preparing to upgrade individual components on Microsoft Windows

    See these topics for additional upgrade considerations and supported upgrade paths.

    2Stop the environment

      To stop the Application Server:

      The stop operation ends running jobs and stops the Application Server, providing a controlled shutdown. You can select options for managing the running jobs. You cannot use the stop operation on an Application Server to which a BMC Server Automation Console is connected.

      1. In the BMC Server Automation Console, from the Configuration menu, select Infrastructure Management.
      2. Expand the Application Servers node.
      3. Right-click the Application Server and select Stop.
      4. In the Stop Application Server dialog box, select the method for managing any running jobs:
        • Stop immediately without waiting for running jobs to finish.
        • Stop when all running jobs finish.
        • Stop when all running jobs finish or after specified number of minutes, whichever comes first.
      5. Click OK.

      Allow a window of time (an hour or so, if possible) to ensure that any running jobs have stopped, and then stop the Application Server service, which will stop the Application Server launcher.

      1. Select Start > Run.
      2. Enter services.msc in the Open field and click OK.
      3. Right-click- BladeLogic Application Server and select Stop from the pop-up menu.

      Related topic: Starting and stopping BMC Server Automation components

      To stop the PXE server:

      1. Select Start > Settings > Control Panel > Administrative Tools > Services. 
      2. Right-click BladeLogic PXE Server and select Stop.

      Related topic: Starting and stopping a PXE server

      To stop the Application Server:

      The stop operation ends running jobs and stops the Application Server, providing a controlled shutdown. You can select options for managing the running jobs. You cannot use the stop operation on an Application Server to which a BMC Server Automation Console is connected.

      1. In the BMC Server Automation Console, from the Configuration menu, select Infrastructure Management.
      2. Expand the Application Servers node.
      3. Right-click the Application Server and select Stop.
      4. In the Stop Application Server dialog box, select the method for managing any running jobs:
        • Stop immediately without waiting for running jobs to finish.
        • Stop when all running jobs finish.
        • Stop when all running jobs finish or after specified number of minutes, whichever comes first.
      5. Click OK.

      Allow a window of time (an hour or so, if possible) to ensure that any running jobs have stopped, and then stop the Application Server service, which will stop the Application Server launcher.

      • Type the command:/etc/init.d/blappserv stop

      Related topic: Starting and stopping BMC Server Automation components

      To stop the PXE server:

      • Type the command:/etc/init.d/blpxe stop

      Related topic: Starting and stopping a PXE server

      3Download the files

      Download and extract the installation package to a temporary location


      1. Download the BBSA87-<platform>.zip file to the host computer of the Application Server
      2. Extract the contents of the file to a temporary location:<temporary location>/Disk1/files
      4Run the configurator utility on all Application Servers and PXE Servers to migrate configuration data

      The configurator performs a database migration and then persists configuration data into the database.

        To run the configurator utility, you must use the unified product installer package for Windows and perform the following steps. Ensure that you have shut down all Application Servers and PXE servers before you proceed with the following steps. Perform these steps on each and every Application Server and PXE server to copy the data from blasadmin into the database.

        Using interactive installation with the GUI

        1. Download and extract the Windows installation package for the operating system level and hardware platform in a <temporary directory> on the Application Server or PXE server. The package follows the naming convention BBSA<version>-<platform>.zip, and contains the unified product installation program files.

        2. Navigate to the <temporary location> directory containing installation files.

        3. Run the setup.exe installation file with the STATELESS option. The –J STATELESS_ONLY=true option is necessary only for a 64-bit platform. It is not necessary for a 32-bit platform. 
          For example:
          setup.exe -J STATELESS_ONLY=true

        4. Follow the instructions in the installation wizard to persist the configuration data to the database. After this process completes, you can upgrade BMC BladeLogic Server Automation using the individual component installer. For more information, see Upgrading using individual component installers.

          Note

          Start the Application Servers and PXE Servers only after you have upgraded the individual BMC BladeLogic Server Automation components.

        Using silent installation

        1. Download and extract the Windows installation package for the operating system level and hardware platform in a <temporary directory> on the Application Server or PXE server. The package follows the naming convention BBSA<version>-<platform>.zip, and contains the unified product installation program files. 

        2. Navigate to the <temporary location> directory containing installation files.

        3. Run the setup.exe installation file in silent mode with the STATELESS option. The –J STATELESS_ONLY=true option is necessary only for a 64-bit platform. It is not necessary for a 32-bit platform. 

          1. In a text editor, create an options.txt file that contains the following line:
            –J STATELESS_ONLY=true

          2. Run the following command from the <temporary location> directory that contains the installation files:
            setup.exe -i silent -DOPTIONS_FILE=<full path to options file>

        4. After this process completes, you can upgrade BMC BladeLogic Server Automation using the silent mode. For more information, see Upgrading silently using the unified product installer.

          Note

          Start the Application Servers and PXE Servers only after you have upgraded the individual BMC BladeLogic Server Automation components.

        To run the configurator utility, you must use the unified product installer package for Linux and perform the following steps. Ensure that you have shut down all Application Servers and PXE servers before you proceed with the following steps. Perform these steps on each and every Application Server and PXE server to copy the data from blasadmin into the database.

        Using interactive installation with the GUI

        1. Download and extract the Linux installation package for the operating system level and hardware platform in a <temporary directory> on the Application Server or PXE server. The package follows the naming convention BBSA<version>-<platform>.zip, and contains the unified product installation program files.
          On a Linux or UNIX machine, you must assign executable permissions to the installation files that you unzipped, by entering the following command.
          chmod +x -R <temporary directory>

           

        2. Navigate to the <temporary location> directory containing installation files.

          Note

          For Linux and UNIX, you must execute the installation as a root user. Do not execute the installation file from a non-root account.
        3. Run the setup.bin installation file with the STATELESS option. The –J STATELESS_ONLY=true option is necessary only for a 64-bit platform. It is not necessary for a 32-bit platform. 
          For example:
          ./setup.bin -J STATELESS_ONLY=true

        4. Follow the instructions in the installation wizard to persist the configuration data to the database. After this process completes, you can upgrade BMC BladeLogic Server Automation using the individual component installer. For more information, see Upgrading using individual component installers.

          Note

          Start the Application Servers and PXE Servers only after you have upgraded the individual BMC BladeLogic Server Automation components.

        Using silent installation

        1. Download and extract the Linux installation package for the operating system level and hardware platform in a <temporary directory> on the Application Server or PXE server. The package follows the naming convention BBSA<version>-<platform>.zip, and contains the unified product installation program files.
          On a Linux or UNIX machine, you must assign executable permissions to the installation files that you unzipped, by entering the following command.
          chmod +x -R <temporary directory>

           

        2. Navigate to the <temporary location> directory containing installation files.

          Note

          For Linux and UNIX, you must execute the installation as a root user. Do not execute the installation file from a non-root account.


        3. Run the setup.bin installation file in silent mode with the STATELESS option. The –J STATELESS_ONLY=true option is necessary only for a 64-bit platform. It is not necessary for a 32-bit platform. 

          1. In a text editor, create an options.txt file that contains the following line:
            –J STATELESS_ONLY=true

          2. Run the following command from the <temporary location> directory that contains the installation files:.
            /setup.bin -i silent -DOPTIONS_FILE=<full path to options file>

        4. After this process completes, you can upgrade BMC BladeLogic Server Automation using the silent mode. For more information, see Upgrading silently using the unified product installer.

          Note

          Start the Application Servers and PXE Servers only after you have upgraded the individual BMC BladeLogic Server Automation components.

        5Run the Application Server upgrade program

          To upgrade the Application Server:

          1. Navigate to the directory that contains installation files and run the installation program for BMC Server Automation. (Installation program names follow the convention: BBSA<version>-<platform>.)
          2. In the Setup Type window, select Upgrade, and then click Next.
          3. To complete the upgrade to your installation, click Finish.

          Related topic: Upgrading the Application Server on Windows

          To upgrade the Application Server:

          1. Log on as root.
          2. Stop the Application Server.
          3. Navigate to the directory that contains Application Server installer files (which follow the naming convention: BBSA<version>-<platform>). Run the installer file using the ./<BL_Installer_file.sh> command. The following message is displayed:
            A previous installation already exists.
            Do you wish to continue (y/n) ?
          4. Enter y.
            A message is displayed that lets you choose a language for the installation program.
          5. Enter the number corresponding to the language that you want to use.
            The following message is displayed:
            Welcome to the BMC BladeLogic Server Automation Release <versionNumber> installation script ...
            A previous installation has been detected. This installation will be upgraded to BMC BladeLogic BMC BladeLogic Server Automation <versionNumber>.
            Do you wish to continue (y/n) ?
          6. Enter y.
            Licensing text is displayed and concludes with the following message:
            Do you agree to the terms of the license agreement (y for Yes) ?
          7. Enter y.
            A list displays the BMC Server Automation components to be upgraded and prompts you to continue.
          8. Enter y.
            A series of messages is displayed, and then the upgrade script is complete.

          Related topic: Upgrading product components on Linux and UNIX

          6Execute postmigration to perform additional upgrade related activities.

          This should be run on only one application server after the previous steps are complete.

            To execute postmigration

            Warning: Prior to running the postmigration file, review the following Knowledge Article from BMC Customer Support to avoid running out of disk space on the Application Server:  When upgrading BMC Server Automation to 8.5.1 Patch 4, 8.6, or 8.7, the postmigration utility fails with "No space left on device" (Knowledge Article ID: 000091406 ) 

            1. Navigate to the postmigration file found within the BMC Server Automation installation directory:

              <installDirectory>\NSH\bin\postmigration 
            2. Run the postmigration file.
              Progress messages regarding the relevant component templates are displayed on-screen and are also written to the postmigration.log file stored in the same location as the postmigration file.

            Related topic: Performing post-migration updates

            To execute postmigration

            Warning: Prior to running the postmigration file, review the following Knowledge Article from BMC Customer Support to avoid running out of disk space on the Application Server:  When upgrading BMC Server Automation to 8.5.1 Patch 4, 8.6, or 8.7, the postmigration utility fails with "No space left on device" (Knowledge Article ID: 000091406 ) 

            1. Navigate to the postmigration file found within the BMC Server Automation installation directory:
              <installDirectory>/NSH/bin/postmigration

            2. Run the postmigration file.
              Progress messages regarding the relevant component templates are displayed on-screen and are also written to the postmigration.log file stored in the same location as the postmigration file.

            Related topic: Performing post-migration updates

            7If the Application Server is running on Microsoft Windows, run the RSCD agent upgrade program on the Application Server and File Server

            To run the RSCD agent upgrade program on the Application Server and File Server

            1. Navigate to the directory containing installation files and run the installation program for the RSCD agent. (Installation program names follow the convention: RSCD<version>-<platform>.)
            2. To begin upgrade, click Next.
            3. If the installation program displays an information message saying that a reboot is required to complete the setup, click OK.
            4. To complete the upgrade, click Finish.
              The installation program starts the RSCD agent.

            Related topics:

            Upgrading RSCD agents on Windows

            Upgrading the file server

            8Start the Application Server

              To start the Application Server:

              1. From the Start menu, select Control Panel > Administrative Tools, and double-click Services.
              2. Right-click BladeLogic Application Server and select Start from the pop-up menu.

              Related topic: Starting and stopping BMC Server Automation components 

              To start the Application Server:

              • From the directory where BMC Server Automation is installed, enter the following:

              /etc/init.d/blappserv start

              Related topic: Starting and stopping BMC Server Automation components 

              9If you are using PXE-based provisioning, upgrade the PXE server

                To upgrade the PXE server:

                1.  Record the following settings for the PXE server:
                  • Installation directory
                  • Database connectivity information
                    The PXE server uses the same database as the Application Server. One way to obtain this information is to start the Application Server Administration Console (also known as the blasadmin utility) and enter the following command:
                    show database all
                  • Host name and IP address of the PXE server
                  • DHCP server location (local or remote)
                  • TFTP root directory
                    You do not have to record the name and location of the data store.
                  • If the Multi-Database mode is being used, make a note of the additional database configuration parameters found in the <install directory>\PXE\br\deployments\_pxe\pxe-data-sources.xml file.
                2. Make a backup copy of configuration files.
                  If you are using the pxe.conf configuration override file, make a copy of the <install directory>\PXE\br\pxe.conf file.
                3. Uninstall the PXE server.
                4. Install the latest version of the PXE server (PXE<version>-<platform>.exe).
                  During installation, ensure that you provide information that matches the settings that you recorded from the previous version, especially the following settings:
                  • Database configuration settings, including Multi-Database mode settings
                  • Any pxe.conf settings that you want to apply during installation
                  For more information, see Installing the PXE server (Windows)
                5. To complete the upgrade to your installation, click Finish.
                6. During the upgrade process, the PXE server global.properties file is overwritten. Copy the global.properties file on the Application Server to the br\deployments directory on the PXE machine.
                7. Restart the PXE server. See Starting and stopping a PXE server.

                Related topic: Upgrading a PXE server on Windows

                To upgrade the PXE server:

                (If the PXE server is installed as part of the Application Server installation, an upgrade of the Application Server also upgrades the PXE server.)

                1.  Log on as root.
                2. Record the following settings for the PXE server:
                  • Database connectivity information
                    The PXE server uses the same database as the Application Server. One way to obtain this information is to start the Application Server Administration Console (also known as the blasadmin utility) and enter the following command:
                    show database all
                  • Host name and IP address of the PXE server
                  • DHCP server location (local or remote)
                  • TFTP root directory
                    You do not have to record the name and location of the data store.
                  • If you are using the Multi-Database mode, make a note of the additional database configuration parameters found in the <install directory>/NSH/br/deployments/_pxe/pxe-data-sources.xml file.
                3. Make a backup copy of configuration files.
                  If you are using the pxe.conf configuration override file, make a copy of the <install directory>/NSH/br/pxe.conf file.
                4. Navigate to the directory that contains upgrade files and run the upgrade script for BMC Server Automation. (Script names follow the convention: BBSA<version>-<platform>.)
                  The following message is displayed:
                  A previous installation already exists.
                  Do you wish to continue (y/n) ?
                5. Enter y.
                  A message prompts you to choose a language for the installation program.
                6. Enter the number corresponding to the language that you want to use.
                  The following message is displayed:
                  Welcome to the BMC BladeLogic Server Automation Release <versionNumber> installation script ...
                  A previous installation has been detected. This installation will be upgraded to BMC BladeLogic BMC BladeLogic Server Automation <versionNumber>.
                  Do you wish to continue (y/n) ?
                7. Enter y.
                  Licensing text is displayed and concludes with the following message:
                  Do you agree to the terms of the license agreement (y for Yes) ?
                8. Enter y.
                  A list displays the BMC Server Automation components to be upgraded and prompts you to continue.
                9. Enter y.
                  A series of messages is displayed, and then the upgrade script is complete.
                10. Copy the backup of the pxe-data-sources.xml file into <install directory>/NSH/br/deployments/_pxe/pxe-data-sources.xml.
                11. Merge the configurations of the <install directory>/NSH/br/pxe.conf and the backed up copy.
                12. During the upgrade process, the PXE server global.properties file is overwritten. Copy the global.properties file on the Application Server to the br/deployments directory on the PXE machine.
                13. Restart the PXE server. See Starting and stopping a PXE server.

                Related topic: Upgrading a PXE server on Linux or UNIX

                10(Windows only) If you are employing patch management in offline mode, re-run the offline Patch Downloader utility

                After upgrading to a new version of BMC Server Automation on Windows platforms, you must:

                1. Re-run the offline Patch Downloader utility.
                2. Run the Catalog Update Jobs.

                Related topics:

                Setting up the Offline Patch Downloader utility

                Updating an existing catalog

                11Upgrade BMC Server Automation Console

                To upgrade the console

                Note: If the console is installed on the Application Server (which is not recommend by BMC), stop the agent and the Application Server and run the console upgrade program.


                  1. Navigate to the directory that contains installation files for BMC Server Automation Console and run the installation program. (Installation program names follow the convention: BBSACONSOLE<version>-<platform>.)
                  2. On the Multi-instance selection window, select the instance of the console that you want to upgrade.
                  3. On the User inputs window, accept the default selections and click Next.

                  4. If you clear the BMC Server Automation Console Upgrade Service check box, the BMC Server Automation Console Upgrade Service is not installed. This service is required for automatically upgrading the BMC Server Automation Console when you upgrade the Application Server to later releases, see BMC Server Automation Console Automatic Upgrade: Windows only.

                  5. On the Installation preview window, click Install.



                  1. Navigate to the directory that contains installation files for BMC Server Automation Console and run the installation program. (Installation program names follow the convention: BBSACONSOLE<version>-<platform>.)
                  2. On the Multi-instance selection window, select the instance of the console that you want to upgrade.
                  3. On the User inputs window, accept the default selections and click Next.

                  4. On the Installation preview window, click Install.


                   

                  Related topic: Upgrading the BMC Server Automation Console 

                  12Upgrade the RSCD agents, as needed

                    To upgrade agents:

                    1. Navigate to the directory containing installation files and run the installation program for the RSCD agent. (Installation program names follow the convention: RSCD<version>-<platform>.)
                    2. To begin upgrade, click Next.
                    3. If the installation program displays an information message saying that a reboot is required to complete the setup, click OK.
                    4. To complete the upgrade, click Finish.
                      The installation program starts the RSCD agent.

                    Related topic: Upgrading RSCD agents on Windows

                    To upgrade agents:

                    1.  Log on as root.
                    2. Navigate to the directory that contains upgrade files and run the installation program for the RSCD agent. (Script names follow the convention: RSCD<version>-<platform>.)
                      The following message is displayed:
                      A previous installation already exists.
                      Do you wish to continue (y/n) ?

                      If you are upgrading a server with components installed other than the RSCD agent, you must use an installation script that includes those other components. For example, if you are upgrading the RSCD agent on a server where Network Shell is also installed, the installation package you are using must include Network Shell.
                      For information about silent upgrade of LINUX and UNIX agents, review the information in Silently upgrading Linux and UNIX agents.

                    3. Enter y.
                      A message is displayed letting you choose a language for the installation program.
                    4. Enter the number corresponding to the language that you want to use.
                      The following message is displayed:
                      Welcome to the BMC BladeLogic RSCD Agent <versionNumber> installation script ...
                      Do you wish to continue (y/n) ?
                    5. Enter y.
                      Licensing text is displayed and concludes with the following message:
                      Do you agree to the terms of the license agreement (y for Yes) ?
                    6. Enter y.
                      A message shows the RSCD agent as the one component to be upgraded and asks if you want to continue.
                    7. Enter y.
                      The following message is displayed:
                      Please choose the rscd log directory. [/opt/bmc/bladelogic/RSCD/log]
                    8. Press Enter to install accept the default RSCD log directory or enter another directory path.
                      The following message is displayed:
                      Enter the directory you want to use for temp files [/tmp]:
                    9. Press Enter to install accept the default directory for temp files or enter another directory.
                      Several messages are displayed, and the upgrade is complete.

                    Related topic: Upgrading the RSCD agent on Linux and UNIX

                    13(MAS environments only) Upgrade additional Application Servers

                    If this is a multiple application server environment (MAS), upgrade your other Application Servers now.

                    For each additional Application Server. repeat steps 2, 3, 4, 5, and 7.

                    14Upgrade the provisioning system for Windows or Linux PXE-based environments

                      1. Extract the new <version>-provision-files.zip.
                        This file is included in the main product package when you download BMC Server Automation from the BMC Electronic Product Distribution (EPD) website.
                      2. Locate the bmilinux.tar and bmilinux-x64.tar file (in the \provisioning\pxe directory) and copy them to the datastore directory.
                      3. Locate the bmiwin.exe file (in the \provisioning\pxe directory) and copy it to the datastore\bmi directory. 
                      4. Locate the bllibeay32.dll and blssleay32.dll files (in the \provisioning\winpe\x86 directory) and copy them to the datastore\bmi directory.
                        See Setting up a data store and the BMC Communities forum article: 8.5 Upgrade - Changes to provisioning files for BMI. 
                      5. Using the new <version>-provision-files.zip, create new Gentoo or WinPE boot images, as discussed in Creating boot image files and placeholders.

                      Note: After the upgrade, you cannot continue using any existing Gentoo or WinPE boot images that were created in the previous version of BMC Server Automation. This is only applicable while upgrading major releases or service packs. You can continue using the existing boot images in case of patch-level upgrades. 

                      1. Extract the new <version>-provision-files.zip.
                        This file is included in the main product package when you download BMC Server Automation from the BMC Electronic Product Distribution (EPD) website. 
                      2. Locate the bmilinux.tar and bmilinux-x64.tar file (in the /provisioning/pxe directory) and copy them to the datastore directory.
                      3. Locate the bmiwin.exe file (in the /provisioning/pxe directory) and copy it to the datastore/bmi directory. 
                      4. Using the new <version>-provision-files.zip, create new Gentoo or WinPE boot images, as discussed in Creating boot image files and placeholders.

                      Note: After the upgrade, you cannot continue using any existing Gentoo or WinPE boot images that were created in the previous version of BMC Server Automation. This is only applicable while upgrading major releases or service packs. You can continue using the existing boot images in case of patch-level upgrades. 

                      15Run the Update Model Objects Job

                      For custom configuration objects to work reliably, the version of the custom object should match the version of the agent.

                      1. Run an Update Server Properties Job on the agents you have upgraded. For more information, see Creating Update Server Properties Jobs.
                      2. If you are not upgrading all of your agents at this time, make copies of all component templates, BLPackages, Snapshot Jobs, and Audit Jobs that reference custom configuration objects that have dependencies on agents running earlier versions. You must maintain a version match between component templates, BLPackages, Snapshot Jobs, and Audit Jobs and custom configuration objects and agents. The objects that you copy in this step are the objects that you can use to maintain the version match.
                      3. If you upgrade to the latest version of BMC Server Automation and you are using BMC Server Automation for virtual environments, you must immediately update the RSCD agent on the system used for the integration and add the new configuration object version for the integration. For example, for the vCenter server, you must upgrade the RSCD agent on either the Windows vCenter server or the AMO proxy and add the new VMware configuration object to the vCenter server object in BMC Server Automation.

                      4. To ensure that all configuration-object-based assets within existing content are upgraded, run an Upgrade Model Objects Job that targets any component templates, BLPackages, Snapshot Jobs, or Audit jobs that you want to upgrade. For more information about the Upgrade Model Objects Job, see Creating or modifying Upgrade Model Objects Jobs.
                        Note: Do not run the Upgrade Model Objects Job against the copies of objects that you created in step 3.
                        If you open an existing component template, BLPackage, Snapshot Job, or Audit Job that references a custom configuration object and a later version of that custom configuration object exists, the system displays a message saying it will automatically upgrade the referenced custom configuration object. To maintain a version match with an earlier agent, close the component template, BLPackage, Snapshot Job, or Audit Job without saving.

                      5. After executing the Upgrade Model Objects Job, display the results of the job run to see which assets were successfully upgraded and which were not. If you find that certain assets were not automatically upgraded, you must upgrade them manually. Perform the following steps:

                        1. Open the object (template, package, or job).
                        2. Manually remove the asset of the earlier version and add the asset of the latest version.
                        3. Save the object.

                       Related topics:

                      Upgrading custom configuration objects

                      Creating or modifying Upgrade Model Objects Jobs

                      Where to go from here

                      During an upgrade, the following tasks are performed automatically by the unified product installer but not when you are upgrading individual components. You can perform them manually at a later time. 

                       

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

                      Comments