Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
Last Published:
2025-04-13
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: 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: Using script entry points on UNIX
The following example shows how to build the FileOnOff agent using scripts. For the below example, we are using Script51Agent script based agent binary.This example implements the online, offline, and monitor entry points only.
See Script based agent binaries.
Example: implementing entry points using scripts
- Create the directory /opt/VRTSvcs/bin/FileOnOff:
mkdir /opt/VRTSvcs/bin/FileOnOff
- Use the VCS agent /opt/VRTSvcs/bin/Script51Agent as the FileOnOff agent. Copy this file to the following path:
/opt/VRTSvcs/bin/FileOnOff/FileOnOffAgent
or create a link.
To copy the agent binary:
cp /opt/VRTSvcs/bin/Script51Agent /opt/VRTSvcs/bin/FileOnOff/FileOnOffAgent
To create a link to the agent binary:
ln -s /opt/VRTSvcs/bin/Script51Agent /opt/VRTSvcs/bin/FileOnOff/FileOnOffAgent
- Implement the online, offline, and monitor entry points using scripts. Use any editor.
Create the file /opt/VRTSvcs/bin/FileOnOff/online with the contents:
# !/bin/sh # Create the file specified by the PathName # attribute. touch $4 exit 0
Create the file /opt/VRTSvcs/bin/FileOnOff/offline with the contents:
# !/bin/sh # Remove the file specified by the PathName # attribute. rm $4 exit 0
Create the file /opt/VRTSvcs/bin/FileOnOff/monitor with the contents:
# !/bin/sh # Verify file specified by the PathName attribute # exists. if test -f $4 then exit 110; else exit 100; fi
- Additionally, you can implement the info and action entry points. For the action entry point, create a subdirectory named "actions" under the agent directory, and create scripts with the same names as the action_tokens within the subdirectory.