Please enter search query.
Search <book_title>...
Cluster Server 8.0.1 Agent Developer's Guide - Windows
Last Published:
2022-05-19
Product(s):
InfoScale & Storage Foundation (8.0.1)
Platform: 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
- Files for use in agent development
- Creating the type definition file for a custom agent
- Building a custom agent on UNIX
- Defining resources for the custom resource type
- 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
Adding the custom type definition to the configuration
You can add the custom type definition to the configuration.
To add the custom type definition to the configuration
- Once you create the file, place it in the directory:
- Add "include FileOnOffTypes.cf" in the main.cf file.
- Restart VCS.
This section describes how to validate your XML file (custom_typeTypes.sun.xml) and add it to your configuration.
To add the type definition when the VCS One Policy Master is running
- Create the following directory:
The variable custom_type represents the name of the resource type you created.
- Copy the custom types XML file into the newly-created directory.
- Verify the XML file.
haconf -verify <xml_dir>
- Run the following command:
This converts the custom types file to a command file called with a .cmd extension in the custom_type directory. The file contains commands needed to add the type definition to the configuration.
- Run the commands included in the file from the policy master:
- Verify the custom type definition is added to the configuration:
hatype -display custom_type
To add the type definition when the VCS One Policy Master is not running
- Convert the configuration in policy master database to XML:
haconf -dbtoxml <xml_dir>
The variable <xml_dir> represents the policy master configuration directory, typically:
- Once you create the type definition file for the custom type, place it in the XML directory:
- Include the custom type definition file in the main.xml file. Add the following line to the main.xml file:
<include>custom_typeTypes.platform.xml</include>
- Verify the updated configuration.
haconf -verify <xml_dir>
- Load the XML configuration to the policy master database.
haconf -loaddb <xml_dir>