InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
- Introduction
- Agent entry point overview
- About agent entry points
- Agent entry points described
- About the action entry point
- About the info entry point
- Considerations for using C++ or script entry points
- About the agent information file
- About the ArgList and ArgListValues attributes
- Creating entry points in C++
- About creating entry points in C++
- Syntax for C++ entry points
- Agent framework primitives
- Agent Framework primitives for container support
- Creating entry points in scripts
- About creating entry points in scripts
- Syntax for script entry points
- Agent framework primitives
- VCSAG_GET_ATTR_VALUE
- Agent Framework primitives with container support
- Example script entry points
- Logging agent messages
- Building a custom agent
- Building a script based IMF-aware custom agent
- Creating XML file required for AMF plugins to do resource registration for online and offline state monitoring
- Testing agents
- Static type attributes
- About static attributes
- Static type attribute definitions
- AdvDbg
- ArgList
- State transition diagram
- Internationalized messages
- Troubleshooting VCS resource's unexpected behavior using First Failure Data Capture (FFDC)
- Appendix A. Using pre-5.0 VCS agents
About the action entry point
Runs a pre-specified action on a resource. Use the entry point to run non-periodic actions like suspending a database or resuming the suspended database.
The SupportedActions attribute is a keylist attribute that lists all the actions that are intended on being supported. Each action is identified by a name (action_token).
See SupportedActions.
For an agent, all action entry points must be either C++ or script-based; you cannot use both C++ and scripts.
If all actions are script based, make sure the action scripts reside within an actions directory under the agent directory. Create a script for each action. Use the correct action_token as the script name.
For example, a script called suspend defines the actions to be performed when the action_token "suspend" is invoked via the hares -action command.
For C++ entry points, actions are implemented via a switch statement that defines a case for each possible action_token.
The following shows the syntax for the -action option used with the hares command:
hares -action <res> <token> [-actionargs <arg1> ...] -sys <system> [-clus <cluster> | -localclus]
The following example commands show the invocation of the action entry point using the example action tokens, DBSuspend and DBResume:
hares -action DBResource DBSuspend -actionargs dbsuspend -sys Sys1
Also,
hares -action DBResource DBResume -actionargs dbstart -sys Sys1