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.

Note

The latest version for the App Visibility Java and .NET agents is 11.3.01 and is compatible with TrueSight App Visibility Server version 11.3.02 and later.

TEA Agent system requirements

Sizing App Visibility Manager and Synthetic TEA Agent components

App Visibility agent for Java system requirements

Support for third-party products

To receive full support for a BMC product, you must have such product installed in a supported environment, as specified in the BMC product documentation. If a third-party vendor cancels support for one of its products (such as an operating system or subsystem), and that third-party product integrates or interacts with the BMC product you have licensed, you must upgrade to a supported version of that third-party product before BMC Customer Support can provide you with support for the affected BMC product. For further information, see BMC's product support policy.

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

Watch the App Visibility agent for Java installation videos.

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

Operating System	Version
Linux
Red Hat Enterprise Linux	7.x 6.x 5.x
CentOS, Oracle Linux	7.x 6.x 5.x
SUSE	12.x 11.x
Ubuntu Server	16 14
Windows
Windows	2016 2012 R2 2012 2008 R2
AIX
AIX	7.x
Oracle Solaris on SPARC
Oracle Solaris on SPARC	11.x

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) 8.5.x	IBM 1.7 IBM 1.8
Oracle WebLogic Server 12c	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.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 .

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Component and module frameworks
OSGi, module system for Java Apache Tuscany
HTTP server APIs
HTTP Java Servlets since version 2.4 (part of J2EE 1.4), except asynchronous APIs in version 3.0 (part of Java EE 6) and later Automatic JavaScript injection is not supported in filters
Web page template standards and Model-View-Controller (MVC) server-side frameworks
Java Server Pages (JSP) since version 2.0 (part of J2EE 1.4) Java Server Faces (JSF) since version 1.1 (part of J2EE 1.4) Struts 1.x (legacy, reached end of live) Spring Web MVC since version 2.x Tuckey UrlRewrite filter since version 3.0
HTTP client APIs
Java JDK's URLConnection Apache HTTP Components Jakarta Commons HTTP Client 3.x (legacy, reached end of live) Apache HTTP Components HttpClient 4.x, except asynchronous API JAX-RS (Java API for XML, Restful Services) 1.x restful client API (part of Java EE 6), supported implementations: Jersey 1.x JAX-RS (Java API for XML, Restful Services) 2.x restful client API (part of Java EE 7), supported implementations: Jersey 2.x, except asynchronous API
REST HTTP Web Services frameworks, server side
JAX-RS (Java API for XML, Restful Services) 1.x restful client API (part of Java EE 6), supported implementations: Jersey 1.x JAX-RS (Java API for XML, Restful Services) 2.x restful client API (part of Java EE 7), supported implementations: Jersey 2.x, except asynchronous API
SOAP HTTP Web Services frameworks, server side
Apache Web Services–Axis JAX-WS (Java API for XML, Web Services) standard since version 2.0 (part of Java EE 5), supported implementations: JAX-WS Reference Implementation
Distributed applications
Java RMI Enterprise JavaBeans since version 2.1 (part of J2EE 1.4) CORBA (Common Object Request Broker Architecture)
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: Microsoft JDBC driver for SQL Server IBM DB2 IBM Informix IBM WebSphere Application Server drivers Oracle Database Oracle WebLogic Server drivers MySQL Teradata Apache Derby SAP Sybase ASE (now SAP Adaptive Server Enterprise) JNetDirect JSQLConnect ASG Mobius Enterprise Content Management (ECM) driver for MS SQL Server Vignette Web Content Management (now OpenText) drivers DDTek drivers
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: APIs: EntityManager, Query, EntityTransaction implementations: RedHat Hibernate ORM
Non-relational databases (also known as NoSQL)
MongoDB Java Driver 2.x
In-Memory Data Grids
Oracle Coherence (from Tangosol acquisition)
Mainframe interfaces
IBM CICS Gateway JCA (Java Enterprise Connector Architecture) Adapter
Asynchronous technology
Java Executors Java ExecutorService

App Visibility agent for .NET system requirements

Support for third-party products

To receive full support for a BMC product, you must have such product installed in a supported environment, as specified in the BMC product documentation. If a third-party vendor cancels support for one of its products (such as an operating system or subsystem), and that third-party product integrates or interacts with the BMC product you have licensed, you must upgrade to a supported version of that third-party product before BMC Customer Support can provide you with support for the affected BMC product. For further information, see BMC's product support policy.

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.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

IIS 7 integrated pipeline and IIS classic pipeline
WCF Invoke
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: No cross-server transaction tracing support for non-HTTP bindings (like NetTcpBinding) No cross-server transaction tracing support for Standalone WCF services No cross-server transaction tracing support for NetNamedPipeBinding WSDualHttpBinding without any HTTP-related information and without cross-server transaction tracing support
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.
Database support
Microsoft SQL Server for the following data providers: .NET Framework Data Provider for SQL Server .NET Framework Data Provider for ODBC .NET Framework Data Provider for OLE DB Asynchronous database calls are supported for Microsoft SQL Server Native Client.
Oracle Database for the following data providers: .NET Framework Data Provider for Oracle Oracle Data Provider for .NET, Unmanaged Driver .NET Framework Data Provider for ODBC .NET Framework Data Provider for OLE DB 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
Asynchronous technology
.NET Framework Task-based Asynchronous Pattern (TAP) support that includes: Support for execution of Task code (Delegate or Lambda) Partial support for Execution of code, if not using Synchronization context. No exception details from the execution Async entry points only supported with Web API Async exit points only supported with the MS SQL server native client

Network Time Protocol (NTP) synchronization

Warning

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.

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
HARMAN

Ensure that you import a KeyStore file to the App Visibility proxy, or change the security protocol to work only with HTTP.