Miscellaneous concepts and functionality

Edit online

This section describes additional functionality available to the Smart Assist developer.

Define the cluster automatically

If the cluster is not defined when the Add an Application to the PowerHA® SystemMirror® Configuration menu selection is made, the Smart Assist framework automatically queries the end user for the nodes in the cluster and creates the cluster. This step is equivalent to the Configure a PowerHA SystemMirror Cluster and Nodes SMIT function.

Query and list commands used in the API

Several utility commands are available to the Smart Assist developer. See Smart Assist commands for a detailed description of these routines:

  • cllsssaapp - List configured Smart Assists application instances.
  • cllsserviceips - List available service IP labels
  • clquerysa - Return attributes of specified Smart Assist
  • clquerysaapp - Return attributes of specified Smart Assist application instance

The clsapre and clsapost routines must be called before and after creating a Smart Assist application instance. They provide hooks back to the framework during these operations. 

clsapre [ -c cluster_name ]   
-c cluster_name Change the name of the cluster to the specified value   
clsapost [ -v ]   
-v Run cluster verification after the application instance is added

Registration and deregistration commands

The REGISTRATION_COMMAND and DEREGISTRATTION_COMMAND specified in the claddsa call allow the Smart Assist developer to perform activities before the Smart Assist is installed and before it is removed.

Smart Assist migration commands

The MIGRATION_COMMAND specified in the claddsa call allows the Smart Assist developer to specify a migration script in case a newer Smart Assist is superseding an older one. If the SMARTASSIST_VERSION values don't match when the claddsa call is made, the MIGRATION_COMMAND specified in the new Smart Assist is called to migrate any existing Smart Assist application instance data to a new format if necessary, or to make modifications to the existing data as necessary.

Smart Assist test command

If a TEST_COMMAND is specified in the claddsa call, the script is called when the end user selects the Test Your Application for Availability menu selection. The test script will be given the name of the application to test as the first argument. It is the test script's responsibility to produced stdout output that conforms to the cluster test tool script format. If a TEST_COMMAND is not specified a default test script will execute if the user chooses to test Planning Names and Values for the Smart Assist for the Discovery Database.