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
| Component | Description | Installation notes |
|---|---|---|
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 | (Optional) The App Visibility proxy receives and processes end-user experience data so that you can see end-to-end transaction time and availability, and browser page performance and availability on your web application. The end user’s browser retrieves JavaScript from the proxy. The proxy, in turn, receives beacons from the browser and sends end-user metrics to the App Visibility collectors. | 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. |
To install the App Visibility server
- Prepare the environment for the App Visibility server installation.
- Install the App Visibility server components using one of the following methods:
- Change the App Visibility default database password.
- Verify the App Visibility server component installations.
After you install the App Visibility server, install the agents that provide data for your environment:
- Installing an App Visibility agent for Java
- Installing an App Visibility agent for .NET
- Installing a BMC Synthetic Transaction Execution Adapter Agent
Related topics
BMC TrueSight Operations Management overview
BMC TrueSight Operations Management basic deployment
App Visibility installation process overview
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks