×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.
BMC Cloud Lifecycle Management 4.1 ... Planning System requirements

System requirements for Windows

This topic summarizes the system requirements for the installer planner 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, hardware, and permissions

Operating systemHardwarePermissions
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit
  • Oracle JRE 1.7 (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:

  1. Open Administrative tools > Local Policies > User Rights Assignments.
  2. Add the user to the Allow log on locally property.
  3. Remove the user from the Deny log on locally property, if present.

Back to top

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

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 by 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 numbers in the table are the default values 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.

Note

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.
ComponentPort numberDescription
BMC Cloud Lifecycle Management  Install Planner12333, 9998

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 applies to all product hosts.

BMC Remedy AR System server (AR System server) and IT Management Suite0 (default value if the portmapper is being used)

Cloud Portal and Database server, AR System server postinstallation , 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 postinstallation  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.

 
 1433 (default value)

Cloud Portal and Database server database port

When the BMC Cloud Lifecycle Management installer installs Cloud Portal and Database, 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 Automation1433 (default value)

BMC Server Automation database port

When the BMC Cloud Lifecycle Management installer installs BMC Server Automation installation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. 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.

 
 4750

BMC Server Automation RSCD agent port

This requirement applies to 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 Automation1433 (default value)

BMC Network Automation database port

When the BMC Cloud Lifecycle Management installer installs the BMC Network Automation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. 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)1433 (default value)When the BMC Cloud Lifecycle Management installer installs PXE, 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. 

Back to top

Preparing 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 check for existing installer

Check if there is an existing installer from a previous installation on the host. If there is, back up and delete the previous C:\Program Files\BMC Software\Planner installation folder. Also, back up and delete the C:\Windows\ProductRegistry.xml file.

To turn off the firewall

Turn off the Windows Firewall on the installer host:

  1. On Windows 2012, go to Start > Control Panel.
  2. Under System and Security, click Check Firewall Status. 
  3. Click Turn Windows Firewall on or off. 
  4. Start the Windows Firewall service, if necessary.
  5. For all three network locations, select Turn off Windows Firewall (not recommended). 
  6. Click OK. 
    For more information about stopping or disabling the firewall service, see the I Need to Disable Windows Firewall topic in the Microsoft TechNet Library. 

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.

Back to top

To remove existing NSH and RSCD

For new installations, the BMC Cloud Lifecycle Management installer installs version 8.6.01 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.

  1. Select Start > Programs > Windows Control Panel and open the Add/Remove Programs utility.
  2. Select the component that you want to uninstall (for example, BMC Server Automation RSCD Agent) and click Change/Remove
  3. After the RSCD Agent is uninstalled, go to C:\Program Files\BMC Software\Bladelogic and delete the RSCD folder.
  4. Manually delete the C:\Windows\rsc folder.

  5. Restart your computer.

    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.

  1.  Select Start > Programs > BMC Software > BladeLogic Server Automation Suite > Uninstall Network Shell.
  2. After the NSH is uninstalled, go to C:\Program Files\BMC Software and delete the NSH folder.
  3. Manually delete the C:\Windows\rsc folder.
  4. Restart your computer.
    For more information, see Uninstalling in the BMC Server Automation 8.3.00 documentation.

Back to top

To verify product host connectivity

Perform the following steps to ensure that you can successfully launch the installation on a product host:

  1. 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>.
  2. 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.

To update Terminal Services configuration options

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.

Note

If you do not configure these items before you run the installer, an installer panel appears listing the steps required to handle these issues.

  1. From the Windows Start menu, click Run.
  2. Type gpedit.msc, and then click OK.
  3. 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
  4. Set the Properties of Do not delete temp folder upon exit to Enabled and then click OK.
  5. Set the Properties of Do not use temporary folders per session to Enabled and then click OK.
  6. If the settings do not take affect, complete the following steps:
    1. From the Windows Start menu, click Run.
    2. Type regedit, and then click OK.
    3. Expand HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server.
    4. Update PerSessionTempDir to 0 and DeleteTempDirsOnExit to 0.

