A server usually runs on a server platform. A server can run server-side applications but can also run client-side applications. As with clients, a server can open connections to many other queue managers on both servers and clients. One of the main characteristics that differentiate a server from a client is that it can handle many concurrent incoming requests. A server often acts as an entry point for many clients into an WebSphere MQ Everyplace network .
MQeServer is the simplest server implementation.
This server can be started with the following command:
qm_server server_QMgr_name [-p private_reg_PIN]
You must supply the -p parameter if the queue manager uses a private registry. Otherwise, the queue manager's registry is treated as a file registry. The program activates the queue manager (including a channel listener listening on port 8081) and goes into an indefinite sleep.
Use ctrl-C to shut down the server.
To delete the constructed queue manager, use the example qm_delete.
When two queue managers communicate with each other, WebSphere MQ Everyplace opens a connection between the two queue managers. The connection is a logical entity that is used as a queue manager to queue manager pipe. Multiple connections may be open at any time.
The new parameters control the use of the connection. The MaxChannels parameter controls the maximum number of connections that can be open at any time. A special value of 0 means that the queue manager can handle an unlimited number of connections.
The following parameters control how incoming network requests are handled:
Once the server has been initialized it must be activated.
When you activate a server the following occurs:
Code to demonstrate server activation is provided in queue manager example Ex2.
MQePrivateServer is an extension of MQeServer with the addition that it configures the queue manager and registry to allow for secure queues. See Security.