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.
Microsoft Windows 2012
Microsoft Windows 2008
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.
Use App Visibility JavaScript injection to implement
App Visibility end-user monitoring
. The JavaScript injection is supported by most web-based applications and browsers:
<head>
element and must be produced dynamically: JavaServer Pages (JSP) or Java servlets for Java application servers, ASP.NET applications for .NET application servers.The following end-user browsers support automatic injection by App Visibility:
Ensure that you import a KeyStore file to the App Visibility proxy, or change the security protocol to work only with HTTP.
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.
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 for supportability | 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 |
collector database
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 |
The App Visibility agent for Java monitors the following application technologies and displays
diagnostics data for a trace
.
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 |
|
Distributed applications |
|
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) |
Mainframe interfaces |
IBM CICS Gateway JCA (Java Enterprise Connector Architecture) Adapter |
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 | ![]() | ![]() | ![]() | ![]() |
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.
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:
|
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. |
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.
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
Browser →
| Microsoft Internet Explorer 11 | Mozilla Firefox 1 | Google Chrome 1 | Apple Safari 1 |
---|---|---|---|---|
Mac OS X Mavericks (version 10.9) |
|
| ![]() | |
iOS 7 | ![]() | |||
iOS 8 | ![]() | |||
iOS 9 | ![]() | |||
Microsoft Windows 7 | ![]() | ![]() | ![]() |
|
Microsoft Windows 8 | ![]() | ![]() | ![]() |
|
Red Hat Linux 6.6, or later |
|
|
| |
Android 4.4 (KitKat) | ![]() | |||
Android 4.3 (Jelly Bean) | ![]() |
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.
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 .
System requirements for Presentation Server
Sizing App Visibility Manager and Synthetic TEA Agent components
Preparing for the App Visibility server installation
8 Comments
Mohamed Eraky
Dears ,
Can i monitor Java Applets using App Visibility Java Agent.
Sara Kamen
Hi Mohamed,
Thank you for commenting!
Java Applets is not one of the technologies that is supported for monitoring.
Regards,
Sara
Pam Dickerman
Pam Dickerman
Winsor Lim
Sara Kamen
Nikhil Shetty
Is App Visibility Java Agent version 10.5 compatible with App visibility manager version 11 and above?
Winsor Lim
Hi Nikhil,
Yes, the App Visibility Agent for Java 10.5 is compatible up to App Visibility Manager 11.0.00. The App Visibility Agent for Java or App Visibility Agent for .NET can be up to -2 version less than the App Visibility Manager version.
Thanks,
Winsor