Back to top

To access target VMs from the installer computer

Before you launch the installer, ensure that you can access target VMs from the installer computer.

Note

If FTP is not enabled, use the following procedure.

  1. On the installer computer, click Run.
  2. 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:

  1. On the target computer, open the Computer Properties dialog box.
  2. Click Advanced system settings.
  3. Click the Computer Name tab.
  4. Click Change to change the workgroup and domain settings.
  5. Select Workgroup.
  6. Enter WORKGROUP and then click OK.
  7. In the Windows Security dialog box, enter the administrator user name and password to remove the computer from the domain, and then click OK.
  8. At the change prompt, click OK.
    After you successfully change the settings, do not restart the computer.
  9. In the System Properties dialog box, click Change.
  10. Select Domain.
  11. Enter the domain.
  12. At the welcome prompt, click OK.
  13. At the change prompt, click OK.Click Close to close the Computer Properties dialog box.
  14. Restart the computer.
  15. 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.

Back to top

To set the minimum JVM heap size

For optimal performance, set the minimum JVM heap size to 1024 MB. Otherwise, the install planner might hang.

To set screen resolution

Set your computer screen to the recommended resolution of 1280 x 800 or greater.

Back to top

(optional) To install FTP 7.5 on Windows Server 2008

Installing FTP 7.5 on the target host is required only if the trust relationship between the install planner and the target host is not working.

To check the trust relationship between the installer and the target host, execute the following command in the Run window to access the target file system. 
\\<targetHost>\C$ 

Note

If you cannot mount a network shared drive, then you must install FTP 7.5 on the target host, not the installer host.

For more information, see Installing FTP 7.5 on Windows Server 2008 in the Microsoft TechNet Library.

Back to top

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. For more information about product-specific hardware requirements per deployment type, see deployment architecture and sizing guidelines.

Note

For new 4.5 installations of Windows products, BMC requires:

  • Microsoft Windows Server 2012 R2 Standard Edition or Microsoft Windows Server 2012 Standard Edition 64-bit as the operating system.
  • Microsoft SQL Server 2012 64-bit SP1 or SP2, or Microsoft SQL Server 2014 Enterprise Edition 64-bit as the database.

However, BMC still supports Microsoft Windows 2008 R2 Enterprise Edition SP1 and Microsoft SQL Server 2008 R2 Enterprise 64-bit if you are upgrading to version 4.5.

