Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Upgrading a small, medium, or large deployment of the BladeLogic Portal

This topic describes how to upgrade a small, medium, or large deployment of the BladeLogic Portal and how to migrate your existing database. These deployments have the BladeLogic Portal server and one or more instances of the DCA Index Server installed on different systems. For more information on deployment types, see Deployment-scenarios.

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.

Before you begin

  1. Review the upgrade pre-requisites described in the "Before you begin the upgrade" section of the main Upgrading topic.
  2. Ensure that you have completed all preliminary tasks described in the "Upgrade procedures based on deployment type" section of the main Upgrading topic.
  3. Set the UNICODE_SUPPORT flag to false for all versions of BladeLogic Portal earlier than version 2.2.01.
    Because of a known issue (DRBLY-30368) in previous releases that prevented the creation of Unicode-compliant databases, you must manually set a flag in the BladeLogicPortalInstalledConfiguration.xml file. You must always perform this action no matter whether you want Unicode or not and whether you are using SQL Server or Oracle.These steps are not necessary if you are upgrading from version 2.2.01 or later.
    1. Navigate to the install location for BladeLogic Portal.
      Typical locations:
      Windows: C:\Program Files\BMC Software\BladeLogicPortal
      Linux: /opt/bmc/BladeLogicPortal
    2. Open the BladeLogicPortalInstalledConfiguration.xml file for editing.
    3. Find the property called UNICODE_SUPPORT. It should appear as follows:
      <property>
            <name>UNICODE_SUPPORT</name>
            <value>true OR false</value>
    4. Set the value to false and save the file.
  4. Take the following actions, depending on the version being upgraded:

    • If you are upgrading from BladeLogic Portal version 2.1:

      • Ensure that you have manually upgraded the DCA Indexing Server by:

        1. Removing the version 2.1 instance(s) from the remote host(s), as described in the "Upgrade procedures based on deployment type" section of the main Upgrading topic.
        2. Installing a version 2.2 or later DCA Indexing Server.  
      • Be aware that an error could occur during the data migration portion of the upgrade. To prevent that error, you can obtain scripts from knowledge base article (000123043). The article provides one script for Oracle and another for SQL Server. Run the scripts to correct the issue before beginning the upgrade procedure.
    • If you are upgrading from BladeLogic Portal version 2.2 or later, ensure that the DCA Index server is upgraded.

How to upgrade a small, medium, or large deployment of the BladeLogic Portal

