This topic provides the system requirements for BMC Application Diagnostics components.
BMC Application Diagnostics no longer supports SUSE Linux 10.4 because of an upgrade to MySQL 5.6.14. For information about MySQL support, see Supported Platforms: MySQL Database .
During BMC Application Diagnostics Server installation, you install a MySQL database locally on the same computer as the BMC Application Diagnostics Portal and Collector host. You cannot connect to a remote database.
Ensure that you have sufficient resources for the optimum performance of the size of your deployment.
BMC Application Diagnostics Server resources for different deployment sizes
Size of deployment | Number of Agents | CPUs required | Memory required | Disk size |
---|---|---|---|---|
Small | 20 | 2 CPUs, 2 GHz each | 8 GB RAM | 100 GB |
Medium | 100 | 2 CPUs, 2 GHz each | 8 GB RAM | 260 GB |
Large | 200 | 4 CPUs, 2 GHz each | 16 GB RAM | 550 GB |
Extra Large | 500 | 8 to 16 CPUs, 2 GHz each | 32 GB RAM | 2100 GB* |
* Divide the required disk size between the number of collectors: <diskSize> / <numberOfCollectors>
The following table lists the default port numbers used by the BMC Application Diagnostics Server components. The listed port numbers are the default values that you can change during installation, or change in the properties files after installation (requires restart of the service). Ensure that you can access the ports.
Default port numbers for Server communication
Port | Protocol | Server component | From | Reference |
---|---|---|---|---|
8100 (8143) | http (https) | Application Diagnostics Portal | Application Diagnostics Agent, Collector, BMC Application Performance Management Console | |
8200 (8243) | http (https) | Application Diagnostics Collector | Application Diagnostics Agent, Portal |
The following application servers have been tested and certified in BMC's test environment. Only those application servers with Java 1.6 or later are supported.
Supported application servers for BMC Application Diagnostics Agent for Java
Application server | JAVA version |
---|---|
Oracle WebLogic Server 9/9.2 | Sun 1.5 |
Oracle WebLogic Server 9/9.2 | Oracle JRockit 1.5 |
Oracle WebLogic Server 10 | Sun 1.5 |
Oracle WebLogic Server 10 | Oracle JRockit 1.5 |
Oracle WebLogic Server 10.3/11 | Sun 1.6 |
Oracle WebLogic Server 10.3/11 | Oracle JRockit 1.6 |
Oracle WebLogic Server 12 | Sun 1.6 |
Oracle WebLogic Server 12 | Oracle JRockit 1.6 |
Oracle WebLogic Server 12 | Sun 1.7 |
IBM WebSphere Application Server 6.1 | IBM 1.5 |
IBM WebSphere Application Server 7 | IBM 1.6 |
IBM WebSphere Application Server 8 | IBM 1.6 |
JBoss Application Server 5.x | Sun 1.5 |
JBoss Application Server 6 | Sun 1.6 |
JBoss Application Server 7 | Sun 1.6 |
Apache Tomcat 6.x | Sun 1.5 |
Apache Tomcat 7.x | Sun 1.6 |
Apache Tomcat 7.x | Sun 1.7 |
Oracle GlassFish Server 2.2.x | Sun 1.5 |
Oracle GlassFish Server 3.x | Sun 1.6 |
Jetty web server 6.x and above | Sun 1.6 |
You can access the user interface through the BMC Application Performance Management Console with the following combinations of operating systems and web browsers. For hardware and software requirements for the console environment, see Preinstallation analysis for the BMC Application Performance Management Console.
Compatible web browsers and operating systems for the Console Microsoft Internet Explorer 9 Microsoft Internet Explorer 8 Mozilla Firefox1 Google Chrome1 Apple Safari1 Mac OS X Microsoft Windows 7 Microsoft Windows XP Linux Ubuntu 10.04 LTS
Operating system ↓
To correctly load current data for BMC Application Diagnostics in Microsoft Internet Explorer 8, use the following browser configuration, based on the default settings:
7 Comments
Paolo Romagnoli
Hi, I think it would be extremely useful to have a table stating all the communication requirements among APM components: APM Console, AD Portal, AD Collector, AD agents, APM Console, Real EUEM Analyzer/Collector.
The table should look like this:
http
This will be highly appreciated from SC, PS, partners and customers.
Thansk
Paolo
Sara Kamen
Thanks, Paolo! I will talk it over with the development team and get a list of default ports.
--Sara
Sara Kamen
Hi Paolo,
We added a table for "Default Server communication ports." Hope this helps!
Regards,
Sara
Ranganath Samudrala
What port is used by AD Portal to push policy/configuration data to Agents - 50000 or 8143?
Paolo Romagnoli
I think that 50000 is just for agent troubleshooting purposes, so I think that agents retrieve policy through AD Portal (8100 or 8143)
Ranganath Samudrala
Ok - thanks.
Should there be an entry for Portal -> APM Console communication - port 443?
Sara Kamen
Just to clarify, the Agent initiates the connection to the Portal (through 8100 or 8143) with every heartbeat, and then receives the configuration version from the Portal. If the Portal configuration data is newer than what the Agent has, the Agent initiates another connection to retrieve the updated configuration.
The Portal does not initiate communication with the APM Console.
Hope this helps.