The consuming MQ application, in this case RFHUTIL, can then consume the message.
在此情况下，使用MQ应用程序rfhutil然后可以使用该消息。
In this section, you learn how to expose an MQ application as a JMS service, using the following steps.
本部分将介绍如何通过下列步骤，将MQ应用程序公开为JMS服务？
The attraction of running an MQ application as trusted is that it gives a performance benefit through reduced code pathlength.
将MQ应用程序作为受信任对象运行的好处在于，这样可通过缩短的代码路径长度提供性能优势。
Generate the deploy code for the process by mapping the Send service port to the service file that you created earlier for the MQ application.
将Send服务端口映射到先前为MQ应用程序创建的服务文件，以生成流程的部署代码。
By contrast, when running as a non Fastpath or standard application an agent process called amqzlaa provides the separation between the mq application and queue manager.
相反，当作为非Fastpath或标准应用程序运行时，名为amqzlaa的代理进程将提供mq应用程序和队列管理器之间的分离。
When writing an MQ application, consider pulling messages off the queue as soon as possible and deciding whether to process them immediately or to send them to a failure queue.
在编写MQ应用程序时，考虑尽快从队列提取消息，并决定是立即处理它们还是将它们发送到故障队列。
The result of this is a message that can be read as a text message from any MQ client application.
最后得到的是可以从任何MQ客户机应用程序作为文本消息读取的消息。
Many enterprises have realized the advantages of MQ technology, and would like other application areas to benefit in the same way.
许多企业已实现了MQ技术的优点，并希望其他应用程序领域也以同样的方式获益。
Additionally, it allows polling of application metrics such as transaction rates and times, MQ queue manager status, message counters, or SLM metrics.
另外，它允许对应用程序指标轮询，如事务率和时间、mq队列管理器状态、消息计数器或SLM指标。
The interpretation of the message is left to the application domain; the MQ infrastructure imposes no semantics or structure onto the message.
对消息的解释留给应用程序域来做；MQ基础结构不对消息施加任何语义和结构限制。
When an enterprise application uses the MQ messaging provider to connect to a queue manager, there are two primary ways in which this connection is made.
企业应用程序使用MQ消息传递提供程序连接到队列管理器时，共有两个主要方法来进行此连接。
In the previous step, you configured the SCA Export with MQ messaging bindings, thus enabling the application to receive messages (inbound) from an MQ-based messaging client.
在前面的步骤中，您使用MQ消息传递绑定配置了sca导出，从而使应用程序能够从基于MQ的消息传递客户端接收消息(入站)。
For example, IBM CICS now provides direct SOAP support, and many systems and application packages can support MQ or SOAP interfaces.
例如，IBMCICS目前直接提供对SOAP的支持，以及许多系统和应用程序包能够支持MQ或SOAP接口。
It would normally be better, though, to use MQ clustering techniques to achieve this, giving each application server its own queue manager.
但是在通常情况下，一种更好的解决此问题的方法是使用MQ集群技术，这将为每个应用程序服务器提供自己的队列管理器。
Serializes the application objects into an MQ LLM message buffer.
序列化应用程序对象到一个MQLLM消息缓存。
The major impacts of WebSphere MQ on application design.
WebSphereMQ对应用程序设计的主要影响。
This article demonstrates how to configure an SSL connection between a JMS application and an MQ queue manager running on Windows 2000.
本文演示了如何配置JMS应用程序和运行在Windows 2000上的mq队列管理器之间的SSL连接。
For example, Message Broker might take data from SAP, and using MQ, send it to an enterprise application running on CICS.
例如，MessageBroker可能使用MQ从SAP取得数据，并将数据发送到运行在CICS上的企业应用程序。
The order entry application writes the MQ Everyplace message to a remote queue defined in the local queue manager.
订单输入应用程序将MQEveryplace消息写入本地队列管理器中所定义的远程队列。
We created a service wrapper which uses the WebSphere MQ protocol to connect to that legacy application.
我们创建一个服务封装器，其使用WebSphereMQ协议与以前的应用程序相连。
In particular, complete installation of the WebSphere MQ client facilitates the application of maintenance and patches, as well as the querying of the installed version.
特别是，WebSphereMQ客户机的完全安装便利了应用程序的维护和修补，以及对所安装版本的查询。
Configuring a JMS application for MQ message classification.
为JMS应用程序配置MQ消息分类。
One of the challenges in debugging is that there are often many layers of system code between the application and the WebSphere MQ API.
调试中的一大挑战就是应用程序和WebSphereMQAPI之间往往存在多层系统代码。
After the application connects to the WebSphere MQ queue, it calls the toolkit to have it dispatch the messages from the queue.
应用程序连接WebSpheremq队列之后，需要调用该工具箱，发送队列中的消息。
A JMS application communicates with WebSphere MQ queue managers via these administered objects.
JMS应用程序通过这些受管理对象与WebSpheremq队列管理器通信。
When the broker runs as a trusted application, WebSphere MQ API calls are processed more efficiently.
当代理作为可信应用程序来运行时，WebSphereMQAPI调用被更高效地处理。
Now that those tools are accessible to every size shop — from global enterprises to a WebSphere MQ client-based application on a laptop — the security model can catch up to the architecture.
既然现在这些工具可由各种规模的企业—从全球企业到便携式计算机上的一个基于WebSphereMQ客户机的应用程序—访问，安全性模型就能适应架构变化的要求。
The steps are the same as before and install and modify the application to use WebSphere MQ JMS section.
步骤与前面的安装和修改应用程序以使用WebSphereMQjms一节相同。
The data exchanged between the database and WebSphere MQ flows through the application — not efficient for high volume data and necessitating a transaction manager.
数据库与WebSphereMQ之间交换的数据要经过应用程序——如果有大量的数据需要交换，那么这显然效率不高，而且必须要有一个事务管理器。
The messages that need to be processed in a sequence are put into the MQ Ext Queue by the client application.
需要按顺序处理的这些消息由客户机应用程序放入MQExtQueue。
应用推荐