Upgrading silently using the unified product installer
As an alternative to performing an interactive upgrade, you can perform an unattended (silent) upgrade of BMC Server Automation on 64-bit Linux and Windows platforms. In a silent installation, you run the unified product installer through a command line.
For lists of the product components that are upgraded and those that are not upgraded by the unified product installer, see the introductory sections in Upgrading on Windows using the unified product installer. This 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:
Before you begin
Ensure that your environment meets the requirements discussed in Preparing for a Windows upgrade using the unified product installer and Preparing for a Linux or UNIX upgrade using the unified product installer.
For BMC Server Automation versions 8.6 SP1 and later, the task of running SQL Update scripts, which was necessary in the past for any upgrade to a BMC Server Automation patch or service pack, is no longer required during an upgrade. The database upgrade is now handled internally by the unified product installer, which was introduced in version 8.6.
step 4 below), use the BSAOneClickInstallMaintenanceTool utility provided in the installation package. After extracting the package (step 1 below), you can find this utility in the temporary directory: \Disk1\utility\BSAOneClickInstallMaintenanceTool.cmd (for Windows) or /Disk1/utility/BSAOneClickInstallMaintenanceTool.sh (for Linux).
You can run this utility in the following ways:
- Interactively - Run the utility, enter your password on the Encrypt tab, and click Encrypt
- Silently - Run the following command from the directory where the utility is located:
BSAOneClickInstallMaintenanceTool.cmd -silent -encrypt -encrypt -password=<password> -confirm_password=<password>
- (Linux) ./
BSAOneClickInstallMaintenanceTool.sh -silent -encrypt -encrypt -password=<password> -confirm_password=<password>
To upgrade in silent mode
- Download and extract the installation package appropriate for the operating system level and hardware platform in a temporary directory. The package follows the naming convention BBSA<version>-<platform>.zip, and contains the unified product installation program files.
Download this package to the host computer of the Application Server that was set up as a configuration server (for more about this type of Application Server setup, see
). If this is a Linux computer, ensure that it has an RSCD agent installed and running.
Extract the RSCDAgent.zip file and copy the rscd folder to one of the following locations before running the unified product installer (The unified product installer uses the RSCD installers while installing or upgrading BMC Server Automation in your environment):
If you are on a Linux machine, assign executable permission to the temporary directory by entering the following command:
chmod +x -R <temporary directory>
In addition, if the temporary directory is at the end of a path (that is, has at least one parent directory), assign read permission to the others class (which includes the bladmin system user) for all directories in the path. To do this, execute the following command on the top-level directory in the path:
chmod o+r -R <top-level directory>
Use the following options to enable access to the Application Server during the upgrade:
Option Description of value
Name of a profile on the Application Server to use during the upgrade for SRP authentication. The profile that you specify must be associated with the same Application Server where you are performing the upgrade.
Name of a user for SRP authentication.
A valid password for the specified user.
PXE Server option
Use the following option to specify a list of remote PXE servers during upgrade of BMC Server Automation:
Option Description of value
A list of PXE servers that reside on hosts that are separate from the current Application Server. This enables the installer to copy installation files to the remote hosts.
To specify the remote PXE servers, use the following format:
Use semicolons between hosts, and enclose the full list in quotation marks.
Note the following additional scenarios:
- If you do not have any PXE server in your BMC Server Automation environment, do not use this option.
- If you have one or more PXE servers in your BMC Server Automation environment, but they are not remote (that is, they reside together with the Application Server), specify this option with an empty value:
Use the following options to authorize the installer to install an RSCD Agent on any remote server where an RSCD Agent is not yet installed (as will be detected by the installer during the upgrade):
Option Description of value
The name of the local super user — root or root-equivalent user on Linux, local Administrator or Administrator-equivalent local user on Windows — to which the RSCD Agent should map incoming connections during the installation.
Host name or IP address of the PSExec host computer.
Whether to use the same credentials (user name and password) to access all remote servers where the RSCD Agent is not yet installed — either
The following options are relevant only when
The name of a user authorized to establish an SSH connection with all remote hosts where the RSCD Agent is not yet installed.
A valid password for the specified user name.
The password once again, for confirmation. The following options is relevant only when
A list of the remote hosts where an RSCD Agent is not yet installed, along with separate credentials for each of these hosts.
To specify the hosts and logon credentials, use the following format:
Use commas within each set of credentials (for each separate host). Use semicolons between sets of credentials. Enclose the full list in quotation marks.In a text editor, create an options file and define values for the relevant upgrade options. Define each option on a separate line. Below is a list of available upgrade options, by category:
Change directory (
cd) to the location where the installation file (setup.exe for Windows or setup.bin for Linux) resides in the temporary directory.
Run the installation program with the
-i silentoption, using the following command. Use an absolute path to the options file. Enclose the path in double quotation marks (" ").
setup.exe|setup.bin -i silent -DOPTIONS_FILE="<OptionsFilePath>"
If product components are detected during the upgrade on remote Windows machines in the BMC Server Automation environment, installers are automatically copied to the C:\BBSAInstallerDumpDir directory on the remote machines. These installers are used to automatically upgrade product components on those machines.
During the upgrade, the original Application Server deployments are backed up. The backup files are stored in <installation directory>/br.
The installation log file, bsainstallupgrade.log, is stored in %TEMP% (on Windows) or in /tmp (on Linux). For more information about the log files created by the unified product installer, see the Troubleshooting section.
Where to go from here
The unified product installer automatically installs agent installer jobs and depot objects such as agent installers and agent bundles that can be used for installing or upgrading agents on servers in the environment. The agent installers, agent bundles, and agent installer jobs are present in the following locations:
Object Depot Path Can be used for Installers /Depot/BMC Maintenance/Agent Installers/ Agent install and upgrade Bundles /Depot/BMC Maintenance/Agent Bundles/ Agent upgrade Jobs /BMC Maintenance/Agent Installer Jobs/ Agent upgrade
The agent installer for the Solaris platform requires additional configuration before first use. See Additional information for Solaris installation packages.
For more information about using these objects, see Installing one or more agents using the BMC Server Automation Console and Upgrading the RSCD Agent using an Agent Installer Job.
Modifying the name or path of these depot objects may cause errors in the agent installation process.
- Upgrade any remaining product components that were not upgraded by the unified product installer.
- If you adjusted security settings before the upgrade (as described in the troubleshooting instructions for security settings), remember to re-adjust your security settings, based on your unique needs and the IT security policies at your organization.
- On SuSE 11, the Application Server does not start automatically at the end of the upgrade. You must start the Application Server manually at the end of the upgrade using the following command: