Upgrade cheat sheet for BMC Server Automation

This cheat sheet topic provides a list of the steps required to upgrade BMC Server Automation. Note that cheat sheet topics are targeted to experienced BMC Server Automation users, and do not include relevant planning and prerequisite information. If you are not an experienced user, see the topics in the Preparing for upgrade section to review the required planning information for upgrading the product.

StepDescription
Stop 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.

Note

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.

  • On Windows, select Start > Run. Enter services.msc in the Open field and click OK. Right-click- BladeLogic Application Server and select Stop from the pop-up menu.
  • On UNIX, type the command:/etc/init.d/blappserv stop
To stop agents on Windows
  1. Choose Start > Settings > Control Panel > Administrative Tools > Services.
  2. Right-click BladeLogic RSCD Agent and select Stop.
To stop agents on UNIX/Linux

Type the command:
 <installDir>/NSH/sbin/agentctl stop

To stop the PXE server on Windows
  1. Select Start > Settings > Control Panel > Administrative Tools > Services. 
  2. Right-click BladeLogic PXE Server and select Stop.
To stop the PXE server on UNIX or Linux

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

Run the Application Server upgrade program.
To upgrade the Application Server on Windows

  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>.) BMC Server Automation does not support multiple instances of the Application Server on the same machine.
  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 on UNIX or Linux

  1. Log on as root.
  2. Stop the Application Server.
  3. 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) ?
  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.2.00 installation script ...
    A previous installation has been detected. This installation will be upgraded to BMC BladeLogic BMC BladeLogic Server Automation 8.2.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 topic: Upgrading the Application Server on Linux and UNIX

If 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.

Note

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. For steps on upgrading custom configuration objects, see Upgrading custom configuration objects.

Related topic: Upgrading RSCD agents on Windows

If this is a version upgrade (for example, upgrading from version 8.3 to version 8.5), run the migration manager to upgrade the database.
To migrate an Oracle database
 Click here to review the steps for migrating an Oracle database.

  1.  Back up the BMC Server Automation file server storage location. For example, copy the entire contents of the storage location to a directory other than the current storage location. BMC recommends using a backup directory that is at or close to the root of a disk drive. This practice avoids excessively long paths. Microsoft Windows paths are limited to 255 characters.
  2. Obtain the 8.2 version of the external-files.zip file and extract its contents. For a description of this file, see Obtaining the installation files.
  3. Using the files extracted from external-files.zip, copy the /db_scripts/ <db_type>/upgradedirectory into a directory on your Application Server.

    Note

    BMC recommends using a directory that is at or close to the root of a disk drive. This practice avoids excessively long paths. Windows paths are limited to 255 characters.

  4. The Oracle DBA must perform the following steps:
    1. Confirm that adequate TEMP and UNDO space is available. See Determining sizing requirements for Oracle databases.
    2. Copy /db_scripts/oracle/upgrade/migration_setup_OM.sql, which you extracted from external-files.zip, to a location where you have access to SQL*Plus.
    3. Log on to SQL*Plus as sysdba.

      Warning

      You must log on as sysdba to run the migration_setup_OM.sql script in the next step.

      Note

      For the core BMC Server Automation database, if the installation schema owner is different from the default schema owner (BLADELOGIC), for the next step, modify the migration_setup_OM.sql script to use the schema owner's user name for the installation.

      After completing data migration, the schema owner's additional migration roles and permissions can be returned to their normal state.

    4. Set the BMC Server Automation user's roles and permissions to allow the migration to be carried out by entering the following command:

      start migration_setup_OM.sql
  5. On the Application Server, use the cd command to navigate to the <installDirectory>/NSH/bin directory for BMC Server Automation.
  6. Launch BMC BladeLogic Data Migration Manager by entering one of the following commands:

    (Windows)

    blmigration_mgr.exe <path_to_migration_directory>

    (Linux and UNIX)

    ./blmigration_mgr <path_to_migration_directory>

    Where <path_to_migration_directory> is the path to the migration directory that you copied to the Application Server in step 3. For example, if you extracted the externalfiles.zip for version 8.2 SP1 under the tmpdirectory, then the path to the migration directory would be:

    (Windows)

    blmigration_mgr.exe C:\tmp\8.2-SP1-external-files\bl_8.2.01\db_scripts\oracle\upgrade

    (Linux and UNIX)

    ./blmigration_mgr /tmp/8.2-SP1-external-files/bl_8.2.01/db_scripts/oracle/upgrade/

    Warning

    Before executing blmigration_mgr, ensure that all connections to the BMC Server Automation database are closed. Connections that are open can cause certain database commands to fail, which causes the upgrade to stop.

    BMC BladeLogic Data Migration Manager creates the stored tasks needed for the data migration and then launches the BMC BladeLogic Data Migration Manager console.

  7. If you choose to execute the validate step separately from the validation that is done as part of the next step, click Validate Environment. For more information, see To validate Oracle environments.
  8. Click Run Migration.
  9. When migration completes, check the blmigration.log.

Related topic: Migrating an Oracle database

