Installing the Fix Pack on the BMC ProactiveNet Server

Applying the Fix Pack on the BMC ProactiveNet Server automatically updates the following components:

  • BMC ProactiveNet Server
  • BMC ProactiveNet Self-Monitoring Service
  • BMC ProactiveNet local Administration Console
  • BMC ProactiveNet local Integration Service
  • BMC ProactiveNet Central Monitoring Administration (for a Central Server installation)

 

This topic presents the following information:

To install the Fix Pack on the BMC ProactiveNet Server (Microsoft Windows)

  1. From the extracted installation files, access the appropriate folder for the operating system. 
  2. Under the BPPMServer\Disk1 directory, open the install.cmd file with the Run as administrator option to launch the service pack installer. Do not use the setup.exe file.
  1. In the Welcome screen, click Next.
  2. Read and agree to the terms of the license agreement and click Next.
    The installer performs the pre-installation checks. 
  3. In the Fix Pack Installation Confirmation screen, select Yes and then click Next. If you select No, the installation does not proceed.
    The installer proceeds to stop the BMC ProactiveNet Server.

  4. In the Configuring KB Migration Path screen, if you had already migrated customized KB definitions to the standard 9.6.00 KB, select Yes, and browse to the path of the customized KB directory.
    The file path should follow this hierarchy structure:
    \topLevelDirectory\mergedKB\server\etc\cellName, where \server\etc\cellName is the standard sub-directory.

    Warning

    If you have KBs to migrate but have not done so, pause the upgrade process and migrate them before proceeding. See Migrating-the-configuration-of-BMC-ProactiveNet-cells.

    The installer copies the KB under the \mergedKB\server\etc\cellName path and overwrites the KB in the default installationDirectory\pw\server\etc\cellName path.

  5. Click Next.
    The installer configures the BMC ProactiveNet Server components and starts the installation process. This might take some time. After the installation, the Installation Summary dialog box displays a summary of the components installed. To view the installation logs, click View Log.
  6. Click Done to complete the installation process.
  7. Restart the computer.

To install the Fix Pack on the BMC ProactiveNet Server (UNIX)

To install the Fix Pack as a non-root user

To install the Fix Pack as a non-root user, run the following command as a root user:

chown -R <non-root user name>:root ./<installation directory>/

For example, chown -R oper:root ./ProactiveNet96/

  1. From the extracted installation files, access the appropriate folder for the operating system.
  2. Under the BPPMServer/Disk1 directory, run install.sh.
    The Welcome screen is displayed.
  3. Click Next.
  4. Read and agree to the terms of the license agreement and click Next.
    The installer performs the pre-installation checks. 
  5. In the Fix Pack Installation Confirmation screen, select Yes and then click Next. If you select No, the installation does not proceed.
    The installer proceeds to stop the BMC ProactiveNet Server.

  6. In the Configuring KB Migration Path screen, if you already migrated customized KB definitions to the standard 9.6.00 KB, select Yes, and browse to the path of the customized KB directory.
    The file path should follow this hierarchy structure:
    \topLevelDirectory\mergedKB\server\etc\cellName, where \server\etc\cellName is the standard sub-directory.

    Warning

    If you have KBs to migrate but have not done so, pause the upgrade process and migrate them before proceeding. See Migrating-the-configuration-of-BMC-ProactiveNet-cells.

    The installer copies the KB under the \mergedKB\server\etc\cellName path and overwrites the KB in the default installationDirectory\pw\server\etc\cellName path.

  7. Click Next.
    The installer configures the BMC ProactiveNet Server components and starts the installation process. This might take some time. After the installation, the Installation Summary dialog box displays a summary of the components installed. To view the installation logs, click View Log.
  8. Click Done to complete the installation process.
  9. Restart the computer.

To configure BMC ProactiveNet after installing the Fix Pack

After installing the Fix Pack on the BMC ProactiveNet Server, perform the following tasks:

Verify if the Fix Pack was installed successfully

From the pw command prompt window, run the pw viewhistory command and verify if the following line is displayed:

BMC ProactiveNet Performance Management Server FixPack 9.6.00.002 261331948 applied

Migrate Knowledge Bases for custom cells

The Fix Pack installer upgrades and migrates the cell created by the installer. For custom cells that are created manually, the installer upgrades the cell binaries but does not migrate the KBs.

To migrate the KBs for custom cells, perform the following steps:

  1. Follow the instructions at Migrating-the-configuration-of-BMC-ProactiveNet-cells.
  2. Compile and restart the custom cells. For more information, see Compiling a Knowledge Base - mccomp.

