Page tree

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.

Skip to end of metadata
Go to start of metadata

Before you install the Fix Pack, perform the following steps:

Infrastructure Management server

  • Ensure that the RMI port 2100 (inbound) is open. This is mandatory to ensure connectivity between the TrueSight Infrastructure Management server and Presentation Server.
    If you have specified a custom RMI port, update it after installing the Fix Pack.
  • (UNIX) 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 and restart the host machine to unlock any process running in the background. 
  • If installing on a virtual machine (VM), back up the VM before installing the Fix Pack.
  • 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 UNIX.
  • Back up critical installation and database files. For more information, see for Oracle and for SAP Sybase SQL Anywhere.
  • 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.

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.

To back up the Infrastructure Management server files on UNIX

  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

Remote Integration Service and remote cell

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

Delete any dormant /server folder

On UNIX, 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.

Ensure that the cell is running in 64-bit mode

If the cell is running in 32-bit mode, convert it to 64-bit by running the mswitchbit command.

After upgrading the cell, you can switch it back to 32-bit if required.

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:

  • (Windows)  \Program Files\BMC Software\BPPMAgent 
  • (UNIX)  /opt/bmc/BPPMAgent

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

Stop the remote Integration Services and remote cells before you start the back up.

To install the Fix Pack on UNIX as a non-root user

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 for create the ProductRegistry.xml file
    • /etc directory for set environment variable
    • (For the Infrastructure Management Server only) /usr and /usr/bin directories for create softlink
    • (For the Integration Service only/etc/patrol.d directory for create patrol security
    • /etc/init.d, /etc/rc.d/rc0.d, /etc/rc.d/rc1.d, /etc/rc.d/rc3.d, and /etc/rc.d/rc5.d directories for create service
    • /tmp and /var/tmp directories
  • Provide read and write permissions for the following files and directories:
    • /etc/csh.cshrc file
    • /etc/profile directory for set environment variable permission 

Note

While installing the Infrastructure Management Server with a non-root user, change the port numbers for Apache and Apache SSL between 1025 to 65535 because the non-root user does not have permissions to use ports below or equals to 1024.

  • 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.
  • Ensure that you remove the /etc/bmc.cshrc and /etc/bmc.profile files if they already exist. 

Note

Installing the Integration Service with the non-root user is supported only on the Linux operating system. It is not supported on the Solaris or AIX operating system.


Where to go from here