Custom plug-ins can be deployed on the Agent Controller and run on remote hosts. The plug-ins are installed in the plugin directory Agent Controller install directory. Each plug-in will have its own pluginconfig.xml specifying the execution environment and the application environment settings in which the plug-in should run.
The execution environment for custom plug-ins should contain a custom class path definition. This will ensure that only the required jar files for the custom plug-in are run. To customize the execution environment:
<AgentControllerEnvironment configuration="default"> <Variable name="CLASSPATH_ORG_MYAPP" position="append" value="%PLUGINS_HOME%/org.myapp/one.jar"/> <Variable name="CLASSPATH_ORG_MYAPP" position="append" value="%PLUGINS_HOME%/org.myapp/two.jar"/> <Variable name="CLASSPATH_ORG_MYAPP" position="append" value="%PLUGINS_HOME%/org.myapp/three.jar"/> </AgentControllerEnvironment>
Note: Any number of <Variable> elements can be added to the environment. The rules are processed on a first-come, first-serve basis.
The application environment for a plug-in is defined within the <Application> element in the pluginconfig.xml file. These settings in this element are visible only to the application. You can also configure your application to use jar files from other applications deployed on the Agent Controller using the <Application> element. To configure the application environment:
<Application configuration="default" executable="myapp2" location="%SYS_TEMP_DIR%" path="%JAVA_PATH%"> </Application>where
<?xml version="1.0" encoding="UTF-8"?> <PluginConfiguration> <Application configuration="default" executable="myapp2" location="%SYS_TEMP_DIR%" path="%JAVA_PATH%"> <Variable name="CLASSPATH" position="append" value="%CLASSPATH_ORG_MYAPP%"/> </Application> <Option name="my.proj2" type="version" value="1.0.0"/> </PluginConfiguration>
Related tasks
Locating the configuration files
Administering the Agent Controller