Requirements for installing all Windows product hosts

  1. Define a local Windows administrator to perform all installations. 
    The user must be:

    1. The local Administrator of the system (not a domain user)

    2. Added to the Administrators group on the system.

  2. Grant appropriate rights to the user:

    1. Open Administrative tools > Local Security Policy > Local Policies > User Rights Assignments.

    2. Add the user to the Allow log on locally property.
    3. Remove the user from the Deny log on locally property, if present.

  3. Standardize the user and system environment variables on the target product hosts so that they are set with the same value (for example, TMP=C:\AppData and TEMP=C:\AppData). 

  4. Ensure that the values of the user and system variables match on both installer and product hosts.

  5. Set the same system time on the installer host and all the product hosts, for example, Pacific Standard Time. 

  6. Delete any files from the C:\Windows\Temp folder. This will speed up the process of installing the RSCD agent. 

  7. Verify the product host connectivity to ensure that you can successfully launch the installation on a product host:

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

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

    3. Record the IP addresses of all the target hosts. You might need these later during installation, for example, if you need to use an IP address in the installer because the host name does not work. 
  8. Ensure that the BMC Server Automation Remote Server Call Daemon (RSCD) Agent is not installed on any target host. 
    For new installations, the BMC Cloud Lifecycle Management installer installs version 8.6.01 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.

    1. To uninstall the RSCD Agent, select Start > Programs > Windows Control Panel and open the Add/Remove Programs utility.
    2. Select the component that you want to uninstall (for example, BMC Server Automation RSCD Agent) and click Change/Remove
    3. After the RSCD Agent is uninstalled, go to C:\Program Files\BMC Software\Bladelogic and delete the RSCD folder.
    4. Manually delete the C:\Windows\rsc folder.

    5. Restart your computer.

      Tip

      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 components on Windows in the BMC Server Automation documentation.

    6.  To uninstall NSH, select Start > Programs > BMC Software > BladeLogic Server Automation Suite > Uninstall Network Shell.
    7. After the NSH is uninstalled, go to C:\Program Files\BMC Software and delete the NSH folder.
    8. Manually delete the C:\Windows\rsc folder.

    9. Restart your computer.
      For more information, see Uninstalling components on Windows in the BMC Server Automation documentation.

  9. Turn off the Windows Firewall on all product hosts:
    1. On Windows 2012, go to Start > Control Panel.
    2. Under System and Security, click Check Firewall Status. 
    3. Click Turn Windows Firewall on or off. 
    4. Start the Windows Firewall service, if necessary.
    5. For all three network locations, select Turn off Windows Firewall (not recommended). 
    6. Click OK. 
      For more information about stopping or disabling the firewall service, see the I Need to Disable Windows Firewall topic in the Microsoft TechNet Library. 
  10. To install the products successfully on all product hosts, you must have administrator privileges for actions, such as setting system environment variables and restarting services. Therefore, having only administrator privileges is not enough. You must set the User Account Control (UAC) to disable the Administrator Approval Mode, as follows:
    1. Open Administrative tools > Local Security Policy > Local Policies > Security Options.
    2. From the list of security options displayed, double-click the User Account Control: Run all administrators in Admin Approval Mode option and set it to Disabled.

  11. Install Microsoft Internet Explorer or Mozilla Firefox on any host on which you want to access the mid tier. In addition, install a browser on the installer host so that you can access the online help.
    For more information about the version of web browsers to install, see http://www.bmc.com/support.

  12. Configure the terminal services.

    1. From the Windows Start menu, click Run.
    2. Type gpedit.msc, and then click OK.
    3. 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
    4. Set the Properties of Do not delete temp folder upon exit to Enabled and then click OK.
    5. Set the Properties of Do not use temporary folders per session to Enabled and then click OK.
    6. If the settings do not take affect, complete the following steps:
      1. From the Windows Start menu, click Run.
      2. Type regedit, and then click OK.
      3. Expand HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server.
      4. Update PerSessionTempDir to 0 and DeleteTempDirsOnExit to 0.
     

  13. Restart the computer.
  14. (Optional) Install SAP BusinessObjects XI R 3.1 SP2 for reporting purposes.

Back to top

BMC Remedy product requirements

The following section lists the product-specific requirements for the BMC Remedy products.

BMC AR System Server – Cloud Portal and Database – Primary

Note

The two-way trust relationship between the database host (if you are using a remote database) and the AR System server host must be working in both directions. To check the trust relationship between the database host and the AR System server host (and vice versa), execute the following command in the Run window to access the file system. 
\\<targetHost>\C$  

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 10526 MB 
    • Temp (tmp) directory: 9064 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit or Microsoft Windows Server 2012 Standard Edition 64-bit
  • Oracle JRE 1.7 (64-bit)
  • Microsoft SQL Server 2012 SP1 or SP2 64-bit, or Microsoft SQL Server 2014 Enterprise Edition 64-bit 

Product-specific requirements:

  • For remote database installations, configure credentials for the startup account of the Microsoft SQL Server service as follows:
    1. On your remote database computer, go to Administrative Tools > Services.
    2. Select SQL Server (MSSQLServer) service and right-click to open the pop-up menu.
    3. Select Properties and select the Log on tab.

    4. Provide administrator credentials in the This account field.

      Ensure that the Administrator user that you provide in this step is added to the Administrators group of the target Enterprise AR System server.

    5. Save the changes and restart the service.

Back to top

BMC Remedy Mid Tier

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 360 MB 
    • Temp (tmp) directory: 2609 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit
  • Oracle JRE 1.7 (64-bit)

