This topic lists the hardware and third-party software requirements for the BMC Atrium Orchestrator product.
You must allocate sufficient resources to a component that is running in a VM. Ensure that BMC Atrium Orchestrator is the only product running on its host computer. System performance is affected by the total size of the modules being activated, not the number of modules in the environment.
The following table lists the system requirements for the BMC Atrium Orchestrator components.
System requirements
These recommendations are for production environments. Development grids may only require half the application memory documented above.
Component | Application memory 1 | Number of processors (quad core or better) | Runtime disk space requirements | Installation disk space requirements |
|---|---|---|---|---|
Access Manager | 2 GB | 1 | 1 GB | 100 MB |
Repository | 2 GB | 1 | 40 GB | 100 MB |
CDP | 8 GB 2 | 2 | 40 GB | 140 MB |
AP | 8 GB 2 | 2 | 40 GB | 140 MB |
LAP | 4 GB | 2 | 40 GB | 100 MB |
HA-CDP | 8 GB 2 | 2 | 40 GB | 140 MB |
BMC Atrium Orchestrator Development Studio | 2 GB | 2 | 20 GB | 300 MB |
BMC Atrium Orchestrator Operator Control Panel | 1 GB | 1 | 1 GB | 100 MB |
Graphing server | 1 GB | 1 | 1 GB | 100 MB |
1 Add the application memory noted to the operating system memory in accordance with the operating system vendor recommendations.
2 If your environment runs with high concurrent volumes and workflow complexities, increase the recommended application memory by a factor of 2x or 3x: from 8 GB to 16 GB or 24 GB; from 4 GB to 8 GB or 12 GB.
For optimal performance, BMC Software recommends that you use a 64-bit operating system. If your BMC Atrium Orchestrator configuration will run medium or large loads, you must use a 64-bit system.
Implementing these parameters in standard environments
To implement the parameters from the preceding table in a single-server demonstration/POC environment, you must provide:
- 6-8 GB for Access Manager, Repository, CDP, BMC Atrium Orchestrator Operator Control Panel, and graphing server
- 2 CPUs
- 10 GB of runtime disk space allocated to BMC Atrium Orchestrator
To implement the parameters from the preceding table in a two-server production environment, you must provide:
- Server 1: 4 GB, 1 CPU, 40 GB disk space allocated to Access Manager and the repository
- Server 2: 8 GB, 2 CPUs, 40 GB disk space allocated to a CDP and BMC Atrium Orchestrator Operator Control Panel
How log files affect disk space
During runtime, each component creates at least one log file set, the size of which depends on your configuration. The CDP, AP, and BMC Atrium Orchestrator Development Studio can also be configured to create a second log file set.
An individual log file can retain up to 4 MB of data. Upon reaching the maximum log size, the active log file is archived and a new active log is created. A standard log set might contain one active log and up to nine archive log files, each requiring 40 MB of disk space.
Third-party software requirements
The following table lists the libraries and Internet software required to run BMC Atrium Orchestrator and its components.
Third-party software requirements
Requirements | Notes |
|---|---|
Network software |
|
Supported operating systems have built-in TCP/IP network software.
| Network software requirements for BMC Atrium Orchestrator instances running on 64-bit OSs are the same as the requirements for those running on 32-bit versions. |
Internet browsers and plug-ins |
|
| Use only these products and versions to run BMC Atrium Orchestrator Operator Control Panel, Grid Manager, Repository Manager, and Access Manager. |
Operating system libraries |
|
Linux |
|
Install all default operating system libraries. |
|
Solaris |
|
Install all default operating system libraries. |
|
Related topic
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
15 Comments
Wallace Roets
I am unable to locate detailed information on platform and OS version:
eg:
Platform
Minimum Operating System version
32 or 64 bit x86 PC Compatible
Windows Server 2000, 2003, 2008 (32 and 64 bit)
The only thing I can find is generic statements like (ie: no platform / version):
You can use the GUI installation to install or upgrade the BMC Atrium Orchestrator components on Red Hat Linux, Sun Solaris, and Windows computers, and BMC Atrium Orchestrator Development Studio on Mac OS computers.
Where is this information located?
Jake Morgan
The information is located in the PAC documentation (requires a BMC Support login): http://www.bmc.com/support/reg/remedy-compatibility-tables.html?a=b
Jake Morgan
Jake Morgan
Matthew Highcove
Artur Tkaczyk
To install Development studio you have to have jre installed, but this is not mentioned any where
Gordon McKeown
Recent versions of AO (7.6.02 onwards) do not require the installation of a JRE – this is included in each of the installation packages.
Ranganath Samudrala
Based on my experience, here are my observations:
Gordon McKeown
I would agree with that; you can comfortably run a CDP with both AM and Repo on an 8GB machine for all but the most intensive workloads, so the CDP component on its own is fine on 4GB. For the LAP, I think 2GB might be a bit of a squeeze in some cases – especially if using a memory-intensive adapter. That said 2GB is fair as a minimum, with 4GB more of a recommended value.
With all that said, most workloads benefit from more memory even if just for disk caching, so I tend to aim for 8GB or 16GB on a combined AM/Repo/CDP.
Ranganath Samudrala
With Java, it is not advisable to allocate too much memory because of how its garbage collector works. It tends keep accumulating memory until it is really required and this can sometimes affect the performance.
Yes, with more workload one will need more memory but that should not be the default.
Gordon McKeown
Totally agree – I was thinking about leaving the excess memory to the OS for its own purposes rather than allocating it all to the JVM
Gordon McKeown
"For optimal performance, BMC Software recommends that you use a 64-bit operating system. If your BMC Atrium Orchestrator configuration will run medium or large loads, you must use a 64-bit system."
From platform version 7.7, you must use a 64-bit OS.
Ranganath Samudrala
I would not hesitate using 32bit for LAPs under some extreme cases. Otherwise it will be 64bit all the way through.
Ranganath Samudrala
PAC for BAO v7.6.02.04/05/06 needs to be updated. I think RH Linux v6.x is supported but it is not listed in the PAC.
Dorothy Poole