Use this page to create and configure one or more application
controllers, also known as application servers, for the resource group.
An application controller is a collection of the start and stop
scripts for an application as defined to PowerHA™ SystemMirror. The start and stop
scripts for the application are the main points of control for PowerHA SystemMirror over the
application. It is very important that the scripts you specify operate
correctly to start and stop all aspects of the application. If the
scripts fail to properly control the application, other parts of the
application recovery might be affected. For example, if the stop script
you use fails to completely stop the application and a process continues
to access a disk, PowerHA SystemMirror
cannot bring the volume group offline on the node that failed nor
recover it on the backup node.
All fields on this page are inactive until you specify information
for the Controller Name field, then all fields
are enabled.
Fields
- Controller name
- Select a predefined application controller from the provided list
or manually specify a unique name for a custom application controller
that you want to define for the resource group. The name you specify
must consist of a minimum of one alphanumeric character and a maximum
of 64 alphanumeric characters. You can use alphabetic characters of
A - Z and a - z, numbers of 0 - 9, as well as underscore (_) characters.
A name cannot begin with a number and cannot be a PowerHA reserved word.
If you choose a
predefined application controller, the Start script and Stop
script for it are also predefined, and these fields are
completed for you and you cannot change them.
- Start script
- Specify the full path and file name of the program to be used
to start the application server, along with any additional arguments
to be passed to the program when it runs. This program is run whenever
the required resources become available, such as when a node joins
the cluster. You can use a maximum of 256 alphanumeric characters.
This script must be in the same location on each cluster node that
might start the server. The contents of the script, however, can differ.
- Stop script
- Specify the full path and file name of the program to be used
to stop the application server, along with any additional arguments
to be passed to the program when it runs. This program is run whenever
the required resources become available, such as when a node joins
the cluster. You can use a maximum of 256 alphanumeric characters.
This script must be in the same location on each cluster node that
might start the server. The contents of the script, however, can differ.
- Application monitor(s)
- Select one or more application monitors from the table to use
with this application. This table contains a list of all predefined
application monitors, as well as lists any application monitors you
defined by using the Application Monitor page.
Actions
- Add Another
- Click Add Another to add another set of
fields so that you can create and configure another application controller
for your custom resource group. All fields for the added application
controller are inactive until you select the first field, typically
the name field. All fields for the added application controller are
inactive until you specify information for the Controller
Name field, then all fields are enabled.
- Remove
- Click Remove to remove the content from
the first set of application controller fields and disable all fields
after the Controller Name field. If applied
to an added application controller on the page, this action removes
the entire set of fields for the added controller.