This integration makes it possible to navigate from NAM Server reports to the associated PurePath data in the AppMon Client and also use the AppMon User Experience Management (UEM) as the data feed for NAM Server. To make this work, configure the NAM Probe for the NAM Server (and, optionally, for the ADS) to monitor the same HTTP traffic that is generated by business applications being monitored by AppMon agents.
Integration of NAM with AppMon, both DATM and UEM, requires AppMon version 6.5 or 2017.
To begin the integration configuration procedure, make sure you have the following:
Access to RUM Console.
Java Virtual Machine installed on the machine on which you intend to launch AppMon Client.
Adobe Flash Player installed on the machine on which you intend to launch AppMon Client.
The AppMon working mode set to continuous .
Optionally : The AppMon Client installed on the same computer where you intend to display the NAM Server reports. If you do not have the Client installed, it will be launched via Java Web Start. Note that you may encounter problems performing drill downs to the client if you assign several AppMon Servers of various releases to the NAM Server.
Added certificates (via the AppMon Certificate Management) for all the NAM Probes that you plan to integrate with AppMon.
To complete AppMon integration with NAM, perform the following steps:
Add AppMon Server in the RUM Console and configure its connection with NAM Server. For more information, see Connecting AppMon and NAM.
Configure AppMon to provide performance data for NAM. For more information, see Configuring AppMon to Receive Performance Data from NAM.
Verify the integration. For more information, see Verifying Integration of AppMon with NAM.
Note that the integration of AppMon with NAM has the following limitations:
Even though the BUC rule definition is based on UEM data from different System Profiles or AppMon servers, the NAM Server drilldown leads to a AppMon report with data limited to one of the AppMon servers and one of the system profiles.
The integration is intended for the front-end Web tier only. Support for subsequent application delivery chain tiers (such as SOAP/XML) is not available.
SOAP front-end monitoring can only work if NAM analysis is performed with the HTTP analyzer.
The NAM reporting hierarchy dimensions, other than Software Service, Server, Operation, Client IP and User name, cannot be used to filter PurePaths on drill down.
Application, Transaction, Tier, Site, and related dimensions have no peer in AppMon.
AppMon continuous mode is supported, while manual (start-stop) is not supported.
Terminal Services should not be used to access AppMon.
The drilldown from the NAM browser can drive only one AppMon Client on a Windows machine.