Prerequisites for installation, installation order, and product dependencies

Enterprise and Cloud AR System components

Install BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary and BMC Remedy AR System – Cloud Database Primary in the same session. For more information, see installation recommendations. These two products depend on each other.

BMC Remedy Mid Tier

BMC Remedy Mid Tier is already installed with BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary for all deployment types. To improve performance for the small, medium, and large, deployments, BMC recommends that you install an additional mid tier on a separate host.

Note: For small, medium, and large deployment types, the mid tier service is stopped by default after installation.

BMC Remedy Mid Tier depends upon BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary.

BMC Atrium Core Web Registry

To avoid installation issues with this product, do not install it on the same hosts as the following products:

• BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary
• BMC Remedy AR System – Cloud Database

BMC Remedy Mid Tier depends upon BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary.

(Optional) BMC Server Automation – File Server

To improve performance, install the file server on a separate host. This product installation has no dependencies.

Note: If the file server is a remote file server (not installed on the same host as the Application Server and Console), install it before you install BMC Server Automation Application Server and Console.

BMC Server Automation – Application Server and Console

Install the primary application server and Automation Console. This installation creates two application instances: one configuration server and one job server. This product depends on BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary. If you plan to install BMC Server Automation – File Server on a separate host, install it before installing BMC Server Automation – Application Server and Console.

Note: Ensure that you use the host name when installing BMC Server Automation instead of using the fully qualified domain name (FQDN). Otherwise, the domain name is truncated due to the character limit.

Note: Oracle JRE 7u71 or greater is required for a successful BMC Server Automation installation.

(Optional) BMC Server Automation – Application Server (MAS)

Install this product on secondary computer to provide multiple Application Server (MAS) support. This installation creates two application instances: one configuration server and one job server. This product installation is required only in a MAS environment.  You must install BMC Server Automation – Application Server and Console before BMC Server Automation – MAS.

Note: Ensure that you use the host name when installing BMC Server Automation instead of using the fully qualified domain name (FQDN). Otherwise, the domain name is truncated due to the character limit.

BMC Atrium Orchestrator products

BMC Atrium Orchestrator includes:

• BMC Atrium Orchestrator Server
• (Optional) BMC Atrium Orchestrator – Configuration Distribution Peer (high availability, or HA) 

If your environment requires scalability, install BMC Atrium Orchestrator – Configuration Distribution Peer (HA) on small, medium, and large deployment types.

Before you install BMC Atrium Orchestrator Server, install the following products:

• BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary
• BMC Server Automation – Application Server and Console

Before you install BMC Atrium Orchestrator – Configuration Distribution Peer (HA), install BMC Atrium Orchestrator Server.

Note: Install both products in the same session.

BMC Network Automation

Before you install BMC Network Automation, install the following products:

• BMC Atrium Core Web Registry Components
• BMC Atrium Orchestrator Server

(Optional) BMC ProactiveNet components

With BMC Cloud Lifecycle Management 3.1, you can now optionally install BMC ProactiveNet Performance Management products. If you already have a third-party performance monitoring product installed in your environment, or if you do not require any monitoring capabilities in your cloud environment, you can skip this installation. 

BMC ProactiveNet Data Collection Host is installed with the BMC ProactiveNet Server installation. Therefore, the Data Collection Host is no longer available for installation in the Workload tier.  

On a proof-of-concept (POC) deployment, you need to install only the BMC ProactiveNet Server.

Warning: Install BMC ProactiveNet Server on the same drive as BMC ProactiveNet Central Server. Installing it on a different drive might cause installation issues.

Note: If you do not install the BMC ProactiveNet products as part of your cloud installation and then decide to install them later, you will have to perform manual configuration tasks to successfully complete installing the products. To perform the manual configuration steps after installing the BMC ProactiveNet products, contact BMC Customer Support.

Before installing BMC ProactiveNet components, ensure that the following prerequisites have been met:

• Ensure that you can log on to the BMC Server Automation application serverand that you can access the BMC Server Automation web services. 
  1. Open a command window.
  2. Change directories to the blasadmin utility (C:\Program Files\BMC Software\BladeLogic\NSH\bin\ on Windows and /NSH/bin/ on Linux).
  3. Enter the following command:
     blasadmin show AppServer enableWebServices
     If the value returned is true, the web services are running.

If the value returned is is false, start the web services and restart the application server:

• 1. In the command window, enter the following command in the NSH\bin directory:
     blasadmin set AppServer enableWebServices true
  2. Restart the application server.
• Ensure that ports 80, 1099, and 8080 are available and are not being used by other products. For example, you cannot install BMC ProactiveNet Central Server on the target computer if Microsoft IIS, the World Wide Web Publishing Service, or the SQL Server Reporting Service is using port 80.
• Stop and disable the Windows Firewall service on the computers targeted for the BMC Proactive Central Server and BMC ProactiveNet Server:
  1. Go to Start > Control Panel > Windows Firewall.
  2. Start the Windows Firewall service, if necessary.
  3. In the Windows Firewall dialog box, click Change Settings.
  4. In the Windows Firewall Settings dialog box, click Off and then click OK.
  5. Disable the Windows Firewall service. 
  6. Restart the computer.
      For more information about stopping or disabling the firewall service, see the I Need to Disable Windows Firewall topic in the Microsoft TechNet Library. 

• Ensure that BMC Server Automation Application Server host can ping the BMC ProactiveNet hosts (and vice versa) by the shortname and the fully-qualified domain name.