Product-specific requirements: None

Back to top

BMC AR System Server – Cloud Portal and Database – Secondary

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 10526 MB 
    • Temp (tmp) directory: 9064 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit
  • Oracle JRE 1.7 (64-bit)
  • Microsoft SQL Server 2012 SP1 or SP2 64-bit, or Microsoft SQL Server 2014 Enterprise Edition 64-bit 

Product-specific requirements: None

Back to top

BMC Atrium Core Web Registry requirements

Hardware and software requirements:

  • 2 CPUs
  • 6 GB RAM
  • Hard disk space: 
    • Installation directory: 1345 MB 
    • Temp (tmp) directory: 5223 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit
  • Oracle JRE 1.7 (64-bit)

Product-specific requirements: None

Back to top

BMC Server Automation product requirements

The following section lists the product-specific requirements for the BMC Server Automation components.

BMC Server Automation – Application Server and Console

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 745 MB 
    • Temp (tmp) directory: 1626 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit
  • Microsoft SQL Server 2012 SP1 or SP2 64-bit, or Microsoft SQL Server 2014 Enterprise Edition 64-bit 

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.

Back to top

(Optional) PXE Server 

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 46 MB 
    • Temp (tmp) directory: 1626 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit

Product-specific requirements: For more information, see the IIS 6 Compatibility components not installed topic in the Microsoft TechNet Library.

Back to top

(Optional) BMC Server Automation – Advanced Repeater

Hardware and software requirements:

  • 2 CPUs
  • 1 GB RAM
  • Hard disk space: 
    • Installation directory: 265 MB 
    • Temp (tmp) directory: 391 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit

Product-specific requirements: None

Back to top

BMC Server Automation – Multiple Application Server (MAS)

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 9 GB 
    • Temp (tmp) directory: 3 GB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit
  • Microsoft SQL Server 2012 SP1 or SP2 64-bit, or Microsoft SQL Server 2014 Enterprise Edition 64-bit 

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.

Back to top

(Optional) BMC Server Automation – File Server

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory:  100 GB 
    • Temp (tmp) directory:  1 GB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit

Note

Storage on the File Server requires additional hard disk space.

Product-specific requirements: None 

Back to top

BMC Server Automation – Remote System Call Daemon (RSCD) Agent

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: Installation directory: 100 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit

Product-specific requirements: None

Back to top

BMC Atrium Orchestrator product requirements

The following section lists the product-specific requirements for the BMC Atrium Orchestrator components.

BMC Atrium Orchestrator – Configuration Distribution Peer

Hardware and software requirements:

  • 2 CPUs
  • 2 GB RAM
  • Hard disk space: 
    • Installation directory: 590 MB 
    • Temp (tmp) directory: 3598 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 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)

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 590 MB 
    • Temp (tmp) directory: 3598 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 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:

Back to top

BMC Network Automation product requirements

The following section lists the product-specific requirements for the BMC Network Automation components.

BMC Network Automation

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 1245 MB 
    • Temp (tmp) directory: 997 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit
  • Microsoft SQL Server 2012 SP1 or SP2 64-bit, or Microsoft SQL Server 2014 Enterprise Edition 64-bit 
  • 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 Setting up for installation on a Windows server in the BMC Network Automation documentation portal.

 

Note

On new Windows installations of BMC Network Automation where BMC now supports MS SQL Server 2014, the installation fails if you do not specify the highest value of the data file path or log file path available. Enter the highest version of the path, for example:

  • C:\Program Files Microsoft SQL Server\MSSQL12. MSSQLSERVER\MSSQL\DATA\bcan_data.mdf (as the data file path)
  • C:\Program Files Microsoft SQL Server\MSSQL12. MSSQLSERVER\MSSQL\DATA\bcan_log.ldf (as the log file path)


BMC Network Automation – Device Agent

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 2093 MB 
    • Temp (tmp) directory: 770 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit  or Microsoft Windows Server 2012 Standard Edition 64-bit

