Walkthrough: Installing individual components for Microsoft Windows and SQL Server environments

This walkthrough topic provides a list of the steps required to install TrueSight Server Automation in a Microsoft Windows/SQL Server environment. Note that walkthrough topics are targeted to experienced TrueSight Server Automation users, and do not include relevant planning and prerequisite information. If you are not an experienced user, see the topics in the Requirements-for-installing-individual-components-on-Microsoft-Windows section to review the required planning information for installation.

The topic includes the following sections:

Before you begin

Review the requirements for installing the components using the individual component installers, as described in Requirements-for-installing-individual-components-on-Microsoft-Windows.

For specific system-level requirements (such as required disk space), see the "Hardware requirements for the individual components" section in Minimum-hardware-requirements.

Step 1: Setting up a database and user for a Microsoft SQL Server database

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Step 2: Setting up a database schema for a Microsoft SQL Server database

  1. Copy install scripts from the db_scripts directory in the main product .zip to a location that you can access from the SQL Server console. For information on the db_scripts directory, see Downloading-the-installation-files.
     The relevant scripts appear in the /files/configurations/dbscripts/sqlserver directory inside the TSSA<version>-<platform>64 installer zip package.
  2. Open a command prompt window.
  3. Change (cd) to /db_scripts/sqlserver.

  4. Run the master script that corresponds to the character sets for which your database is configured, using the following syntax:
    <master_script.bat> <db_server> <db_name> <bl_user> <bl_pwd>
    For example:
    sqlserver_master.bat QLDS0002 BLADELOGIC BLADELOGIC bmcAdm1n
    Replace the variables with the following values:

    Variable

    Value

    <master_script.bat>

    sqlserver_master.bat if your database is configured for char/varchar character sets or sqlserver_nchar_master.bat if your database is configured for nchar/nvarchar character sets

    <db_server>

    Name of the database server.
    If the server uses a nonstandard port, the server name and port number must be enclosed in quotation marks, as shown in the following example: "QLDS0002,1381"
    To use a named server instance, append the named instance, including the complete path, as shown in this example:
    sqlserver_master.bat <db_server>\<instance_name> <db_name> <db_user> <db_password>

    <db_name>

    Name of the TrueSight Server Automation database that you created while setting up the database

    <bl_user>

    Logon name for the TrueSight Server Automation database user

    <bl_pwd>

    BMC  Server Automation database user password

Note

When the master script runs, the following warnings might appear:

Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'rsave_cond_result_subtree'. The stored procedure will still be created. Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'rsave_cr_group_result_subtree'. The stored procedure will still be created.

These warnings are expected and can be ignored.

Back to top

Step 3: Install the agent on the file server

Click here to see a list of requirements for the file server.

A file server should meet the following requirements:

  • An RSCD agent must be installed and should be the same version as the Application Server.
  • Do not limit access to the file server by pushing agent ACLs to the agent on the file server. All users must be mapped to the same user on the file server.
  • As a minimum, a file server must have 72 GB of available, nonredundant, disk space. BMC recommends that the file server be allotted 200 GB or more of available RAID 5 disk space.
  • Define a user name (for example, blfsro) on the file server with read only permission on the storage, and map all users to that user name. Without this mapping, a user may not be able to access a file that another user has stored on the file server. To accomplish the necessary mapping, create an entry like the following in the exports file on the file server:
    <appServer> ro,user=blfsro
    Where <appServer> is a comma-separated list of Application Server names or IP addresses (IPv4 or IPv6).
    The default location of the exports file is:
    • (Windows) C:\Windows\rsc
    • (Linux): /etc/rsc

  • Map the built-in System:System role/user to the user name (for example, blfsrw) defined on the file server with full permission on the storage. To accomplish the mapping, create an entry like the following in the users.local file on the file server:
    System:System rw,map=blfsrw
    Where blfsrw is the name to which the built-in System:System role/user is mapped, typically used when Application Server accesses the file server.
    If the required directory structure does not already exist on the file server, the system process attempts to create it.
    The default location of the users.local file is:

    • (Windows) C:\Windows\rsc
    • (Linux): /etc/rsc

    For examples on configuring the file server agent ACLs, see Configuring-the-file-server-agent-ACLs.

  • If your file server location is on partition or a mounted storage, you must ensure that the mount point for the storage or partition is consistent even if the file server host is restarted.
    For example, on Linux, you can ensure this by configuring the fstab file in the etc folder of your machine. The fstab file maps the Universally Unique Identifier (UUID) of a storage or partition to the directory it should be mounted on.

