Use this procedure to install the BMC Server Automation Application Server and the Network Shell on Microsoft Windows platforms on which no previous versions of these components are installed. You can perform either:
- A full installation of all components
- A custom installation of selected components
If a previous version is already installed, see Upgrading the Application Server on Windows.
This topic contains the following sections:
Before you begin
- To perform this installation, you must have local administrator privileges.
- The BMC Server Automation Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. Communication between BMC 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 BMC Server Automation Console. To view the console, you must install it. For information, see Installing the BMC 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:
- Install in Install mode rather than Execute mode. For information, see Using Install mode instead of Execute mode.
- Install using the Windows Add or Remove Programs utility.
- You must set up your database schema. See Setting up an Oracle database for BMC Server Automation and Setting up a SQL Server database and user for BMC 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 Jython utility before installing the Application Server.
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 BMC 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.
To install the Application Server and Network Shell
| 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 Sizing and performance. 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 BMC 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. |  |
Where to go from here
- To configure the Application Server and set up administrator passwords,use the Post-Install Configuration wizard. See Configuring a single default Application Server on the host.
- If you plan to assign the Application Server to a user that is not a member of the Administrators group, confirm that the user has full access to the BMC Server Automation directory structure.
- (optional) Install the BMC Server Automation Console on the computer. See Installing the BMC Server Automation Console and Network Shell (Windows).
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks