System requirements for App Visibility agents for Java and .NET
This topic provides the hardware and software system requirements for TrueSight App Visibility Manager agents for Java and .NET.
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.
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. The following operating systems have been individually tested and certified in the BMC lab, yet the App Visibility agent for Java is supported on other operating systems where supported application servers and Java version are installed.
The App Visibility agent for Java is supported only on 64-bit operating systems.
Tested operating systems for the App Visibility agent for Java
Red Hat Enterprise Linux
|CentOS, Oracle Linux|
Oracle Solaris on SPARC
Oracle Solaris on SPARC
The App Visibility agent for Java is supported on the following application servers.
IBM WebSphere Application Server (Full Profile) 8.5.x
Oracle WebLogic Server 12c
JBoss EAP 6
|WildFly 8 (formerly JBoss AS)||Oracle 1.8|
Apache Tomcat 7.x
Apache Tomcat 8.x
Technologies monitored by the App Visibility agent for Java
The App Visibility agent for Java monitors the following application technologies and displays .
|Component and module frameworks|
|HTTP server APIs|
|Web page template standards and Model-View-Controller (MVC) server-side frameworks|
|HTTP client APIs|
|REST HTTP Web Services frameworks, server side|
|SOAP HTTP Web Services frameworks, server side|
|Message-oriented standards and middlewares|
|Java Message Service (JMS) API version 1.1 (part of J2EE 1.4) except the topics API|
|Relational Database Management Systems (RDBMSs) and related frameworks|
Java Database Connectivity (JDBC) API except batch processing API
Supports all JDBC drivers although special support is needed for parameterized queries, supported for the following:
Java Transaction API (JTA) since version 1.0.1 (part of J2EE 1.4)
Java Persistence API (JPA), Object-Relational (ORM) specification, supported since version 2.0 (part of Java EE 6) for the following:
|Non-relational databases (also known as NoSQL)|
|MongoDB Java Driver 2.x|
|In-Memory Data Grids|
|Oracle Coherence (from Tangosol acquisition)|
|IBM CICS Gateway JCA (Java Enterprise Connector Architecture) Adapter|
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.
|Windows server||IIS||4.6.2||4.6.1||4.6.0||4.5.2||3.5 SP1|
|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 .
The standard synchronous ASP.NET pipeline is supported.
|IIS 7 integrated pipeline and IIS classic pipeline|
Used for synchronous implementation of the service
BMC supports and tests BasicHttpBinding, WS2007HttpBinding (SOAP Web Services), WebHttpBinding (REST), and NetTcpBinding (binary, SOAP-like), with the following WCF support limitations:
|ASP.NET Web Services (.asmx)|
|Pre-WCF SOAP web services, extension of standard ASP.NET and handled as a special case|
|.NET Framework Remoting|
|Synchronous, all protocols supported|
|ASP.NET MVC (indirect support)|
Technologies like ASP.NET MVC are supported indirectly as they are built over one of the underlying technologies (no rules specifically for ASP.NET MVC).
ASP.NET MVC synchronous over classical ASP.NET pipeline is supported.
Microsoft SQL Server for the following data providers:
Asynchronous database calls are supported for Microsoft SQL Server Native Client.
Oracle Database for the following data providers:
Support for .NET Framework Data Provider for Oracle has been deprecated.
Oracle Data Provider for .NET, Managed Driver is not supported.
|MongoDB .NET Driver versions 1.9.0 – 1.11.0|
.NET Framework Task-based Asynchronous Pattern (TAP) support that includes:
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, you might see incorrect or partial data, or you might not see any data.
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.
- 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 to work only with HTTP.