TrueSight Server Automation uses the file server to store the contents of files included in snapshots, Network Shell scripts, BLPackages, software packages, and other types of information that is not easily stored in the database. The file server must have a RSCD agent installed on it, as described in the following procedure.

Step
Example screen

1

    1. Extract the TSSA<version>-RSCDAgents.zip file that you downloaded from EPD to obtain the rscd folder. The folder contains separate installers for 32-bit and 64-bit Windows systems.
    2. Navigate to the windows_64 folder, which is inside the rscd folder, and run the RSCD<version>-WIN64.msi file.
    3. Click Run.
      The installation wizard is displayed.
    4. Click Next.

Welcome.png
2

    1. Accept the license agreement, and click Next.
    2. Configure the following Smart Agent parameters to connect to the Smart Hub for sending work requests, and click Next.
      • Enable Smart Agent: Specify whether you want to enable the Smart Agent service. The service is enabled by default, which indicates that the Smart Agent is started automatically after installation.
      • Smart Hub hostname: The name of the host where the Smart Hub is installed.
      • Smart Hub port: The listener port of the Smart Hub. The default port is 443.
      • Enroll as: The server is enrolled in the Application Server using this value. Specify one of the following identifiers to be used for the enrollment:
        • <HOSTNAME>: Indicates the server host name. This is the default identifier.
        • <SMARTHUB_PEER_IP>: Indicates the IP address of the server. A server might have multiple IP addresses. The IP address that is used for connecting to the Smart Hub is represented by this field.
        • <SMARTHUB_PEER_FQDN>: Indicates the fully qualified domain name for the <SMARTHUB_PEER_IP>.
        • <UUID>: Indicates a random UUID value. Use it to enroll the target server in the AWS public cloud data center.
      • Enroll interval time (mins): The interval at which the server enrollment request is sent to the Smart Hub. The default interval is 15 minutes. Specify the interval in the range 1 - 360 minutes.
      • Heartbeat interval time (mins): The interval at which the agent sends heartbeats to the Smart Hub for status updates. The default interval is 5 minutes. Specify the interval in the range 1 - 360 minutes.
      • Access key: The access key that is configured for the Smart Hub. This key is used for authenticating with the Smart Hub. To obtain the access key, see Configuring the Smart Hub.
      • Smart Hub polling interval time (sec): The interval (in seconds) at which the Smart Hub is polled for work requests. The default is 300 seconds.
      • Tunnel feature: Specify whether you want to enable or disable (default) the Tunnel feature. 
SmartAgent.png
3
Select one of the following options, and click Next:

    • Typical: Installs the agent with the default settings.
    • Custom: Allows you to customize the default settings.
 setuptype.png
4
 Click Install to begin the RSCD agent installation.


 ReadytoInstall.png
5
The installer checks whether Microsoft Visual C++ 2015 Redistributable is installed on the server. If this is not installed, the installation program aborts installation with an error message.
RSCD_MSVC.png
6
Select one of the following options for the BladeLogicRSCD user password, and click Next:

    • Use random password: Installs the agent with a random password generated by the installer.
    • Use specified password: Installs the agent with the password specified by you.
You can change the password later by using the command or agentctl utility. For more information, see Changing-the-BladeLogicRSCD-account-password.
Security.png
7
You can select the Show the Windows Installer log option to view a detailed report of the installation process.Click Finish to exit the wizard.
 Complete.png

Back to top

Step 4: Install the Application Server

