Preparing to apply feature packs or fix packs on Infrastructure Management

Before you install feature packs or fix packs, perform the following steps:

Complete the preinstall tasks for Infrastructure Management server

  • Ensure that you have upgraded the TrueSight Presentation Server to the latest service pack or fix pack version before upgrading your Infrastructure Management to the latest version. For more information, see  Supported Presentation Server integrations with TrueSight Operations Management components.
  • As a best practice and to avoid a file lock happening during the upgrade process, exclude the installation directory from the on-access virus scanner. For more information, see  On-access virus scanners.
  • (Linux) If you are not installing Infrastructure Management silently, ensure that x11 is installed and configured. Both 32-bit and 64-bit RPMs must be installed.
  • (Windows) Ensure that:
    • Disable User Account Control (UAC) and turn off Data Execution Prevention (DEP) for install.cmd.
    • Stop the Infrastructure Management server by running the pw system stop command and restart the host machine to unlock any process running in the background.
    • Run the pw process list command to ensure that all processes are running before you begin the upgrade.
  • If installing on a virtual machine (VM), back up the VM before installing the Fix Pack.
  • Ensure that your migrated or unmigrated KB is successfully compiled.
  • If installed on a physical computer, back up the complete Infrastructure Management server installation, so that the original Infrastructure Management server installation can be restored in case of an issue with the Fix Pack installation. For more information, see backing up the installation on Windows or Linux, later in this topic.
  • Back up the database files. For more information, see for  Oracle  and for  SAP Sybase SQL Anywhere
  • Back up the ProductRegistry.xml file. The ProductRegistry.xml file is located at (Windows) c:\windows, or (Linux) /opt/bmc.
  • If you are using an Oracle database, ensure that it is running before and during installation of the Fix Pack on the Infrastructure Management server.
  • Ensure that the BPPM_SERVER_HOME environment variable is set to the server installation directory. For example, on a Windows computer, this environment variable is set to C:\Program Files\BMC Software\TrueSight.
  • (Windows) To overcome the 260-character file path length restriction, extract the downloaded installation files from the download directory. For example, C:\temp.
  • Based on whether you are upgrading from a small to medium or medium to large, you must update the following parameters in the pronet.conf file:

    File pathSmall to MediumMedium to Large

    (Windows)

    pw\conf\pronet.conf

    • pronet.deployment.type=medium
    • pronet.instance.medium.max=60000
    • pronet.deployment.type=large
    • pronet.instance.large.max=250000

    (Linux)

    pw/conf/pronet.conf

    • pronet.deployment.type=medium
    • pronet.instance.medium.max=60000
    • pronet.deployment.type=large
    • pronet.instance.large.max=250000

To back up the Infrastructure Management server files on Microsoft Windows

  1. Check the size of the InstalledDirectory\TrueSight\pw folder and verify that you have sufficient disk space for the backup.
  2. Stop the Infrastructure Management server by running the pw system stop command.
  3. Ensure that none of the processes are running by running the pw process list command.
  4. Create an archive of the Infrastructure Management server installation directory. For example, if the Infrastructure Management server is installed at C:\Program Files\BMC Software\TrueSight, create an archive of the entire TrueSight directory.
  5. Restart the Infrastructure Management server by running the pw system start command.

To back up the Infrastructure Management server files on Linux

  1. Check the size of the InstalledDirectory/TrueSight/pw folder and verify that you have sufficient disk space for the backup.
  2. Stop the Infrastructure Management server by running the pw system stop command.
  3. Ensure that none of the processes are running by running the pw process list command.
  4. Create an archive of the Infrastructure Management server installation directory. For example, if the Infrastructure Management server is installed under /opt/bmc/TrueSight/pw then go to /opt/bmc/TrueSight and run the following command:
    tar -cvf <backupfilename>.tar pw
  5. Restart the Infrastructure Management server by running the pw system start command.

To back up the Infrastructure Management server SAP SQL Anywhere database (applicable to version 11.3.03)

