Sender and receiver channel exits are invoked prior to data being sent to, or received from a queue manager, respectively.
在通过队列管理程序发送和接收数据之前，应该分别调用发送方和接收方通道出口。
The cluster sender channel must point to one of the queue managers that hosts a cluster repository.
集群发送器通道必须指向承载集群存储库的队列管理器之一。
In other words, the JMS provider can assure a message's sender that it was delivered to it's destination (a queue or topic) once and only once.
换句话说就是，JMS提供者可以向消息的发送方保证将消息发送到目的地(一个队列或主题)，并且是一次性发送。
To make the queue manager available to the cluster, two additional channels have to be defined: a cluster receiver and a cluster sender channel.
为了确保队列管理器对集群可用，必须定义两个额外的通道：一个集群接收器 通道和一个集群发送器通道。
A JMS sender puts a message in a JMS queue similar to a sender putting an envelope in the mail box.
JMS发送者推送一条消息到JMS消息队列就如同寄件人把一封信件放到了邮箱。
In a queue-based system, there is an explicit third party (the queue) where messages the sender must put messages and the receiver get messages from.
在队列系统中，总会存在一个显式的第三方队列系统，发送者放入消息，接收者再从中取出。
The sender, similar to the RM Source, keeps monitoring the Queue for messages to be sent, identifies them, and immediately sends them to the RM Source.
与RMSource中相似，发送方将持续监视Queue，以获得要发送的消息，并将对这些消息进行标识，然后立即将其发送到RMSource。
Sender MQ channel name: busToMQ (This can be any name of your choosing, but it must match the receiver channel name in the MQ queue manager.
SenderMQchannelname：busToMQ（这可以是任意选择的名称，但它必须与 MQ队列管理器中的接收方通道名称相匹配。）
It includes an example of the XML response that notifies the message Sender that a message was successfully processed and causes the message Sender to move the message onto the success queue.
它包含一个XML响应的示例，该响应通知MessageSender成功创建了一条消息，并导致Message Sender将该消息移动到成功队列中。
After completion, create CLUSTER sender and CLUSTER receiver channels between the full repository queue managers by issuing the commands below.
完成上述操作之后，运行以下命令，在完整存储库队列管理器之间创建CLUSTER发送器和CLUSTER接收器通道。
In the topology used in this article, the cluster sender channels of both put queue managers will point to each other.
在本文所使用的拓扑中，两个put队列管理器的集群发送器通道都指向对方。
The WebSphere MQ link sender channel establishes a connection to a receiver channel on the target WebSphere MQ queue manager.
WebSphereMQ链接发送方通道建立到目标 WebSphere MQ队列管理器上的接收方通道的连接。
The WebSphere MQ link receiver channel enables a sender channel within a WebSphere MQ queue manager to establish a connection to a messaging engine within the service integration bus.
WebSphereMQ链接接收方通道支持WebSphere mq队列管理器内的发送方通道，以建立到服务集成总线内的消息传递引擎的连接。
The WebSphere MQ sender channel will be used to send messages from the WebSphere MQ queue manager to the service integration bus.
WebSphereMQ发送方通道将用于把消息从WebSphere mq队列管理器发送到服务集成总线。
The inbound transport chain, with which the sender channel on the WebSphere MQ queue manager communicates, is dependent on the configuration of the WebSphere MQ sender channel.
入站传输链（WebSphereMQ队列管理器上的发送方通道与之进行通信）依赖于 WebSphere MQ 发送方通道的配置。
Each channel has two ends: a sender channel that is defined within the originating queue manager, and a receiver channel that is defined within the destination queue manager, as shown in Figure 4.
每个通道都有两个端点：在起始队列管理器内定义的发送端(sender)通道和在目的队列管理器内定义的接收端(receiver)通道，如图4中所示。
The message Sender will then await acknowledgement - a confirmation or rejection from the external system - to decide if it will move the message onto the success or reject queue.
Messagesender会等待回执(来自外部系统的确认或拒绝)，以决定将消息移动到成功队列还是拒绝队列中。
Receiver MQ channel name: MQToBus (This is a name of your choosing, but it must match the sender channel name in the queue manager.)
ReceiverMQchannelname：MQToBus(这可以是任意选择的名称，但它必须与队列管理器中的发送方通道名称相匹配。)
In order to support the connectivity between the Sender and the Receiver with respect to a particular EPM, Sandesha architecture USES an in-memory Queue by default.
为了支持根据特定的EPM在Sender与Receiver之间建立连接，Sandesha体系结构将在缺省情况下使用内存中的队列。
The sender does not have the access rights needed to place the message in the destination queue.
寄件人没有将讯息放到目的伫列所需的存取权限（本页面可能为英文）。
Because we might start the receiver before the sender, we want to make sure the queue exists before we try to consume messages from it.
因为有可能我们在发送者发送消息之前就开始接收了，所以在我们从中接收消息之前得确定存它在呀。
The sender ID is set by Message Queuing and is used by the receiving Queue Manager to verify whether the sender has access rights to a queue.
寄件人ID是由讯息伫列所设定，并由接收伫列管理员使用以验证传送者是否具有伫列的存取权限。
Setting up is the same as the sender; we open a connection and a channel, and declare the queue from which we're going to consume.
设置也和上面一样，打开一个连接和信道，声明一个我们要消费(接收消息)的队列。
The sender ID is only trustworthy if the message was authenticated when it reached the destination queue.
只有在讯息到达目的伫列时已经过验证，传送者识别码才是可信任的。
The sender ID is only trustworthy if the message was authenticated when it reached the destination queue.
只有在讯息到达目的伫列时已经过验证，传送者识别码才是可信任的。
应用推荐