Use this option to protect a user-defined application that has no associated recovery kit. Templates are provided for the user supplied scripts referenced below in $LKROOT/lkadm/subsys/gen/app/templates. Copy these templates to another directory before customizing them for the application that you wish to protect and testing them.
Note: For applications depending upon other resources such as a file system, disk partition, or IP address, create each of these resources separately, and use Create Dependency to create the appropriate dependencies.
On the Edit menu, select Resource, then Create Resource Hierarchy. A dialog box entitled Create Resource Wizard will appear with a drop down menu listing all recognized recovery kits installed within the cluster. For each of the options that follow, click Help for an explanation of each choice.
Select Generic Application and click Next.
Select either intelligent or automatic for Switchback Type.
Select the Server on which you want to create the resource.
Enter the path to the Restore Script for the application. This is the command that starts the application. A template restore script, restore.template, is provided in the templates directory. The restore script must not impact applications that are already started.
Enter the path to the Remove Script for the application. This is the command that stops the application. A template remove script, remove.template, is provided in the templates directory.
Enter the path to the quickCheck Script for the application. This is the command that monitors the application. A template quickCheck script, quickCheck.template, is provided in the templates directory.
Enter the path to the Local Recovery Script for the application. This is the command that attempts to restore a failed application on the local server. A template recover script, recover.template, is provided in the templates directory.
Enter any Application Information next. This is optional information about the application that may be needed by the restore, remove, recover, and quickCheck scripts.
Select either Yes or No for Bring Resource In Service. Selecting No will cause the resource state to be set to OSU following the create; selecting Yes will cause the previously provided restore script to be executed. For applications depending upon other resources such as a file system, disk partition, or IP address, select No if you have not already created the appropriate dependent resources.
Enter the Root Tag, which is a unique name for the resource instance. (This is the label you will see for this resource in the status display.)
Click Create Instance to start the creation process. A window will display a message indicating the status of the instance creation.
Click Next. A window will display a message that the hierarchy has been created successfully.
At this point, you can click Continue to move on to extending the generic application resource hierarchy, or you can click Cancel to return to the GUI. If you click Cancel, you will receive a warning that your hierarchy exists on only one server, and it is not protected at this point.