• Spaces
  • Collections
  • Help
    • ×
     
     
    •  
    BMC BladeLogic Server Automation 8.1

    Page tree

    The following sections describe how to install the service pack files or patch files (if the patch uses full installers).

    Before you upgrade

    Perform the following tasks before you upgrade.

    Perform pre-upgrade tasks

    Unknown macro: {multi-excerpt}

    Note

    BMC strongly recommends that you back up the database before performing database migration and post-migration tasks.

    • Back up your installationDirectory/br/deployments folders.
    • Shut down all BMC BladeLogic services (such as BladeLogic Application Server and BladeLogic Process Spawner).
    • Stop the RSCD agents running on any application servers.
      Both the agent and Application Server services must be stopped before upgrading.
    • Close all instances of the client.
    • Download the files. See Downloading the installation files.
    • If you are performing a fresh installation, create the database schema prior to running the installers. See Performing a fresh installation.

    Perform verification

    Before upgrading, perform the following verification procedure to ensure that the upgrade is successful:

    Blasadmin -s _template show data all
\# Ensure the correct information is present

Blasadmin -s _template show file all
\# Ensure the correct information is present

\*For _spawner, _pxe (if present) and any other instance in the deployments
directory (excluding _launcher), run:
Blasadmin -s <instancename> show data all
\# Verify that the correct settings are returned.

    Review upgrade considerations

    Unknown macro: {multi-excerpt}

    Review the information in the following table before you begin the upgrade.

    Note

    The Application Server and RCP Client (console) must be upgraded to the same Service Pack version
    level, whether they are located on the same system or different systems.

    Platform

    Notes

    All

    • If the Application Server and the BMC BladeLogic Server Automation console are on the same computer, you must upgrade the Application Server before upgrading the console.
    • The Application Server and BMC BladeLogic Server Automation console must be upgraded to the same version level, whether they are located on the same system or different systems.
    • Before you upgrade the BMC BladeLogic Server Automation console, ensure that port 9998 (TCP) is not being used. Upgrading the console requires use of this port; if it is already in use, the installation fails.
    • Before running the product, you must upgrade the agent on the computer on which your file server resides. The file server and the database must be at the same version. If your file server is on the same system as the Application Server and the Application Server is running UNIX, the Application Server installer performs the agent upgrade. In this case, you do not need to upgrade the agent separately.

    Microsoft Windows

    • To perform the service pack installations, you must have local Administrator privileges. On Windows Server 2008 you must select the Run As Administrator option when you run the installer, even if you are logged on as a local Administrator.
    • If you are using Windows Terminal Services or Citrix Presentation Server to install or you are installing on Windows Server 2003 or 2008, you must install in Install mode rather than Execute mode, or you must 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.
    • For a server to provide information about Windows Group Policy objects, the secedit.exe file must be installed on the server, and it must be included in the server’s executable path.
    • If you are installing an agent on a Windows server that is a Windows domain controller, confirm that the Netlogon service is enabled and running before installing the agent. This ensures that the agent is installed with correct service dependencies.
    • The patch analysis function of BMC BladeLogic requires the Microsoft XML (MSXML) parser version 3.0 or later to be installed on the server where the RSCD agent is installed. You can install the RSCD agent on a computer where MSXML is not installed, but patch analysis will not function correctly until MSXML 3.0 or later is installed.

    UNIX

    • Exit the NSH before executing the installer.
    • Computers that are configured as PXE servers must also have NSH installed before upgrade.
    • The UNIX or Linux file system partition where you are going to install the Application Server must not be mounted with the nosuid option.
    • Set umask for the root and bladmin users to 0027 on the Application Server host computer.
    • If you are installing the Application Server on a computer running Red Hat Enterprise Linux version 6 x64 KVM, ensure that the glibc-2.3.2-95.3 package is installed.
    • You must have an X Window server installed and configured.

    Before you upgrade - BMC BladeLogic Atrium Integration

    You can perform a full installation by using the files included in the service pack. There is no requirement to install BMC BladeLogic Atrium Integration before you install the service pack. For installation and setup information, see “Upgrading BMC BladeLogic Integration to Atrium” in the BMC BladeLogic Integration for Atrium: Implementation Guide.

    BMC BladeLogic Atrium Integration does not have an upgrade path. You must remove any installed version of BMC BladeLogic Atrium Integration before installing a new version.

    When you upgrade BMC BladeLogic Atrium Integration from an earlier version, all customizations are deleted, including Discovery Job and SnapShot Job history, data exchanges, data mappings, and reconciliation rules.

    Installing in Microsoft Windows or UNIX environments

    Unknown macro: {multi-excerpt}

    Run the installers according to the instructions in the following sections of the "Upgrading from an earlier version" chapter in the [_BMC BladeLogic for Server Automation Installation Guide_|PDFs^BMCBladeLogicInstallation.pdf]:

    • Upgrading Application Servers
    • Upgrading the BMC BladeLogic Server Automation console
    • Upgrading RSCD agents

    Installing the agent in VMware environments

    Follow the instructions in the "Setting up a VMware vSphere environment" chapter of the BMC BladeLogic for Server Automation Installation Guide.

    After you upgrade

    Perform the following tasks after you upgrade.

    Execute the SQL upgrade script

    Unknown macro: {multi-excerpt}

    The script is available from the latest SQL_Update_Scripts.zip file. Follow the instructions in Running the SQL update scripts.

    Upgrading custom configuration objects

    You must maintain a version match between component templates, BLPackages, jobs, and custom configuration objects and agents.

    Unknown macro: {multi-excerpt}

    If a BLPackage, job, or a Component Template was created with a version of a custom configuration object (for example, Unix Users, Unix Groups, Processes, Unix Services, and so on) older than the version on the target systems (systems with BMC BladeLogic Server Automation Agents installed), then you will need to upgrade the content.

    To do so, perform either of the following procedures:

    • Create and run an Update Model Object Job against the objects. For more information, see the "Upgrading custom configuration objects" section of the "Configuration objects" chapter of the [BMC BladeLogic Server Automation User Guide|PDFs^BMCBladeLogicUserGuide.pdf].

    Note

    If you are not upgrading all of your agents at this time, make copies of all component templates, BLPackages, and any jobs that reference custom configuration objects that have dependencies on agents running earlier versions.

    • Open the object and click OK on the pop-up message asking to update the objects.

    Note that if your BLPackages, Component Templates and other objects do not contain any configuration objects, then running the Upgrade Model Object Job is not required.

    © Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.