• For all three products, ensure that you can view view both the 8.3 short name and the long name for the installation directory. Before starting the installation, you should be able to create a directory over 8 characters in a command line window, and then enter dir /x.
   
  If the 8.3 name is missing, a setting is not correct. You must then set Ntfsdisable8dot3namecreation in the Windows Registry to 2. 
  1. Select Start > Run > regedit.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
  3. Select NtfsDisable8dot3NameCreation and edit it.
  4. Set Value data to 2.
  5. Click OK.
  6. Restart the computer after you make changes to the Registry.
     When you finish, ensure that you can see both the 8.3 short name and the long name by entering dir /x in a command window.

• Before you install BMC ProactiveNet Central Server, install BMC Server Automation – Application Server and Console.
• Before you install BMC ProactiveNet Server, install BMC ProactiveNet Central Server.

• If you are using Oracle Automatic Shared Memory Management (ASMM), turn it off before running the SQL script to prepare the BMC ProactiveNet Performance Management database instances. If you do not, the installation will fail. 

  Ensure that the libraries listed in the BMC ProactiveNet Server requirements for Linux topic in the BMC ProactiveNet online technical documentation are present to install BMC ProactiveNet Server in the GUI mode.

  Note: If 32-bit RPMs are required, the RPM must be the same version as the most current 64-bit version of that RPM.

• Before installing BMC ProactiveNet Central Server on Red Hat Linux 6.2, you must:
  • Increase the JVM heap size to on the configuration Application Server to 4 GB.
  • If Application Server instances other thanjob_deployment and config_deployment (required by the BMC Cloud Lifecycle Management installation program) are running, stop them before proceeding with the installation:
  1. 1. Log on to the BMC Server Automation console.
     2. Under the Configuration tab, click Infrastructure Management.
     3. Expand Application Servers.
     4. Right-click the Application Server instances, and click Stop.
• If you want to manage your VMware Virtual Center version 5.1 using BMC Performance Manager for Virtual Servers, you must upgrade your Virtual Server modules on the BMC ProactiveNet Data Collection host computer to version 3.2.00:
  1. Log on to the EPD site at https://webapps.bmc.com/epd/faces/licensedProd.jsp.
  2. Search for BMC Performance Manager for Virtual Servers and download the BMC PATROL version 3.2.00 for VMware vSphere (OS specific) and BMC ProactiveNet Performance Management Infrastructure (Agent) – Common Install version 7.5.64 (OS specific) installers.
  3. Extract both the installers into a folder namedbmc_products appropriate to your operating system.
  4. Run the setup.exe/setup.sh -serveronlycommand.
  5. Copy the prompt into the URL address field of your browser (preferably Mozilla).
  6. Follow the instructions in the installer to complete the installation.

Cloud Database Extensions

Install this product on the same computer where you installed BMC Remedy AR System Server – Cloud Database Primary.

Cloud Database Extensions depends upon BMC Remedy AR System Server – Cloud Database Primary.

Cloud Platform Manager

Before you install Cloud Platform Manager, install the following products:

• BMC Remedy AR System Server – Cloud Database Primary
• BMC Server Automation
• BMC Network Automation
• BMC ProactiveNet Server ( for POC deployment) and BMC ProactiveNet Central Server (for small deployment)
• Cloud Database Extensions
• BMC Atrium Orchestrator Server

Cloud Portal AR Extensions – Primary

Before you install Cloud Portal AR Extensions – Primary, install the following products:

• BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary
• BMC Atrium Orchestrator Server
• Cloud Platform Manager

(Optional) Enterprise AR System Secondary

Note: If you changed the password for the Demo user between the time you installed the Enterprise AR System server – Primary and Secondary servers, you must reset the password to blank on the Primary server before you install the Secondary server. This is because the Enterprise AR System server installation does not permit you to change the AR System user passwords in between installations.

Install BMC Remedy AR System and BMC Remedy IT Service Management Suite – Secondary for small, medium, or large deployments only if you need failover or high-availability systems for performance reasons.

Before you install BMC Remedy AR System and BMC Remedy IT Service Management Suite – Secondary, install the following products:

• BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary
• Cloud Portal AR System Extensions 

Tip: The BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary host is your administrative server.

(Optional) Cloud AR System Secondary

Install Cloud Database Secondary for small, medium, or large deployments only if you need failover or high-availability systems for performance reasons.

Before you install BMC Remedy AR System – Cloud Database Secondary, install BMC Remedy AR System Server – Cloud Database Primary.

Cloud Portal AR Extensions – Secondary

Install Cloud Portal AR Extensions – Secondary on the same host as BMC Remedy AR System and BMC Remedy IT Service Management Suite – Secondary.

Before you install Cloud Portal AR Extensions – Secondary, install the following products:

• Cloud Portal AR Extensions – Primary 
• BMC Remedy AR System and BMC Remedy IT Service Management Suite – Secondary

(Optional) PXE Server

This product installation is required for physical and virtual bare-metal provisioning. BMC recommends that you install BMC Server Automation – Application Server and Console and PXE Server on separate hosts to manage resources appropriately. Therefore, the BMC Cloud Lifecycle Management Installer prevents you from installing both products on the same host.

Before you install PXE Server, install BMC Server Automation – Application Server and Console.

(Optional) BMC Server Automation – Advanced Repeater

Install the Advanced Repeater for small, medium, or large deployments only if you need high-availability for performance reasons. 

This product installation has no dependencies.

(Optional) BMC Network Automation – Device Agent

Install the Device Agent for small, medium, or large deployments only if you need high-availability for performance reasons. 

This product installation has no dependencies.