System requirements
This topic lists the hardware and third-party software requirements for BMC Atrium Orchestrator Platform and Content.
You must allocate sufficient resources to a component that is running on a virtual machine (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
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.
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. | |
| Install basic calculator on the OS | The basic calculator is typically installed on your Linux system. If not, ensure that you install the basic calculator on the OS. |
Solaris | |
Install all default operating system libraries. |
Related topic
BSM environment recommendations
Comments
Log in or register to comment.