Walkthrough: Installing on Linux using the unified installer

Application Server

2

This BSA environment consists of two Application Servers:

• A default Application server installed by the unified product installer on a Red Hat Enterprise Linux (x64) system.
• An additional Application Server installed on a Red Hat Enterprise Linux (x64) system to improve the performance of BSA.

PXE/TFTP server

2

This BSA environment consists of two PXE/TFTP servers:

• The PXE/TFTP server installed by the unified product installer on the default Application Server node
• A PXE/TFTP server that is manually installed on a separate machine (recommended for high performance environments).

Database

1

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. 

Console

2

This BSA environment consists of two instances of the BSA console:

• The console installed by the unified product installer on the default Application Server node.
• A console that is manually installed on a separate machine (recommended for high performance environments)

File server

1

This BSA environment uses a separate Linux file server machine that is installed by the unified product installer.

• unzip BBSA86-LIN64.zip -d <path_to_extracted_packages>
unzip BBSA86-LIN64.zip -d /tmp/BBSA86-LIN64 
• unzip BBSA86-RSCDAgents.zip -d <path_to_extracted_packages>
unzip BBSA86-RSCDAgents.zip -d /tmp/BBSA86-RSCDAgents

chmod +x -R <path_to_extracted_packages>

./setup.bin

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.

Click Next.

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

Click Next.

Read the BSA copyright information and select I agree to the terms of the license agreement.

Click Next.

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.

• Enter the Host name or IPv4 address of the server that runs the database. Note that if your server is on an IPv6 address system you can only enter the host name of the server.
• Enter the Port that the database listens on. The default port is 1521 for an Oracle Database.
•  Enter the SID of your database instance that runs on the Linux database server.
  
• Enter the database user name that you created while setting up the database. Ensure that you have assigned the required permissions to the user, see Walkthrough: Creating the BladeLogic Database for Oracle.
• Enter the password of the database user that you created while setting up the database, see Walkthrough: Creating the BladeLogic Database for Oracle.
• Enter the names of the BSA table space and BSA index table space that you created while setting up the Oracle database, see Walkthrough: Creating the BladeLogic Database for Oracle.
• Click Next.
  
  

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.

Click the File Server tab and enter the file server details.

• To install the file server on a separate machine, select the Install file server on a separate host option (In version 8.6, this option was called Use Remote file server).
• Because we have not manually installed the RSCD Agent on the file server, we must ensure that the RSCD agent is already installed option is not selected.
• Enter the Host name or IPv4 address of the file server. Note that if your server is on an IPv6 address system, you can only enter the host name of the server.
• Enter the directory on the file server where data is stored.
• Select Linux as the operating system that runs on the separate file server.
  Note: For a Linux Application Server, the unified product installer can only install the RSCD agent on a separate file server that is also running on Linux. If the separate file server is running on Windows, you must manually install the RSCD Agent based on the procedures in Installing an RSCD agent (Windows).
• Enter the name of a Linux user with superuser permissions.
• Enter the password of the Linux user with superuser permissions.
• Confirm the password.

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.

• Certificate Password
  The BSA Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. 

    Click here for more information.

  Communication between BSA and servers being provisioned 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.

• BLAdmin Password
  BSA creates a built-in user called BLAdmin during the installation process. The BLAdmin user is only assigned the BLAdmins role.

    Click here for more information.

  To activate the default user, it must be assigned a password and granted access to servers in your network. You can use the RBAC Manager folder to perform these actions, but to start the console the first time, you must define a password for the BLAdmin user. For more information, see RBACAdmin and BLAdmin users.

• RBACAdmin Password
  BSA creates a built-in user called RBACAdmin during the installation process. The RBACAdmin user is only assigned the RBACAdmins role.

    Click here for more information.

  To activate the default user, it must be assigned a password and granted access to servers in your network. You can use the RBAC Manager folder to perform these actions, but to start the console the first time, you must define a password for the RBACAdmin user. For more information, see RBACAdmin and BLAdmin users.

Click the Agent Mapping tab.

Enter the name of the local super user, either root (the default) or a root-equivalent user, to which the RSCD Agent should map incoming connections during the installation.

Click Install to proceed with the installation.

The unified product installer performs the following setup operations:

• Creates a BSA schema in the database
• Installs the default application server
• Installs the console
• Installs a PXE/TFTP server
• Installs the Network Shell
• Connects the default Application Server machine to the database
• Installs the separate file server and the RSCD agent
• Installs out-of-the-box compliance content
• Installs pre-packaged sample content (blcontent) and imports various zipkits with pre-defined content for specific tasks

In case 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. 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.

Start the BMC Server Automation Console and log on using your BL Admin credentials that you created here. For more information, see Starting the BMC Server Automation Console.

Perform the following:

