Step 3: Upgrading BMC ProactiveNet Report Engine

After backing up the existing universe, you can upgrade BMC ProactiveNet Report Engine.

Supported upgrade paths

The following table lists the supported versions for direct upgrade to 9.6.00:

You cannot directly upgrade to BMC ProactiveNet Report Engine 9.6.00 from 8.6.xx. To upgrade to BMC ProactiveNet Report Engine 9.6.00, perform the following steps:

1. Upgrade to BMC ProactiveNet Report Engine version 9.0.xx or 9.5.02.
   For information about upgrading to version 9.0.xx, see https://docs.bmc.com/docs/display/public/bppmreporting90/Performing+the+upgrade.
   For information about upgrading to version 9.5.02, see https://docs.bmc.com/docs/display/public/bppmreporting952/Step+3%3A+Upgrading+BMC+ProactiveNet+Report+Engine. 
2. Upgrade to BMC ProactiveNet version 9.6.00.

You cannot directly upgrade to BMC ProactiveNet Report Engine 9.6.00 from 9.5 or 9.5.01. To upgrade to BMC ProactiveNet Report Engine 9.6.00, perform the following steps:

1. Upgrade to BMC ProactiveNet Report Engine version 9.5.02. 
   For information about upgrading to version 9.5.02, see https://docs.bmc.com/docs/display/public/bppmreporting952/Step+3%3A+Upgrading+BMC+ProactiveNet+Report+Engine. 
2. Upgrade to BMC ProactiveNet version 9.6.00.

To upgrade BMC ProactiveNet Report Engine

1. Log in as an administrator (Windows) or a root user (Linux/Solaris).

1. Back up the BMC_PROACTIVENET_REPORTENGINE_HOME directory.
2. (Windows) Backup the %SystemRoot%\ProductRegistry.xml and %SystemRoot%\ProductRegistry.xsd files.
3. Back up the Report Engine Database.
4. Close all the running applications, folders, and command prompts related to Report Engine. For example, bppmr_config.bat.

5. Navigate to the Reports/ReportEngine/<platform> folder, where <platform> is Solaris/Linux or Windows.
   
   

   Note

   If there is not enough space in the temporary directory, the system prompts you to select an alternate directory. On UNIX-based computers, you can set the IATEMPDIR environment variable to an alternate directory which has enough space.

   • For Windows, double-click ReportEngine9.6.00_bbuildNumber.exe.

   • For Solaris and Linux systems, at the command line, run the command: ReportEngine9.6.00_b<buildnumber>.bin

     Note

     For Solaris and Linux installations, the installation file supports only the graphical user interface (GUI) mode, not the console or silent mode.

6. In the Welcome page, click Next.
7. In the License Agreement page, click I agree to the terms of the license agreement.
8. Enter BPPM Server Cell Name on the BPPM Server Registration Page.  
9. In the Feature Selection page, select the appropriate features that you want to install.
    If you manually imported BIAR files before the upgrade, the installer will not detect this and will continue to show the Import universe and Reports option. Click Next and continue with the upgrade as follows.
   • Upgrade BMC ProactiveNet Report Engine 9.6.00
   • Import universe and reports 9.6.00 — imports the BMC ProactiveNet Performance Management universe and reports into SAP BusinessObjects Enterprise automatically. This eliminates the need for manual import. If you are installing BMC ProactiveNet Report Engine for the first time, BMC recommends to use the automatic import option.

10. In the SAP BusinessObjects BI CMS Server Information page, provide the necessary information using the values that you populated in the Planning sheet for installation and configuration, and click Next.

    Note

    If you deselect the Import Universe and Reports checkbox on the Feature Selection page, the BusinessObjects Information page is not displayed. Post-installation, you can import the BPPM_DataMart.lcmbiar or BPPM_DataMart_96.lcmbiar manually using the steps described in Manually-importing-the-BMC-ProactiveNet-Performance-Management-universe-and-reports-into-supported-SAP-BusinessObjects.

11. In the Installation Preview page, click Install.
    
    

    Note

    If you have BMC Impact Manager version earlier than 9.5.00, ensure to add the following entries in the gateway.reportengine file located in the BMCProactiveNetServerInstallationDir\pw\server\etc directory and restart BMC Impact Manager before proceeding with the installation:

    add.new=[cell_name=$CNAME]

    add.mod=[cell_name=$CNAME]

    The installer begins the installation process.

12. Click Done.
    
     BMC ProactiveNet Report Engine is upgraded, and the latest BMC ProactiveNet Performance Management universe and reports are also imported.

To upgrade multiple Report Engines that use a single database

• If your environment consists of multiple Report Engines (9.0.22 or 9.5.02) that point to a single database, you can directly upgrade the Report Engine 9.6.00. Perform the following steps:

1. 
   
   1. Stop Report Engine service for all report engines.
   2. Upgrade all report engines one-by-one. 
   3. Migrate all report engines. See Step-4-Migrating-existing-data.

• If your environment consists of only a single Report Engine, you can directly upgrade the Report Engine from a previous version (9.0.00, 9.0.20, 9.0.22, or 9.5.02) to 9.6.00. Later, you can install more instances of the Report Engine and use the same database user that you used in while upgrading the single instance of the Report Engine.

To upgrade from 32-bit BMC ProactiveNet Report Engine

If you are upgrading from 32 bit BMC ProactiveNet Report Engine, from any of the versions mentioned in the table, you must perform the following steps: 

1. Access the database host to run the Export command and copy the exported dump in the database host.
2. Create new Report Engine User as described in Creating-tablespaces-and-user-on-Oracle-database. Import the dump that you exported in the previous step.
3. Start a fresh installation of Report Engine on the 64 bit machine with the newly created Report Engine user.  See Installing-BMC-ProactiveNet-Report-Engine-with-Oracle-database.
4. Unsubscribe the Cell and subscribe it again as described in cell_config-command.
5. Upgrade to Reporting Engine 9.6.00 and migrate the existing data.