Universal Messaging Concepts : Deployment : Client : Client Jars
Client Jars
Depending on the functionality used by your Universal Messaging application, different jar files are required. This following table illustrates 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)
nP2P.jar
Provides Universal Messaging Peer-to-Peer functionality
nClient.jar
nJMS.jar
Provides Universal Messaging Provider to support JMS functionality
nClient.jar, gf.javax.jms.jar
nJ2EE.jar
Provides Universal Messaging support for interacting with Application servers that support J2EE
nClient.jar, JMS.jar, gf.javax.jms.jar
nAdminAPI.jar
Provides Universal Messaging Administration & Monitoring functionality
nClient.jar, nP2P.jar
nAdminXMLAPI.jar
Provides Universal Messaging Configuration XML Import / Export functionality
nClient.jar, nP2P.jar, nAdminAPI.jar
nEnterpriseManager.jar
Contains the Enterprise Manager tool
nClient.jar, nP2P.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)
Copyright © 2013-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback