Forward migration involves upgrading an existing queue manager to a later version (such as WebSphere MQ V6.0 to WebSphere MQ V7.0) and is supported on all platforms.
向前迁移指的是将现有队列管理器更新到更新的版本(比如从WebSphereMQV6.0到WebSphere MQV7.0)，所有平台都支持向前迁移。
Unlike communications from one MQ server to another, MQ channels are not defined for transmission queues from an MQ server to a gateway queue manager.
与从一个MQ服务器到另一个的通信不同，从MQ服务器到网关队列管理器的传输队列没有定义MQ通道。
Using this option, each of the MQ servers would be part of an MQ cluster.
使用这一选项，每个MQ服务器都将是MQ集群的一部分。
This article describes the most common best practices in designing, building, running, and maintaining MQ solutions in order to achieve the full benefits of MQ.
本文描述有关设计、构建、运行和维护MQ解决方案的最常见最佳实践，以便实现MQ的全部好处。
The introduction of the MQ failed event type allows for easy recovery options from errors experienced while processing MQ messages.
MQ失败事件类型的引入，使您在处理 MQ消息时可从错误经验中轻松地恢复选项。
If you are using MQ rather than the default messaging provider, you should of course use SSL to MQ.
如果您使用的是mq而非缺省的消息传递提供程序，则当然应该对MQ使用SSL。
Note: Please check with MQ support to verify the Settings, since MQ might change from time to time.
注意：请咨询MQ支持部门以验证那些设置，因为MQ可能随时间而更改。
In the reverse pattern, it's easy for MQ-based applications to connect to other non MQ applications using standard MQ messages.
在相反的模式中，基于MQ的应用程序很容易使用标准MQ消息连接到其他非mq应用程序。
It USES the MQ Telemetry Transport (MQTT) protocol to enable you to monitor enterprise sensors using IBM MQ technology.
它使用MQ遥测传输(MQTT)协议支持您使用IBM MQ技术来监测企业传感器。
JMS request queue Connection Factory: Used by the listener port to connect to the MQ queue manager that hosts the request MQ queue.
JMS请求队列连接工厂：由侦听器端口用于连接到承载请求mq队列的mq队列管理器。
MQ binding — Used typically by pure MQ clients, also called legacy MQ clients.
MQ绑定——一般由纯MQ客户端使用，也称为旧式MQ客户端。
These bindings now use the MQ V7 JCA resource adapter, which provides support to both MQ V7 and earlier interfaces.
这些绑定现在使用MQV 7JCA资源适配器，这支持MQV7和更早的接口。
MQ JMS implementations can interoperate with other MQ programs without the need for Bridges.
MQJMS实现无需桥接即可与其他MQ程序互操作。
Configuring MQ messaging provider activation specifications is very similar to configuring MQ messaging provider connection factories.
配置MQ消息传递提供程序激活规范非常类似于配置MQ消息传递提供程序连接工厂。
This article was written based on MQ V6 and assumes you have a basic knowledge of MQ.
本文是基于MQV6 编写的，并假设您具备 MQ 的基础知识。
For example, in the case of the JDBC adapter, this queue will be the "event table", and in the case of the MQ adapter, this queue will be an MQ queue.
例如，对于JDBC适配器，此队列将为“事件表”，而对于MQ适配器，此队列将为一个mq队列。
In your workspace, a folder is created with a path similar to c: \ workspace \ MQTest \ gen \ SRC \ test \ mq \ COBOL \ mq.
在您的工作区中，将创建一个其路径类似于c： \Workspace \MQTest \gen \src \test \mq \cobol \ mq的文件夹。
In order to send messages from a device running MQe to MQ, or from MQ to a device, the system architecture consists of three components.
为了将消息从运行MQe的设备发送到MQ，或者从MQ发送到一台设备，系统体系结构由三个组件构成。
When you invoke any WebSphere MQ function exchanging a message with MQ, you must be within a transaction, implicit or explicit.
任何用于与MQ交换消息的WebSphere mq函数都必须在一个事务中显式或隐式地调用。
Using multiple bridge queues and client connection objects can dramatically increase the throughput of messages from WebSphere MQ Everyplace to WebSphere MQ.
使用多个网桥队列和客户端连接对象可以显著提高从WebSphereMQeveryplace到websphere MQ的消息吞吐量。
A convenient way to manage queue managers is to use the MQ Explorer utility program provided with WebSphere MQ.
一种管理队列管理器的方便方法就是使用WebSphereMQ提供的 MQExplorer实用程序。
As with messages going from device queue managers to MQ, the gateway does the reverse transformation from MQ to MQe message format.
对于从设备队列管理器到MQ的消息，网关执行从MQ到MQe消息格式的逆向转换。
An Import — MQ binding is used when you want to access the WebSphere MQ Messaging Provider from a component.
当您想从一个组件访问WebSphereMQ消息传递提供程序时，需要使用导入- MQ绑定。
An MQ messaging client puts a message on an MQ local queue, EXPORTQ.
MQ消息传递客户端将消息放在MQ本地队列EXPORTQ中。
On the MQ side, MQ channels are defined to communicate with the specific SIBus messaging engine.
在MQ端，MQ通道定义为与特定的SIBus消息传递引擎进行通信。
This enables sending a message from an MQ client to an MQ queue, and then forwarding the message automatically to a destination in SIBus.
这可以将消息从MQ客户机发送到mq队列，然后将消息自动转发到SIBus中的目的地。
It is assumed that you have a working knowledge of WebSphere MQ and MQ JMS, and that you have already created a queue manager and properly configured your JMS environment.
我们假定您有使用WebSphereMQ和MQJMS的经验，还假设您已经创建了一个队列管理器并且正确地配置了JMS环境。
Select the type of bindings it applies to, for now tick MQ andOn the import configure an MQ binding with the same data format as above.
选择它适用的绑定类型，现在勾选MQ和在导入上，按照上述同一数据格式配置MQ绑定。
Since the provider is WebSphere MQ in this case, the instructions provided here are WebSphere MQ-specific.
由于在本例中提供程序是WebSphereMQ，所以这里提供的说明是特定于WebSphereMQ的。
JMS reply queue Connection Factory: Used by the Web service to connect to the MQ queue manager that hosts the reply MQ queue.
JMS应答队列连接工厂：由Web服务用于连接到承载应答mq队列的mq队列管理器。
应用推荐