Applying the fix pack 11.3.03 upgrades SAP SQL Anywhere database from version 16 to 17. Therefore, you must create the backup of SAP SQL Anywhere database files of version 16 using pw database archive command before applying the fix pack. Complete the following steps:

  1. Stop access to the TrueSight Infrastructure Management database from other BMC products such as TrueSight Operations Management Reporting, or TrueSight Capacity Optimization. You can restore access to the database once the upgrade process is complete. 
  2. Create a backup of the SAP SQL database by running the following command:

    pw database archive <archiveDirectory>

    <archiveDirectory>: Specify the directory where you want to archive the database files. Ensure that the directory has sufficient disk space to store the database. For more information about the pw database archive command, see  pw database archive.

    Tip

    If the upgrade fails, run the pw database restore command to restore the database from the archive directory. For more information about the pw database restore command, see pw database restore.

    For more information about the archiving and backup of database, see 

    • Archiving or backing up the Infrastructure Management Server
    • Backing up configuration and database files (SAP SQL Anywhere)

Complete the preinstall tasks for remote Integration Service, Cell, and Administrator Console

Perform the following steps before you install the Fix Pack on the remote Integration Service and remote cell:

To enable Java support

The following prerequisites are applicable only to:

  • TrueSight Integration Service and Remote cell version 11.3.02 and later.
  • TrueSight Remote Administrator Console version 11.3.02 and later.

  • If you plan to install a fresh instance of Integration Service or remote cell:

    • If the host computer does not have any existing instance, ensure that the host computer has a compatible Java version installed on it and update the JAVA_HOME environment variable point to this Java version.

    • If the host computer has an existing instance of the Integration Service / remote cell version 11.3.01 or earlier:
      • Ensure that the host computer has a compatible Java version installed on it and update the JAVA_HOME environment variable to point to this Java version.
      • Ensure that the JAVA_HOME environment variable is not pointing to the JRE that is bundled with an existing instance of the Integration Service and Remote cell.

      Note

      • Ensure that JAVA_HOME is pointing to 64-bit jre.
      • Ensure that the JAVA_HOME must point till the jre directory as shown in the following examples:
        • C:\Program Files\Java\jdk1.8.0_20\jre (if you have installed JDK on the host computer)
        • C:\Program Files\Java\jre1.8.0_20 (if you have installed only jre on the host computer)
  • If you plan to install Remote Administrator Console, ensure that the host computer has a compatible Java version installed on it and update the JAVA_HOME environment variable point to this Java version.
    Note: Ensure that JAVA_HOME is pointing to 64-bit jre.

For additional details about Java version details, see  Support for Java.

Support for SUSE Linux Enterprise Server 15

If you are planning to install a fresh instance of an Integration Service on the SUSE Linux Enterprise Server 15 operating system, ensure that you install the insserv-compat-0.1-18.2.noarch.rpm RPM package before you proceed with the installation.

Update the remote Integration Service and administrator console installers

To ensure that the updated installers for the remote Integration Service and administrator console are available from the Infrastructure Management server, perform the following steps:

  1. Remote Integration Service: 
    1. From the downloaded Fix Pack installation files, access the TSIMAgent\<OS> folder and copy the TSIMAgent file to the installedDirectory\pw\pronto\web\html\download\<OS> directory of the Infrastructure Management server.
    2. To easily identify the installer version, rename the TSIMAgent file. For example, TSIMAgent_11.3.02 to indicate the 11.3.02 installer.
    3. Repeat the preceding steps for each operating system installer file.
    4. Ensure that the BPPM_AGENT_HOME environment variable is set to the Integration Service installation directory. For example, on a Linux computer, this environment variable is set to /opt/bmc/TSIMAgent.
  2. Administrator console:
    1. From the downloaded Fix Pack installation files, access the TSIMAdmin\<OS> folder and copy the Admin file to the installedDirectory\pw\pronto\web\html\download\<OS> directory of the Infrastructure Management server.
    2. To easily identify the installer version, rename the Admin file. For example, Admin_11.3.02 to indicate the 11.3.02 installer.
    3. Repeat the preceding steps for each operating system installer file.

