Preparing to upgrade individual components on UNIX and Linux
This topic provides the information you need to prepare your environment for the upgrade process on Linux and UNIX systems using individual component installers. It includes information about supported upgrade paths and instructions for preparing to upgrade the BMC Server Automation system.
The topic includes the following sections:
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:
The following sections provide information about the latest builds and the supported upgrade paths.
EPD version number
|Patch 5 for version 8.7||8.7.00.306||8.7.00.005||July 7, 2017|
|Patch 4 for version 8.7||8.7.00.295||8.7.00.004||November 19, 2016|
|Patch 3 for version 8.7||8.7.00.280||8.7.00.003||June 8, 2016|
|Patch 2 for version 8.7||8.7.00.263||8.7.00.002||January 6, 2016|
|Patch 1 for version 8.7||8.7.00.256||8.7.00.001||December 3, 2015|
Base version 8.7
September 15, 2015
EPD version number
|Patch 2 for version 8.6 SP1||8.6.01.107||8.6.01.002||October 15, 2016|
|Patch 1 for version 8.6 SP1||8.6.01.71||8.6.01.001||December 3, 2015|
|Service Pack 1 for version 8.6||8.6.01.66||8.6.01||May 18, 2015|
|Patch 1 for version 8.6||8.6.00.216||8.6.00.01||December 15, 2014|
Base version 8.6
December 12, 2014
Supported upgrade paths
BMC Server Automation supports direct upgrade from versions 8.5.xx and 8.6.xx. If you need to upgrade from BMC Server Automation version 8.3.x. or earlier, you must first upgrade to one of the following:
- The latest 8.6 service pack, (as discussed in the Upgrading section of the BMC Server Automation 8.6 online documentation)
- The latest 8.5 service pack, (as discussed in the Upgrading section of the BMC Server Automation 8.5 online documentation)
Afterwards, you can upgrade from version 8.5.xx or 8.6.xx to 8.7.x.
The following figures illustrate the supported upgrade paths to BMC Server Automation 8.7.x.
In the above diagrams, abbreviations are defined as follows:
- BSA stands for BMC Server Automation
- SP stands for Service Pack
- P stands for Patch
Step 1: Review requirements and limitations
Prior to upgrading, it is important to carefully review the following requirements and limitations.
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
If your BMC Server Automation environment includes BMC Cloud Lifecycle Management, you need to ensure that you maintain compatibility with BMC Cloud Lifecycle Management. For more information, see the following topic in the BMC Cloud Lifecycle Management online technical documentation:Component BMC product service pack and patch levels
For a complete list of platforms supported by the component installers, see:
|X server requirement|
You must run the installer from a computer where an X server is installed. Follow these steps before you install the product from a computer with the X server software:
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. Therefore, as part of the upgrade process, you must distribute the latest versions of the custom configuration objects that are not included as part of an RSCD agent.
The product installation is automatically upgraded to the appropriate version when you upgrade the agent. However, you must upgrade any custom configuration objects that are not included with the agent by running a Distribute Configuration Objects Job. Configure this job to target servers to which custom configuration objects need to be distributed. For a list of those objects that are included as part of an agent installation and those that are not included with the agent and require distribution, see Custom configuration objects.
To upgrade custom configuration objects
Click here to see the steps for upgrading custom configuration objects.
To upgrade virtualization configuration objects
Click here to see the steps for upgrading virtualization configuration objects.
The Upgrade Model Object Job is not supported for upgrading virtualization configuration objects.
To upgrade configuration objects that you distributed in prior versions, complete the following steps:
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. Therefore, as part of the upgrade process, you must distribute the latest versions of custom configuration objects for the custom configuration objects that are not included as part of an agent. The installation are automatically upgraded to the appropriate version when you upgrade the agent. (See Custom configuration objects for a list of those objects.) You should upgrade any custom configuration objects not included with the agent by running a Distribute Configuration Objects Job. The job should target servers to which custom configuration objects should be distributed.
Click here to review a list of potential issues you can encounter during an upgrade.
If your id.pem certificate was created with a key size of 1024 bits (or less), you will need to regenerate it with a higher key size (2048 or higher). This is due to a change in the FIPS requirement for minimum key length (now 2048 bits).
Step 2: Prepare the database
During an upgrade process, core data is migrated to the upgraded BMC Server Automation database. To ensure that this migration completes successfully, you must prepare your database before performing the upgrade. To prepare your database, review the following list of prerequisite tasks and perform the tasks that are relevant for your environment.
|Back up the BMC Server Automation database.|
You must back up before beginning the data upgrade process.
The data upgrade occurs in place. If, for any reason, it should become impossible to complete the upgrade, the only way to
Checking for temp space (when upgrading from 8.3 or earlier only)
Note: If you are upgrading from version 8.5 or later, you do not need to perform this step.If you are upgrading from version 8.3 or earlier, you must first upgrade to the latest 8.5 or 8.6 service pack. Prior to this interim upgrade, you must ensure that your Oracle database has the free space required for successful data migration. To determine those requirements, use the sizing_8x_temp_undo.sql script provided by BMC Server Automation.
For details see Determining sizing requirements for Oracle databases in the online technical documentation for BMC Server Automation version 8.5. (This task is not required if upgrading from version 8.5 or later).
|Remove unnecessary deployments|
The migration process uses the database system ID information in the _template deployment to identify the database to migrate. In addition,
Certain deployments are transitory and can be removed before an upgrade as they are not needed for normal operation.
|Ensure that the database configuration information on the deployments of the Application Server is up-to-date|
Before upgrading the Application Server, ensure that the database configuration information on the deployments of the
You can use the blasadmin utility to check the database related and file server related information for each of the deployments (except _launcher).
You can use the following blasadmin commands. If either of these commands returns an error, you can use the blasadmin utility to
If these commands return an error, use the blasadmin utility to correct the configuration so that those commands do not return an error.
|(Oracle only) Grant privileges explicitly to the user account|
For an Oracle database, you must grant certain privileges explicitly to the user account (typically BLADELOGIC) that will be used during the upgrade.
Some of the privileges can be revoked after database migration is performed during the upgrade. For the complete list, see List of required database permissions.
Step 3: Prepare the automation environment
Perform these tasks in order. Many steps are prerequisites for other steps that occur later in the process.
- 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.
- Shut down the BMC Server Automation environment:
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:
Ensure that there is an agent installed on the Application Server. For agent installation on Linux or UNIX, use the
-localoption (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.
- Ensure that you have 4 GB on disk with temp space and 4 GB on disk with installation directory.
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=ssoproxyentry 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