System requirements for App Visibility Manager
App Visibility server (portal, collector, and proxy) system requirements
Supported operating systems
You can install the App Visibility server components on computers running the following operating systems.
Windows
Microsoft Windows 2016
- Microsoft Windows 2016 Standard Edition (64-bit)
- Microsoft Windows 2016 Datacenter Edition (64-bit)
Microsoft Windows 2012
- Microsoft Windows 2012 Standard Edition (64-bit)
- Microsoft Windows 2012 Datacenter Edition (64-bit)
- Microsoft Windows 2012 R2 Standard Edition (64-bit)
- Microsoft Windows 2012 R2 Datacenter Edition (64-bit)
Microsoft Windows 2008
- Microsoft Windows 2008 R2 Standard Edition (64-bit)
- Microsoft Windows 2008 R2 Datacenter Edition (64-bit)
- Microsoft Windows 2008 R2 Enterprise Edition (64-bit)
Linux
- Red Hat Enterprise Linux (64-bit versions):
- 7.4 (Supported on TrueSight Operations Management version 11.0.00.002 and later)
- 7.3
- 7.2
- 7.1
- 7.0
- 6.8
- 6.7
- 6.6
- SUSE Linux Enterprise Server (64-bit versions):
- 12.1
- 12
Database requirements
During App Visibility portal installation, a local PostgreSQL database is automatically installed on the same computer as the App Visibility portal. Likewise, during App Visibility collector installation, a local PostgreSQL database is automatically installed on the same computer as the App Visibility collector.
For either component, you cannot connect to a different database.
App Visibility requirements for JavaScript injection
Use App Visibility JavaScript injection to implement App Visibility end-user monitoring. The 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 automatic injection by App Visibility:
- Chrome, latest version
- Firefox, latest version
- Internet Explorer, versions 10 and 11
- Safari (iOS 10.x), version 6.x
Ensure that you import a KeyStore file to the App Visibility proxy, or change the security protocolto 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-Manager-and-Synthetic-TEA-Agent-components for guidelines about estimating the equipment you need depending on the size of your environment.
Database size calculations assume a retention period of 35 days.
App Visibility collector resources for different deployment sizes
* Divide the required disk size between the number of collectors: <diskSize> / <numberOfCollectors>
App Visibility portal resources for different deployment sizes
App Visibility proxy resources
App Visibility server (portal and collector) system requirements for Synthetic Monitor
Ensure that you have sufficient resources for the optimum performance of the size of your deployment. See also Sizing-App-Visibility-Manager-and-Synthetic-TEA-Agent-components for guidelines about estimating the equipment you need depending on the size of your environment.
Database size calculations assume a retention period of 35 days.
App Visibility collector database resources for different deployment sizes for synthetic transactions
*For large deployments, increase the heap size on your collector to 4 GB. See Changing the heap size on App Visibility components for more details.
**If you are likely to exceed the number of transactions per hour, BMC recommends you add an additional collector to your deployment.
Calculations are for transactions using the URLChecker script, with 10 custom timers or page timers per transaction, and approximately 20% of transactions with 1 error each. For transactions that don't use timers and have fewer errors, database size requirements may be smaller.
Calculations assume approximately 10% of transactions generate events. Sustained peaks of event generation and fluctuating event levels can adversely affect performance.
App Visibility portal database resources for different deployment sizes for synthetic transactions
*For large deployments, increase the heap size on your portal to 4 GB. See Changing the heap size on App Visibility components for more details.
Calculations are for transactions using the URLChecker script, with 10 custom timers or page timers per transaction, and approximately 20% of transactions with 1 error each. For transactions that don't use timers and have fewer errors, database size requirements may be smaller.
Network bandwidth utilization for App Visibility portal and collector with Synthetic Monitor
In TrueSight App Visibility Manager, the bandwidth is often measured as the amount of data that is carried to and from the App Visibility portal and collector over a specified period of time.
The bandwidth test simulated 300 Synthetic TEA Agents executing 50 transactions every five minutes.
The following values show the network bandwidth utilization for all traffic sent and received by the component:
Component | Network bandwidth |
|---|---|
App Visibility portal |
|
App Visibility collector |
|
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
App Visibility agent for Java system requirements
Minimum space requirements for App Visibility agent for Java
- Installation disk space: 270 MB
- Recommended reserved space: 5MB per application server per day of log retention
This recommendation is based normal conditions and default log levels. The numbers can vary greatly under other conditions and should be monitored by your IT department.
Watch videos on YouTube
Supported application servers and Java versions
The Java environment includes a wide variety of application servers that are supported on a wide variety of operating systems. While BMC makes every effort to support the listed application servers and Java versions, the following operating systems have been individually tested and certified in the BMC lab.
The App Visibility agent for Java is supported only on 64-bit operating systems.
Tested operating systems for the App Visibility agent for Java
Operating System | Version |
|---|---|
Linux | |
Red Hat Enterprise Linux |
|
CentOS, Oracle Linux |
|
SUSE |
|
Ubuntu Server |
|
Windows | |
Windows |
|
AIX | |
AIX | 7.1 |
Oracle Solaris on SPARC | |
Oracle Solaris on SPARC | 11.3 |
The App Visibility agent for Java is supported on the following application servers.
Supported application servers for the App Visibility agent for Java
Application server | Java version |
|---|---|
IBM WebSphere Application Server (Full Profile) 7.0.x | IBM 1.6 |
IBM WebSphere Application Server (Full Profile) 8.0.x | IBM 1.6 |
IBM WebSphere Application Server (Full Profile) 8.5.x | IBM 1.7 IBM 1.8 |
Oracle WebLogic Server 10gR3 | Oracle 1.6 |
Oracle WebLogic Server 11g | Oracle 1.6 |
Oracle WebLogic Server 12c | Oracle 1.6 Oracle 1.7 Oracle 1.8 |
JBoss EAP 6 | Oracle 1.7 |
WildFly 8 (formerly JBoss AS) | Oracle 1.8 |
Apache Tomcat 7.x | Oracle 1.6 Oracle 1.7 |
Apache Tomcat 8.x | Oracle 1.7 Oracle 1.8 |
Technologies monitored by the App Visibility agent for Java
The App Visibility agent for Java monitors the following application technologies and displays diagnostics data for a trace.
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.2 | 4.6.1 | 4.6.0 | 4.5.2 | 3.5 SP1 |
2016 | 10.0 | ✅️ |
|
|
|
|
2012 R2, 64 bit | 8.5 | ✅️ | ✅️ | ✅️ | ✅️ | ✅️ |
2012, 64 bit | 8.0 | ✅️ | ✅️ | ✅️ | ✅️ | ✅️ |
2008 R2 SP1, 64 bit | 7.5 | ✅️ | ✅️ | ✅️ | ✅️ | ✅️ |
Technologies monitored by the App Visibility agent for .NET
The App Visibility agent for .NET monitors the following application technologies and displays diagnostics data for a trace.
The standard synchronous ASP.NET pipeline is supported.
Network Time Protocol (NTP) synchronization
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, System-requirements-for-Presentation-Server.
Compatible web browsers and operating systems for the console
1 Use the latest version of the browser.
2 Safari and Chrome on iOS 9.2.1 have issues with editing long text entries.
3 The Adobe Flash player is not enabled by default. Enable the Adobe Flash player to use options such as the Trace Details page of App Visibility Manager and for cross-launching to the Infrastructure Management server. For more information, see https://helpx.adobe.com/flash-player/kb/enabling-flash-player-safari.html.
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 .