This topic summarizes the system requirements for the installer host, the supporting products, and databases used by BMC Cloud Lifecycle Management on Microsoft Windows operating systems:
Windows installer host requirements
Before you launch the BMC Cloud LifeCycle Management installer, ensure that the installer host meets the requirements described in the following sections, based on your operating system. An installer host is the physical or virtual machine host on which you run the installer.
Installer host operating system requirements
Click here to see the OS and hardware requirements for the installer host.
| | |
|---|
- Microsoft Windows Server 2008 (R2 64-bit)
- Microsoft Internet Explorer 7.0 or later, or Mozilla Firefox 3.5 or later
| - Minimum 30 GB free hard-disk space for storing installation applications
- Minimum 1 GB free hard-disk space for the installation directory
- 2 CPUs (3-GHz dual processor)
- Minimum 1 GB RAM during installation
| These permissions apply to BMC Cloud Lifecycle Management installer host and all target hosts. You need local Windows administrator credentials to perform all the installations. The user must be: - The local Administrator of the system (not a domain user)
- Added to the Administrators group on the system
You must also perform the following steps: - Open Administrative tools > Local Policies > User Rights Assignments.
- Add the user to the Allow log on locally property.
- Remove the user from the Deny log on locally property, if present.
|
Installer host environment variables
Ensure that the user and system environment variables on the installer host are set with the same value (for example, TMP=C:\Support and TEMP=C:\Support). Also ensure that the values of these user and system variables match on both installer and product hosts.
Installer host port requirements
Click here to see the port requirements for the installer host.
If a firewall is configured in your environment, ensure that the firewall allows communication from the BMC Cloud Lifecycle Management installer host to the target computers, using the ports listed in the following table. The installer uses these ports to run commands to check application connectivity, database connections, RSCD connectivity, remote installation status, and so on. The port number in the table is the default value and might change based on user input or user environment configuration. For example, the database might be installed on port 1522 instead of port 1521. In that case, you must ensure that the port is enabled in the firewall.
WarningNote
The Cloud Portal and Database server is installed by default on portmapper; the port number assigned in that case is port 0. For the Cloud Portal and Database server, you cannot change the port number during the install.
| | |
|---|
BMC Cloud Lifecycle Management Install Planner | | Installer ports On the BMC Cloud Lifecycle Management installer host, ensure that port 12433 is free. The BMC Cloud Lifecycle Management installer executes product installations remotely using a silent installation. The product installations that are launched on the target hosts use port 12333 or 9998, as applicable, during invocation on the target host. The BMC Cloud Lifecycle Management installer queries the ports over the network to check whether the installation launched successfully. If a firewall is between the BMC Cloud Lifecycle Management installer host and a target host, ensure that these ports are not blocked. This requirement is applicable for all product hosts. |
BMC Remedy AR System server (AR System server) and IT Management Suite | 0 (default value if the portmapper is being used) | Cloud Portal and Database server, AR System server post-installation, and Cloud Portal AR Extensions port The default value on which Cloud Portal and Database server is installed by the BMC Cloud Lifecycle Management installer is port 0 if the AR System portmapper is being used. The BMC Cloud Lifecycle Management installer queries the port (chosen randomly by the portmapper) over the network during AR System server post-installation to check whether the AR System server is running. Make sure there is no firewall is between the BMC Cloud Lifecycle Management installer host and a target host. |
| | Cloud Portal and Database server database port During the Cloud Portal and Database server installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is up and running. If the target Oracle database is installed using default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
| | BMC Server Automation database port During the BMC Server Automation installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is running . If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
| | BMC Server Automation RSCD agent port This requirement is applicable for all hosts (product hosts as well as the BMC Cloud Lifecycle Management installer host). If a firewall is between the BMC Cloud Lifecycle Management installer and a target host, ensure that port 4750 is not blocked, because the BMC Cloud Lifecycle Management installer runs remote commands for target host installations to the RSCD agent on the target host (which uses port 4750). |
| | BMC Network Automation database port During the BMC Network Automation install using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is running . If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
Preboot Execution Environment (PXE) | | During the PXE install using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is up and running . If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. |
For more information about the ports used by BMC Cloud Lifecycle Management, see Port-mappings.
Preparing the installer host
Click here to see a list of the preparatory tasks you must complete for the installer host .
Before you start installing the products in the BMC Cloud Lifecycle Management solution, prepare the Microsoft Windows computer on which you will run the installer.
To verify credentials and access
For all new installations with the installer host, verify the following credentials:
- The Windows user credentials must have access to both the installer host, the target Enterprise-AR host, and Enterprise-AR database host.
- The installer host, the target Enterprise-AR host, and Enterprise-AR database host must be in the same domain.
To update the BMC Server Automation RSCD agent and NSH to the required version
For new installations, the BMC Cloud Lifecycle Management installer installs version 8.5 of the BMC Server Automation Remote Server Call Daemon (RSCD) Agent and BMC Network Shell (NSH). The installer uses NSH to execute silent installation commands, which are accepted by the RSCD agent installed on the target hosts. The RSCD agent executes the commands so that the installer can remotely install the supporting BMC products.
If an existing RSCD Agent and NSH are installed, uninstall them, as described in the following procedures.
Click here to review the steps for uninstalling the BMC Server Automation RSCD agent.
- Select Start > Programs > Windows Control Panel and open the Add/Remove Programs utility.
- Select the component that you want to uninstall (for example, BMC Server Automation RSCD Agent) and click Change/Remove
- After the RSCD Agent is uninstalled, go to C:\Program Files\BMC Software\Bladelogic and delete the RSCD folder.
- Manually delete the C:\Windows\rsc folder.
Restart your computer.
SuccessTip
If you don't restart your computer, installing the RSCD Agent can take an extended period of time to perform, sometimes over an hour.
For more information, see Uninstalling in the BMC Server Automation 8.3.00 documentation.
Click here to review the steps for uninstalling NSH.
- Select Start > Programs > BMC Software > BladeLogic Server Automation Suite > Uninstall Network Shell.
- After the NSH is uninstalled, go to C:\Program Files\BMC Software and delete the NSH folder.
- Manually delete the C:\Windows\rsc folder.
- Restart your computer.
For more information, see Uninstalling in the BMC Server Automation 8.3.00 documentation.
Perform the following steps to ensure that you can successfully launch the installation on a product host:
- Ensure that you can contact all target hosts (on which you want to install BMC products) from the installer computer (for example: ping <host name>.
- Run the ipconfig command on the target host, and verify that the IP address returned in the previous step matches the the target computer's IP address returned in this step.
If you are using Terminal Services, update the Terminal Services configuration options as needed before running the installer. The installer runs only when Terminal Services is configured correctly.
WarningNote
If you do not configure these items before you run the installer, an installer panel appears listing the steps required to handle these issues.
Click here to review the steps for updating the Terminal Services configuration options.
- From the Windows Start menu, click Run.
- Type gpedit.msc, and then click OK.
- Navigate to the Temporary folders policies:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders
or:
Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Terminal Server > Temporary folders - Set the Properties of Do not delete temp folder upon exit to Enabled and then click OK.
- Set the Properties of Do not use temporary folders per session to Enabled and then click OK.
- If the settings do not take affect, complete the following steps:
- From the Windows Start menu, click Run.
- Type regedit, and then click OK.
- Expand HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server.
- Update PerSessionTempDir to 0 and DeleteTempDirsOnExit to 0.
Before you launch the installer, ensure that you can access target VMs from the installer computer.
WarningNote
If FTP is not enabled, use the following procedure.
Click here to review the steps.
- On the installer computer, click Run.
- Enter \\<targetmachinename>\C$ (or the D$drive) for every target computer.
If you do not see an error message, the installer is ready to install the RSCD Agent on the target host.
If you do see an error message (for example, The trust relationship between this workstation and the primary domain failed), your computer is not synced with the domain controller, and you must perform the following steps:
- On the target computer, open the Computer Properties dialog box.
- Click Advanced system settings.
- Click the Computer Name tab.
- Click Change to change the workgroup and domain settings.
- Select Workgroup.
- Enter WORKGROUP and then click OK.
- In the Windows Security dialog box, enter the administrator user name and password to remove the computer from the domain, and then click OK.
- At the change prompt, click OK.
After you successfully change the settings, do not restart the computer. - In the System Properties dialog box, click Change.
- Select Domain.
- Enter the domain.
- At the welcome prompt, click OK.
- At the change prompt, click OK.Click Close to close the Computer Properties dialog box.
- Restart the computer.
- When the computer restarts, click Run and then enter \\<targetmachine_ame>\C$.
The installer is now ready to install the RSCD Agent on the target host.
WarningNote
If you cannot mount a network shared drive, you must install FTP 7.5.
See Installing FTP 7.5 on Windows Server 2008 in the Microsoft TechNet Library.
Set your computer screen to the recommended resolution of 1280 x 800 or greater.
Windows supporting product host requirements
This section lists the hardware and software requirements, and the tasks that you must perform before you install the BMC Cloud Lifecycle Management solution on Microsoft Windows. The requirements outlined in this topic are for a POC deployment only. For more information about product-specific hardware requirements per deployment type, see deployment architecture and sizing guidelines.
BMC Remedy product requirements
The following table lists the product-specific requirements for the BMC Remedy products.
| |
|---|
BMC Remedy AR System & IT Service Management Suite – Primary |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 8 GB RAM
- Hard disk space:
- Installation directory: 10526 MB
- Temp (tmp) directory: 9064 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
- Oracle JRE 1.7 (64-bit)
- Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities. Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.
Product-specific requirements: - For remote database installations, configure credentials for the startup account of the Microsoft SQL Server service as follows:
- On your remote database computer, go to Administrative Tools > Services.
- Select SQL Server (MSSQLServer) service and right-click to open the pop-up menu.
- Select Properties and select the Log on tab.
Provide administrator credentials in the This account field. WarningEnsure that the Administrator user that you provide in this step is added to the Administrators group of the target Enterprise AR System server. - Save the changes and restart the service.
|
BMC Remedy AR System & IT Service Management Suite – Secondary |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 8 GB RAM
- Hard disk space:
- Installation directory: 10526 MB
- Temp (tmp) directory: 9064 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
- Oracle JRE 1.7 (64-bit)
- Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities (shares the database with BMC AR System Server - Cloud Portal and Database - Primary). Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.
Product-specific requirements: None |
|
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 4 GB RAM
- Hard disk space:
- Installation directory: 360 MB
- Temp (tmp) directory: 2609 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
- Oracle JRE 1.7 (64-bit)
Product-specific requirements: None |
BMC Atrium Core Web Registry requirements
Click here to see the hardware, software, and product-specific requirements for the BMC Atrium Core Web Registry.
Hardware and software requirements:
- 2 CPUs
- 6 GB RAM
- Hard disk space:
- Installation directory: 1345 MB
- Temp (tmp) directory: 5223 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
- Oracle JRE 1.7 (64-bit)
Product-specific requirements: None
BMC Server Automation product requirements
The following table lists the product-specific requirements for the BMC Server Automation components.
| |
|---|
BMC Server Automation – Application Server & Console |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 8 GB RAM
- Hard disk space:
- Installation directory: 745 MB
- Temp (tmp) directory: 1626 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
- Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities (for remote or local database).
Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations
Product-specific requirements: Before you begin installing BMC Server Automation – Application Server & Console, ensure that port 9700 is available on the host on which you want to install the product. |
BMC Server Automation – Multiple Application Server (MAS) |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 8 GB RAM
- Hard disk space:
- Installation directory: 9 GB
- Temp (tmp) directory: 3 GB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
- Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities (shares the database with BMC Server Automation Application Server & Console).
Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations
Product-specific requirements: Before you begin installing BMC Server Automation – Application Server & Console, ensure that port 9700 is available on the host on which you want to install the product. |
BMC Server Automation – Remote System Call Daemon (RSCD) Agent |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 8 GB RAM
- Hard disk space: Installation directory: 100 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
Product-specific requirements: None |
BMC Server Automation – Advanced Repeater (Optional) |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 1 GB RAM
- Hard disk space:
- Installation directory: 265 MB
- Temp (tmp) directory: 391 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
Product-specific requirements: None |
|
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 1 GB RAM
- Hard disk space:
- Installation directory: 46 MB
- Temp (tmp) directory: 1626 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
Product-specific requirements: For more information, see the IIS 6 Compatibility components not installed topic in the Microsoft TechNet Library. |
BMC Server Automation – File Server (Optional) |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 8 GB RAM
- Hard disk space:
- Installation directory: 50 MB
- Temp (tmp) directory: 1 GB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
WarningNote Storage on the File Server requires additional hard disk space. Product-specific requirements: None |
BMC Atrium Orchestrator product requirements
The following table lists the product-specific requirements for the BMC Atrium Orchestrator components.
| |
|---|
BMC Atrium Orchestrator – Configuration Distribution Peer |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 2 GB RAM
- Hard disk space:
- Installation directory: 590 MB
- Temp (tmp) directory: 3598 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
Product-specific requirements: Install the BMC Atrium Orchestrator Development Studio client so that you can export the IP Address Management (IPAM) modules to the BMC Atrium Orchestrator grid. For more information, see Installing BMC Atrium Orchestrator Development Studio. |
BMC Atrium Orchestrator – Configuration Distribution Peer (HA) |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 4 GB RAM
- Hard disk space:
- Installation directory: 590 MB
- Temp (tmp) directory: 3598 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
- Msvcr71.dll
Product-specific requirements: Install the BMC Atrium Orchestrator Development Studio client so that you can export the IP Address Management (IPAM) modules to the BMC Atrium Orchestrator grid. For more information, see Installing BMC Atrium Orchestrator Development Studio. For more information about a missing Msvcr71.dll file, see: |
BMC Network Automation product requirements
The following table lists the product-specific requirements for the BMC Network Automation components.
| |
|---|
|
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 4 GB RAM
- Hard disk space:
- Installation directory: 1245 MB
- Temp (tmp) directory: 997 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
- Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities (for remote or local databases). Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations
- Microsoft .Net framework
Product-specific requirements: Ensure that you have Microsoft Windows 8.3 file-name setting enabled before the installation. For more information, see Enabling Windows 8.3 file names in the BMC Network Automation documentation portal. . |
BMC Network Automation – Device Agent |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 4 GB RAM
- Hard disk space:
- Installation directory: 2093 MB
- Temp (tmp) directory: 770 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
Product-specific requirements: Ensure that you have Microsoft Windows 8.3 file-name setting enabled before the installation. For more information, see enabling Windows 8.3 file names. |
BMC Cloud Lifecycle Management requirements
The following table lists the product-specific requirements for the BMC Cloud Lifecycle Management components.
| |
|---|
Cloud Database Extensions |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: Install the Cloud Database Extensions on the same host as BMC Remedy AR System – Cloud Database. Hard disk space: - Installation directory: 521 MB
- Temp (tmp) directory: 1933 MB
Product-specific requirements: None |
|
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: - 2 CPUs
- 2 GB RAM
- Hard disk space:
- Installation directory: 521 MB
- Temp (tmp) directory: 1933 MB
- Windows 2008 R2 Enterprise Edition SP1 (64-bit)
- Oracle JRE 1.7 (64-bit) (You can install JRE that is bundled with the product or you can use an existing installation.
Product-specific requirements: None |
Cloud Portal AR Extensions – Primary |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: Install the Cloud Portal AR Extensions on the same host as BMC AR System Server - Cloud Portal and Database - Primary. Hard disk space: - Installation directory: 521 MB
- Temp (tmp) directory: 1933 MB
Product-specific requirements: None |
Cloud Portal AR Extensions – Secondary |
Click here to see the hardware, software, and product-specific requirements.
Hardware and software requirements: Install the Cloud Portal AR Extensions – Secondary on the same host as BMC AR System Server - Cloud Portal and Database – Secondary. Hard disk space: - Installation directory: 521 MB
- Temp (tmp) directory: 1933 MB
Product-specific requirements: None |
Database requirements for Windows
The following sections outline the database requirements for Windows platforms.
This section outlines the requirements that are common to Microsoft SQL Server and Oracle.
The BMC Cloud Lifecycle Management solution supports the following databases:
Microsoft SQL Server 2008 R2 Enterprise 64-bit (if you require Cluster capabilities) on Microsoft Windows 2008 R2 64-bit OS.
Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.
- Oracle Database 11g R2 64-bit on Red Hat Enterprise Linux 5.5 64-bit OS
Unicode and character set requirements for databases
The following Unicode and character set requirements apply to both MS SQL Server and Oracle databases:
- You must synchronize all your databases so that their character sets and Unicode settings are correctly aligned with their <product>, for example, BMC Remedy AR System settings.
- You must run Unicode to Unicode or non-Unicode to non-Unicode. Do not mix these settings.
- For Oracle, you must set the character sets to AL32UTF8.
- For MS SQL Server, you must set the Unicode data types to nchar, nvarchar, and ntext.
SQL Server requirements for Windows
For SQL Server databases, you can have the installer create a database during the installation process or you can precreate a database for your products, as indicated in the table in product-specific database requirements. However, the installer requires you to authenticate a precreated database. The BMC Cloud Lifecycle Management solution supports Microsoft SQL Server 2008 R2 Enterprise 64-bit (if you require Cluster capabilities) on Microsoft Windows 2008 R2 64-bit OS. Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.
WarningNote
You must have DBA credentials to create the database and users for the precreated database and installer-created database option.
Precreate database support and requirements for Windows
In the table in product-specific database requirements, the values for the precreated database support for SQL Server are as follows:
- Yes, but optional — A precreated database is supported. However, you can optionally choose to have the installer create the database during the installation process.
- Yes, and mandatory — You must use a precreated database.
- No — A precreated database is not supported. You must allow the installer to create a database and a user.
WarningNote
The BMC Cloud Lifecycle Management Installer creates an SQL Server database with the default data and log file sizes listed in the table in the following section, and users for products that require them. If you want to use the precreated database option, ensure that you use the file size details listed in the table.
For more information about precreated databases, see the documentation for the respective product in the documentation for related products.
The following table lists the requirements for SQL Server databases. For specific preparatory tasks that you must perform before you complete product installation, see the Additional information column.
