7 minute readApplies to: v4

How to create an Enterprise Application

For Squared Up v4 we have defined a new type of SCOM object called an Enterprise Application (EA). Enterprise Applications are like regular SCOM Distributed Applications (DAs), but improved, to give you an easy way to model and monitor all of your applications from the point of view of users. Enterprise Application Monitoring (EAM) features are available with the Enterprise edition. For more information see What are Enterprise Applications?.

To create an Enterprise Application (EA) click the + button on the Getting Started dashboard, or from Applications > Enterprise Applications, or click the Create new application button from system > EAM.

First, give your application a name. You can then configure availability tests, map the components or monitor external dependencies. Even if you just use availability tests you can still build accurate application availability dashboards and SLAs. You can even create an EA that simply displays the manually set health status/availability of the application.

This training video below (30 mins) takes you through configuring Enterprise Application availability monitoring:

1. Availability - Configure availability tests

Only the availability monitors configured here roll up to be displayed as the health of the EA. These monitors test whether the application is actually available to the end user.

  1. Click the configure availability monitoring button.

  2. Change the enable monitoring toggle button from off to on.

    Availability Monitoring

  3. Select the type of availability monitoring you wish to configure:

    • Simple URL monitoring - create a simple URL monitor
    • Simple TCP monitoring - create a simple TCP monitor
    • Custom PowerShell - use a PowerShell script to test application availability
    • Existing monitoring - allows you to add any availability monitor or object that you already have in SCOM, for example Web application availability monitoring or Web application transaction monitoring.
  4. Complete the details required.

  5. Select a group of test clients (Watchers) from the test from drop down box (this is not required for existing monitoring because this will already have been configured in SCOM). This is where you want the tests to be run from, and should be physically close to the end users who will be using the application. This is simply a SCOM group where the name starts with EAM_, see How to create Availability Test Groups.

The outcome of the chosen availability test will roll up to the overall health of the Enterprise Application. If you consider editing the rollup see How to edit Enterprise Application rollups.

Remember you can also manually set the health state of an application.

For a deep dive on Application Availability Monitoring features take a look at the v4 webinar (40 mins) Advanced Application Availability Monitoring.

2. Map

The second stage is to dynamically map your application using Visual Application Discovery and Analysis (VADA) in Discover mode. This 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.

  1. Click the map components button to get started.

  2. Manually add your first server / component by typing in the box, and selecting it from the SCOM search drop down.

    Add Object To Map

  3. Discovery runs automatically on any server manually added to the map and / or on the server hosting any component manually added.

  4. Discovered components are shown. Greyed out processes have already been added to global filters. No discoveries are put onto the map yet.

  5. Select a process and click add to add all related discoveries to your map. Or click filter to add it to global filters.

  6. Upstream connections are closed by default, but you can expand these if you wish.

    Expand Connections

    To find out more about how to use VADA Discover mode see VADA

  7. 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).

  8. 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 VADA.

3. Dependencies

Add other items monitored in SCOM upon which this application depends, for example:

  • a server that runs a batch job

  • a domain controller or exchange server

  • another application, such as email, that your app depends upon.

The health of these dependencies will not roll up to the health of the Enterprise Application, but can be seen on the EA dashboard.

Saving and viewing the EA

  1. Click save and check the Management Pack ID.

  2. Click save. This may take a few minutes as the Enterprise Application (EA) is saved into SCOM.

  3. Click the view dashboard button at the top right of the page. After first saving an EA you will need to wait a few minutes for SCOM to update before the dashboards show anything meaningful.

    From here you can:

  4. To return to editing the Enterprise Application click the edit app button.

For more information about creating your own dashboards to show Enterprise Applications take a look at the v4 training video (24 mins) Building Enterprise Application Dashboards.

FAQs

How do I delete an EA?

In SCOM go to the Administration workspace, then Management Packs > Installed Management Packs and locate or search for your EA, and then right click on it and select Delete.

Who can create, edit and delete EAs?

Only SCOM admins can manage Enterprise Applications.

Can I edit Enterprise Applications in SCOM?

You can update your EAs in Squared Up at any time, or by editing the management pack XML and importing/re-importing. EAs are not editable in the SCOM Distributed Application (DA) Designer.

Troubleshooting Enterprise Applications

Availability for an EA is not correct after the SCOM availability test group is changed

See EA Availability doesn't update properly in SCOM if the watcher group is changed

A group renamed to EAM_ is not appearing in the test from drop down list

See Renaming an existing group

Application mapping or VADA issues

If you are having problems with application mapping see Troubleshooting VADA.

What are Enterprise Applications?

What is VADA?

How to use the VADA perspective

How to manually set the health state of an application

How to create Availability Test Groups

v4 training video - Availability Monitoring

v4 training video - Building Enterprise Application Dashboards

Advanced Application Availability Monitoring Webinar

Squared Up Ltd. (c) 2019Report an issue with this article