To migrate an SQL Server database
 Click here to review the steps for migrating an SQL Server database.

  1. Back up the BMC Server Automation file server storage location. For example, copy the entire contents of the storage location to a directory other than the current storage location. BMC recommends using a backup directory that is at or close to the root of a disk drive. This practice avoids excessively long paths. Microsoft Windows paths are limited to 255 characters.
  2. Obtain the most recent version of external-files.zip and extract its contents. For a description of this file, see Obtaining the installation files.
  3. Using the files extracted from external-files.zip, copy the /db_scripts/ <db_type>/upgrade directory into a directory on your Application Server.

    Note

    BMC recommends using a directory that is at or close to the root of a disk drive. This practice avoids excessively long paths. Windows paths are limited to 255 characters.

  4. On the Application Server, use the cd command to navigate to the <installDirectory>/NSH/bin directory for BMC Server Automation.
  5. Launch BMC BladeLogic Data Migration Manager by entering one of the following commands:


    Where <path_to_migration_directory> is the path to the migration directory that you copied to the Application Server in step 3. For example, if you extracted the version 8.2 SP1 externalfiles.zip under the tmp directory, then the path to the migration directory would be :

    (Windows)

    C:\tmp\8.2-SP1-external-files\bl_8.2.01\db_scripts\sqlserver\upgrade\

    (Linux and UNIX)

    /tmp/8.2-SP1-external-files/bl_8.2.01/db_scripts/sqlserver/upgrade/

    Warning

    Before executing blmigration_mgr, ensure that all connections to the BMC Server Automation database are closed. Connections that are open can cause certain database commands to fail, which causes the upgrade to stop.

    BMC BladeLogic Data Migration Manager creates the stored tasks needed for the data migration and then launches the BMC BladeLogic Data Migration Manager console.

  6. Click Run Migration.
  7. When migration completes, check the blmigration.log.

Related topic: Migrating an SQL database

Run any required SQL scripts.

This step applies to both SP and version upgrades (for example, upgrading from version 8.1 to 8.2.01 would include both data migration and SQL update scripts).

To run the update script for an Oracle database
 Click here to review the steps for running the SQL update scripts for an Oracle database.

  1. Obtain the zipped package of SQL Update scripts from the BMC Electronic Product Distribution (EPD) website, as described in Obtaining the installation files. This zipped package is named 82-<SP level>-SQL_Update_Scripts.zip file, where <SP level> can be one of the following values: SP4, SP3, or SP2
  2. Extract the contents of the zipped package of SQL Update scripts to a temporary local directory.
  3. Navigate to the directory that contains the update scripts  (temporaryDirectory/8.2.0x/Remediation/oracle).
  4. Log on to SQL*Plus as the BMC Server Automation database owner (as provided to blasadmin during BMC Server Automation schema creation).
  5. Run the script, as follows:

    SQL>start install_hotfix_update_oracle_script.sql
    

Related topic: Running the SQL update scripts 

To run the update script for an SQL Server database
 Click here to review the steps for running the SQL update scripts for a Microsoft SQL Server database.

  1. Obtain the zipped package of SQL Update scripts from the BMC Electronic Product Distribution (EPD) website, as described in Downloading the installation files. This zipped package is named 82-<SP level>-SQL_Update_Scripts.zip file, where <SP level> can be one of the following values: SP4, SP3, or SP2
  2. Extract the contents of the zipped package of SQL Update scripts to a temporary local directory.
  3. Navigate to the directory that contains the upgrade scripts (temporaryDirectory/8.2.0x/Remediation/sqlserver).
  4. Execute the install_hotfix_update_sqlserver_script.bat file with the following input parameters:
    install_hotfix_update_sqlserver_script.bat <DBServerName> <DBName> <Username> <Password>

    Example


    install_hotfix_update_sqlserver_script.bat testserver test_db BLuser BMC123

    Recommendation

    After upgrading the SQL update scripts from version 3.1.01 to 4.1, the scripts do not execute when the password has special characters.

    BMC recommends entering the password in double quotes while executing this script on command prompt.

Related topic: Running the SQL update scripts 

Start the Application Server.
To start the Application Server

    MultiExcerpt named 'start_specific_appserver' was not found
The page: Managing multiple Application Servers on the same host was found, but the multiexcerpt named 'start_specific_appserver' was not found. Please check/update the page name used in the 'multiexcerpt-include macro.

If you are using PXE-based provisioning, upgrade the PXE server.
To upgrade the PXE server on Windows
 Click here to review the steps for upgrading a PXE server on Windows.

  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.

Related topic: Upgrading a PXE server on Windows

To upgrade the PXE Server on UNIX or Linux

Note: If PXE is installed on the Application Server, the Application Server installer will upgrade it automatically.

 Click here to review the steps for upgrading a PXE server on Linux or UNIX computer where the PXE server was not installed as part of the Application Server installation. (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 8.2.00 installation script ...
    A previous installation has been detected. This installation will be upgraded to BMC BladeLogic BMC BladeLogic Server Automation 8.2.00.
    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.

Related topic: Upgrading a PXE server on Linux or UNIX

Upgrade the 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. On the Installation preview window, click Install.

Note

If you stopped the RSCD Agent before upgrading the console, restart it before you begin the next process.

Related topic: Upgrading the BMC Server Automation Console 

Upgrade the RSCD agents, as needed.
To upgrade agents on Windows

  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.

Note

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. For steps on upgrading custom configuration objects, see Upgrading custom configuration objects.

Related topic: Upgrading RSCD agents on Windows

To upgrade agents on UNIX or Linux

  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) ?

    Note

    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 8.2.00 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.

Note

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. For steps on upgrading custom configuration objects, see Upgrading custom configuration objects.

Related topic: Upgrading the RSCD agent on Linux and UNIX

Run 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. Run a Distribute Configuration Objects Job to distribute the latest version of custom configuration objects stored in the Configuration Object Dictionary. The job should target agents that you have upgraded. The system prevents you from distributing custom configuration objects to agents running an incompatible version. For more information, see Creating or modifying a Distribute Configuration Objects Job.
  3. 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.
  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.

    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

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

Comments