Owner manual

For more information about CIP, see the Cluster I/O Protocols (CIP) Configuration and Management
Manual.
SQL/MX database
NSMQ uses SQL/MX database for persisting messages and achieving fault tolerance. For more
information, see “Fault tolerance” (page 12).
For more information, see the NonStop SQL/MX documentation.
Features of NSMQ
The features of NSMQ are as follows:
• Clustering — A mechanism where you configure multiple brokers to form a cluster. In such an
environment, all brokers are networked and if a broker fails, the load is distributed among
the remaining brokers in the cluster. In clustering, multicasting and dynamic discovery is not
supported.
• Client API support — Only JMS clients are supported. C++, .NET clients are not supported.
• Persistence — Messages are stored in SQL/MX database.
• Destinations — Specifies the destinations that must be created when a broker starts. The
following destinations are supported:
◦ Queue — Queues are used for Point-To-Point messaging in first-in first-out order. Messages
are consumed from the queue in the order in which they are received. See http://
docs.oracle.com/javaee/6/tutorial/doc/bncdx.html#bnceb.
◦ Topic — Topics are used for Publish and Subscribe (Pub/Sub) messaging. The message
producer is referred as Publisher and the message consumer is referred as Subscriber.
See http://docs.oracle.com/javaee/6/tutorial/doc/bncdx.html#bnced.
However, the durable subscription of messages for topics is not supported in NSMQ.
◦ Composite destinations — Composite destinations provide a mechanism for producers
to send the same message to multiple destinations at the same time. See http://
activemq.apache.org/composite-destinations.html.
◦ Virtual destinations — Virtual destinations provide a mechanism for publishers to broadcast
messages through a topic to a pool of receivers subscribing through queues. See http://
activemq.apache.org/virtual-destinations.html.
◦ Wildcards — Wildcards provide a mechanism for consumers to subscribe to multiple
destinations at the same time. See http://activemq.apache.org/wildcards.html.
Architecture
Although ActiveMQ supports various topologies to configure brokers, NSMQ supports the complete
grid topology on a NonStop system.
In this architecture, you can have multiple brokers on a NonStop node. Multiple brokers can run
on the same or different CPUs. However, HP recommends you to run brokers on different CPUs to
achieve uninterrupted availability.
Figure 1 (page 10) illustrates the architecture of NSMQ.
Features of NSMQ 9