Delete any dormant /server folder

On Linux, check if any dormant /server folder exists under the remote Integration Service base installation folder. These dormant folders would not contain any cell-related information. Delete such dormant folders if they exist.

Back up the remote Integration Service files

The local Integration Service files are backed up when you back up the Infrastructure Management server files. You need to manually back up all the remote Integration Services that are connected to the Infrastructure Management server. The default installation paths are:

  • (WindowsC:\Program Files\BMC Software\TSIMAgent 
  • (Linux)  /opt/bmc/TSIMAgent

Stop the remote Integration Services and remote cells before you start the backup.

Check the size of the installation directory and verify that you have sufficient disk space for the backup.

Update the S81pronto script on SUSE Linux Enterprise Server

Perform the following steps before upgrading the Integration Service on SUSE Linux Enterprise Server:

Root user

  1. Manually create the S81pronto.0.<instance number> script in all the etc/rc.d/rc<runLevel>.d
  2. If multiple instances of Integration Services are installed, create that number of S81pronto.0 with respective instance number. For example:
    1. S81pronto.0.1
    2. S81pronto.0.2
    3. S81pronto.0.3
  3. Update the installation directory in the S81pronto file, as per the installed Integration Service.

    #
    # Start BMC ProactiveNet Agent processes
    #
    if [ -x <INSTALLATION-DIRECTORY>/pw/pronto/bin/startremotepw ] ; then
      /opt/bmc/TSIMAgent/pw/pronto/bin/startremotepw &
      /bin/echo  'BMC ProactiveNet Agent\c'
    fi
  4. Provide the required execute permissions to all S81pronto.* files.

Non-root user

  1. If you installed the Integration Service as a non-root user, the S81pronto.0.<instance number> script is created in <installationDirectory>/pw/pronto/bin folder.
  2. Manually copy the s81pronto.xxxx file from <installationDirectory>/pw/pronto/bin to all the etc/rc.d/rc<runLevel>.d.
  3. Provide the required execute permissions to all S81pronto.* files.

Configure custom cells and HA cells

  • If you deleted the default cell that is created through the installer and a custom cell is set as the default cell, edit the following parameters in the installedDirectory\TSIMAgent\BPPMAgentInstalledConfiguration.xml file:
    <name>CELL_NAME</name>
    <value>custom_cell_name</value>
  • In you have configured cell HA, update the host name as represented in the mcell.dir of respective HA cells.
     <name>CELL_PRIMARY_HOST</name>
     <value>primary_host_name</value> 

    <name>CELL_SECONDARY_HOST</name>
    <value>secondary_host_name</value>

Complete the additional tasks for Linux

On Linux computers, you can install the Infrastructure Management Server or the Integration Service as a root user as well as a non-root user. However, you must provide certain permissions to the non-root user as the root user. 

  • Provide read, write, and execute permissions for the following directories:
    • Installation directory (destination directory where you are planning to install the product)
    • /opt/bmc directory or the parent installation directory to create the ProductRegistry.xml file
    • /etc directory for set environment variable
    • /etc/init.d directory for create service
    • /tmp and /var/tmp directories
    • (Infrastructure Management Server only) /usr and /usr/bin directories for create softlink
    • (Integration Service only/etc/patrol.d directory for create patrol security
    • (Remote cell on SUSE Linux Enterprise Server only/home directory

  • Provide read and write permissions for the following files and directories:
    • /etc/csh.cshrc file
    • /etc/profile directory for set environment variable permission
    • (Remote cell on AIX only/home directory
  • If the init file is not copied to the /etc/rc3.d directory, the Integration Service corresponding to the init file is not listed as installed (in the list of existing Integration Service installations) during installation of other integration services.
  • Verify if the non-root user owns the /etc/bmc.cshrc and /etc/bmc.profile files. If not, run the following commands as a root user:
    chown <non-root user name> /etc/bmc.cshrc 
    chown <non-root user name> /etc/bmc.profile 


Was this page helpful? Yes No Submitting... Thank you

Comments