Upgrading
When you upgrade an existing version of BladeLogic Portal, you can migrate the existing database and update the portal software using the same installation program.
When you upgrade, you should take all necessary preliminary steps, such as backing up all relevant data.
This topic includes the following sections:
Supported upgrade paths
BladeLogic Portal supports the following upgrade paths:
Current configuration | Possible upgrade paths |
---|---|
Compact, small, medium, or large deployment | 2.2.01 → 2.2.02 |
2.2.00.002 → 2.2.02 2.2.00.002 → 2.2.01 | |
2.2.00 → 2.2.02 2.2.00 → 2.2.01 2.2.00 → 2.2.00.002 | |
2.1.00 → 2.2.02 2.1.00 → 2.2.01 2.1.00 → 2.2.00.002 2.1.00 → 2.2.00 | |
Stand alone DCA Index Server | 2.2.01 → 2.2.02 |
2.2.00.002 → 2.2.02 2.2.00.002 → 2.2.01 | |
2.2.00 → 2.2.02 2.2.00 → 2.2.01 2.2.00 → 2.2.00.002 |
Required supporting products
When upgrading, you must be running supported versions of your endpoint managers ( (BMC Server Automation or BMC Network Automation):
Endpoint manager | Supported versions |
---|---|
BMC Server Automation | 8.7 patch 3, patch 4, patch 5 |
8.8.x | |
8.9.x If you are using Threat Director for SuSE 12 patch analysis with zypper support, you must be running BMC Server Automation 8.9 patch 1 or later. Note: TrueSight Server Automation version 20.02 or later is not supported with the fresh or upgraded installation of BladeLogic Portal version 2.2.x. | |
BMC Network Automation | 8.9 or later |
If you are running SQL Server, only Microsoft SQL Server 2012 (or later) is supported for database upgrade/migration.
Note
All versions of BladeLogic Portal earlier than 2.2.01 did not support Unicode. Even if you selected Unicode Support when installing BladeLogic Portal, a known issue (DRBLY-30368) prevented creation of a Unicode-compliant database. When upgrading earlier versions to version 2.2.01, conversion from a non-Unicode to a Unicode database is not possible.To create a Unicode database, you must perform a fresh installation.
Upgrade procedures based on deployment type
The upgrade procedures vary depending on the type of deployment you are upgrading:
- A small, medium, or large deployment has the BladeLogic Portal server and one or more instances of the DCA Index Server installed on different systems.
- A compact deployment has both the portal and the DCA Index Server installed on the same system, and is typically used for testing and demonstration purposes rather than production.
For more information on deployment types, see Deployment scenarios.
The table below outlines the tasks involved with upgrading each type of deployment.
Deployment | Procedure |
---|---|
Small, medium, or large |
This procedure results in the following:
|
Stand-alone DCA Index Server (upgrade only available for version 2.2 or later) |
|
Compact |
This procedure results in the following:
|
Before you begin the upgrade
- Download the installation files needed to install and upgrade BladeLogic Portal.
- The upgrade must run on the following platforms:
- 64-bit Microsoft Windows 2008 or 2012
- 64-bit Red Hat Enterprise Linux versions 6.0 (or later) or 7.0 (or later)
- If you are running SQL Server, note that only Microsoft SQL Server 2012 (or later) is supported for database upgrade/migration.
- A supported version of BMC Server Automation must be installed and its Application Server started.
Supported versions:
- Version 8.7 patch 3, patch 4, patch 5
- Version 8.8.x
- Version 8.9.x
- BMC Network Automation version 8.9 must be installed and its application server started, if you are using Threat Director and monitoring network vulnerabilities.
- The BladeLogic Portal server, the portal database, and the BMC Server Automation Application Server must all reside on the same LAN.
- Ensure you are performing the upgrade on the same computer where the existing installation of BladeLogic Portal is running.
- Port number 9300 should be free to allow for transport layer traffic with the DCA Index Server that is installed as part of this procedure. If the installation indicates there is a problem communicating with the DCA Index Server, you can manually specify a port.
Ensuring a clean portal server
To ensure the portal server is a clean environment with no operations currently running, shut down the portal server and then reboot it.
- Shut down the portal server using the following actions:
- Linux:
/etc/init.d/BladeLogic_Portal stop
- Windows: From the Windows Control Panel, select Administrative Tools > Services . Then stop the BladeLogic Portal service.
- Linux:
- Restart the portal server using the following actions:
- Linux:
/etc/init.d/BladeLogic_Portal start
- Windows: From the Windows Control Panel, select Administrative Tools > Services . Then start the BladeLogic Portal service.
- Linux:
Backing up portal information
The following sections describe backup tasks that BMC recommends you perform before installing or upgrading.
Backing up portal installation information
A good precaution is to back up information describing the location of the current BladeLogic Portal installation.
Backing up portal installation information in Linux
- Open the /opt/bmc/ProductRegistry.xml configuration file.
- Within that file, search for:
<productHomeVariableName>BMC_AUTOMATION_PORTAL_HOME</productHomeVariableName> - In the line above, find
<productHome><PORTAL_HOME></productHome>
.
In that row,<PORTAL_HOME>
identifies the path to the portal installation. - Cd to
<PORTAL_HOME>
. - Determine a location with sufficient disk space to which you can copy portal information. This procedure calls that location <BMCPortalV2.2_FULLBACKUP>.
- Copy the contents of the portal installation by entering the following command:
find . --depth --print | cpio --dump /<BMCPortalV2.2_FULLBACKUP>
- Copy /opt/bmc/ProductRegistry.xml to <BMCPortalV2.2_FULLBACKUP>.
Backing up portal installation information in Windows
Open the \Windows\ProductRegistry.xml configuration file.
Within that file, search for:
<productHomeVariableName>BMC_AUTOMATION_PORTAL_HOME</productHomeVariableName>In the line above, find
<productHome><PORTAL_HOME></productHome>.
In that row,
identifies the path to the portal installation.<PORTAL_HOME>
Cd to
<PORTAL_HOME>
.Use any backup tool to make a copy of the
<PORTAL_HOME>
directory to <BMCPortalV2.2_FULLBACKUP>.Copy \Windows\ ProductRegistry.xml to <BMCPortalV2.2_FULLBACKUP>.
Backing up the portal database
A database administrator must perform a full backup of the portal database. The administrator should create a backup dataset in case a backout or restore procedure is needed.
Use this procedure to obtain the information needed to access the existing portal database.
- Open <PORTAL_HOME>/portal/configuration/bmc-config.json.
See Backing up portal installation information to determine the location of <PORTAL_HOME>. - Within the bmc-config.json file, find the section called foundation_db_service.
It provides the host name, port, user, database name, and database type for the portal database.
Backing up configuration information
BMC recommends you back up the following important configuration file:
<PORTAL_HOME>/portal/configuration/bmc-config.json
Troubleshooting the upgrade
If you encounter issues with the upgrade, see the following sections in Troubleshooting an installation or upgrade:
- What do I do if the database migration fails during upgrade?
- How do I manually synchronize the database with the DCA Index Server?
- How do I add a second BMC Server Automation or BMC Network Automation primary site after installing or upgrading?
- How do I connect the portal to a different database?
- I'm seeing a database migration error with duplicate keys.
Where to go next
Set up a backup procedure for the DCA Indexing Server. If BladeLogic Portal was already installed and you have just installed another instance, you must be certain that each instance has an identical backup configuration.
If you want to disable HTTP traffic with the DCA Indexing Server, see Disabling or enabling HTTP traffic with the DCA Indexing Server.
If you are using roles with a limited set of permissions for Data Refresh, see Configuring Data Refresh.
When those tasks are complete, see Configuring after installation.
Comments
Log in or register to comment.