As shown in figure 2, you should see the Started Server log message.
您将看到已启动的服务器日志消息，如图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.
然而，在一般情况下，当两个节点在单独的消息流中时(例如，图2)，您需要自己将必要的相关性信息转发给应答流。
Listing 2 shows a typical message exchange for this service.
清单2显示了服务的一个典型的消息交换。
You should see a message congratulating you on deploying the application successfully (Figure 2).
您应该能看到一条祝贺您应用程序部署成功的消息（图2）。
If you do not have both of those, you will get the message shown in Figure 2.
如果您没有这两样，那么您就会得到如图2所示的信息。
Figure 2 shows the success message.
图2显示了一个成功消息。
Notice that a dotted line guide shows you exactly where the message set will be dropped (see Figure 2).
注意一个带点的线将会向您显示消息集合的精确位置(如图2所示)。
The response, message 2, supplies the SCT to the client.
此响应，消息2，则向客户机提供了此sct。
As shown in Listing 2, the response message works the opposite way.
如清单2所示，响应消息按相反的方式处理。
See Listing 2 for the response to the SOAP message.
请参阅清单2了解对SOAP消息的响应。
A corresponding example message to illustrate how the configuration directs message creation is shown in Listing 2.
清单2中给出了一个相应的示例消息，演示了该配置如何指导消息的创建。
Create a port type, an operation, and an input message as in Figure 2.
如图2所示，创建一个端口类型、操作和输入消息。
UDDI version 2 has modified some existing message APIs and changed the version identifier on all incoming and outgoing messages.
UDDI版本2修改了一些已有的消息api，并改变了所有进入和发出的消息上的版本标识符。
Listing 2 shows that each WSDL message has two WSDL parts and each part refers to a global element.
清单2显示每个WSDL消息有两个WSDL部分，每个部分引用一个全局元素。
Once the connection is successful, you will get a message indicating success as shown in Figure 2.
连接一旦成功，您就会获得显示成功的消息，如图2所示。
The essential aspects of this message transfer code are shown in Listing 2.
该消息传递代码的基本内容如清单 2所示。
Listing 2 shows the XML output message that is produced by the map.
清单2给出这个映射产生的XML输出消息。
Section 2 of the message flow extracts the schema from the WSDL document that is passed as part of the logical tree from the HTTP node.
消息流的第2部分从http节点作为逻辑树的一部分传递的WSDL文档提取模式。
The basic structure of a SOAP message is shown in figure 2.
SOAP消息的基本结构如图2所示。
We will use the "Scenario 2" message flow with the addition of a filter node.
我们将使用“场景2”中的消息流，并添加一个筛选器节点。
Scenario 2: Batch processing with message enrichment.
场景2：使用消息充实的批处理。
Table 2 lists the properties of a message stereotype.
表二列出了一个消息原型的属性。
For example, a message published at QoS 2 to a subscriber that specified QoS 1 for that topic is delivered at QoS 1.
例如，以QoS2向订阅者发布的消息，若订阅者指定此主题的级别为QoS1，那么主题就会以QoS 1传递。
The output from Listing 2 shows a log message with a time stamp in uppercase
清单2的输出显示了一个大写的、带时间戳的日志消息
You see the SQL0440N error message from Listing 2 for object TEST.v2.
您会在清单 a 中看到 TEST.v2对象的SQL0440N错误消息。
The code in listing 2 publishes a message to indicate that Air Freedom's flight 1024 has arrived at London Heathrow Airport (LHR).
清单2中的代码发布的消息表明AirFreedom的1024次航班已经抵达伦敦希思罗机场(LHR)。
Figure 2: Synchronous, reliable message delivery.
图2：同步的、可靠的消息传递。
To implement this portlet, first define an interface to abstract the implementation details of the message store (Listing 2).
为了实现这个portlet，首先要定义一个接口以对消息存储器的实现细节进行抽象(清单2)。
Open test/reports/html/index.html in your Web browser to see the error message shown in Figure 2
在Web浏览器中打开test/reports/html/index.html，您将看到如图 2所示的错误消息。
The alphaWorks implementation also supports Web services integration by providing an Apache Axis 2 message handler, which you can install in the Axis 2 request flow.
该 alphaWorks实现还提供了ApacheAxis2消息处理程序来支持Web服务集成，可将其安装到 Axis 2 请求流中。
应用推荐