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.

Upgrading product components on Linux and UNIX

An upgrade of the Application Server on Linux and UNIX also upgrades all components that were installed as part of the previous installation. These components can include the Network Shell, the RSCD agent, and the PXE server.
Upgrading the Application Server does not upgrade the BMC Server Automation Console. You must upgrade the console separately.

Note

  • You must upgrade the Application Server and BMC Server Automation Console to the same version, whether they are located on the same computer or different computers.
  • If the Application Server and the BMC Server Automation Console are on the same computer, you must upgrade the Application Server before upgrading the console.
  • If you are upgrading from version 7.6.xx or 7.7.xx, you should be aware that the upgrade changes the location of your installation directory. The upgrade process keeps the old version's installation location and creates an NSH directory there. Then the upgrade moves user files to the NSH folder and copies new files there. For example, if the old version's installation location is: /usr/nsh, the upgrade moves it to: /usr/nsh/NSH

If the host computer on which you are installing the Network Shell has:

  • A supported version of Perl installed — The Network Shell installation automatically installs the Network Shell Perl module. For information about the Perl versions that BMC Server Automation supports, see Perl support.
  • An unsupported version of Perl installed — The installation copies files that allow you to install the Perl module after you have installed the supported version of Perl.

To perform a silent upgrade of an Application Server, see Using-silent-mode-to-upgrade-components-on-Linux-or-UNIX.

Prerequisite

Before upgrading the Application Server, ensure that the database configuration information on the deployments of the Application Server is up-to-date.

You can use the blasadmin utility to check the database- and file server-related information for each of the deployments (except _launcher). You can use the following blasadmin commands:

  • blasadmin -s <delpoyment name> show database all (for _pxe deployments use blasadmin -s _pxe show pxe all)
  • blasadmin -s <deployment name> show file all

If either of these commands return an error, you can use the blasadmin utility to correct the configuration information and proceed with the upgrade.

To upgrade the Application Server on Linux and UNIX

  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 8.3.00 installation script ...
     A previous installation has been detected. This installation will be upgraded to BMC BladeLogic BMC BladeLogic Server Automation 8.3.00.
     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 topics

Release-notes-and-notices

 

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