Click here to see the prerequisites for installing the Application Servers.
  • To perform this installation, you must have local administrator privileges.
  • The TrueSight Server Automation Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. Communication between TrueSight Server Automation and servers being provisioned and between the Application Server and the process spawner uses the Transport Layer Security (TLS) protocol and X.509 certificates. The password must be at least 6 characters. For more information about certificates and the TLS protocol, see Authentication.
  • The Application Server installation does not install the TrueSight Server Automation Console. To view the console, you must install it. For information, see Installing-the-TrueSight-Server-Automation-Console-and-Network-Shell-Windows. 
  • To use provisioning with the Application Server, select the option to enable provisioning.
  • If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on a Windows operating system, use one of the following methods to install:
  • You must set up your database schema. See Setting-up-an-Oracle-database-for-TrueSight-Server-Automation and Setting-up-a-SQL-Server-database-and-user-for-TrueSight-Server-Automation .
  • On 64-bit Windows systems, confirm that the <WINDIR>\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.
  • If you plan to use the bljython utility, install the Application Server before installing Jython.
  • If the host computer on which you are installing the Network Shell has:
    • A supported version of Perl installed--The Network Shell installation automatically installs the Network Shell Perl module. (For information about the Perl versions that TrueSight Server Automation supports, see Perl support.)
    • An unsupported version of Perl installed--The installation copies files that allow you to install the Perl module after you have installed the supported version of Perl.

 

Step

Example screen

1

  1. On the computer where you plan to install the Application Server, log on as Administrator.
  2. From the BMC Software Electronic Product Distribution (EPD) website, download and extract the TSSA<version>-WIN64.zip installer package. For steps on downloading files from the EPD website, see Downloading-the-installation-files.
  3. Navigate to the directory containing the Application Server installation file, which is TSSA<version>-WIN64.zip/files/installers/appserver_64/. Installation program names follow the convention: TSSAversion-platform. 
  4. Start the 64-bit installation program for the Windows operating system. The Choose Setup Language panel is displayed.
  5. Choose a language and click Next.
    The Welcome panel is displayed.

appserver1.png

2

Click Next.

The Acknowledgement panel is displayed.

appserver2.png

3

Click Next.

The License Agreement panel is displayed.

 

appserver3.png

4

Click Yes.

The Customer Information panel is displayed.

appserver4.png

5

  1. Enter a user name and company name.
  2. Click Next.

The Setup Type panel is displayed.

appserver5.png

6

  1. At the Setup Type window, select the type of installation:

    • Full — Installs the Application Server, the Network Shell, and documentation.
    • Custom — Installs the components you select.

    This example uses a custom installation.

  2. Click Next.

The Choose Destination Location panel is displayed.

appserver6.png

7

Click Browse to specify an installation directory, or click Next to accept the default directory, C:\Program Files\BMC Software\BladeLogic.

The Select Features panel is displayed.

appserver7.png

8

  1. Select the components for installation (custom installation only):
    • Application Server
    • Network Shell
    • Documentation components
  2. Click Next.
    The Application Server JVM Settings panel is displayed.

 

 

appserver8.png

9

Specify the maximum heap size, in megabytes, to use for the Java Virtual Machine (JVM) for the Application Server Launcher. In a multiple-Application Server (MAS) environment, the Application Server Launcher configures and controls all Application Servers on the host.

Specify a value above the minimum 512 megabytes. The default is 4095 MB.

Best practice: If you are setting up a MAS environment, set the MaxHeapSize to 512 MB. Then when you configure each Application Server instance, set MaxHeapSize to a value appropriate for the architecture and operating system. For recommended maximum Java heap sizes, see Recommendations-for-Application-Servers-of-type-All.

Click Next.

The Certificate Password panel is displayed.

appserver9.png

10

Specify a certificate password (must be at least 6 characters).

The Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. Communication between TrueSight Server Automation and servers being provisioned and between the Application Server and the process spawner uses the Transport Layer Security (TLS) protocol and X.509 certificates. The password must be at least 6 characters. For more information about certificates and the TLS protocol, see Authentication.

Click Next.

The Selected Components panel is displayed.

appserver10.png

11

Review the selected components and click Next to start the installation.

appserver11.png

12

The status panel displays the installation progress.

When installation completes, the Post-Configuration panel is displayed.

appserver12.png

13

Do one of the following:

To configure the Application Server at a later time, click Next.

