App Visibility monitors and identifies performance and availability issues in Java and .NET enterprise web applications. You can monitor server metrics, latency times, and errors from the end user's browser through the completion of a transaction. App Visibility can also use synthetic executions to predict application health and user experience.
This topic provides an overview of the App Visibility installation components and sequence, and links to relevant installations sections.
The App Visibility environment requires the following installation components:
App Visibility installation components
|BMC TrueSight Presentation Server||The Presentation Server is the hub of the operations management environment; it receives and analyzes data that is displayed in the TrueSight Console.|
Install the Presentation Server first.
|App Visibility server|
The App Visibility server comprises the following components: portal, collector, and proxy. The server receives and analyzes data from the end user's browser and from agents that are installed on web application servers.
Typically, the App Visibility environment uses separate hosts for the portal, one or more collectors, and one or more proxies.
The portal and the collector installations include a database: a small one for configuration and connection information on the portal; a large one for the App Visibility data on the collector.
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.
Install the proxies (optional) in the network's demilitarized zone (DMZ).
After you install the App Visibility server components, configure the connection between the systems in the Component Management page of the TrueSight console.
|Installing the App Visibility server components|
|App Visibility agents for monitoring Java and .NET application servers||The App Visibility agents for Java and agents for .NET monitor the performance and availability of applications running on application servers. Agents also monitor metrics of the server, such as CPU and memory use.|
Install an agent on each application server of the application that you want to monitor.
The agent installation references the portal.
Borland Silk Performer Synthetic Transaction Monitoring for BMC
BMC Synthetic Transaction Execution Adapter (TEA) Agent
The TEA Agent monitors the performance and reliability of worldwide applications through synthetic (also called robotic) transactions.
An application specialist uses Silk Performer to record or author .ltz scripts that simulate user transactions. The scripting utility also serves as an execution module to run scripts on the computer with the TEA Agent.
Install Silk Performer before you install the TEA Agent.
Install the TEA Agent and enter connection details for the App Visibility server.
For installation instructions for Silk Performer, see the PDF file on the product's Documentation page on the