Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Configure protected application in Orion Failover Engine

Configure protected application in Orion Failover Engine

Table of contents
No headers


This Knowledge Base article describes the procedure for configuring protected applications and for configuring monitoring of protected applications.


More Information

Orion Failover Engine Application Protection and Monitoring

The Applications screen of the SolarWinds Orion Failover Manager consists of five tabs: Summary, Services, Tasks, Rules, and Plugins. Each of the tabs provides direct access to function indicated by the tab name.

  • Summary tab - The Summary tab indicates which server (primary or secondary) is active, the Application State, Application Health, Application Status, and shows the Application Log.
  • Services tab - The Services tab shows a listing of all services monitored by Orion Failover Engine and allows ordering of the services for starting and stopping. It also provides the ability to edit the actions to take should a service fail and allows services that are running or services that are set to automatic to be added to the monitored services.
  • Tasks tab - The Tasks tab shows a list of tasks to be performed by their classification (Network Configuration, Pre Start, Post Start, Pre Stop, Post Stop, Pre Shadow, Post Shadow, Periodic, and Rule Action). Only configured tasks are visible in the pane and the task list can be ordered. Rule Action tasks created in this screen become available as an action on the Services and Rules screens. This screen also provides the ability to add, edit, and remove tasks and to run an individual task on command. It also provides the ability to add account information should a task require other than the default credentials.
  • Rules tab - Orion Failover Engine uses Rules to set parameters for monitoring operations and services on the server and the protected applications. Rules are created only by plug-ins and cannot be manually created. The Rules tab allows the user to modify the parameters for the Rule and when the Rule is enabled, to configure up to three successive actions to take when the performance of the system or protected application falls outside the defined parameters.



How to Configure the Protected Applications and Monitoring

To configure protected applications, follow the steps below:

  1. Open the SolarWinds Orion Failover Manager by navigating to Start > All Programs > SolarWinds Orion > Orion Failover Engine > Manage Server.
  2. Select the server pair on the Server Pair Overview screen. Select the Applications tab, and then select each of the tabs as indicated below and configure the protected applications as indicated below.


To configure Applications:

  1. Select the Summary tab and select the desired application, and then click on Edit. The Stop Timeout and Start Timeout fields are available for editing the period of time to wait for the application to start or stop before Orion Failover Engine considers the action a failure of the application.
  2. When complete, click on OK.


To configure Tasks:

  1. Tasks should be created before configuring either Services or Rules. After creating a user-defined task, it then becomes available as an action in the list of both the Services and Rules. Only Network Configuration tasks can be run on either the primary or secondary server. All other tasks can only be run on the primary server. To create a task, select the Tasks tab and then click on the Add button.

    Note: The Tasks pane also provides the ability to order tasks. The procedure used to sequence tasks is the same for both tasks and services. See the Services section below to find out more about assigning a specific sequence for tasks.
  2. Assign a name to the task.
  3. Select the task type from the drop down menu.
  4. Type the path or browse to the location of the file or script to execute.
  5. Select the user account, which is authorized to run the task from the Run As drop down.

    Note: If an account other than the local/system is required to execute the task, the new account credentials can be added by clicking on the User Accounts button in the upper right of the screen.
  6. Click on OK.


To configure Services:

  1. Select the Services tab.
  2. Select a service associated with the protected application and click the Edit button.
  3. Click on each of the three available fields (On First Failure, On Second Failure, On Third Failure) and select the desired action to take upon failure of the service.
  4. Click on OK.
  5. Repeat for each service associated with the protected application.

    Note: Starting with Orion Failover Engine, the sequence in which services are started and stopped can be ordered as necessary to meet the needs of the user environment.

    CAUTION - Default ordering is established based upon application and service dependencies. When modifying service ordering, ensure that service dependencies are taken into account when establishing other than default ordering. Failure to properly order services may cause a protected application not to start or to fail.
  6. Use the Up and Down buttons to change the order of services as required.


To configure Rules:

  1. Use the Rules tab to enable/disable rules for performance monitoring of the system or protected application. Select the Rules tab.

    Note: Rules are only created by plug-ins and cannot be created by the user.
  2. Select the desired rule and then click the Edit button.
  3. The Edit Rule dialog allows the user to configure the parameters for monitoring the desired function. It also provides the ability to configure three successive actions to perform should the performance of the function fall outside of the defined parameters.
  4. Configure each of the fields as required to meet user requirements.

    Note: Default parameters are preconfigured by Orion Failover Engine but can be modified. SolarWinds recommends that SolarWinds Orion Failover Engine Diagnostics be used to assist in defining performance thresholds.

Applies To

All Versions

Last modified