图3显示了简单的请求流，其中Input节点(表示来自Export1的请求)与中介组件接口关联。
Figure 3 shows the simple request flow in which the Input node (representing the request from Export1) is associated with the mediation component interface.
在图13中所示的此示例Messagebroker流中，SRRetrieveEntity节点用于从特定实体检索所有元数据内容。
In this sample Message Broker flow shown in Figure 13, the SRRetrieveEntity node is used to retrieve all metadata contents for a specific entity.
该模式采用图19所示的消息流，通过TCP/IP接收数据，使用WebSphereTX节点进行解析，然后将数据写入到 WebSphere MQ队列。
This pattern uses a message flow shown below in Figure 19, which receives data over TCP/IP, parses it using a WebSphere TX node, and writes it to a WebSphere MQ queue.
然而，在一般情况下，当两个节点在单独的消息流中时(例如，图2)，您需要自己将必要的相关性信息转发给应答流。
However, in general when the two nodes are in separate message flows (for example, Figure 2), you need to forward the necessary correlation information to the reply flow yourself.
图12显示测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 12 shows the network stream throughput and CPU utilization for the test runs while using the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图3显示双向可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 3 shows the network stream throughput and CPU utilization for the bidirectional scalability test runs while using the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图6显示双向可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 6 shows the network stream throughput and CPU utilization for the bidirectional scalability test runs while using the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图6展示了居中节点所实现的双向工作流。
Figure 6 depicts bidirectional workflow implemented by the middle node.
图1显示netserver可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 1 shows the network stream throughput and CPU utilization for the netserver scalability test runs while using the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图5显示netperf可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 5 shows the network stream throughput and CPU utilization for the netperf scalability test runs while using the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图7显示netserver可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 7 shows the network stream throughput and CPU utilization for the netserver scalability test runs while using the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图11显示netperf可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 11 shows the network stream throughput and CPU utilization for the netperf scalability test runs while utilizing the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图4显示netserver可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 4 shows the network stream throughput and CPU utilization for the netserver scalability test runs while utilizing the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图8显示netperf可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 8 shows the network stream throughput and CPU utilization for the netperf scalability test runs while utilizing the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图2显示netperf可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 2 shows the network stream throughput and CPU utilization for the netperf scalability test runs while utilizing the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
图10显示netserver可伸缩性测试的网络流吞吐量和系统cpu利用率，分别使用SUT中1、2和4个节点上的系统板载以太网适配器。
Figure 10 shows the network stream throughput and CPU utilization for the netserver scalability test runs while utilizing the system board Ethernet adapters on 1, 2, and 4 nodes of the SUT.
在图15所示的中介流中，任何请求处理必须发生在Router自定义中介元素之前，并且任何响应处理必须发生在InputResponse节点之前。
In the mediation flow shown in Figure 15, any request processing must occur before Router custom mediation primitive, and any response processing must occur before the InputResponse node.
如果使用Route节点替代floworder节点来执行与上文相同的订购流程，请考虑图3中的消息流。
To perform an identical customer ordering process to the above, replacing the FlowOrder node with the Route node, consider the message flow in Figure 3.
图7显示了自动从采用“Automatic”模式的Timeout Notification节点为Timeout Control节点生成控制消息的流。
Figure 7 shows a flow that automatically generates a control message for the TimeoutControl node from a TimeoutNotification node in "automatic" mode.
XMLT技术示例的 XMLT_Sample_Flow消息流演示了如何使用该节点，样式表将图1中的输入消息转换为图2 中的输出消息。
The XMLT_Sample_Flow message flow from the XMLT technology sample demonstrates the use of the node, and the stylesheet will transform the input message in Figure 1 into the output message in Figure 2.
图1展示了一个涉及CICSRequest节点的样例消息流。
A sample message flow involving the CICSRequest node is shown in Figure 1 below. The nodes used in this message flow are.
图1展示了一个涉及CICSRequest节点的样例消息流。
A sample message flow involving the CICSRequest node is shown in Figure 1 below. The nodes used in this message flow are.
应用推荐