Sizing BMC Server Automation Application Servers in a VM environment
This topic was created by a BMC Contributor and has not been approved. More information.
The following sizing recommendations have been formulated from the experiences of customers who run BMC Server Automation Application Servers as VM guests in vSphere environments. While these recommendations have not been officially tested by BMC, they seem to work well in many customer environments.
- Each Guest VM should have 10-12 gigabytes of memory allocated and reserved per BSA deployment
- Each Guest VM should have 2vCpu reserved per BSA deployment.
- Each Guest VM should have 20-50 gigabytes of disk
- Each Guest VM should run a single, 6-8 gigabyte (MaxHeapSize) Application Server deployment or two 6-8 gigabyte deployments
- BMC Server Automation Application Server deployments should not be of type ALL or a combined JOB/CONFIG. Desirable types are JOB, CONFIG, NSH_PROXY, combined JOB/NSH_PROXY, and combined CONFIG/NSH_PROXY.
- The JVM on the Applications Servers should be x86_64
- The MaxWIT setting in the JOB deployments should be 100.
- The MaxJobExecutionConnections in the JOB deployments should be 200
- If more capacity is needed, there are two possibilities:
- Additional VMs can be added. They can be configured as either JOB or CONFIG Application Servers.
- An additional Application Server instance can be added for a total of two instances per guest, assuming the vCpu and memory are also increased.
- The file server should be on a dedicated system (not on any one Application Server) or (for UNIX) should be an NFS mount that is mounted on all Application Servers.
- Guest OS can be Windows or Linux