System requirements for App Visibility Manager server components

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

Ensure that the App Visibility portal, collector, and proxy environment includes the following requirements.

Supported operating systems for App Visibility server components

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 R2 Standard Edition (64-bit)  
  • Microsoft Windows 2012 R2 Datacenter Edition (64-bit)
  • Microsoft Windows 2012 Standard Edition (64-bit)  
  • Microsoft Windows 2012 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.6
    • 7.4
    • 7.3
    • 7.2
    • 6.9
    • 6.8
  • SUSE Linux Enterprise Server (64-bit versions):
    • 12.3
    • 12.1

Database requirements for the App Visibility portal and collector

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.

Hardware sizing for App Visibility server components

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.

If all App Visibility server components are installed together, such as for a very small environment or a test environment, approximately 2.1 GB of disk space is required and 10 GB RAM.


Database size calculations assume a retention period of 35 days.

App Visibility collector resources for different deployment sizes

BMC recommends that all nodes in TrueSight App Visibility Manager Proxy cluster have approximately the same disk size.


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>

To install the App Visibility collector software and database, the computer must have approximately 2 GB of free disk space and a minimum of 4 GB RAM (8 GB recommended).

The App Visibility collector database must be scaled for the number of App Visibility agents in your environment. To calculate the maximum database size, use the following equation:

10 GB x number of agents = maximum database size

The default maximum database size is 100 GB, which is enough for 10 App Visibility agents in an average environment. For information about changing the App Visibility collector database settings, see Managing the App Visibility database .

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

To install the App Visibility portal software and database, the computer must have approximately 2 GB of free disk space and a minimum of 4 GB RAM (8 GB recommended).

Disk space requirements are the same, even if many App Visibility collectors are used.

App Visibility proxy resources for different deployment sizes

Size of deployment

Number of requests

Number of nodes

CPUs required

Memory required

Disk size

Small

up to 10 per second

1*

4 CPUs, 2 GHz each

6 GB RAM

50 GB

Medium up to 500 per second 2 4 CPUs, 2 GHz each 8 GB RAM 100 GB
Large up to 2000 per second 3 4 CPUs, 2 GHz each 16 GB RAM 200 GB

*For high availability, more than one proxy node is required.

To install the App Visibility proxy software, the computer must have approximately 220 MB of free disk space and a minimum of 6 GB RAM (8 GB recommended).

 

App Visibility 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.

Hardware sizing for App Visibility deployments with Synthetic Monitor

Database size calculations assume a retention period of 35 days.

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


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 for more details.

**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.

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
  • Average: 30 KB per second
  • Minimum: 25 KB per second
  • Maximum: 55 KB per second
App Visibility collector
  • Average: 41 KB per second
  • Minimum: 25 KB per second
  • Maximum: 65 KB per second

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

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

Changing App Visibility collector settings

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
8304 HTTPS App Visibility beacon receiver End-user browser
8305 HTTPS App Visibility beacon receiver End-user browser

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.


 

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


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 10.12.6 (Sierra) 3

(tick)

(tick)

Mac OS X 10.11.6 (El Capitan) 3

(tick)

(tick)
iOS 10       (tick)2
iOS 9       (tick)2

Microsoft Windows 10

(tick) (tick) (tick)

Microsoft Windows 8

(tick) (tick) (tick)

Microsoft Windows 7

(tick) (tick) (tick)

Red Hat Enterprise Linux 6.9, or later

(tick)

Android Nougat     (tick)  
Android Marshmallow     (tick)  
Android Lollipop     (tick)  

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 .

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

Comments