App Visibility server components provide the infrastructure to proactively analyze data received from monitored applications and end user's browsers. You can install the App Visibility server components with a graphical interface (wizard) or in silent (unattended) mode.
Typically, the App Visibility environment uses separate hosts for the server components, but for a very small environment or a proof-of-concept environment, you might install all the components on the same computer.
App Visibility server components
App Visibility portal
|The portal analyzes data from the end-user's browser and from agents that are installed on web application servers. The portal serves as a central access point to the App Visibility system.
Install the portal before the other server components because the collector and proxy reference the portal during installation. The App Visibility agents also reference the portal during installation.
The portal includes a small database for configuration and connection information. If you install a portal and a collector on the same computer, they share the same database.
|App Visibility collector
|The collector receives data about monitored applications and applications servers from App Visibility agents, and receives end-user experience data from App Visibility proxies.
You can install several collectors, depending on the volume of your transactions. Install each collector on a separate computer.
Each collector includes a database for App Visibility data. If you install a portal and a collector on the same computer, they share the same database.
|App Visibility proxy
Install each proxy on a separate computer in the network's demilitarized zone (DMZ).
The proxy uses SSL-encrypted beacons and injection requests and therefore requires a KeyStore with a certificate that is trusted by the end-users’ browsers. You can import the KeyStore during proxy installation or after installation.
After you install the App Visibility server, install the agents that provide data for your environment: