这将使用工作流队列为工作流传递请求。
This will use the well-known workflow queue for passing requests to workflow.
表单不仅显示一条记录，而且为用户提供一系列工作流选项：拒绝、修改并继续、转到另一个Web服务、转向其他人或者工作流队列。
The form not only displays a record but also gives the user a list of workflow options: reject, fix and continue-processing, route to another Web service, or route to another person or workflow queue.
在场景1中，大量消息被发送到数据流并通过集群中的两个队列管理器进行处理。
In Scenario 1, a large number of messages are sent to the flow and processed by both queue managers in the cluster.
每个流定义了一组源目的地(例如，一组主题和队列)和一个目标目的地(消息将发往该目的地)。
Each flow defines a set of source destinations (for example, a set of topics and queues) and a target destination to which the messages are to be delivered.
典型的消息代理系统经常将以异步方式处理来自相同流或并行队列的多个请求。
A typical message broker system will often be processing multiple requests from the same stream or queue in a parallel, asynchronous manner.
最初的例子为流使用队列对象。
清除队列可以避免为测试和调试流带来混乱。
Clearing queues avoids confusion when testing and debugging flows.
注意，数据库和队列存储类型的流使用自定义中介原语来记录请求到达的事实。
Notice that the flows for the database and queue storage types use custom mediation primitives to record only the fact that the request has arrived.
在PROVIDER队列上的消息包含一个消息标识符，生成的消息流使用它将请求和响应关联起来。
The message on the PROVIDER queue contains a message identifier, which is used by the generated message flows to correlate the requests and responses.
正如下面约束与限制部分中所述，消息流必须仅访问JDBCxa数据源和mq队列，而不是其他OD BC数据源或资源管理器。
As noted in the Restrictions and Limitations section below, the message flow must access only the JDBC XA data source and MQ queues, and not other ODBC data sources or resource managers.
数据流充当值的绑定队列，因此可以通过代码定义的结构灌注数据，保留相同的有益属性。
Dataflow streams act as bounded queues of values, so data can be poured through the structure defined by the code, maintaining many of the same beneficial properties.
企业需要访问广泛的信息，比如XML、消息队列、文档、流视频和其他富媒体类型。
Companies need access to a wide range of information such as XML, message queues, documents, streaming video, and other rich media types.
响应消息流从response队列读取消息。
The response message flow read your message from the response queue.
响应消息流等待RESPONSE 消息队列。
The response message flow waits on the RESPONSE message queue.
连接基于普通的TCP客户端流，所以用户仍然能访问原始数据管理、发送队列管理等功能。
Connection is based off a vanilla TCP client stream so a user still has access to those features: raw data management, send queue management et cetera.
使用下面展示的JmsProducer实用工具将消息发送到网关队列管理器，然后后者会将消息发送到消息流的输入队列。
Use the JmsProducer utility as shown below to send the messages to the gateway queue manager, which in turn will send the messages to the input queues of the message flows.
在部署消息流之前，您还需要创建模式所需的队列。
Before you deploy the message flows, you will create the queues required by the pattern.
在本例中，您还需要创建额外的WebSpheremq队列，其中将错误和日志消息流写入其消息。
In this example, you will also need to create additional WebSphere MQ queues where the error and log message flows will write their messages.
不单是音频流更小，但也少得多复杂得多访问您的Netflix队列。
Not only is an audio stream smaller, but also far less complex than accessing your Netflix queue.
通过利用点对点队列，以及通过MQ使是事件流负荷从入站边保持平衡，可以确保没有复制事件被BusinessEvents接受。
Through the use of point-to-point queues and having the event stream load balanced by MQ from the inbound side, you can ensure that there are no duplicate events being received by Business Events.
现在，使用ASCII数据流为现有的IBM 6252(名为lp0)打印机创建一个名为atc _ QUEUE的新本地打印队列。
Now create a new local print queue named ATC_QUEUE with an ASCII data stream for an existing IBM 6252 printer named lp0.
该流匹配它发送到response队列的请求消息。
The flow matched up the request message it sent to the PROVIDER queue.
可配置特性提供了一种机制，在这种机制下，不用重新编译流应用程序即可配置系统对象名称(例如，数据库连接或MQSeries队列的名称)。
Configurable properties provide a mechanism for system object names (such as database connections, or the name of an MQSeries queue) to be configured without recompiling a flow application.
例如，在将已编译的消息流从测试域移动到包含不同队列和数据源名称的生产域的时候，可以使用相同的已编译消息流。
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.
如果一个组中的所有端点的所有令牌都已分配出去，那么仲裁流请求将储存在一个fifo队列中，直至有令牌转变成未占用状态。
IF all tokens of all endpoints in the group are assigned, the mediation flow request is stored in a FIFO queue until a token becomes free.
退出队列是一个单线程操作，即使消息流本身配置为多实例时也是如此。
Dequeuing is single threaded, even if the message flow itself is configured for multiple instances.
解析后的数据布局被放到消息流的末端，其后紧接着被写入到名为OUT .QUEUE的输出队列的消息。
This parsed data layout was taken at the end of the flow, immediately before the message was written out to the output queue named OUT.QUEUE.
流控制和队列——除了请求分类外，ODR负责控制请求流，此功能允许根据所定义的标准更改请求流。
Flow control and queuing - Besides the request classification, the ODR is responsible for controlling the flow of requests, which allows it to change the request flow based on defined metrics.
当流启动时，我们刚刚放进输入队列的消息由流来处理，转换成XML，并放入到输出队列Q.OUT。
Since the flow is started, the message that we just put in the input queue should be processed by the flow, transformed into XML, and put in the output queue Q.OUT.
到达生成的消息流中的Web服务请求将被放入到一个队列中，这是使用MessageBroker需要解决的常见问题。
Web service requests arriving at the generated message flow will be put onto a queue, which is a common problem to be solved using message Broker.
应用推荐