To configure the Application Server and set up administrator passwords using the Post-Install Configuration wizard, select the Configure the Application Server option and click Next. See Configuring-a-single-default-Application-Server-on-the-host for instructions for completing that wizard.

appserver13.png

14

Click Finish to exit the installation program.

appserver14.png

Back to top

Step 5: Run the post-install configuration utility

The Post-Install Configuration wizard consolidates the minimum configuration steps that must be performed to set up an Application Server. 

  1. Before you configure the Application server, add the property local account name for the file server to /etc/rsc/exports (Linux) or C:\windows\rsc\exports (Windows).
    Linux:
    * rw,user=root

    Windows:

    * rw,user=Administrator These permissions grant wide-open access to the file server. For more information, see File-server-requirements.

  2. To start the Post-Install Configuration wizard, do one of the following:
    • Perform an installation that includes installation of the Application Server. The installation program gives you the option of launching the wizard at the end of the installation procedure.
    • From the Windows Start menu, select Programs > BMC Software > BladeLogic Server Automation Suite > Utilities > Application Server Configuration Wizard.
    • Start the wizard manually by running one of the following commands in the directory where TrueSight Server Automation is installed. Enter the following:

      • (Windows)

        bin\blappconf.exe

      • (UNIX)

        ./br/blappconf

        Note

        If you invoke the wizard without passing the -i (install) flag, the wizard displays configuration settings that have already been entered for the Application Server and allows you to change those settings.

        The configuration wizard opens.

  3. Read the introductory page and click Next. The Database page appears.
  4. Choose a Database Type (either Oracle or SQL Server).
  5. If you are not using a custom connection string, provide the following database configuration information (and do not select the Advanced option):
    • Database Server — Host name or IP address (IPv4 or IPv6) of the server running the database.

    • Database Port— Port the database listens on. By default a TrueSight Server Automation installation uses the following database ports:

    • Database Name — Microsoft SQL server database name. By default, the database name is bladelogic . (This option is only available for SQL server databases.)
    • SID — System ID of the Oracle database. (This option is only available for Oracle databases.)
    • User ID — User name that the database needs to authenticate your connection.
    • Password — Password assigned to the user ID.
      or...
      If you are using a custom connection string, provide the following database configuration information:
    • User ID — User name that the database needs to authenticate your connection.
    • Password — Password assigned to the user ID.
    • Advanced — Select this option to indicate that you are providing a custom connection string.
    • Connection String — Type the custom connection string in the field below the Advanced check box.
  6. Click Next. The File Server page appears.
  7. Provide the following file server configuration information:
    • File Server Name — Host name or IP address (IPv4 or IPv6) of the server where data is stored. By default, the file server is created on the same machine as the Application Server.
    • File Server Storage Location — Directory on the file server where data is stored. By default, the directory of the file server is <appserverInstallDirectory>/storage.
  8. Click Next. The Notification Servers page appears.
  9. Provide information identifying an email server by entering the following under SMTP Options:
    • SMTP Server — Name or IP address (IPv4 or IPv6) of the host managing email. (SMTP stands for simple mail transfer protocol.)
    • E-mail From — email address from which TrueSight Server Automation-generated email is sent. TrueSight Server Automation jobs can generate email upon their completion.
  10. If you are using SNMP trap notifications, provide information identifying the SNMP server by entering the following under SNMP Options:
    • SNMP Server — Name or IP address (IPv4 or IPv6) of the host to which SNMP traps should be sent.
    • SNMP Port — The port on the SNMP server that listens for SNMP traps. By default, the port is set to the standard SNMP port of 162.
  11. Click Next. The User Passwords page appears.
  12. Under both RBACAdmin User and BLAdmin User, enter a password and then retype the password to confirm your entry. If a password is already set, you cannot enter a password.
    Passwords are used to authenticate the RBACAdmin and BLAdmin users through the SRP authentication protocol.
    The RBACAdmin user has full permission to manage roles and users in the RBAC Manager workspace in the TrueSight Server Automation Console, where you can assign permissions for all TrueSight Server Automation users. The BLAdmin user has Read access for all system objects within TrueSight Server Automation. For more information about the RBACAdmin and BLAdmin users, see RBACAdmin-and-BLAdmin-users.
  13. (optional) In the Advanced Configuration panel, set Enable Provisioning for bare metal provisioning. You must also set up the provisioning system, create components used by the provisioning process, prepare devices, and create and execute Provision Jobs that perform the unattended installation of the operating system. For more information, see Implementation-process-for-provisioning.
  14. Click Finish.

  15. After you have created the new Application Server, perform the following step if you have configured the file server agent ACLs. In this case you need to allow access to the file server by adding the newly created Application Server to the exports file of the file server.
    Use the following sample code:<application server 1>,<application server 2>,<application server n...> ro,user=blfsro

    The exports file is located in the /etc/rsc folder in Unix and C:\Windows\rsc folder in Windows. 

