Connection styles

MQe supports client/server operation. A client can initiate communication with a server. A server can respond only to the requests initiated by a client. The components involved are:
Listener
Listens for incoming connection requests.
Queue manager
Supports applications through the provision of messaging and queuing capabilities.
Table 1. Connection styles
  Queue manager Listener
Client Yes No
Client/server Yes Yes
Server Yes Yes
Servlet Yes No
Table 1 shows the relationship between these components and the connection style. The client/server connection style describes the situation where MQe can operate in either client or server mode. The servlet option describes the case where MQe is configured as an HTTP servlet with the HTTP server itself responsible for listening for incoming connection requests.

MQe applications are not directly aware of the connection style used by the queue managers. However, the style is significant in that it affects what resources are available to the parties, which queue managers can connect with other queue managers, how much memory MQe uses, and which connections can concurrently exist.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.