This will ensure that you do not interfere with any triggering that might already be set up on the test queue manager. Go ahead and define these now.
这将确保您不会干扰可能已经在测试队列管理器上设置好的任何触发机制。
For our test with only one triggered queue, there is almost no difference in behavior between these options.
鉴于我们的测试只有一个已触发队列，这些选项的表现几乎没有任何区别。
You can delete the files and remove the message from the queue to prepare for the next test.
您可以删除这些文件并从队列删除这条消息，以准备下一次测试。
The next step is to write a simple test script that adds an entry to the queue.
下一步是编写一个简单的测试脚本，这个脚本将一个条目添加到队列中。
In the original test client, we sent a plain string to the queue.
在最初的测试客户机中，我们向队列发送一个普通字符串。
For instance, when moving a compiled message flow from a test domain to a production domain that contains different queue and data source names, the same compiled message flow can be used.
例如，在将已编译的消息流从测试域移动到包含不同队列和数据源名称的生产域的时候，可以使用相同的已编译消息流。
Have the injector applications connect (using bindings) to a local queue manager and use MQ networking to move the messages onto the test system.
将注入器应用程序连接(使用绑定)到本地队列管理器，并且使用MQ网络将消息移到测试系统中。
This article outlined the concepts and basic architecture of MI queue mangers and MI brokers, and explained and how to create, configure, manage, and test these MI components for high availability.
本文简述了mi队列管理器和mi代理的概念和基本架构，解释了如何创建、配置、管理和测试这些mi组件以获得高可用性。
Whether or not the plans and environments for test and production differ, it is always possible to find problems when migrating the production cluster queue managers.
无论测试和生产的计划和环境是否一致，总是会在迁移生产集群队列管理器时发现问题。
It is reasonable to leave days between migrating each queue manager in the cluster, in order to test applications before wholly committing all queue managers to run at the new version.
在迁移集群中的各个队列管理器之间最好间隔几天，以便在所有队列管理器完全在新版本下运行之前测试应用程序。
Because the new queue manager can peacefully coexist with the existing one, it is possible to test much of the deployment well ahead of cutover.
由于新的队列管理器可以与现有的队列管理器和平共存，因此可以在切换之前充分测试该部署。
Document and test the plan before migrating production queue managers.
在迁移生产队列管理器之前要测试计划并创建文档。
We'll also demonstrate how to configure the message queue connector to accept these messages, and how to place a test CBE message onto the expected JMS queue to test the configuration.
我们还将演示如何配置消息队列连接器来接受这些消息，以及如何在预期jms队列上放置测试CBE消息，以测试配置。
The order of queue execution is variable: An optional feature, on by default, will reorder test execution based on results of a previous run, yet still showing the results in order.
测试的执行顺序是变化的：这是一个可选的功能，默认会根据上一次执行的结果重新排列执行顺序，但结果还是按照之前的顺序显示。
For the non-SACK test cases, I used the typical length of the delayed ACK queue reported by the client as an approximation of the lower bound of the sender's window size.
对于非sack测试用例，我使用客户机报告的延迟应答队列的典型长度作为发送方窗口大小的近似值。
Queue execution is stopped when a test indicates that it needs to run asynchronous, and restarted once that test indicates its done.
当某个测试需要异步执行时，会等到测试执行结束后再执行下一条。
Test the connection by sending a message from the client to the WebSphere MQ queue manager.
通过将消息从客户端发送到WebSphereMQ队列管理器来测试连接。
Enter the queue manager name as TEST and click Next.
输入队列管理器名称TEST并单击Next。
The Test Client shows a message placed on the PROVIDER queue by the message flow, as shown in Figure 15 below.
TestClient显示一条消息流放置在provider队列上的消息，如下面的图15所示。
If you have taken more than three minutes between sending the Web service request and writing the response message to the response queue, then the Test Client may have timed out.
如果发送Web服务请求和将响应消息写到response队列之间的时间超过3分钟，那么TestClient将超时。
To simplify the test, a simple servlet (JMSReader) that receives a message from the queue is available with this article.
为了简化测试，本文中提供了一个用来从队列中获取消息的简单的servlet (JMSReader)。
Provide a test message payload with the following format (Figure 12) : Click put message to put the message to the queue.
使用以下格式提供测试消息负载(图12)：单击PutMessage将消息放入到队列中。
Next, change the name of the queue that the test message will be sent to since, instead of sending the message to the queue the MDB listens on, you want the message sent to the WebSphere ESB export.
接下来，更改接收测试消息的队列的名称，因为您不想将消息发送到mdb侦听的队列，而是希望将消息发送到WebSphereES b导出。
If no VM is available or the VM is available but the socket is not active, put the StereoCable in the working queue for processing, specifying the roles and test environment that it needs.
如果没有vm可用，或者有VM可用但插座没有激活，就把这个StereoCable放在要处理的工作队列中，指定它需要的角色和环境。
Queue manager names should be unique in the MQ network and reflect the location, function, and environment of the queue manager (dev, test, etc.).
队列管理器名称在MQ网络中应该是唯一的，并反映队列管理器的位置、功能和环境(dev、test等)。
If issued at regular intervals during a normal production or test cycle, you can capture and track the number of messages that have been processed during that interval and the queue high depth.
如果在正常的生产或测试周期中按一定的间隔发出此命令，则可以捕获和跟踪在此期间已处理的消息数量和队列最高深度。
After rerunning your test, you'll be able to trap messages being sent and examine them in the queue, as shown in Figure 26.
运行测试之后，您将能够捕获在队列中发送的消息，并对其进行检查，如图26中所示。
For this test scenario, I adopted the Point-to-Point domain, and wrote a simple application to place a message on the queue.
针对该测试案例，我采用点到点(Point -to - Point)域，并编写了一个简单的应用程序来将消息放到队列中。
The component test harness Events window is updated to reflect the writing of the requested number of messages to the JMS queue, as shown in Figure 9.
componenttestharnessEvents窗口进行了更新，以反映请求的消息数量被写入到jms队列中，如图9所示。
This section Outlines the steps needed to test the high availability of the queue manager, ha.queue.manager.
本节列出了测试队列管理器ha . queue . manager的高可用性所需要的步骤。
应用推荐