Enterprise Applications - How to map an Enterprise Application using VADA
The article describes how to dynamically map your Enterprise Application (EA) using Visual Application Discovery and Analysis (VADA) in Discover mode.
An Enterprise Application (EA) can be made up of 3 elements:
- Availability test (see Enterprise Applications - How to configure an availability test)
- Dependencies (see Enterprise Applications - Dependencies)
To find out more about Enterprise Applications see How to create an Enterprise Application.
Discovery is powered by lightweight, point-in-time, on-demand discovery data using a 'Filter In' methodology, where you choose what you want to put on your map, everything else is excluded by default.
- Click the map components button to get started.
Manually add your first server / component by typing in the box, and selecting it from the SCOM search drop down.
- Discovery runs automatically on any server manually added to the map and / or on the server hosting any component manually added.
- Discovered components are shown. Greyed out processes have already been added to global filters. No discoveries are put onto the map yet.
- Select a process and click add to add all related discoveries to your map. Or click filter to add it to global filters.
Upstream connections are closed by default, but you can expand these if you wish.
To find out more about how to use VADA Discover mode see Visual Application Discovery & Analysis (VADA).
- Before you can save your application map you must ensure that each group (blue box) is named. (Save is disabled if there are any untitled groups).
- Click save at the top of the page.
The health of objects on the map will not roll up to the overall health of the Enterprise Application, but will be surfaced on the EA dashboard when clicking the view dashboard button.
If you are having problems with application mapping see Troubleshooting Visual Application Discovery and Analysis (VADA).