Add missing cell-specific parameters

If you migrated the customized KB during the cell upgrade, parameters in mcell.conf that were added by new features in the product do not reflect in the cell-specific mcell.conf.

Solution: Compare the parameters in the InstalledDirectory\pw\server\etc\mcell.conf file with the InstalledDirectory\pw\server\etc\<cell name>\mcell.conf file and add the missing parameters to the relevant cell-specific mcell.conf file.

Update the custom RMI port information

If you have specified a custom RMI port, it is replaced with port 2100 after installing the Fix Pack.

To update the custom RMI port number, perform the following steps:

  1. Edit the InstalledDirectory\pw\jboss\server\minimal_jms\conf\jboss-service.xml file.

  2. Update the following attribute and replace 2100 with the custom RMI port number.

    <attribute name="RmiPort">2100</attribute>
  3. Restart the BMC ProactiveNet Server by using the pw sys start command.

Configure the path for BMC event adapters

After you upgrade from Fix Pack 1 to Fix Pack 2, BMC event adapters might fail to start.

To resolve this issue, perform the following steps:

Windows

Use a text editor to edit the mcxa.cmd and mcxasvc.bat files located in the InstalledDirectory\pw\server\bin directory and correct the paths.

mcxa.cmd

mcxasvc.bat

set MCELL_HOME=<installed directory>\pw\server

set PERL_EXE=<perl base directory>\bin\perl.exe

set MCELL_HOME=<installed directory>\pw\server

set PERL_EXE=<perl base directory>\bin\perl.exe

set WINSVC=mcxa

UNIX

Use a text editor to edit the mcxa.sh and mcxa_daemon.sh files located in the InstalledDirectory\pw\server\bin directory and correct the paths.

mcxa.sh

mcxa_daemon.sh

set MCELL_HOME=<installed directory>/pw/server

set PERL_EXE=<installed directory>/pw/server/perl

Note: Comment out the unset PERL5LIB line so that it reads as:

#unset PERL5LIB

PERL5LIB="<perl base directory>/lib/5.16.3/i686-linux:/<perl base directory>/lib/5.16.3"

set MCELL_HOME=<installed directory>/pw/server

set PERL_EXE=<installed directory>/pw/server/perl

set WINSVC=mcxa

Note: Comment out the unset PERL5LIB line so that it reads as:

#unset PERL5LIB

PERL5LIB="<perl base directory>/lib/5.16.3/i686-linux:/<perl base directory>/lib/5.16.3"

Reinitialize the BMC Atrium CMDB integration

After installing the Fix Pack, publishing might fail with a pclassinfo error. This is caused due to a class information sync issue.

To resolve this issue, perform either one of the following steps:

  • Using the Operations Console:
    1. Go to Options > Administration and click Edit next to the Integrations option.
    2. Clear and then select the BMC AR Server / CMDB checkbox.
    3. Click Apply to reinitialize the BMC Atrium CMDB integration.
  • Using pclassinfo:
    1. Run pclassinfo -x -o mc_sm_object.baroc.
    2. Replace the existing mc_sm_baroc.object file of the target cell in the installationDirectory/pw/server/etc/cellName/kb/classes directory.
    3. Recompile the cell's Knowledge Base and restart the cell.

Apply the SAP Sybase SQL Anywhere EBF update

After installing the Fix Pack, apply the SAP Sybase SQL Anywhere EBF update. Applying the EBF update prevents the SAP Sybase SQL Anywhere database from hanging after you run the pw system stop command. These EBFs also prevent fatal database assertion errors and are more stable than previous EBFs.

You can ignore this step if you already applied the following EBF updates:

Operating system

EBF version

Windows

16.0.0.2018

Linux

16.0.0.2184

Solaris

16.0.0.2087

To verify the current EBF version, perform the following steps:

  • (Windows) Depending on the host computer’s architecture, from either the InstallationDirectory\pw\sybase\Bin32 or InstallationDirectory\pw\sybase\Bin64 directory, run the following command:
    sqli “select @@version”
  • (Linux and Solaris) From the InstallationDirectory/pw/sybase/SYBSsa16/bin64 directory, run the following command:
    sqli “select @@version”

To download the EBF update and for instructions to apply the EBF update, go to ftp://ftp.bmc.com/pub/BPPM/PATCHES/9.6/GA/EBF-16.0.0.2087and2018/

Where to go from here

If you have an integration with BMC Remedy ITSM, install the BMC CMDB Extensions. If not, install the remote Administration Console.

Related topics

Downloading-the-Fix-Pack

Installing-the-Fix-Pack-silently

 

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