On this page: Related pages:
On this page:
What is the Cross Application Flow Map?
While business applications often represent completely separate application environments, it's possible that different business applications share certain services or infrastructure components like databases.
The cross application flow map lets you see shared points in your application environment. This allows you to organize business applications by the services, infrastructure, and software components in your environment in the way that best fits your needs, while still being able to see business application interdependencies.
Using the Cross Application Flow Map
A user with View Business Flow account-level permission in the Controller UI can see the cross application flow by clicking View All Applications link on the Controller UI Home page. The page appears as follows:
In the context of a given business application, the call to another application is considered an exit call. If the other application is an AppDynamics-instrumented business application, the call is shown as cross application flow. For an example, see the All Applications Flow Map on Flow Maps. All users of one application can see correlated applications on the flow map. However, to drill into metrics and snapshots for a correlated application, a user must be a member of a role with view permissions to the correlated application. See Roles and Permissions.
Hiding Components or Business Application on the Flow Map
You can hide backend components, applications, or queues in the right-clicking menu for the component on the cross application flow map.
For applications monitored with the Java Agent, you can exclude a node from being resolved to a cross application flow by setting the following app agent node property to false:
You may choose to do this, for example, if you wanted the cross application call to be represented as a backend call in the calling applications flow map (and metric scheme), rather than as a call to another application. This ensures that metric data reflecting interactions with the tier in the external business application are retained as backend call metrics.