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
Example of amfregister.xml for registration of process-based resource with AMF for online monitoring
Assuming the process in the ps output is displayed as follows, you can use the subsequent steps to register a process-based resource for online monitoring:
"/usr/sbin/rpc.statd -d 0 -t 50"
If you are sure about the path and arguments, you must specify your process in the following format in the amfregister.xml file:
<xml> <Register> <RegType>PRON</RegType> <ProcPattern>/usr/sbin/rpc.statd -d 0 -t 50</ProcPattern> </Register> </xml>
If you are not sure about the arguments but are sure about the path, you must specify your process in the following format in the amfregister.xml file:
<xml> <Register> <RegType>PRON</RegType> <PronOptions>IGNORE_ARGS</PronOptions> <ProcPattern>/usr/sbin/rpc.statd</ProcPattern> </Register> </xml>
Note:
If there are more than one processes or instances with different arguments, all get registered.
For example:
"/usr/sbin/rpc.statd -d 0 -t 50" "/usr/sbin/rpc.statd -xyz"
Both the above processes get registered with AMF.
If you are not sure about the path but are sure about the arguments, you must use the following format of the amfregister.xml:
<xml> <Register> <RegType>PRON</RegType> <PronOptions>IGNORE_PATH</PronOptions> <ProcPattern>rpc.statd -d 0 -t 50</ProcPattern> </Register> </xml>
Note:
If there are more than one processes/instances with different paths, all get registered.
For example:
"/usr/sbin/rpc.statd -d 0 -t 50" "/home/<testuser>/rpc.statd -d 0 -t 50"
If you are not sure about the path or the arguments, you must use the following format of the amfregister.xml:
<xml> <Register> <RegType>PRON</RegType> <PronOptions>IGNORE_ARGS IGNORE_PATH</PronOptions> <ProcPattern>rpc.statd</ProcPattern> </Register> </xml>
Note:
If there are more than one processes with the same base name, all get registered irrespective of the path and arguments.
For example:
"/usr/sbin/rpc.statd -d 0" "/home/<testuser>/rpc.statd -d 0 -t 50"