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
Implementing entry points using scripts
If entry points are implemented using scripts, the script file must be placed in the directory $VCS_HOME/bin/resource_type. It must be named correctly.
See About creating entry points in scripts.
If all entry points are scripts, all scripts should be in the directory $VCS_HOME/bin/resource_type.
Copy the script based agent binary into the agent directory as $VCS_HOME/bin/resource_type/resource_typeAgent.
See Script based agent binaries.
For example, if the online entry point for Oracle is implemented using Perl, the online script must be: $VCS_HOME/bin/Oracle/online.
We also recommend naming the agent binary resource_typeAgent. Place the agent in the directory $VCS_HOME/bin/resource_type.
The agent binary for Oracle would be $VCS_HOME/bin/Oracle/OracleAgent, for example.
If the agent file is different, for example /foo/ora_agent, the types.cf file must contain the following entry:
... Type Oracle ( ... static str AgentFile = "/foo/ora_agent" ... )