Client Deployment
Depending on the functionality used by your Nirvana
application, different jar files are required. This
following table illustrates the deployement dependencies
between the jar libraries installed by the Nirvana installer.
JAR File |
Description |
Dependency |
| nClient.jar |
Provides Nirvana Client functionality (Pub/Sub
and Queues) |
None |
| nJ2MEMIDP1.jar |
Provides Nirvana Client functionality (J2ME MIDP
1.0) |
None |
| nJ2MEMIDP2.jar |
Provides Nirvana Client functionality (J2ME MIDP
2.0) |
None |
| nP2P.jar |
Provides Nirvana Peer 2 Peer functionality |
nClient.jar |
| nJMS.jar |
Provides Nirvana JMS 1.1 functionality |
nClient.jar |
| nAdminAPI.jar |
Provides Nirvana Administration & Monitoring
functionality |
nClient.jar, nP2P.jar |
| nAdminXMLAPI.jar |
Provides Nirvana Configuration XML Import / Export
functionality (Note: Uses JAXB specification, JRE
1.4 is required) |
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 Nirvana Realm Server |
None |
| Nirvana.tlb |
Provides Nirvana Client Functionality for ActiveX
applications |
nClient.jar & Nirvana ActiveX Bridge |
|
