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
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.2
- 7.1
- 7.0
- 6.8
- 6.7
- 6.6
- SUSE Linux Enterprise Server (64-bit versions):
- 12.1
- 12
- 11 SP 4
- 11 SP 3
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 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.
Database size calculations assume a retention period of 35 days.
App Visibility collector resources for different deployment sizes
Size of deployment | Number of agents | CPUs required | Memory required | Database 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* |
* Divide the required disk size between the number of collectors: <diskSize> / <numberOfCollectors>
App Visibility portal resources for different deployment sizes
Size of deployment | Number of agents | CPUs required | Memory required | Database size |
|---|---|---|---|---|
Small | 20 | 2 CPUs, 2 GHz each | 8 GB RAM | 20 GB |
Medium | 100 | 2 CPUs, 2 GHz each | 8 GB RAM | 100 GB |
Large | 200 | 4 CPUs, 2 GHz each | 16 GB RAM | 200 GB |
App Visibility proxy resources
Size of deployment | Number of agents | CPUs required | Memory required | Disk size |
|---|---|---|---|---|
Any | Any | 2 CPUs, 2 GHz each | 8 GB RAM | 220 MB |
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 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* 120000 4 CPUs, 2 GHz each 16 GB RAM 200 GB *For large deployments, increase the heap size on your collector to 4 GB. See
Changing the heap size on App Visibility components
**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 Size of deployment CPUs required Memory required Database size Small 2 CPUs, 2 GHz each 8 GB RAM 2 GB Medium 2 CPUs, 2 GHz each 8 GB RAM 10 GB Large* 4 CPUs, 2 GHz each 16 GB RAM 20 GB *For large deployments, increase the heap size on your portal to 4 GB. See
Changing the heap size on App Visibility components
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.
for more details.
for more details.
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
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 |
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
Watch videos on YouTube
Watch the Installing App Visibility Agent for Java video playlist.
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 (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 JBoss EAP 7 Oracle 1.8 Apache Tomcat 7.x Oracle 1.6 Oracle 1.7 Apache Tomcat 8.x Oracle 1.7 Oracle 1.8
WildFly 8 (formerly JBoss AS) 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
.
| 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 |
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 |
|
|
|
|
|
| 2008 SP2, 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.
| 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. |
| Database support |
Microsoft SQL Server for the following data providers:
|
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 |
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.
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
Browser →
| Microsoft Internet Explorer 11 | Mozilla | Google | Apple |
|---|---|---|---|---|
Mac OS X 10.12 (Sierra) 3 |
|
|
|
|
Mac OS X 10.11 (El Capitan) 3 |
|
|
|
|
| iOS 10 | ||||
| iOS 9 | ||||
Microsoft Windows 10 |
|
|
|
|
Microsoft Windows 8 |
|
|
|
|
Microsoft Windows 7 |
|
|
|
|
Red Hat Enterprise Linux 6.7, or later |
|
|
|
|
| Android Nougat |
| |||
| Android Marshmallow |
| |||
| Android Lollipop |
|
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 .
Related topics
System requirements for Presentation Server
Sizing App Visibility Manager and Synthetic TEA Agent components
Preparing for the App Visibility server installation
Overview
Content Tools
Add-ons
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
13 Comments
Winsor Lim
Sara Kamen
Alexandre Boyer
Sara Kamen
Sara Kamen
Alexandre Boyer
Michael Ashall
Alexandre Boyer
Michael Ashall
Alexandre Boyer
Agar Merouane
Hello,
Need support of AVM 10.7 on Redhat 7.3
As it is for TSPS 10.7 TSIM 10.7 TSIS 10.7
Best regards,
Merouane AGAR
Sara Kamen
Hello,
While we don't expect any issues with Red Hat 7.3, it has not been tested and verified with App Visibility 10.7. Therefore, it is not officially supported with this version.
Red Hat 7.3 is officially supported with App Visibility 11.0.
Regards,
Sara
| Sara Kamen | Lead Information Developer | BMC Software |
Agar Merouane
Hello Saea,
The problem is that we have deployed (TSPS 10.7, TSIM 10.7, TSIS 10.7 and ASSO 9.02) in RHEL 7.3
App Visibility 11.0 is not compatible with (TSPS 10.7 and ASSO 9.02).
Regards,
Merouane AGAR