Walkthrough: Installing on Linux using the unified installer
This topic walks you through the process of installing BMC Server Automation on Linux, using the unified product installer and component installers. The steps in this topic apply to versions 8.6 and later, except where specifically noted.
This topic is intended for system administrators preparing to install the BSA product. The goal of this topic is to demonstrate how to use the unified product installer to install all essential components of the BSA product in a Linux environment.
What is the unified product installer?
The unified product installer simplifies and improves the installation experience by providing a centralized UI for installing the default Application Server node. It installs a set up that consists of the following components:
- Oracle Database: The unified product installer creates a BSA schema on your database server.
- Default Application Server: This is the primary server that is installed in a BSA environment. The unified product installer configures the default Application Server to connect to your database server. It also installs an RSCD agent on the default Application server. The default Application Server is also referred to as a default Application server node, because it hosts more than one component.
- File server: You can choose to install the file server on the same machine as the default Application server (called as the local file server) or install it on a separate machine (called as a separate file server.) In the case of a separate file server, you can choose to manually install the RSCD agent or have it installed by the unified product installer.
Console and PXE/TFTP server: The unified product installer installs the PXE/TFTP server and the optional console on the default Application Server.
What does this walkthrough show?
In this walk through, we will:
- Use the unified product installer to install a small BSA environment (Application Server, console, file server, PXE/TFTP).
- Use the quick start page to import servers to the new environment and to add agents to those servers.
- Use individual component installers to manually install additional components such as additional Application Servers, a separate PXE/TFTP server, and a separate console server, to complete a production-level environment.
The BSA environment will have the following characteristics:
Number of components
This BSA environment consists of two Application Servers:
This BSA environment consists of two PXE/TFTP servers:
The default Application Server connects to an existing Oracle database server.
Note: Although the BSA schema is created by the unified product installer, you must have access to an existing database that has been set up on an Oracle Server. For a description of that process, see Walkthrough: Creating the BladeLogic Database for Oracle.
This BSA environment consists of two instances of the BSA console:
This BSA environment uses a separate Linux file server machine that is installed by the unified product installer.
What do I need to do before I get started?
Perform the following prerequisite steps before executing this walkthrough scenario:
- Ensure that your environment complies with the installation requirements discussed in Requirements for installing individual components on UNIX and Linux.
- Create the Oracle table space to hold the the BSA schema, database user, and database permissions required to create the BSA schema. For detailed instructions, see Walkthrough: Creating the BladeLogic Database for Oracle.
Download the unified product installer files to a temporary location. The BBSA89-LIN64.zip and BBSA89-RSCDAgents.zip files, required in this walkthrough, can be downloaded from the Electronic Product Distribution (EPD) website. For instructions on downloading the files, see Downloading the installation files.
- If you use the unified product installer, you no longer have to use the DB scripts that are shipped with the product. However, before you run the unified product installer, you must ensure that you have a SQL database server, with an empty tablespace that the unified product installer uses to create the BSA schema. You also need to create a database user to allow the unified product installer to set up your BSA schema. For a step-by-step procedure on setting up the Oracle database, see Walkthrough: Creating the BladeLogic Database for Oracle .
RSCD agents can be automatically installed on servers that are added as additional Application Servers or as target servers. However, if the server being added runs on Windows, you will need to first set up a PsExec server to install the agents automatically. To set up a PsExec server, download the Microsoft Sysinternals Suite from the Microsoft tech support site and copy the PsExec file to the %PATH% variable (typically C:\Windows\System32\) on any Windows Server. The Windows server is now configured as a PsExec server and can be used to install agents. For more information, see Setting up a PsExec server.
NoteA PsExec server is not required if you choose to manually install the RSCD agent on the Windows server that is being added.
Bash UNIX shell must be the default shell on all machines on which BMC Server Automation is being installed.
The unified product installer needs to be run by a super user — root or a root-equivalent user on Linux. This enables the installer to install components on the Application Servers.
Linux platforms on which you plan to install the Application Server, Console, or Network Shell must have the appropriate version of libtermcap.so.2 and libtermcap.so.6 shared library installed. Install the shared library before installing these components. For more information, click the following link:Expand steps for installing prerequisite libraries
Requirement for RHEL 6
In RHEL 6 the package name has changed to compat-libtermcap. To install compat-libtermcap on Red Hat version 6, you can use one of the following commands:
- If you have YUM installed and configured:
yum install compat-libtermcap
- If you have the RPM package (available from the installation CD):
rpm -Uvh compat-libtermcap-2.0.8-49.el6.x86_64.rpm
Requirement for RHEL 7
In RHEL 7, libtermcap is no longer available, and you must create a link to libtinfo instead. Use the following command:
ln -s /lib64/libtinfo.so.5 /lib64/libtermcap.so.2
If libtinfo is not available on your system, obtain it by installing the ncurses-libs package.
- If you have YUM installed and configured:
- You must have an X Window display system installed and configured on your Linux machine.
- You must have 4 GB on disk with temp space and 4 GB on disk with installation directory.
How to install the default Application Server and separate file server using the unified installer
We start the installation process by using the unified product installer to:
- Install the default Application Server node
- Install the separate file server
- Configure the database
Install the console and the PXE/TFTP on the default Application Server
This example uses BMC Server Automation version 8.9; however, the process is applicable to versions 8.6 and later.
Extract the BBSA89-LIN4.zip and BBSA89-RSCDAgents.zip files that you downloaded from the EPD website to obtain the BBSA89-LIN64 and the rscd folder.
|2||Ensure that you have permission or assign an executable permission to the directory in which you have extracted the packages.||chmod +x -R <path_to_extracted_packages>|
|3||Copy the rscd folder from within the BBSA89-RSCDAgents.zip extractedpackage to the BBSA89-LIN64/Disk1/files/installers folder.||mv <path_to_extracted_packages>/rscd<path_to_extracted_packages>/BBSA89-LIN64/Disk 1/files/installers/|
mv /tmp/BBSA89-RSCDAgents/rscd /tmp/BBSA89-LIN64/Disk1/files/installers/
|4||Run the setup.bin file that is in the BBSA89-LIN64/Disk1 folder.||./setup.bin|
|5||Select the language in which you want to run the installer and click OK.|
Read through the basic information about the unified product installer and the types of nodes that are installed in the environment.
Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement.
Read the BSA copyright information and select I agree to the terms of the license agreement.
Enter the database server details.
TIP: You may need the help of the database administrator who set up the Oracle database server you want to connect to.
Click here if you want to use a connection string to connect to the database server
The Advanced option is only selected if you want to provide a custom connection string to your database. Note that all other fields are disabled when this option is selected.
Type the database connection string in the field adjacent to the Advanced check box. An example of a connection string for an Oracle database server is as follows:
Replace the variables in the above connection string, as follows:
A summary of the database parameters, default installation location, Application Server base port, and file server parameters is displayed.
The name of the local super user for RSCD Agent mapping is also listed.
Click Customize Configuration.
The Installation Directory tab displays the path where BSA is installed. The default path is /opt/bmc/bladeLogic/ for Linux. You can customize the Installation Directory based on your requirements, as shown in the screenshot. Make sure that you select a directory with sufficient space for installation.
Click the File Server tab and enter the file server details.
Note: If the file server is on a separate machine and if it runs on Windows, ensure that you have configured the default Application Server as a PsExec server.
Click the Ports tab at the top of the screen.
Enter the Application Server Base port. Application Server ports are normally configured from a base port, with 9800 being the default base port. Arbitrary port assignments can be made in all cases. For more information, see Application Server ports.
Click the Passwords tab at the top of the screen.
Enter new passwords in each for the fields based on the guidelines given below.
Note: The default password for each entry is password. However, BMC does not recommend using the default passwords provided by the system.
As an option, click the Console tab.
Select Install BladeLogic Server Automation Console.
BMC does not recommend installing the console on the same machine as the Application Server. When you upgrade the Application Server, the console is not automatically upgraded. You must manually upgrade it yourself.
|12||Click Update Configuration to apply all the configuration changes that you entered on the various tabs.|
Click Install to proceed with the installation.
The unified product installer performs the following setup operations:
If you encountered any errors while installing, 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. You can also find more information about resolving common issues in Troubleshooting the unified product installer.
If all operations are completed successfully, click Done to exit the wizard.
How to add additional Application Servers
To meet the demands of a larger data center, you can deploy additional Application Servers. The additional Application Server is used for improving the performance of BMC Server Automation. The method described here for adding additional Application Servers is relevant only if you installed your default Application Server node using the unified product installer.
This example uses BMC Server Automation version 8.7; however, the process is applicable to all versions 8.6 and later.
From BMC Server Automation 8.9.02 and later, Microsoft Visual C++ 2015 Redistributable Update 3 is installed automatically for all Microsoft Windows RSCD agent versions, provided the platform on which you are trying to install the product is supported.
Perform the following:
The PsExec Server is added to the BSA environment.
Select the Configuration menu and then click Add BSA Application Server Machine.
Enter the following details.
Click the Advanced Options tab at the top and enter the following details.
NEWClick the Validation tab at the top.
The additional Application Server is installed. Click OK.
How to add servers and install agents from the quick start page
The next step in setting up the BSA environment is to import servers and add agents to those servers. An easy way to this is by using the quick start page.
You can import multiple servers by specifying a text file that contains a list of server names and properties assigned to each server.
Create a server import text file using a comma-separated values (CSV) format, use the following syntax:
Save the text file (say Servers.txt) at any location in the default Application Server node (for example, C:\Program Files\BMC Software\BladeLogic\appserver).
For this walkthrough we will be adding two servers to the BSA environment (without properties).
Click here to see more samples of server import files with properties for each server.
The first example shows the simplest syntax — you simply list the host names of the servers you want to add:
The following example shows how to set the Customer property for each server:
If you need to include spaces in a property value, you must enclose the property value in double quotes:
Log on to the BSA Console.
The quick start page (BMC Welcome Page) appears.
To enroll servers, click Enroll, under Server Enrollment.
Alternative step: To Import Servers wizard, right-click the Servers folder and select Import Servers.
The Import Servers wizard appears.
Use the File selection tree to select the text file (Servers.txt) you created at the beginning. Ensure that the If agent does not exist, install using Agent installer job option is not selected. We will be installing agents on the servers later in the walkthrough.
Note: For the purpose of this walkthrough, we do not need to add any additional ACL policies. However if you need to control server access with agent ACLs click Next.
For more information about the UI elements on the Permissions screens, see Import Servers - Permissions.
For more information about ACL policies, see Controlling server access with agent ACLs.
|5||The servers are successfully added to your environment.|
The next step is to install RSCD agents on the enrolled servers.
From the quick start page, under Server Enrollment, click Install, on the quick start page.
Alternative step: To start the unified agent installer, right-click the Servers folder and select Unified Agent Installer.
The Unified Agent Installer wizard appears.
Provide a prefix that is attached to the name of all objects that unified agent installer creates.
Perform the following steps:
Note: The unified agent installer uses the information you provide on this panel to create an agent bundle. For detailed information about this type of object, see Creating an agent bundle.
|9||Click Addto open the Add Remote Host Authentication (non-Windows) window.|
The Remote Host Authentication (non-Windows) window lets you provide the following information, which is used for authenticating to agentless devices. If you are installing on multiple platforms, typically you define at least one set of authentication information for each platform.
For more information about the different authentication protocols that you can use, see Unified Agent Installer - Remote Host Authentication (non-Windows). This page also provides information about selecting an existing automation principal.
The Remote Host Authentication (Windows) window lets you provide the following information, which is used for authenticating to agentless devices. If you are installing on multiple platforms, typically you define at least one set of authentication information for each platform.
For Windows 7 and Windows 2008 target servers
BMC recommends that when you install agents on Windows 7 and Windows 2008 devices that are not enabled for a domain, specify a PsExec server that is not part of a domain. When you install agents on Windows 7 and Windows 2008 devices that are enabled for a domain, specify a PsExec server that belongs to the same domain. Ensure that the automation principals you are using to access the agentless devices are associated with the same domain.
Click Add to open the New Rule wizard.
The unified agent installer uses the information you provide on this panel to create remote host authentication rules. These rules match remote host authentication definitions with agentless devices. For detailed information about this type of object, see Creating or modifying rules for remote host authentication.
Click Add Property Condition. A window opens.
|15||Create property conditions to identify the two target servers we want to install the agents on.|
Select the non-Windows remote host authentication (created earlier) that should be used to authenticate the clm-pun-016809 server. Click the right arrow to move your selection to the list on the right.
Create a similar rule for clm-pun-016803, but this time using the Windows remote host authentication that we created.
The RSCD agents are successfully installed on the target servers.
To verify the successful installation of an RSCD agent on a target server, you can execute a custom command that provides you with agent information. Perform the following steps:
How to complete the install for a production environment
The unified product installer installs the console and the PXE/TFTP server on the default application server node to provide you with a ready-to-use test environment. However, for high-performance production environments, BMC recommends that you install and use additional instances of the console and the PXE/TFTP server on separate machines.
Installer file name
Note: Although you have different installers for 32-bit and 64-bit Windows for most components, for installing a a PXE/TFTP server you only have a 32-bit installer that you must use in both cases.
In this walkthrough we will install additional instances of the console on a Windows server and the PXE/TFTP on a Linux server.
Manually installing an additional instance of the console
Note that in this walkthrough we are installing the console on a Windows operating system and not a Linux operating system. However, if you need to install the console on a Linux or UNIX operating system, see Installing the BMC Server Automation Console (Linux and UNIX).
- MultiExcerpt named 'windows_console_install' was not found
Manually installing an additional instance of the PXE/TFTP server
Copy the installer to the machine where you want to install the PXE/TFTP server.
Extract the BBSA87-LIN4.zip file that you downloaded from the EPD website to obtain the BBSA87-LIN64 folder.
Navigate to the directory that contains the installation file (for example, BBSA87-LIN64.sh). You use this same file to install a standalone version of PXE/TFTP.
Run the installation script for BMC Server Automation, which in this case is BBSA87-LIN64.sh. Script names typically follow the convention: BBSAversion-platform.sh
Note: Do not execute the installation script from a non-root account.
|4||To install BMC Server Automation in /opt/bmc/bladelogic, press Enter, or enter another directory path.|
|5||A message prompts you to choose a language for the installation program. Enter the number representing the language that you want to use for the installation.|
Read through the acknowledgments, third-party software license agreements, and terms and conditions, as follows:
Perform the following:
Enter a password for a self-signed certificate, so that the Application Server can use the TLS protocol. The password must be 6 characters.
Confirm the password by entering it again.
Specify the max heap size for the Application Server JVM. Specify a size between 512 - 2048 megabytes.
Note: If you are installing on Linux and one of the following conditions is not satisfied, the installer warns that some BMC Server Automation components do not function until the appropriate RPM is installed.
|10||Enter y (yes) or n (no) for the following series of questions:|
Enter y (yes) or n (no) for the following series of questions:
Specify whether you want to manually start the RSCD agent or have it automatically started by the system on reboot.
Enter the directories in which you want to save the RSCD log files and the temp files. To accept the default values provided by the system, press enter.
|13||Installation of PXE/TFTP server and RSCD agent is now complete. The PXE/TFTP Server Post-Install Configuration wizard automatically starts.|
Wrapping it up
Congratulations! You have successfully set up a small BSA environment.
Where to go from here
- During installation, default security settings are applied to the Application Server and file server. BMC recommends that you adjust the security level on the Application Server host computer and the file server host computer after completing the installation. For more information, see Security planning.
- If you wish to manually install additional components to your environment, see Installing individual components.
To add servers to your new environment, see Walkthrough: Adding a Windows managed server and Walkthrough: Adding multiple target servers to the environment.