WebSphere MQ----Channel

channels (channel)

A channel is actually a point-to-point communication connection between queue managers, and messages can only flow in one direction in a channel. If you need two-way communication, you can set up a pair of channels, a send side and an accept port. From the point of view of the queue Manager the flow of the message can be divided into input channels and output channels. By configuring the message to be placed in the local transport queue, the Queue Manager automatically sends it through the output channel and feeds it to the other's remote destination queue.

Two queue managers can have multiple channels responsible for transmitting different content, so the design tends to stagger different priority messages, running at different rates of network connections. Or even if all the channels are running on the same network physical connection, you can separate the different sizes of the messages so that small data transfers are blocked by large files. If multiple channels share a physical connection to a network, the rate of the channel is limited and the network speed. This increases the concurrency of the transfer but does not increase the overall transmission speed.

different communication protocols can be configured on the channel, which makes the programming interface independent of the communication protocol. The configurations on both sides of the channel must match and have the same name, otherwise they will not be able to connect. The communication between the queue managers is configured by the channel to connect, the queue manager on both sides of the channels should be able to correspond to the parameters of the channel, a channel can only use one communication protocol, but different channels can have different communication protocols. So the channel in MQ has a juchongruoqing effect on transmitting messages.

type of channel ( The MQ Channel type attribute) contracts the active and passive put in the connection handshake protocol between two communicating parties and the flow direction of the application message.

• the active party of the SDR Sender Handshake protocol, which belongs to the sender of the message in MQ

• The passive side of the RCVR receiver Handshake protocol, which belongs to the receiving party of the message in MQ

• The SVR Server can be either an active or a passive party in the Handshake Protocol, which is typically the sender of the message in MQ

• Rqstr requester in the handshake protocol can be either the active or the passive side, which is typically the receiver of the message in MQ.

• Clntconn Client Connection. When a client-server connection is defined, the Client Connection definition table is used, the initiator of the Handshake protocol, and the sender of the message.

• SVRCONN server Connection, when you define a server-side connection when the Client-server is connected, the passive side of the handshake protocol, the receiver of the message

• CLUSSDR Cluster Sender. Send configuration information and application information in the cluster. The active party of the Handshake Protocol, the sender of the message

• CLUSRCVR Cluster Receiver isused to accept configuration information and application information during cluster configuration. The receiver of the Handshake protocol

The channel type pairing of the two sides of the communication is not a combination of random combinations, there are six kinds,

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M02/8C/76/wKioL1htst3z6qsPAABtNWEVB3Y148.png-wh_500x0-wm_3 -wmp_4-s_597762208.png "title=" 2.PNG "alt=" Wkiol1htst3z6qspaabtnwevb3y148.png-wh_50 "/>

The thin lines in the figure represent the active connector of the Handshake protocol, and the thick line represents the flow of the application message. Messages are routed one-way across all channels.

• Sender/receiver makes all links the simplest and most common one. Sender is the active side of the channel and the sender of the message.

• Requester/server is also a common way to connect. Requester is the active side of the channel, but the channel is connected to it as the receiver of the message, in fact the Server is the sender of the message.

• Server/receiver similar to Sender/receiver,the Server is the sender of the message and the active side of the connection. similar to the Sender definition,the CONNAME parameter must be specified in the Server definition .

• Sender/requester connection process is slightly more complicated,requester first connect with Sender , after notifying the other connection parameters, the connection disconnects. Sender makes a reverse connection, and the message is also reverse-routed, a reverse connection, called Callback Connection.

• Sender connection/receiver Connection is the same way as Sender/receiver. For MQI channels between client\server

• Cluster Sender/cluster Receiver is the same as the sender/receiver method. Used for connections between cluster queue managers.

This article is from the "Snail in BizTalk" blog, so be sure to keep this source http://6060579.blog.51cto.com/6050579/1889191

WebSphere MQ----Channel