结果事件原语格式化结果事件。
结果事件反过来生成一个或多个动作。
将结果事件添加到处理动作的中介流中。
将此结果事件重命名为Recheck。
文章中没有介绍结果事件。
将自动生成结果事件。
什么是结果事件？
下面，您需要添加原语以将结果事件格式化到中介流。
Next, you need to add the primitives for formatting result events to the mediation flow.
人工事件是取代交互块中的某个操作而被使用的结果事件。
Synthetic events are result events that are used instead of an action in an interaction block.
在下一小节中，我们将把结果事件添加到动作的处理流程中。
In the next section, we'll add result events to the processing of actions.
现在让我们创建一个结果事件，操作方法和附带项目中的方法一样。
Now let's create a result event, as we did in the attached project.
这个导入用于将结果事件提交到BusinessEvents以便处理。
The import is used to submit result events to Business events for processing.
作为动作流的一部分，一个结果事件被发送到BusinessEvents。
As part of the action flow, a result event is sent to Business Events.
导出结果事件模式并将其导入IntegrationDeveloper。
Export the result event schema and import it into Integration Developer.
这些结果事件有助于进一步形成BusinessEvents能够识别的模式。
These result events can contribute to further patterns that Business Events can identify.
这个非常简单的项目定义了一个事件、一个动作、一个结果事件和该结果事件生成的动作。
This very simple project defines one event, one action, one result event and the action it generates.
以两个新原语的形式添加了格式化结果事件以发送到BusinessEvents的支持。
Support for formatting result events to send to Business events has been added in the form of two new primitives.
操作连接器也可以返回结果，该结果放在入站消息队列中，并且可以将其作为结果事件进行评估。
An action connector may also return a result, which is placed on the inbound message queue and can be evaluated as a result event.
要使ESB成为一个完整的BusinessEvents连接器，它需要能够发送结果事件。
In order for ESB to be a full Business events connector, it needs to be able to send result events.
首先，我们看看结果事件是什么，它们在什么时候有用以及如何在DesignData中定义它们。
First, let's look at what result events are, when they're useful and how to define them in Design Data.
要定义名为“Recheck statusafter7days”的结果事件，请执行以下操作
To define a result event called "Recheck status after 7 days:"
然后，我们查看处理动作流的ESB 流如何将结果事件发送到BusinessEvents 中。
Then we'll see how an ESB flow processing action flow can send result events into Business Events.
通过将该结果事件连接到一个表示Business Events的JMS导入实现实际的发送。
The actual sending is achieved by wiring it to a JMS import representing Business Events.
如何将特定于esb的信息添加到结果事件并将结果事件从esb流发送到BusinessEvents。
How to add ESB-specific information to result events and how to send result events from an ESB flow into Business events.
我们将向您展示如何将事件发送到BusinessEvents，如何处理动作，以及如何添加结果事件。
We'll show you how to send events into Business events, how to process actions and how to add result events.
然后WSDL文件将转换为Touchpoint 部分中的接触点、操作和结果事件，如图11 所示。
The WSDL file will then be transformed to touchpoint, action, and result events in the Touchpoint section, as shown in Figure 11.
结果事件定义后，可以像其他事件一样在BusinessEvents中使用。可以定义由于它的到达而触发的到中间对象的映射和交互集。
Once the result event is defined, you can use it in Business Events like any other event, you can define mappings to intermediate objects and interaction sets triggered by its arrival.
没有这个功能，ESB将不能成为一个真正的BusinessEvents连接器，基于结果事件的Business Events的交互集将不能作为ESB流程动作触发。
Without this function, ESB would not be a proper Business events connector and Business events interaction sets based on result events will not be triggered is ESB processes actions.
结果取决于条件以及事件如何发展。
The outcome depends on conditions as well as how events unfold.
我们今天看到的是进化事件的产物，是大约6万到7万年前少数人类从非洲迁徙而来的结果。
What we see today is the product of evolutionary events, resulting from the dispersal of a few human populations out of Africa around 60,000 to 70,000 years ago.
应用推荐