Client Jars

Depending on the functionality used by your Universal Messaging application, different jar files are required. The following table shows the deployment dependencies between the jar libraries installed by the Universal Messaging installer.

JAR File Description Dependency
nClient.jar Provides Universal Messaging Client functionality (Pub/Sub & Queues) (none)
nJMS.jar Provides support for JMS 1.1 and 2.0 nClient.jar, gf.javax.jms.jar
nAdminAPI.jar Provides Universal Messaging Administration & Monitoring functionality nClient.jar
nEnterpriseManager.jar Contains the Enterprise Manager tool nClient.jar, nAdminAPI.jar, nAdminXMLAPI.jar (Optional), gf.javax.jms.jar
nServer.jar Contains the Universal Messaging Realm Server (none)
nPlugin.jar Contains the Universal Messaging Server plugins nServer.jar
gf.javax.jms.jar JMS reference jar (none)
nJakartaMessaging-3.0.jar Provides support for Jakarta Messaging 3.0 nClient.jar, jakarta.jms-api-3.0.0.jar

The jar files are located in <InstallDir>/UniversalMessaging/lib.

Client Jar files that are no longer available

The following table indicates Jar files that were delivered with previous product versions, but which are not delivered as Jar files any more. Their classes have now either been folded into other Jar files, or have been removed from the product altogether.

JAR File Description Status
nJ2EE.jar Provided Universal Messaging support for interacting with Application servers that support J2EE.

The Jar file is no longer available.

nAdminXMLAPI.jar Provided Universal Messaging Configuration XML Import / Export functionality. The Jar file is no longer available, but the contents have been folded into nAdminAPI.jar.
nP2P.jar Provided Universal Messaging Peer-to-Peer functionality. The P2P functionality was removed from the product in version 9.12. The Jar file is no longer available, and the contents have not been folded into any other Jar file.