Setting Up for EJB API

The SnmpTarget interface of the EJB API is used in the client application for performing many of the common operations, such as GET, GETNEXT, and SET operations.

The EJB standard restricts users from performing certain protocol functions, such as socket access. The protocol-specific functions required by the EJB components are provided by an SnmpEJBServer factory that runs outside the EJB container. This operates in a similar fashion to the SNMP RMI factory. The SnmpEJBServer factory should be started within the EJB application server.

Following are the jar files available in the <WebNMS_Home>\SNMPAPI\reference\ejb directory.

• std_MibOperationsEJB.jar

• std_SnmpTableEJB.jar

• std_SnmpTargetEJB.jar

These jar files conform to the EJB standards. The deployment procedure would be different for each EJB application server as there are wide range of EJB servers available in the market.

The classes needed for EJB client to access the WebNMS SNMP API are provided in the com.adventnet.snmp.ejb package. The CLASSPATH should be set to WebNMS SNMP <classes> directory or the AdventNetEJB.jar

Requirements

The standard jar file available with WebNMS EJB API should also contain the weblogic-ejb-jar.xml file with the ejb-jar.xml file.

For example, if the std_SnmpTargetEJB.jar is to be added to the WebLogic server, the jar file should contain the following in the package structure according to the EJB standards.

• SnmpTarget.class

• SnmpTargetEJB.class

• SnmpTargetHome.class

• ejb-jar.xml

• weblogic-ejb-jar.xml

Go through the deployment procedure provided in the WebLogic documentation for more details.