EV Reach - IT Process Automation Tutorial - Monitoring an Application on a Server

Last modified on 2023/07/12 14:35


   These tutorial is for demonstration purposes. Please test all Scope Actions before deploying them into production.


Ping is great but Ping does not tell you when your server is not doing what is supposed to be doing. You must monitor the applications that run on the server as well. In this tutorial, you will learn to use EV Reach's Process Automation framework to create a workflow that will monitor an application on the server and report back when a component is not functioning properly.

Monitoring a Windows application running on a server comes down to a few key areas.

  • Monitoring a running process
  • Monitoring a service state
  • Verifying communication between different component servers (ie: can the Exchange Hub Transport Server communicate with the Client Access Server or internet DNS servers)

With a EV Reach Scope Action, we can create an action module for each of these areas.


  • We will use the example of monitoring an Exchange Server Setup. For the purposes of this, we will simplify the topology a bit.
    Add or remove components as needed. Also, this method can apply to any application server or line of business application on Windows.
  • We will need two scope actions. One for each server being monitored. We need this because each server will have different processes and services to monitor.
    If you have several servers that have the same criteria, feel free to add them to the same scope action.
  • The number of action modules will depend on the how you wish to monitor the objects. For example, if you add all the processes or services to the same action module, EV Reach will alert you if any one of them is no longer running. If you create an action module for each process or service then you can be notified of the specific process or service that has failed.
  • For this tutorial, we will go with the latter. Each Process and Service will have its own action module. This method will provide the most granularity for monitoring your server.


  • This feature requires EV Reach v8.01.08 or higher.

  • You will need access to the full version of EV Reach and its Process Automation framework. If you don’t currently own a valid license, you can download a free version of our remote access software on our website. The 15-day trial is free and no credit card is required.

Best Practice



In this topology, we would like to monitor some processes, services and internet access.


Step by Step Tutorial

Step 1: Defining the Scope Module

1. Create one module with a list of servers that will have the same monitoring criteria.

For example, all of the Exchange mailbox servers or all of the SQL servers.

Step 2: Defining the Action Module

The Action module should look like the following for our example.

  • Remember you can replace any of these modules for specific criteria you wish to monitor.
  • All the action modules follow the same format.


1. Add the email action.

  • This can be found under Add \ Remove --> Execute Computer Action --> Logged in User --> Send Email.

Caution: The email action does not require any user to be logged in to the server or anywhere.

  • Here is how the arguments should be set for the email action.



2. Define the condition of the action module. This is where we define what we wish to monitor.

  • You can enter a condition in the section labeled "Only if the following is true."


  • In this example, we choose Add \ Remove --> Set Computer Condition --> Processes --> Name.
    • We set the condition to NOT=. This means, if the process does not exists, proceed with the action, in this case Send Email.
    • The desired value is the Process name we are monitoring.

3. The service action modules are nearly identical except there are two conditions.


  • The first condition is Add \ Remove --> Set Computer Condition --> Services --> Software Services --> Name. Set the condition to = and the desired value is the service name. This is the actual service name, not the "friendly" name.
  • The second condition is Add \ Remove --> Set Computer Condition --> Services --> Software Services --> State Set the condition to NOT= and the desired value is Started.

Step 3: Testing Connectivity for the Client Access Server

The final action module will be for the Client Access Server.

In this scenario, we want to make sure that the server can ping some outside resource. In this case, it will be an internet DNS server. We can utilize the WMI class Win32_PingStatus. I love this method because we can see connectivity between two remote machines.

See the tutorial Monitoring and Reporting on Connectivity Between Remote Systems on how to create the Win32_PingStatus report action module.

Step 4: Grouping the monitoring Scope Action into a single Master Scope Action

Using the technique in the following KBA, you can take all of your monitoring Scope Actions and group them into a single master scope action.

See the tutorial Running Multiple Workflows Within One Scope Action to schedule the master scope action for simple, easy to administer monitoring solution.

Powered by XWiki © EasyVista 2024