Installing components in non-default installation paths using the local flag

Many components of TrueSight Server Automation normally install files in the /bin, /lib, and /etc directories. You can choose to install with the local option, which places all of the files into a directory of your choice. This option is not available for the installation of the TrueSight Server Automation Console. You can install Agents on a non-default path using the .sh installers, and not the native installers. If you use the native installers, the Agent is installed on the default path.

For more general information about installation, especially about prerequisite tasks and post-installation tasks, see Installing-the-Application-Server-and-components-Linux-and-UNIX.

Note

The -local option is specific to the shell installer and does not apply to the native installer.
The -local option is required when you install a component in a Solaris Sparse zone, because the /etc, /usr, and /lib file systems are inherited from the Global zone.
The -local option is not required when you install a component in a Solaris Global zone, because the /etc, /usr, and /lib file systems already have write permissions.
The -local option can be used on other UNIX Operating Systems to keep the installation files contained in a single directory.
The -local option can also be run using the bladmin OS account, and the application server can run directly under this account.

To perform installation using the local option as root

When you start the installation script, add the -local option to the command line to start the installer. For example:

BBSA87-SOL10-SPARC.sh -local

At the end of installation, the installer tells you to set the NSHDIR and LD_LIBRARY_PATH environment variables if you want to manually start the Network Shell (NSH) or manually run the RSCD Agent, Application Server, or any other TrueSight Server Automation service. If you start the service with the associated startup script, setting these values is not required.

To perform the Application Server installation using the local option as bladmin

You can install the TrueSight Server Automation Application Server as the bladmin user instead of installing as root.

Create the bladmin group and account.
For example:
groupadd bladmin
useradd -g bladmin bladmin
Log on directly to the system with the account that you created in the previous step (not as su or sudo), and run the installer using a command such as the following example command:
BSA87-LIN32.sh -local

At the end of installation, the installer tells you to set the NSHDIR and LD_LIBRARY_PATH environment variables.

To perform a silent installation using the local option

You can run the installer with silent install options, as described in Using-silent-mode-to-install-TrueSight-Server-Automation-components-Linux-or-UNIX, in combination with the -local option.
If you perform this installation as bladmin (and not as root), you must set the INSTALL_DIR option in the nsh-install-defaults file.

For example:
BSA87-SOL10-SPARC.sh -local -silent

At the end of installation, the installer tells you to set the NSHDIR and LD_LIBRARY_PATH environment variables.

File locations for a local installation

If you are using a Linux system with systemd support and opt for a local installation, the service files are located in /etc/systemd/system. These files are named using the pattern rscdlocal${LOCAL_AGENT_NUMBER}.service.

For example:

/etc/systemd/system/rscdlocal1.service
/etc/systemd/system/rscdlocal2.service
/etc/systemd/system/rscdlocal3.service

If systemd is not supported, and you choose the local option, startup scripts are placed in <install>/NSH/conf instead of in /etc/init.d. The group of scripts includes scripts for the RSCD Agent, Application Server, and the blpxe utilitity. If you want to have these services start at boot, manually apply a symbolic link (symlink) or copy them to the appropriate run-level location for your system (for example: /etc/init.d or /etc/rcN.d).