This topic provides the hardware and software system requirements for App Visibility components. See also Sizing App Visibility and Synthetic TEA Agent components for guidelines about estimating the equipment you need depending on the size of your environment.
App Visibility server (portal, collector, and proxy) system requirements
Supported operating systems
Windows
Microsoft Windows 2012 Microsoft Windows 2008
Linux
- Red Hat Enterprise Linux versions (64-bit versions):
- 6.4
- 6.5
- 6.6
- 6.7
- 7.0
- 7.1
- 7.2
- SUSE Linux Enterprise Server (64-bit versions):
- 11 SP 2
- 11 SP 3
- 12
Database requirements
During App Visibility portal and collector installations, a local PostgreSQL database is automatically installed on the same computer as the App Visibility portal and collector host. You cannot connect to a remote database.
App Visibility requirements for JavaScript injection
The App Visibility JavaScript injection is supported by most web-based applications and browsers:
- HTML pages must contain the
<head>element and must be produced dynamically: JavaServer Pages (JSP) or Java servlets for Java application servers, ASP.NET applications for .NET application servers. - For end-user browsers that support navigation-timing API, App Visibility provides end-to-end time and network time. For browsers that do not support navigation-timing API, App Visibility provides only end-to-end time.
- When cookies are enabled on the server and client, App Visibility returns statistics about the number of users.
The following end-user browsers support the web beacon that is injected by App Visibility:
- Internet Explorer, versions 10 and 11
- Firefox, latest version
- Chrome, latest version
- Safari (iOS 10.x), version 6.x
Ensure that you import a KeyStore file to the App Visibility proxy, or change the security protocol to work only with HTTP.
Required resources
Ensure that you have sufficient resources for the optimum performance of the size of your deployment. See also Sizing App Visibility and Synthetic TEA Agent components for guidelines about estimating the equipment you need depending on the size of your environment.
App Visibility server resources for different deployment sizes—without synthetic transactions
Size of deployment | Number of agents | CPUs required | Memory required | Disk size |
|---|---|---|---|---|
Small | 20 | 2 CPUs, 2 GHz each | 8 GB RAM | 200 GB |
Medium | 100 | 2 CPUs, 2 GHz each | 8 GB RAM | 1000 GB |
Large | 200 | 4 CPUs, 2 GHz each | 16 GB RAM | 2000 GB |
Extra Large | 500 | 8 to 16 CPUs, 2 GHz each | 32 GB RAM | 5000 GB* |
* Divide the required disk size by the number of collectors: <diskSize> / <numberOfCollectors>
App Visibility server resources for different deployment sizes—with synthetic transactions
Size of deployment | Number of transactions per hour | CPUs required | Memory required | Database size |
|---|---|---|---|---|
Small | 12000 | 2 CPUs, 2 GHz each | 8 GB RAM | 20 GB |
Medium | 60000 | 2 CPUs, 2 GHz each | 8 GB RAM | 100 GB |
Large | 120000 | 4 CPUs, 2 GHz each | 16 GB RAM | 200 GB |
Extra Large | 300000 | 8 to 16 CPUs, 2 GHz each | 32 GB RAM | 500 GB |
Calculations are for transactions with ten custom timers or page timers per transaction. For transactions that don't use timers, database size requirements may be smaller.
Database size calculations assume a retention period of 35 days.
Default server communication ports
The following table lists the default port numbers used by the App Visibility 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 the App Visibility portal and collector ports can receive communication from the App Visibility agents. Specifically, ensure that your firewall enables this communication.
Default port numbers for server communication
Port | Protocol | Server component | From | Reference |
|---|---|---|---|---|
8100 | HTTPS | App Visibility portal | App Visibility collector, App Visibility proxy, agents, and the TrueSight Presentation Server | |
| 8101 | HTTPS | App Visibility portal KM integration and supportability port | App Visibility portal | |
| 8800 | HTTPS | App Visibility portal database | App Visibility portal | |
8200 | HTTPS | App Visibility collector | App Visibility portal, App Visibility proxy, and agents | |
| 8201 | HTTPS | App Visibility collector supportability port | App Visibility collector | |
| 8800 | HTTPS | App Visibility collector database | App Visibility collector | |
| 8300 | HTTPS | App Visibility proxy | App Visibility portal and collector | Changing App Visibility proxy settings |
| 8301 | HTTPS | App Visibility proxy supportability port | App Visibility proxy | |
| 880 | HTTPS | App Visibility beacon receiver | End-user browser | |
| 8444 | HTTPS | App Visibility beacon receiver | End-user browser |
App Visibility agent for Java system requirements
Minimum space requirements for App Visibility agent for Java
- Installation disk space: 10 MB
- Recommended reserved space: 30 MB per instance of the agent
Java requirements
- The computer on which you are installing the App Visibility agent for Java must have Java already installed for the App Visibility agent installation script to run correctly.
- Ensure that the JAVA_HOME environment variable is configured with Java 1.6 or later.
Supported application servers and Java versions
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 by BMC.
Supported application servers for App Visibility agent for Java
Application server | Java version |
|---|---|
IBM WebSphere Application Server 7.0.x | IBM 1.6 |
IBM WebSphere Application Server 8.0.x | IBM 1.6 |
IBM WebSphere Application Server 8.5.x | IBM 1.7 |
Oracle WebLogic Server 10.3/11 | Sun 1.6 |
Oracle WebLogic Server 11g | Sun 1.6 |
Oracle WebLogic Server 12c | Sun 1.6 |
Oracle WebLogic Server 12c | Sun 1.7 |
JBoss Application Server 6 | Sun 1.6 |
JBoss Application Server 7.x | Sun 1.6 |
JBoss Application Server 7.x | Sun 1.7 |
| WildFly 8 (formerly JBoss AS) | Sun 1.7 |
Apache Tomcat 7.x | Sun 1.6 |
Apache Tomcat 7.x | Sun 1.7 |
Apache Tomcat 8.x | Sun 1.7 |
App Visibility agent for .NET system requirements
Minimum space requirements for App Visibility agent for .NET
- Installation disk space: 180 MB
- Recommended reserved space: 120 MB
Supported systems for App Visibility agent for .NET
The computer on which you are installing the App Visibility agent for .NET must have IIS already installed for the App Visibility agent installation utility to run correctly.
The following application servers have been tested and certified in the BMC test environment.
| .NET Framework | |||||
|---|---|---|---|---|---|
| Windows server | IIS | 4.6.1 | 4.6 | 4.5.2 | 3.5 SP1 |
| 2012 R2 64 bit | 8.5 |  | | | |
| 2012 64 bit | 8.0 | | | | |
| 2008 R2 64 bit | 7.5 | | | | |
| 2008 64 bit | 7.5 | | | | |
Network Time Protocol (NTP) synchronization
The data handled by application monitoring components, including all server components and agents, is time sensitive. If the time between components is not synchronized, data might not be displayed in the TrueSight console. Consult your operating system documentation to synchronize each component's internal clock with an NTP server on your network or on the Internet. Ensure that the clocks are regularly synchronized.
TrueSight console browser compatibility
You access App Visibility Manager functionality through the TrueSight console, which is the consolidated user interface for performing activities with the Presentation Server. The TrueSight console is compatible with the following combinations of operating systems and web browsers. For hardware and software requirements for the Presentation Server environment, Presentation Server system requirements.
Compatible web browsers and operating systems for the console Microsoft Internet Explorer 11 Mozilla Firefox 1 Google Chrome 1 Apple Safari 1 Mac OS X Mavericks (version 10.9) iOS 7 iOS 8 Microsoft Windows 7 Microsoft Windows 8 Red Hat Linux 6.4, or later 1 Use the latest version of the browser.Browser →
Operating system ↓Microsoft Internet Explorer 10 iOS 9 Android 4.4 (KitKat) Android 4.3 (Jelly Bean)
Production Environment Considerations
App Visibility server components are deployed with a Jetty web server and built-in remote diagnostics components. The components are used for a secure login by BMC personnel for support purposes. To disable this feature, contact Customer Support .
Related topics
Sizing App Visibility and Synthetic TEA Agent components
Preparing for the App Visibility server installation
Preparing for installation of App Visibility agent for Java
Preparing for installation of App Visibility agent for .NET
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
3 Comments
Daniel Diaz
Sara Kamen
Winsor Lim
This web page did not list which operating systems are supported by the App Visibility agent for Java and App Visibility agent for .NET agents. It only states which operating systems are supported by the App Visibility Server (Portal, Collector, and Proxy).
Please list the supported operating systems for the agents.
Thanks,
Winsor