After you set up the App Server Agent and the Network Agent together, the Network Agent automatically:
Monitors TCP connections
Identifies the application flow that uses each connection
Maps the connection to the flow
However in some cases, there is not enough context to associate a connection with a specific application flow resulting in an unmapped connection. In this case, you need to map the connection manually. If a connection remains unmapped, the Network Agent collects metrics for that connection but cannot associate these metrics with any monitored application flow.
To resolve an unmapped connection:
Go to the Network Dashboard and select Mapping Wizard (under Connections on the right). You can also open this wizard directly from a Tier Dashboard, if that tier has any unmapped connections.
The Connection Mapping Wizard appears. The left pane shows all tiers with unmapped connections. When you select a tier, the Connections list (right pane) shows all the unmapped connections for that tier. The workflow is to iterate through each tier, and specify the mapping for each connection for that tier. For each unmapped connection:
Determine the application flow that uses the unmapped connection.
You need to know the source tier, destination tier, and the call type (ENTRY/EXIT) for the application flow. If you do not know this information, contact someone else who knows the application well.
Select a tier in the left pane.
In the right pane, group the IP addresses by Destination VIP or Prefix (bit mask).
Right-click a connection and select Map Connection(s).
Specify the Call Type, Source Tier, and Destination Tier for the application flow that uses that connection.
