This topic provides the hardware and software system requirements for App Visibility components. 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. 

App Visibility server (portal, collector, and proxy) system requirements

Supported operating systems

Windows

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 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 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:

  • 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 Manager and Synthetic TEA Agent components for guidelines about estimating the equipment you need depending on the size of your environment.

App Visibility collector database 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 between the number of collectors: <diskSize> / <numberOfCollectors>

App Visibility collector database resources for different deployment sizes—with synthetic transactions

Size of deployment

Number of transactions per hour

CPUs required

Memory required

Database size

Small

15000

2 CPUs, 2 GHz each

8 GB RAM

20 GB

Medium

75000

2 CPUs, 2 GHz each

8 GB RAM

100 GB

Large*

150000

4 CPUs, 2 GHz each

16 GB RAM

200 GB

Extra Large*

360000

8 to 16 CPUs, 2 GHz each

32 GB RAM

500 GB

*For large and extra large deployments, increase the heap size on your collector to 6 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.

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

Changing App Visibility portal settings

8101HTTPSApp Visibility portal for supportabilityApp Visibility portal
8800HTTPSApp Visibility portal databaseApp Visibility portal

8200

HTTPS

App Visibility collector

App Visibility portal, App Visibility proxy, and agents

Changing App Visibility collector settings

8201HTTPSApp Visibility collector supportability portApp Visibility collector
8800HTTPSApp Visibility collector databaseApp Visibility collector
8300HTTPSApp Visibility proxyApp Visibility portal and collectorChanging App Visibility proxy settings
8301HTTPSApp Visibility proxy supportability portApp Visibility proxy
880HTTPSApp Visibility beacon receiverEnd-user browser
8444HTTPSApp Visibility beacon receiverEnd-user browser

 

collector database

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 the supported versions of Java.

 

 

Watch videos on YouTube

Supported application servers and Java versions

The App Visibility agent for Java is supported on the following application servers.

The BMC test environment includes Windows, Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Solaris, Ubuntu, and AIX operating systems, and the agent has been tested and certified on the listed application servers.

BMC supports App Visibility Agent for Java on only the following application servers and Java versions. 

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 10gR3

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

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 .

Start adding filters for your table either in the macro settings or on the filtration pane.

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

The table is being loaded. Please wait for a bit ...
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

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 serverIIS4.6.14.64.5.23.5 SP1
2012 R2 64 bit8.5yesyesyesyes
2012 64 bit8.0yesyesyesyes
2008 R2 64 bit7.5yesyesyesyes
2008 64 bit7.5yesyesyesyes

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.

Start adding filters for your table either in the macro settings or on the filtration pane.

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

The table is being loaded. Please wait for a bit ...
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.

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

Compatible web browsers and operating systems for the console

 

Browser →


Operating system ↓

Microsoft Internet Explorer 11

Mozilla Firefox 1

Google Chrome 1

Apple Safari 1

Mac OS X Mavericks (version 10.9)

 

yes

 

yes

iOS 7

   yes

iOS 8

   yes2
iOS 9   yes2

Microsoft Windows 7

yesyesyes

 

Microsoft Windows 8

yesyesyes

 

Red Hat Linux 6.6, or later

 

yes

 

 

Android 4.4 (KitKat)  yes 
Android 4.3 (Jelly Bean)  yes 

1 Use the latest version of the browser.

2 Safari on iOS 8.4 and Safari and Chrome on iOS 9.2.1 have issues with editing long text entries.

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

System requirements for Presentation Server

Sizing App Visibility Manager 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

Was this page helpful? Yes No Submitting... Thank you

6 Comments

  1. Dears , 

    Can i monitor Java Applets using App Visibility Java Agent. 

    1. Hi Mohamed,

      Thank you for commenting!

      Java Applets is not one of the technologies that is supported for monitoring.

      Regards,

      Sara

  2.  

    1.  

  3.  

    1.  

© Copyright 2013-2016 BMC Software, Inc.
© Copyright 2013-2016 BladeLogic, Inc.
Legal notices