To do Step 4, we need to mediate a destination to transform the reply message.
要完成第4步，我们需要将目的地作为中介来转换应答消息。
Step 12: the SE internally denormalizes the message and invokes the required business logic.
第12步：SE在内部将消息解除规范化并调用所需业务逻辑。
Step 6: the SE internally denormalizes the message and invokes the required business logic.
第6步：SE在内部将消息解除规范化，并调用所需的业务逻辑。
They also add an unnecessary extra step to what should be a fairly simple message.
他们还在本应非常简单的信息里添加了不必要的额外步骤。
Step 3: The BC transforms the service invocation request into a normalized message.
第 3步：BC 将服务调用请求转换成规范化消息。
Step 6: the BC connected with the second JBI environment denormalizes the message.
第6步：连接到第二个JBI环境的BC将消息解除规范化。
Refer to Option 1 Step 3 to see an excerpt of the message log.
参考选项1 -步骤3查看一个消息日志节选。
The goal of this step is to determine whether the message has been flagged as invalid.
这一步的目的是确定消息是否被已被标记为无效。
Refer to Option 1 Step 3 to see the excerpt of the message log.
参考选项1 -步骤3查看一个消息日志节选。
Message digested. The next step is to respond.
信息消化完毕，下一步是做出回应。
This data is highlighted, in the sample XML transaction message below, which would represent step 4 in Figure 2.
下面的示例XML事务消息突出显示了该数据，它表示图2中的步骤4。
After this step is complete, the WSRR nodes will become operational within the message flow.
完成此步骤以后，WSRR节点将在消息流中变得可操作。
When you conclude this step, the SOAP for CICS message adapter for the existing program WBCSCUST is now ready to process service requests.
当结束该步骤后，用于CICS的SOAP消息适配器（用于现有的WBCSCUST 程序）可处理服务请求。
The first step is to set the transport for the message.
第一步是为消息设置传输方式。
The final step is to receive the XML message from the queue and deserialize the instance.
最后一步是从队列接收XML消息，并反系列化实例。
Step 4: the BC hands over the normalized message to NMR.
第4步：BC将规范化消息移交给nmr。
Step 5: The NMR forwards the normalized message to the BC connected with the second JBI environment.
第 5步：NMR 将规范化消息发送给连接到第二个 JBI 环境的BC。
The initial step is to process the SIP INVITE message and respond with a 200 OK.
初始步骤是处理SIPINVITE消息并使用一个200OK进行响应。
Step 6: Process the response message.
步骤6：处理响应消息。
Step 4: Compose a request message.
步骤4：编写请求消息。
Step 6: Test the end-to-end message flows.
步骤6：测试端到端的消息流。
Use the saved Message Digest signature (see step 2, above) to verify the integrity of the retrieved image.
使用保存的MessageDigest签名(参见上面的第2步)检查接收到的映像的完整性。
In Step 10, the CalculatorMessageListener receives the notification message.
在步骤10,calculatormessagelistener接收通知消息。
Let us step through the message flow that occurs when the client sends a request; the step Numbers correspond to those in Figure 1.
让我们一步一步地完成客户机发送请求时发生的消息流；步骤编号与图1相对应。
Once the match action is place, click and drag the AAA step into the message processing policy as shown in Figure 53.
选择了匹配操作后，单击并将AAA步骤拖放到消息处理策略，如图53所示。
When this step completes, you will receive a successful confirmation message below the Upload button.
这个步骤完成后，您将在Upload按钮下接收到一条操作成功确认消息。
The last step implements the message transformation, here we remove the WS-Security header and generate an LTPA token (at the transport level) built on the mapped identity (the role "Guest").
最后一步实现了消息转换，在这里，我们删除了WS - Security头并生成一个建立在映射身份(角色“Guest”)上的ltpa令牌(在传输级别)。
Step 5. Send the SOAP message to the Web Service end point
步骤5.将SOAP消息发送到Web服务端点
TTC (Trace Template Children) produces a message for every step of processing within the template, allowing you to see the stylesheet's execution in much more detail.
TTC （跟踪模板的子模板，Trace TemplateChildren） ，为模板中的每个处理步骤生成一条消息，从而允许您更详细地查看样式表的执行。
Hardware-accelerated high performance, multi-step, wire-speed message processing for XML -, XSLT -, and XPath-based transformations and XML schema validation.
通过硬件加速为基于XML、XSLT和XPath的转换和XML模式验证实现高性能、多步和快速消息处理。
应用推荐