Owner manual

Figure 1 Architecture of NSMQ
N
o
n
S
t
o
p
C
l
u
s
t
e
r
I
/
O
P
r
o
t
o
c
o
l
s
t
c
p
:
/
/
<
H
o
s
t
n
a
m
e
I
P
A
d
d
r
e
s
s
>
:
<
P
o
r
t
N
o
.
>
SQL/MX Database
Producer
Consumer
Bn
B1
B3
B2
Bn
B1
: Brokers
......
SQL/MX database:
SQL/MX database is used as a data store for storing messages. The brokers connect to the database
to store and retrieve messages.
Cluster:
The cluster is made up of network of brokers and is used for handling additional load.
All the brokers are connected to each other using a duplex network connector to exchange
information and states of each broker. These brokers listen on a local loopback address with
different port numbers and are used exclusively for clustering.
In such a cluster, all the messages are accessible to all the brokers. A new broker can be introduced
by adding the broker to the local grid without disturbing the existing cluster, thus achieving scalability
(page 11).
Every broker is a combination of master and slave broker and is configured to run as two TS/MP
server classes — one process each for a master instance and a slave instance. The master instance
10 Introduction to NSMQ