23.0 Packaging the Multi-Protocol agent

23 1 Overview

23.2 Jars Required for Packaging the Multi-Protocol agent

23.3 Package Agent

23.1 Overview

Once the Multi-Protocol agent is deployed, it is ready for packaging. Please follow the steps given in this section to know how to package a Multi-Protocol agent.

23.2 Jars Required for Packaging the Multi-Protocol agent

The jars required for packaging a Multi-Protocol agent are given below:

• For Multi-Protocol Agent (in general)

• The compiled class files generated by the JMX Compiler in the output directory.

• xmojo.jar

• crimson.jar

• jaxp.jar

• xalan.jar

• AdventNetAgentRuntimeUtilities.jar

• AdventNetJmxAgent.jar

• AdventNetAgentUtilities.jar

• AdventNetLogging.jar

Along with these, the following jars should be available for the multi-protocol agent to run in the below said adaptors:

• For SNMP Adaptor

• AdventNetSnmp.jar

• AdventNetSnmpAgent.jar

• For TL1 Adaptor

• AdventNetTL1.jar

• AdventNetTL1Agent.jar

• For HTML Adaptor

• servlet.jar

• webserver.jar

• AdventNetAgentWCF.jar

23.3 Running the Agent in Any Environment

The option Package Agent  in Build Menu of the JMX Compiler, when selected ,

• copies the required jars for running the agent from <Agent Toolkit Home>/jars directory to the ./jmxprojects/<projectName>/agent/bin/jars directory. 

• creates a mibs folder under ./jmxprojects/<projectName>  and copies the MIB file used in the project.

• creates an external files folder under ./jmxprojects/<projectName> and copies any external files used in the project.

This makes the agent self-contained and it can be used as an independent project.