Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Before you upgrade

This topic provides information and instructions on tasks that must be completed before upgrading. By completing these tasks you will avoid data loss (for example, in the reports data warehouse) and upgrade failure.

Verify ETL

Ensure that all ETL runs have completed and that ETL is not running by using Metadata Navigator. For more information about Metadata Navigator, see Using-the-Metadata-Navigator.

Verify versions

  • Ensure that you have version 8.1 or later of 

    The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    Network Shell installed.
  • Verify that you are upgrading from a supported version.
     For more information about supported versions, see Supported-upgrade-paths.

Run the database assessment script

You run the database assessment script, bdssa_db_config_recommendation.sql, with the Database Administrator role. The assessment script checks if the database-level parameters are compliant with the BMC recommended settings. Update the database-level parameter settings to the BMC recommended values as specified in the script output.

Note

Upgrading the database without updating the non-compliant parameters might result in database upgrade taking a long time or causing an upgrade failure due to insufficient space.

  1. Click the BMC BladeLogic Decision Support for Server Automation 8.2.00 servicepackVersion Upgrade Help Toolkit link on the BMC Electronic Product Distribution (EPD) website.
  2. Extract the BDSSA82-Upgrade-Help-Toolkit.zip file to the BLREPORTS_HOME directory. The bdssa_db_config_recommendation.sql file is extracted into the BLREPORTS_HOME/BDSSA82-Upgrade-Help-Toolkit/dbscript directory.
  3. From the command prompt, navigate to the dbscript directory.
  4. Log on to SQLPlus as a sysdba user.

  5. Enter the following command:

    SQL> @bdssa_db_config_recommendation.sql

    Note

    Ensure that you have the write permission to create the spool file when you run bdssa_db_config_recommendation.sql script.

    You can view the output of the command in the bdssa_db_config_recommendation_log.out file created in the current working directory. This output file contains the database-level parameters and their current settings and also determines whether these settings are compliant with the BMC recommended settings.

Back up databases and Inventory templates

  • Back up the following databases:
    • Reports warehouse database
    • The portal content store database 
    • ETL (ODI) master and ETL (ODI) work repository databases
  • Back up the Inventory templates.

Export reports

You can export reports by using the export utility available in Content Administration in IBM Cognos Administration (see IBM Cognos Administration and Security Guide at PDFs).

All reports are exported to a zip file that is located on the reports server in the BDSSAInstallationDirectory/portal/deployments directory. When the report export is complete, ensure that you back up the export file to another known location.

Back up your customized files

If you customized files (for example, if you manually edited any portal configuration files), these changes are not maintained when you upgrade the product. You must reapply those changes. Before upgrading the product, back up your files so that you can use them to restore your customizations.

You can replace some of the new files with your original customized files after the upgrade, but not all of them. Some files are modified during the upgrade and you cannot replace them with your older customized files. Instead, you must modify the new files after the upgrade. Record the directory path of the customized files so that you can copy them to the correct location after the upgrade or easily locate the new files that you need to customize.

Back up the following files:

  • system.xml files in the BDSSAInstallationDirectory/portal/templates/ps or the BDSSAInstallationDirectory/portal/templates/ps/qs directory. After upgrade, you can replace this file with the back up copy.
  • coglocale.xml in the BDSSAInstallationDirectory/portal/configuration directory. After upgrade, you can replace this file with the back up copy.
  • server.xml in the BDSSAInstallationDirectory/portal/tomcat4.1.27/conf or BDSSAInstallationDirectory/portal/tomcat/conf directory. After upgrade, you can replace this file with the back up copy.
  • blappserv_login.conf and blappserv_krb5.conf in the BDSSAInstallationDirectory/br directory. After upgrade, you can replace this file with the back up copy.
  • system.xml file in the BDSSAInstallationDirectory/portal/templates/ps/portal directory. After upgrade, you cannot replace this file with the back up copy. You must reapply your changes to the new file.

If you exported any report content, you should back up these files so that you can import the content from the files after the upgrade. For more details about exporting and importing, see Importing-and-exporting-report-definition-content-and-package.

Where to go from here

Supported-upgrade-paths
Performing-the-upgrade

 

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