Product-specific requirements: Ensure that you have Microsoft Windows 8.3 file-name setting enabled before the installation. For more information, see Setting up for installation on a Windows server in the BMC Network Automation documentation portal.

Back to top

BMC Cloud Lifecycle Management requirements

The following table  lists the product-specific requirements for the BMC Cloud Lifecycle Management components.

Cloud Database Extensions

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

Cloud Platform Manager 

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 521 MB 
    • Temp (tmp) directory: 1933 MB
  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit or Microsoft Windows Server 2012 Standard Edition 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

Back to top

Cloud Portal AR Extensions – Primary 

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 

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

Back to top

SQL Server database requirements for Windows

The following sections outline the SQL Server database requirements for Windows platforms. 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. However, the installer requires you to authenticate a precreated database. 

Note

You must have DBA credentials to create the database and users for the precreated database and installer-created database option.

Database requirements overview

Not every product in the BMC Cloud Lifecycle Management solution requires a database. Certain products can share a database with other products in the solution. You can install the database on the same host as the BMC product, or you can install a remote database. Regardless of where you install the database, you can use the precreate database option if you meet the requirements listed in this topic.

This section explains the database requirements for the following products:

  • BMC AR System Server – Cloud Portal and Database
  • BMC Server Automation
  • BMC Network Automation

Supported SQL Server database version

On Microsoft Windows Server 2012 R2 Standard Edition 64-bit, the BMC Cloud Lifecycle Management solution supports:

  •  Microsoft SQL Server 2012  64-bit SP1 or SP2
  • Microsoft SQL Server 2014 Enterprise Edition 64-bit

Tip

Microsoft Support provides useful information on determining the version and edition of SQL Server and its components.

Back to top

Unicode and character set requirements for the SQL Server database

The following Unicode and character set requirements apply to the MS SQL Server database:

  • 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 MS SQL Server, you must set the Unicode data types to nchar, nvarchar, and ntext.

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.

Note

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.

Back to top

Windows database requirements for supporting 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.

Product

SQL Server requirements for Windows

Additional information

BMC AR System Server – Cloud Portal and Database

  • Data file: 6000 MB
  • Log file: 1024 MB
  • Precreated database support: Yes, but optional 

    Note: When you precreate the database, specify the database name as ARSystem.
  • Changing the database name for BMC AR System Server – Cloud Portal and Database is not supported.
  • The DBMS administrator and password are required to create the necessary database.
  • For information about which products in the solution can share a database, see Sizing Windows.
  • SQL Server clustering is supported for BMC AR System Server – Cloud Portal and Database if you use Microsoft SQL Server 2012 or 2014 Enterprise Edition 64-bit.
  • On Microsoft Windows, install the required MS SQL Server drivers.

BMC Server Automation

  • Data file: 80 MB
  • Log file: 10 MB
  • precreated database support: Yes, but optional
  • The DBMS administrator and password are required to create the necessary database.
  • For more information on how to precreate a database, see setting up an SQL Server database for BMC Server Automation.
  • For information about which products, both SQL Server and Oracle, in the solution can share a database, see Sizing Windows.
  • SQL Server clustering is supported for BMC Server Automation if you use Microsoft SQL Server 2012 or 2014 Enterprise Edition 64-bit.

BMC Network Automation

  • Data file: 500 MB
  • Log file: 50 MB
  • pre-created database support: Yes, and optional
  • The DBMS administrator and password are required to create the necessary database. The installer prompts you for inputs to create the database user and tablespace during the BMC Network Automation installation. However, you can also optionally pre-create user and tablespace information.
  • For more information about creating database and user, see Setting up BMC Network Automation on Windows.
  • For information about which products in the solution can share a database, see Sizing Windows.

Back to top

Where to go from here

End-to-end installation flow


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Last modified by John Stamps on Mar 28, 2017
ol ports network_traffic_flow network_traffic network_ports

Comments

Log in or register to comment.

Database requirements
System requirements for Linux
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.