Recommendation

BMC recommends that you synchronize the clock on the Application Server and all client machines. Clocks should be synchronized to the minute. For example, if an Application Server is in Boston, where the time is 7:04 Eastern Time, set the clock on client machines in San Francisco to 4:04 Pacific Time.

Back to top

Step 6: Install the console on your client system

Click here to see a list of prerequisites for installing the console.
  • BMC recommends that you do not install the console on the same system as the Application Server. Copy the files from the Application Server installation (for example, ..\TSSA<version>-WIN64\Disk1\files\installers\rcp) to a different system and perform the installation there.
  • Before you install the TrueSight Server Automation Console, ensure 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.

  • Update the Windows Terminal Services Server Settings for temporary folders. (In Windows Server 2008 R2 and later versions, Terminal Services is renamed to Remote Desktop Services).

    Click here for steps about updating the Windows Terminal Services

    To update the Windows Terminal Services (or Remote Desktop Services) configuration perform either of the following steps:

    Server settings method

    1. On the computer where you are installing the TrueSight Server Automation Console, select Start > Run.
    2. For Open, enter gpedit.msc, and then click OK.
    3. Navigate to the Temporary folders policies:
      Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services >Remote Desktop Session Host > Temporary folders
      or: 
      Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Terminal Server > Temporary folders
    4. Set the Properties of Do not delete temp folder upon exit to Enabled and then click OK.
    5. Set the Properties of Do not use temporary folders per session to Enabled and then click OK.
    6. Restart the computer.
       If the settings do not take effect, use the Registry Editor (regedit):

    Registry editor method

    1. Click Start > Run and enter regedit.
    2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
    3. Set the DeleteTempDirsOnExit and the PerSessionTempDir values to 0.
    4. Restart the computer.

    Note: The installation program uses temporary folders to preserve the install log. Usually, you can perform this update only one time; you do not need to update the configuration every time you install. However, if your Server Settings are different from those needed for installation, after you finish installing the console you can change the settings back to their previous settings.

This example uses TrueSight Server Automation version 8.9.03.

 

Step

Example screen

1

Navigate to the directory containing the installation files that you copied from the Application Server and run the installation program for the console (for example, ..\TSSA<version>-WIN64\Disk1\files\installers\rcp). Different installers are provided for 32-bit and 64-bit Windows.

In this example, we are running the TSSACONSOLE89-SP3-WIN64 file on the Windows machine on which you plan to install the console.

Select a language to use for the installation and click OK. 

The installer extracts the installation files, and the Introduction window opens.

 

TSA Console installation-1.png 

2

Ensure that you have closed all applications before you proceed.

Click Next.

The Review License Agreement window opens.

TSA Console installation-2.png

3

Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement if you wish to proceed.

Click Next.

The Directory Selection window opens.

TSA Console installation-3.png

4

The default installation location for the console is C:\Program Files\BMC Software\BladeLogic. Click Next to use the default location.

Alternatively, you can click Browse to change the installation location.

TSA Console installation-4.png

 5

A window opens in which you can select components to install. By default, all components are selected.

The Network Shell is automatically installed when you install the console.

Note: If you clear the TrueSight Server Automation Console Upgrade Service check box, the TrueSight Server Automation Console Upgrade Service is not installed. This service is required for automatically upgrading the TrueSight Server Automation Console when you upgrade the Application Server.

Click Next.

 

 

TSA Console installation-5.png