1. Minimize the quick start page
2. Right-click Servers, and click Add Server to add a PsExec server to the BSA environment.
   Note: If you did not copy the PsExec file to %PATH% (typically C:\Windows\System32\) of the PsExec server, you see an error in this step.
3. Enter the host name or IP address of the PsExec server 
4. Click Finish.

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.

• Host name or IPv4 address of the Application Server. Note that if your Application Server is on an !Pv6 address system you can only enter the host name of the server.
• User name of an account with Administrator privileges on the additional Application Server machine.
• Password of the account with Administrator privileges on the additional Application Server machine.
• Confirm the password of the account with Administrator privileges on the additional Application Server machine.
• Select the PsExec server from your environment.

Click the Advanced Options tab at the top and enter the following details.

• Path to the location where you want to install the additional Application Server. The default path used is C:\Program Files\BMC Software\BladeLogic\
• 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.
• Enter the location you want to use as the temporary staging directory during the installation.

The additional Application Server is installed. Click OK.

/BBSA86-LIN64/files/installers/rcp

BBSACONSOLE86-LIN64

/BBSA86-LIN64/files/installers/pxe_64

PXE86-LIN32  

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.

/BBSA86-LIN64/Disk1/files/installers/rcp

BBSACONSOLE86-LIN64

 /BBSA86-LIN64/Disk1/files/installers/appserver_64

 BBSA86-LIN64.sh

Navigate to the directory containing the installation files that you copied from the Application Server and run the installation program for the console. Different installers are provided for 32-bit and 64-bit Windows.

In this example, we are running the BBSACONSOLE87-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.

Ensure that you have closed all applications before you proceed.

Click Next.

The Review License Agreement window opens.

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.

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.

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 BMC Server Automation Console Upgrade Service check box, the BMC Server Automation Console Upgrade Service is not installed. This service is required for automatically upgrading the BMC Server Automation Console when you upgrade the Application Server.

Click Next.

In case 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. 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.

Start the console.

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

Click on the Authentication Profiles tab and click Add.

BSA 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.

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 BMC Server Automation authentication mechanisms. The default Port is 9840. For more information about Console ports, see BMC 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.

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.

The quick start page is the first page that is displayed once you log on the the BSA Console. It introduces you to the main use cases of BMC Server Automation and allows you to execute them from a centralized UI immediately after installing the BSA set up. For information about using the quick start page, see Quick start page.

For general information about the UI of the BSA Console, see Navigating the interface.

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.

<path_to_extracted_packages>/BBSA-LIN64/Disk1/files/installers/appserver_64/

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.

./BBSA87-LIN64.sh

Read through the acknowledgments, third-party software license agreements, and terms and conditions, as follows:

1. A welcome message is displayed, followed by a prompt to read the third-party software license agreements. Press Enter.
2. An acknowledgment is displayed, listing the third-party software that BMC Server Automation uses. Press Enter.
3. A message prompts you to scroll through and review the terms and conditions for using this software. Press Enter.

4. The following message is displayed:
   Do you agree to the terms of the license agreement (y for Yes)?
   Enter y.

Perform the following:

1. For successful provisioning, the RSCD agent must be installed on the same host computer as the PXE server and TFTP server. Therefore, in this step, enter 1PT.

   A plus sign (+) appears next to RSCD agent, PXE server, and TFTP server, indicating that you have chosen to install them.

2. Enter 9 to start the installation.

3. A message lists the components that you have chosen to install and asks if you want to continue. Enter y.

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.
A series of messages indicate the progress of the installation.

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.

• On Red Hat Linux, the compat-libstdc++-33 RPMs must be installed. Also, the XFree86-libs or xorg-x11-libs RPMs must be installed.
• On SUSE 9.x, either the compat or compat-32bit RPM must be installed and the xf86 RPM must be installed.
• On SUSE 10.x, either the compat or compat-32bit RPM must be installed and the xorg-x11 RPM must be installed.

1. A message lists the host name and IP address of this server. This information is needed to configure a connection with the TFTP server and the data store. If the information identifies the server correctly, press y.

2. Specify whether your DHCP server is located on this server or a separate machine.
   
   

     Click here for more information ...

   If the DHCP server is located on another server, the installation program automatically configures this server to function as a DHCP proxy. You must configure the DHCP server differently, depending on whether it is installed on the same host computer as the PXE Server. For more information on configuring the DHCP server, see Configuring a DHCP server on Windows and Configuring a DHCP server on Linux.

3. Specify whether you want to use digitally signed logs for RSCD agents.

4. Specify whether you want use keystroke logs for nexec commands.

Enter y (yes) or n (no) for the following series of questions:

1. Specify whether you want to provide root permissions to the root clients on this host (root equivalency). By default, the RSCD agent does not provide root permissions to root clients.
2. Specify whether you want a particular client associated with a local user on this machine. If you enter y, you must enter the name of the user and the client that you want to map to.

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.