In this procedure all screen shots depict an upgrade to BladeLogic Portal version 2.2.01. If you are upgrading to another version of the product, the procedure is the same but version numbers that appear in in the upgrade wizard are different.

  1. Copy the installation file to an appropriate location on the computer where you are upgrading the portal.
    • Windows: the installation file is called BTD22.WIN64.zip.
      In versions earlier than 2.2.01, the file is called BLPortal22.WIN64.zip.
    • Linux: the installation file is called BTD22.LIN64.tar.gz.
      In versions earlier than 2.2.01, the file is called BLPortal22.LIN64.tar.gz.
  2. Extract the contents of the installation file. 
    This extraction generates a file structure where the top level directory is named BladeLogicPortal.
  3. Navigate to the installer program and launch it.
    • Windows: Navigate to \BladeLogicPortal\windows\Disk1, right-click setup.exe, and select Run as Administrator.

    • Linux: Change (cd) to BladeLogicPortal/linux/Disk1 and enter the command ./setup.bin

      Note

      For Linux, make sure BladeLogicPortal/linux/Disk1/setup.bin has execute permissions. If necessary, run the following command to grant execute permission on the file: 
      chmod +x BladeLogicPortal/Disk1/setup.bin

      The portal installer program opens.

      Splash2201.gif

  4. Select the language you want to use in the installation program and click OK.
    A welcome window opens. 

    UpgradeWelcome2201.gif

  5. Click Next.
    The Select Product features window opens.

    Note

    If you are upgrading from BladeLogic Portal 2.1, you must manually upgrade the DCA Indexing Server by removing the version 2.1 instance(s) from the remote hosts as described in the "Upgrade procedures based on deployment type" section of the main Upgrading topic, and then installing a version 2.2 or later DCA Indexing Server. During the upgrade, the installer will detect that the DCA Index Server for this Portal Server is pointing to a the remote host, and not the local host. The DCA Index Server on this host does get upgraded, but the service is not started.


    UpgradeFeatures2201.gif

  6. Click Next.
    A window outlining special precautions you should take prior to upgrading appears. Before upgrading, ensure that you:
    1. Take a snapshot of the VM or backup the physical server(s) where the Bladelogic Portal and the DCA Indexing Server are running.
    2. Backup the database for the BladeLogic Portal. 
  7. Click Next.
    A window provides an option to configure a connection to BMC Network Automation, which was introduced in version 2.2. If you are using Threat Director, you are able to monitor network vulnerabilities by connecting to an existing BMC Network Automation installation.
    SelectFeatures.GIF

  8. To enable a connection to BMC Server Network Automation, select the option and click Next.
    A window requests information about the connection to BMC Network Automation.
    InstallerBNA.gif
  9. Provide the following connection information:
    • Host Name—Fully qualified name or IP address of the server that hosts the BMC Network Automation application server.
    • HTTPS Port—Web service communication port configured on the BMC Network Automation application server. Typically, the application server is configured to use 443 for its web server communication port.
    • User Name—Name of the administrative user for BMC Network Automation. This user should have access to all device objects in BMC Network Automation. For this version of the portal, use sysadmin.
    • Password—Password for the administrative user.
    • Realm Name—Name of the realm that represents the network or set of devices managed by BMC Network Automation. Each device belongs to a single realm. When you initially install BMC Network Automation, all devices belong to a single realm called Default.
  10. Click Next.
    A window requests information to configure the user details that enable BladeLogic Portal to access the most current information from BMC Server Automation.
    Note that this window only appears when upgrading to version 2.2.01. When upgrading to earlier versions, this window does not appear. 

    DataRefreshBSA2201.gif
  11. Provide the following credentials for the Data Refresh user:
    • User Name—Name of a BMC Server Automation user with credentials that can be used for obtaining data from BMC Server Automation. 
    • Password—Password for the user.
    • Auth Method—Method for authenticating the user with BMC Server Automation. Possible choices are Secure Remote Password, Domain Authentication, and LDAP Authentication. Other forms of authentication such as RSA are not compatible with the Data Refresh mechanism.
    • Role Name(s)—One or more roles with at least read-level access to BMC Server Automation. When entering multiple roles, use a comma-separated list. To learn more about specifying roles with a minimum set of permissions, see Configuring-Data-Refresh. 
    • Select Use the credential specified above for automated scan import if you plan to set up a scanner connection used for automatic scan imports. 

  12. Click Next.
    A window requests information to configure the user details that enable BladeLogic Portal to access the most current information from BMC Network Automation.

    DataRefreshBNA2201Labelled.gif

  13. Provide the following credentials for the Data Refresh user:
    • User Name—Name of a user with at least read-level access to BMC Network Automation. 
    • Password—Password for the user.
    • Select Use the credential specified above for automated scan import if you plan to set up a scanner connection used for automatic scan imports. This option is new in version 2.2.01 and does not appear when upgrading to earlier versions.
  14. Click Next.
    A window describes the existing portal database that the installer has detected. It asks if you want the installation program to migrate the existing portal database.
    If you do not want the installer to migrate the database, click Cancel and use the procedure for manually migrating the portal database.
    PreviousDBDetected2201.gif

  15. Select Migrate Portal database and click Next.
    An information window provides the status of the database migration. If the migration is successful, the window instructs you to create a backup of the database (as shown below). If problems occur during the final phases of the upgrade, having a backup enables you to skip the database migration phase should you need to re-run the upgrade.  
    upgradeBackUpDB.GIF
    If the migration was not successful, the window instructs you to check the upgrade log file for errors. The log file is located in:

    Windows:%TEMP%\bmcautomationportal_install_log.txt
    Linux:/tmp/bmcautomationportal_install_log.txt
    After the errors are resolved, you can retry the migration by clicking Previous and then clicking Next.

  16. Click Next.
    A preview window describes the installation to be performed.

    UpgradePreview2201.gif
  17. Click Install.
    Progress bars show installation activity until the Installation Summary window provides details about the completed upgrade.
  18. Click Done.

Troubleshooting the upgrade

If you encounter issues with the upgrade, see the following sections in Troubleshooting-an-installation-or-upgrade:

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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*