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
- Step 1: Setting up a database and user for a Microsoft SQL Server database
- Step 2: Setting up a database schema for a Microsoft SQL Server database
- Step 3: Install the agent on the file server
- Step 4: Install the Application Server
- Step 5: Run the post-install configuration utility
- Step 6: Install the console on your client system
- Step 7: Connect to the Application Server
- What if I have problems?
- Where to go from here
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.
Step 2: Setting up a database schema for a Microsoft SQL Server database
- 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. - Open a command prompt window.
- Change (cd) to /db_scripts/sqlserver.
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
Step 3: Install the agent on the file server
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.
The installation wizard is displayed.
Step 4: Install the Application Server
| Step | Example screen |
---|---|---|
1 |
| |
2 | Click Next. The Acknowledgement panel is displayed. | |
3 | Click Next. The License Agreement panel is displayed.
| |
4 | Click Yes. The Customer Information panel is displayed. | |
5 |
The Setup Type panel is displayed. | |
6 |
The Choose Destination Location panel is displayed. | |
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. | |
8 |
| |
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. | |
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. | |
11 | Review the selected components and click Next to start the installation. | |
12 | The status panel displays the installation progress. When installation completes, the Post-Configuration panel is displayed. | |
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. | |
14 | Click Finish to exit the installation program. |
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.
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.
- 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/blappconfThe configuration wizard opens.
- Read the introductory page and click Next. The Database page appears.
- Choose a Database Type (either Oracle or SQL Server).
- 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.
- Click Next. The File Server page appears.
- 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.
- Click Next. The Notification Servers page appears.
- 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.
- 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.
- Click Next. The User Passwords page appears.
- 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. - (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.
- Click Finish.
Step 6: Install the console on your client system
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.
|
|
2 | Ensure that you have closed all applications before you proceed. Click Next. The Review License Agreement window opens. | |
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. | |
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. | |
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.
| |
6 | The window displays your selections. Click Install. The installer pre-analyzes your environment:
The window displays installation progress, then displays a message when installation is complete. The console and Network Shell are installed on your machine. | |
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.
| |
8 | Start the console. To configure the console so that it connects to the default Application Server, click Options. | |
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. | |
10 | Enter the following information.
| |
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. |
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.
|
|
2 | Ensure that you have closed all applications before you proceed. Click Next. The Review License Agreement window opens. | |
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. | |
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. | |
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.
| |
6 | The window displays your selections. Click Install. The installer pre-analyzes your environment:
The window displays installation progress, then displays a message when installation is complete. The console and Network Shell are installed on your machine. | |
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.
| |
8 | Start the console. To configure the console so that it connects to the default Application Server, click Options. | |
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. | |
10 | Enter the following information.
| |
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. |
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.
- Using the Authentication profile tab, select an authentication profile.
- 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.
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.
- 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. - 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.
- 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.) Click OK. The TrueSight Server Automation Console appears.
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:
| ||||||||
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:
To set logging levels on the TFTP server:
|
Where to go from here
- Perform the following tasks that are specified in Importing-out-of-box-content-and-enabling-the-dashboards-and-quick-start-page:
- Import agent installers, agent bundles, and Agent Installer Jobs.
- Activate the Health and Value dashboards.
- Configure TrueSight Server Automation . For more information, see Configuring-after-installation.