System requirements
The following topics provide the requirements for installing the product:
Topic | Describes |
---|---|
Supported platforms by component | This topic provides the list of supported platforms for each BMC Server Automation component. |
Minimum hardware requirements | This topic describes hardware requirements for components of a BMC Server Automation system. |
Minimum software requirements | This topic describes software requirements for installing components of a BMC Server Automation system. |
RSCD agent licenses | In previous releases, RSCD agents required licenses. Since version 8.2, you no longer need to explicitly license agents. Instead BMC Server Automation users report agent usage. This topic describes how to use a BLCLI command, Utility:agentLicenseUsageReportByRelativeDateRange , to obtain current agent utilization. |
BMC Server Automation ports | This topic lists the ports that are required for a basic BMC Server Automation installation. Your firewall must allow communication through these ports for the associated components to function. |
User accounts | This topic lists the various user accounts created by BMC Server Automation during component installation. |
Patch vendor site access | If you are using the BMC Server Automation Patching functionality, then outbound internet access is required from either the Application Server(s) or the system running the offline patch downloader (or the HPUX Helper specifically for HPUX), depending on which method is being used. This topic lists the vendor sites to which you would need internet access, categorized by OS. |
Note
For the BMC Sever Automation Console (the RCP client), BMC recommends the following bit configuration:
- On Windows: 64-bit or 32-bit RCP clients, as appropriate
- On Linux or UNIX: 32-bit RCP clients (although 64-bit RCP clients are also supported)
Was this page helpful? Yes No
Submitting...
Thank you
Comments