Installing the TrueSight Server Automation Console (Linux and UNIX)

This topic provides instructions for installing the TrueSight Server Automation Server Automation Console and Network Shell on Linux or UNIX.

Before you begin

• To install the TrueSight Server Automation Console, you can use the installation wizard in the user interface or silent mode. You cannot use console mode. To use the installation wizard, follow the steps below. To use silent mode, see Using-silent-mode-to-install-the-TrueSight-Server-Automation-Console-Linux-and-UNIX.
• You must have an X Window server installed and configured.
• You must have write access to the /tmp directory, as well as sufficient disk space. To review the hardware requirements for the console, see Minimum-hardware-requirements.
• Make sure that port 12333 (TCP) is not being used. Installation of the console requires use of this port; if it is already in use, the installation fails.
• Linux platforms on which you plan to install the TrueSight Server Automation Console (RCP client) or Network Shell must have the libtermcap.so.2 shared library installed. Install the shared library before installing these components. For more information, see Requirement for installing the Application Server, TrueSight Server Automation Console, or Network Shell on Linux.
• If the version of the RSCD Agent does not match the version of the console, uninstall the old RSCD Agent and install a new version that matches the console. Stop the RSCD Agent before you try to install the console.
• You must close all the NSH shell windows while installing TrueSight Server Automation Console.

To install the console

1. Navigate to the directory containing installation files and run the installation script for the TrueSight Server Automation Console. (Script names follow the convention: TSSACONSOLE<version>-<platformbit>, for example, TSSACONSOLE89-SP3-LIN64.bin) You must execute the installation from a root shell. Do not execute the installation script from a non-root account.
2. The TrueSight Server Automation Installation window opens.
3. Select a language, and then click OK.
   A series of messages indicate progress. This process might take several minutes. Then the Welcome window opens.
   
4. Click Next.
   The Review License Agreement page opens.
   
5. To accept the license agreement, select I agree to the terms of the license agreement, and then click Next.
   The User Inputs window opens.
   
6. (optional) Remove the check marks from any components that you do not want to install, and then click Next.
   A series of messages indicate progress.
   
7. (optional) Select Check to install the default .nsh resource files into /etc/skel.
   
8. Click Next.
   The Installing window previews the features to be installed.
   
9. To install, click Install. To change your selections, click Previous.
   A series of messages indicate progress. This process might take several minutes. Then the Installation Summary window opens, indicating successful installation.
   
10. (optional) Click View Log.
11. Click Done.
    The window closes. Installation is complete.
12. Start the RSCD Agent and then start the console (for example, /opt/bmc/BladeLogic/CM/rcp/launcher). To configure the console so that it connects to the default Application Server, click Options.
    
13. Click the Authentication Profiles tab and click Add. TrueSight Server Automation clients use authentication profiles to facilitate single sign-on feature. You must create an Authentication profile before you start using the Console. For more information about why we use Authentication Profiles, see System-capabilities-related-to-security.
    
14. Enter the following information.
    
    
    1. Assign a name to the authentication profile. For example, you could assign a name such as QATeam, DevTeam, or defaultProfile.
    2. Enter the name or IP address (IPv4 or IPv6) of the default Application Server to which the client should connect.
    3. Enter an Authentication Port number to which the client should connect. The same port is used for all TrueSight Server Automation authentication mechanisms. The default Port is 9840. For more information about Console ports, see TrueSight-Server-Automation-ports.

    4. Select any one authentication mechanism for the authentication profile:

       • Secure Remote Password.
       • AD/Kerberos Single Sign-on.
       • Domain Authentication.
       • LDAP.
       • RSA SecurID Authentication.
       • Public Key Infrastructure Authentication.

       In this walkthrough we will use the Secure Remote Password mechanism. For information about implementing the other authentication mechanisms, see Implementing-authentication. 

    5. Click OK.
15. Click Connect to log on the Application Server using the BLAdmin user that is created while installing the default Application Server node.
    
16. If you see a security alert that the certificate is not initially trusted, optionally, you can view the certificate. Or you can simply click Yes to proceed. 
    
17. The quick start page is the first page that is displayed once you log on the the Console. It introduces you to the main use cases of TrueSight Server Automation and allows you to execute them from a centralized UI immediately after installing the TrueSight Server Automation set up. For information about using the quick start page, see Quick-start-page. For general information about the UI of the TrueSight Server Automation Console, see Navigating-the-interface.