NonStop JMS User's Manual (NonStop JMS 2.0+)

Introduction to NSJMS
NonStop Server for Java Message Service User’s Manual—522356-002
1-4
SQL/MX
SQL/MX
SQL/MX is the HP relational database management system that provides access to
large distributed databases. JMS clients use SQL/MX to access messages and
information stored in NSJMS SQL databases.
JNDI API
The JNDI API provides a generic set of interfaces that enables the administrative utility
to access naming and directory services.
JNDI Provider
The JNDI provider implements the naming and directory services.
Supported Platform
NSJMS is supported on NonStop RISC-based servers running a version of the
NonStop Kernel operating system released with G06.18.5 or later.
Compliance Information
NSJMS conforms to Sun Microsystems published specification, Java Message
Service, Version 1.0.2b, August 27, 2001, except as noted. The specification is
available on the Sun Microsystems Java Message Service (JMS) Web site
(http://java.sun.com/products/jms/docs.html).
•
JMS Application Server Facilities refers to server-side facilities in a JMS
implementation that could be used by an expert application. These features are
optional interfaces (ConnectionConsumer, ServerSession and SeverSessionPool)
and are not available in the NSJMS implementation.
•
A JMS provider can provide Java Transaction API (JTA)-aware connections and
sessions by using the XAConnectionFactory, XAConnection, XASession, and so
on. On the HP NonStop Kernel platform, the transaction integration of NSJMS and
other products is provided by HP NonStop Transaction Management Facility
(TMF). Although these XA interfaces are not implemented in NSJMS, you can use
JTA to start or commit transactions which involve NSJMS.
•
The JMS specification defines the priority value as 0 (zero), the lowest priority, and
9, the highest. Priority does not affect delivery of messages in the NSJMS
implementation.