Upgrading the Application Server on Windows
This topic describes how to upgrade an Application Server that is running on Microsoft Windows. It includes the following sections:
Important information about upgrading on Windows
An upgrade of the Application Server on Windows upgrades both the Application Server and the Network Shell.
Upgrading the Application Server does not upgrade the BMC Server Automation Console, the RSCD agent, the PXE server, or the file server. You must upgrade those components separately.
- 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.
- Upgrade the Application Server and NSH to the same version, so that the NSH proxy works properly. The NSH supports backward compatibility but not forward compatibility. For example, the 8.8 NSH can communicate with 8.7 RSCD agents but not with 8.9 agents.
- 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: C:\Program Files\BMC BladeLogic\OM, the upgrade moves it to: C:\Program Files\BMC BladeLogic\OM\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 the Application Server (Windows).
Before you begin
- To perform the upgrade of the Application Server, you must have local Administrator privileges.
- If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on Windows 2003 or 2008, use one of the following methods to install:
- Install in Install mode rather than Execute mode. For information, see Using Install mode instead of Execute mode.
- Install using the Windows Add or Remove Programs utility.
- On 64-bit Windows systems, confirm that the <WINDIR>\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.
Ensure that database configuration information is current and correct in all deployments of the Application Server. To check the values, use the
blasadminutility and specify the name of each deployment (except _launcher) and validate that the Database section and FileServer section display correct information. If the database section is incorrect, then one or both of the following commands will produce an error.
blasadmin -s <deloyment name> show database all(for the _pxe deployment use
blasadmin -s _pxe show pxe all)
blasadmin -s <deployment name> show file all
blasadminutility to correct the configuration so that these commands return the correct response.
- Perform the upgrade steps in this order:
- Shut down the Application Server.
- Upgrade the RSCD agent before upgrading the Application Server. These two components must bet at the same version level.
Afterwards, to verify that the agent is running and has been upgraded, run the following command:
- If the file server is not on the Application Server, upgrade the file server before you upgrade the Application Server.
- Upgrade the Application Server.
To upgrade the Application Server on Windows
BMC Server Automation does not support multiple instances of the Application Server on the same machine.
- 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>.)
- In the Setup Type window, select Upgrade, and then click Next.
- To complete the upgrade to your installation, click Finish.
Where to go from here
Upgrade at least one BMC Server Automation Console. See Upgrading the BMC Server Automation Console.