Configuring application controllers

Edit online

A PowerHA® SystemMirror® application controller is a cluster resource used to control an application that must be highly available. It contains application start and stop scripts.

About this task

When you configure an application controller the following occurs:

Associates a meaningful name with the application. For example, the application you are using with PowerHA SystemMirror is named dbinst1. You use this name to refer to the application controller when you define it as a resource. When you set up the resource group that contains this resource, you define an application controller as a resource.
Points the cluster event scripts to the scripts that they call to start and stop the application.
Allows you to configure application monitoring for that application. You can configure multiple application monitors for one application. For more information, see Steps for configuring multiple application monitors.

Review the vendor documentation for specific product information about starting and stopping a particular application.

Verify that the scripts exist on all nodes that participate as possible owners of the resource group where this application controller is defined.

To configure an application controller on any cluster node:

Procedure

From the command line, enter smit sysmirror
In SMIT, select Cluster Applications and Resources > Resources > Configure User Applications (Scripts and Monitors) > Application Controller Scripts > Add Application Controller Scripts, and press Enter.

Enter the field values as follows:

Table 1. Add Application Controller Scripts fields
Field name	Value
Application controller name	Enter an ASCII text string that identifies the application controller. You use this name to refer to the application controller when you add it to the resource group. The controller name can include alphanumeric characters and underscores. Use a maximum of 64 characters.
Start Script	Enter the full path name of the script followed by arguments that are called by the cluster event scripts to start the application. This field can have a maximum of 256 characters. Although, this script must have the same name and location on every node, the content and function of the script can be different. You can use the same script and runtime conditions to modify a node’s runtime behavior.
Stop Script	Enter the full path name of the script that is called by the cluster event scripts to stop the application. This field can have a maximum of 256 characters. This script must be in the same location on each cluster node that can start the application. Although, this script must have the same name and location on every node, the content and function of the script can be different. You can use the same script and runtime conditions to modify a node’s runtime behavior.
Resource Group Name	Specify the resource group to contain this resource. Use F4 to view a picklist. If you have not configured your resource groups yet, you can leave this field blank and add the resource to the group later.
Startup Mode	Specify how the application controller startup script is called. Select background, the default value, if you want the start script called as a background process and event processing continues even if the start script has not completed. Select foreground if you want the event to suspend processing until the start script exits. Note: This field is only available in PowerHA SystemMirror 7.1.1, or later.
Enable CPU usage statistics	Specify No to disable CPU monitoring. Specify Yes to enable CPU monitoring. The default value is No.
Process to monitor CPU usage	Specify the full path name of the application binary that you want to monitor. You can use this field to determine the associated process-id (PID) to monitor.
CPU usage monitor interval	Specify the time interval in minutes to wait after each CPU and Memory usage reading. Valid values are between 1 and 120 minutes inclusively.

Press Enter to add the application controller as a cluster resource. Remember that you must verify and synchronize this change to add it to the cluster definition on all nodes in the cluster.