Universal Messaging 9.9 | Installation Guide | Common Post-Installation Procedures for Standalone and Suite Installation | Client Deployment
 
Client Deployment
Client Deployment
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 and Queues)
None
nP2P.jar
Provides Universal Messaging Peer 2 Peer functionality
nClient.jar
nJMS.jar
Provides Universal Messaging Provider for JMS functionality
nClient.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)
nServer.jar
Contains the Universal Messaging Realm Server
None
Universal Messaging.tlb
Provides Universal Messaging Client Functionality for ActiveX applications
nClient.jar & Universal Messaging ActiveX Bridge

Copyright © 2013-2015 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release