6

The window displays your selections.

Click Install.

The installer pre-analyzes your environment:

  • Checks whether the platform on which you are trying to install the product is supported. If the platform check is successful, Microsoft Visual C++ 2015 Redistributable Update 3 is installed automatically.
  • If the platform check fails, the installation program aborts installation with an error message. Also, the error message is added to the log file.

The window displays installation progress, then displays a message when installation is complete.

The console and Network Shell are installed on your machine.

TSA Console installation-6.png

 7

If all operations are completed successfully, click Done to exit the wizard.

 If you encountered any errors while installing, you can click View Log to view a detailed report of the installation.

Tip: BMC recommends that you save a copy of the log, before you contact technical support for further assistance.

 

TSA Console installation-7.png

 8

Start the console.

To configure the console so that it connects to the default Application Server, click Options.

TSA Console installation-8.png

9

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.

TSA Console installation-9.png

10

Enter the following information.

  1. Assign a name to the authentication profile. For example, you could assign a name such as QATeam or DevTeam.
  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.

 

TSA Console installation-10.png

11

You can now log on the the Console using the BLAdmin user that is created while installing the default Application Server node, see step 10.

Click Connect.

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 Console, see Navigating-the-interface.

TSA Console installation-11.png

This example uses TrueSight Server Automation version 8.9.03.

 

Step

Example screen

1

Navigate to the directory containing the installation files that you copied from the Application Server and run the installation program for the console (for example, ..\TSSA<version>-WIN64\Disk1\files\installers\rcp). Different installers are provided for 32-bit and 64-bit Windows.

In this example, we are running the TSSACONSOLE89-SP3-WIN64 file on the Windows machine on which you plan to install the console.

Select a language to use for the installation and click OK. 

The installer extracts the installation files, and the Introduction window opens.

 

TSA Console installation-1.png 

2

Ensure that you have closed all applications before you proceed.

Click Next.

The Review License Agreement window opens.

TSA Console installation-2.png

3

Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement if you wish to proceed.

Click Next.

The Directory Selection window opens.

TSA Console installation-3.png

4

The default installation location for the console is C:\Program Files\BMC Software\BladeLogic. Click Next to use the default location.

Alternatively, you can click Browse to change the installation location.

TSA Console installation-4.png

 5

A window opens in which you can select components to install. By default, all components are selected.

The Network Shell is automatically installed when you install the console.

Note: If you clear the TrueSight Server Automation Console Upgrade Service check box, the TrueSight Server Automation Console Upgrade Service is not installed. This service is required for automatically upgrading the TrueSight Server Automation Console when you upgrade the Application Server.

Click Next.

 

 

TSA Console installation-5.png

6

The window displays your selections.

Click Install.

The installer pre-analyzes your environment:

  • Checks whether the platform on which you are trying to install the product is supported. If the platform check is successful, Microsoft Visual C++ 2015 Redistributable Update 3 is installed automatically.
  • If the platform check fails, the installation program aborts installation with an error message. Also, the error message is added to the log file.

The window displays installation progress, then displays a message when installation is complete.

The console and Network Shell are installed on your machine.

TSA Console installation-6.png

 7

If all operations are completed successfully, click Done to exit the wizard.

 If you encountered any errors while installing, you can click View Log to view a detailed report of the installation.

Tip: BMC recommends that you save a copy of the log, before you contact technical support for further assistance.

 

TSA Console installation-7.png

 8

Start the console.

To configure the console so that it connects to the default Application Server, click Options.

TSA Console installation-8.png

9

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.

TSA Console installation-9.png

10

Enter the following information.

  1. Assign a name to the authentication profile. For example, you could assign a name such as QATeam or DevTeam.
  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.

 

TSA Console installation-10.png

11

You can now log on the the Console using the BLAdmin user that is created while installing the default Application Server node, see step 10.

Click Connect.

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 Console, see Navigating-the-interface.

TSA Console installation-11.png

 

Back to top

Step 7: Connect to the Application Server

From the Start menu, select Programs > BMC Software > BladeLogic Server Automation Suite > Server Automation ConsolereleaseNumber.

A logon dialog box appears. To log on, you must choose an authentication profile. For more information about creating authentication profiles, see Setting-up-an-authentication-profile. Perform the following steps to start the console and connect to the Application Server.

  1. Using the Authentication profile tab, select an authentication profile.
  2. If you:
    • Possess a valid cached session credential, skip this step and go to the next step.
    • Are using Active Directory/Kerberos (ADK) or public key infrastructure (PKI) authentication, skip this step and go to the next step.
    • Are using SRP, LDAP, or SecurID authentication, enter your user name and password. For SecurID, your password consists of a PIN followed by the current token code displayed on your RSA SecurID token.
    • Are using Domain Authentication, enter your user name and domain. The domain name must always be capitalized. If you are defined as a member of the default realm, you do not have to enter a domain name. For information about how to set up the default realm for Domain Authentication, see Configuring-Domain-Authentication.

  3. To change the setting for caching session credentials or the display language, click Options. The logon window expands to show additional options in a tabbed format. By default the Generaltab is open.

    Save credential for this session

    Saves a session credential between sessions.

    By default, this option is not checked. The setting for this option remains in effect for future logons until you change the setting. If a session credential is already cached, this option is dimmed.

    Language

    Displays your choice of language (either your previous choice or your acceptance of the installation default). Select a new display language for the console or keep the current user preference. The selection remains in effect as your default language for future logons until you make a new choice.

  4. Click Connect.
    If the Application Server presents the TrueSight Server Automation Console with an X.509 certificate that is not trusted, a security alert appears. Most Application Servers use self-signed certificates, so typically you encounter this dialog box the first time you access a particular Application Server.
  5. If a security alert does not display, skip this step and go to the next step. If a security alert describes an untrusted certificate, do one of the following:
    • To return to the logon dialog box, click No. You can cancel the logon session or use a different authentication profile to log on.
    • To accept the unknown certificate and proceed with the logon, click Yes.
    • To examine details about the certificate, click View Certificate. For more information about this procedure, see Viewing-an-untrusted-certificate. After examining the certificate, click Yes or No, as described above.
  6. If multiple roles are associated with your user name, the Assume Role dialog box appears. From this dialog box, for Select Role, choose the role you want to use. 
    If you prefer, you can switch roles later at any time during a session. (See Switching-roles.)

  7. Click OK. The TrueSight Server Automation Console appears.

    Note

    When the console starts, by default it loads certain types of information by running a background operation. The Show background operations icon g_v95_showBackgroundOperationsIcon.gifin the lower right corner of the console indicates a background process is running. For information about background processes, see Running-background-operations.

Back to top

What if I have problems?

The following table provides troubleshooting information for common installation issues.

Component

Issue

Troubleshooting

 Database 

Migration of database data during upgrade fails

Migration of database data during the upgrade process fails if:

  • You close the upgrade GUI — Do not close the upgrade GUI.
  • The session times out — If you are running the upgrade using a remote console, disable session timeouts before performing the upgrade.
  • The session loses connection to the upgrade process for any reason — Check network connections.

Schema changes

BMC does not recommend, nor does it support database schema changes.

PXE and TFTP server

Setting debug logging for PXE and TFTP servers

To set logging levels on the PXE server:

  1. In a text editor, open the log4j2.xml file. The file is located at:

    UNIX

    installDirectory/NSH/br/deployments/_pxe

    Windows

    installDirectory/PXE/br/deployments/_pxe

  2. For each property for which you want to log debugging information, change the value to DEBUG or INFO.

To set logging levels on the TFTP server:

  1. In a text editor, open the tftpsvr.cffile. The file is located in:

    UNIX

    installDirectory/NSH/br/

    Windows

    installDirectory/PXE/br

  2. For each property for which you want to gather debugging information, change the value to DEBUG or INFO.

Where to go from here

  1. Perform the following tasks that are specified in Importing-out-of-box-content-and-enabling-the-dashboards-and-quick-start-page:
    1. Import agent installers, agent bundles, and Agent Installer Jobs.
    2. Activate the Health and Value dashboards.
  2. Configure  TrueSight Server Automation . For more information, see Configuring-after-installation.

 

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