Configuring installation settings for Linux and UNIX

This topic describes how to configure installation settings when installing TrueSight Server Automation components on Linux and UNIX. It includes the following sections:

Methods for reducing installation space on Linux and UNIX

You can reduce the disk space required by a Linux or UNIX installation by setting the installer to read from a shared drive or by setting the INSTALL_FILES_TEMP environment variable. 

The space required for an installation depends on:

  • Size of the installation
  • Space required for expanding installation files
  • Size of the installation directories

For example, assume an RSCD agent installer for UNIX is 150 MB. You start the installation process by copying the installer file to the target host. When you run the installer, it extracts the files it needs and expands them into a file extraction area. The installer then installs files from the extraction area into the actual target system directories. If all of these actions take place on the same disk partition, then the required disk space equals Installer Size + Expanded Size + Installation. The total might be approximately three times the installer size, or 450 MB. 

To reduce space required for installation you can do the following:

  • Set the installer to read from a shared drive.

  • Set the installer to write the expanded files to a temporary area on a different partition, instead of /tmp. Before running the installer, set the INSTALL_FILES_TEMP environment variable. Enter the following commands at the operating system command line:

    INSTALL_FILES_TEMP=<temporaryDirLocation>
    export INSTALL_FILES_TEMP 

    where:
    <temporaryDirLocation> is the location where the installer should expand the installation files.

Changing the installation path on UNIX

Before version 8.2, installation directories for the application server, agent, and other TrueSight Server Automation components were in the following format: /opt/bmc/BladeLogic/<version>/NSH. This path format does not allow product upgrades to install into the same directory structure.

Use the following procedure to move/rename the installation directory on the application server on a Linux host computer.

Note

This workaround process might not work in all environments.

To change the installation directory path

  1. Create a backup of the directories whose path you want to modify.
  2. Stop the various TrueSight Server Automation components (such as application server and RSCD Agent).
  3. Move the directory from /opt/bmc/BladeLogic/<version>/NSH to /opt/bmc/bladelogic/NSH.
  4. Change the path in /usr/lib/rsc/HOME.
  5. Change any paths in /usr/lib/rsc/log4crc.txt.
  6. Change the path in the /etc/init.d/blappserv, blpxe, bltftp, rscd and blprocserv scripts.
  7. Change the path in any files in the NSH/br directory (such as *.cfg or blappserv — grep for the old path in this directory).
  8. Change the path in /opt/bmc/bladelogic/install.ini.

By following this process, you have changed any pointers to the old path. If your storage directory is in the NSH directory, then you need to follow the procedure to change your file server. You might also need to update Extended Object locations and other things if they pointed to the application server directory.

 

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