System requirements
Note
For software requirements and compatibility information for this release of BMC Atrium Orchestrator, see BMC Solution and Product Availability and Compatibility Utility (SPAC requires a Support login). Log in using your support ID, search for BMC Atrium Orchestrator Platform and choose the current release to display compatibility information.
The following table lists the system requirements for the BMC Atrium Orchestrator components.
Component | Application memory (Java Heap)1 | Number of processors (quad core or better) | Runtime disk space requirements | Installation disk space requirements |
|---|---|---|---|---|
Repository | 2 GB | 1 | 40 GB | 100 MB |
CDP | 8 GB2 | 2 | 40 GB | 140 MB |
AP | 8 GB2 | 2 | 40 GB | 140 MB |
LAP | 4 GB | 2 | 40 GB | 100 MB |
HA-CDP | 8 GB2 | 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 |
| Dashboards | 4 GB | 2 | 40 GB | 100 MB |
1 Add the application memory noted to the operating system memory in accordance with the operating system vendor recommendations.
Note
Application memory is different than the physical RAM required for the server. Application memory is the amount of memory BMC Atrium Orchestrator applications can use out of the total available physical memory on the server.
2.a If your environment runs with high concurrent volumes and workflow complexities, increase the recommended application memory by a factor of 2x or 3x: from 8GB to 16GB or 24GB; from 4GB to 8GB or 12GB.
2.b As the total size of the activated modules in your environment increases, you may need to increase the application memory by 2x: from 8GB to 16GB.
Note
These recommendations are for production environments. Development grids may only require half the application memory documented above.
BMC Atrium Single Sign-On: To view the system requirements for BMC Atrium Single Sign-On see,
System requirements
.
Note
For optimal performance, BMC Software recommends that you use a 64-bit operating system. You can configure an LAP to run on 32-bit operating system, but the allocated memory is limited to 1.5GB.
Implementing system 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 the repository, CDP, and BMC Atrium Orchestrator Operator Control Panel
- 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: 2 GB, 1 CPU, 40 GB disk space allocated to 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.
Test
Comments
Log in or register to comment.