Application Monitoring and Control Overview
Application Monitoring and Control
The Application Monitoring and Control feature of Universal Controller allows you to use it as a network control and monitoring tool. You can use Application Monitoring and Control to start, stop, and query any application running on any machine where you have Universal Agent installed and running.
Application Monitoring and Control is comprised of three components:
- Application resource records allow you to define the name and location of your applications, along with the specific commands to control (Start, Stop, and Query) the applications. The Applications list displays a status for the application that is defined in each Application resource record.
Three Application Control tasks are automatically generated when you create an Application resource record: one each for executing the Start, Stop, and Query commands (which you specified in the Application resource record) against the application. You can use these control tasks to schedule the Start, Stop, and Query commands in Workflows and triggers. You also can manually create customized Application Control tasks.
Note
You can manually run an Application Control task to execute a command specified in an Application resource record, but it is simpler to just execute the command from the Applications list or Application resource record.
- Optional Application Monitor triggers allow you to launch other tasks based on the status of an application being monitored.
Processing Flow
The following steps show a sample process flow for the manual monitoring (that is, not via a trigger or Workflow) of an application:
Step 1 | From the Agents & Connections navigation pane, select System > Applications and create an Application resource record, specifying the name of an application and the start, stop, and query commands to control it. The Controller will automatically create three Application Control tasks that you can use in Workflows and triggers for starting, stopping, and querying the application. |
---|---|
Step 2 | Start the application defined in the Application resource record either by:
|
Step 3 | The Controller executes the Start Command provided by the user in the Application Details. It puts the application into Starting status, and saves the Start Time.
|
Step 4 | After 30 seconds, the Controller automatically executes the Query Command provided by the user in the Application Details to determine the status of the application. The Controller continues executing the Query Command every 120 seconds thereafter until the user stops the monitoring by issuing a Stop command from the Controller. |
Step 5 | The purpose of the Query is to determine whether or not the application is Active. The Controller uses the specifications provided by the user in the Query Exit Code Processing fields in Application Details to make this determination.
The Controller writes any Exit Code captured by the Query in the Query Exit Code field of the Application resource record. |
Step 6 | After starting the application, the Controller continues monitoring by sending out the Query Commands every 120 seconds.
|
Step 7 | To stop monitoring an application, issue the Stop command against it. the Controller stops the application and puts it into Inactive status, which means it is no longer monitoring. |