So the ESB is the ideal habitat for a BPEL engine.
因此，ESB是BPEL引擎理想的栖息地。
In this article, we'll only look at the BPEL engine component of Process Server.
在本文中，我们只介绍ProcessServer的BPEL引擎组件。
I wouldn't be surprised if a vendor pitched a BPEL engine as a choreography product.
要是哪个供应商声称一个BPEL引擎是某种编排产品，我也不会感到奇怪了。
The main strength of a BPEL engine is the ability to orchestrate a business process.
BPEL引擎的主要优点是能够编排业务流程。
BPEL engine: The BPEL engine implements your process-execution layer's execution logic.
BPEL引擎：BPEL引擎实现流程执行层的执行逻辑。
The standard way of executing processes in the SOA world is the use of a BPEL engine [2].
在SOA的世界中，执行流程的标准方式是使用一个BPEL引擎[2]。
In response, the partner service responds by sending a SOAP response back to the BPEL engine.
相应地，合作伙伴服务会做出响应，并而向BPEL引擎发回一个SOAP响应。
The specification defines a message exchange protocol between the BPEL engine and a task component.
这个规范定义了BPEL引擎和任务组件之间的消息交换协议。
So the choice that most people have made to standardize on a BPEL engine is the right choice... by far.
因此，大多数人将BPEL引擎作为标准选择是正确的……目前为止是这样。
CreateInstance specifies whether the BPEL engine will create a new instance of the process being executed.
createInstance指定BPEL引擎是否要创建正在执行的流程的一个新实例。
However, WS-BPEL engine is needed to integrate the different services and to implement the complex process.
整合不同的服务、实现各种复杂流程需要WS - BPEL引擎来实现。
A composition often manages the state of its services, similar to what a BPEL engine would do for its composed services.
组合常常对其服务的状态进行管理，与BPEL引擎处理其所组合的服务的方式相似。
You can however use WCF as a service container implementing services that can be invoked from SCA and your favorite BPEL engine.
但是，你可以将WCF当作服务容器实现服务，你可以从SCA和你喜爱的BPEL引擎中调用这些服务。
The data that the BPEL engine needs to maintain relates to the domain models like customers, clients, suppliers, products and so on.
BPEL引擎需要维护的数据和领域模型(如顾客、客户、提供商等等)有关。
For example, a transaction could wrap the fetch from a JMS queue that is then sent to a BPEL engine and persisted as a variable in a flow.
例如，事务将从JMS队列中获取的内容打包，之后发送给BEPL引擎，同时作为一个流程变量被持久化。
After receiving the production order, the BPEL engine executes all the steps of the merged production workflow, which I discuss in a moment.
收到生产指令之后，BPEL引擎就会执行合并的生产工作流程的所有步骤，我稍候再对此进行讨论。
Another strength of a WS-BPEL engine such as WebSphere process Server, is the ability to have a long-running business process where state is maintained.
WS - BPEL引擎(如websphereProcessServer)的另一个优点是能够让业务流程长时间运行并维持其状态。
SCA will let you choose the most appropriate invocation mechanism of a decision service (running in process with your BPEL engine if it is technically possible).
SCA会让你选择决策服务的最佳调用机制（技术上可行的话，它可以和你的BPEL引擎一起运行在过程中）。
Tuscany USES Apache ODE as a reference WS-BPEL engine, and ships part of ODE with its distribution. As for what's next, the following items come from a discussion on the subject.
Tuscany使用ApacheODE作为一个参考的WS - BPEL引擎，同时利用了随这一发行版发布的部分ODE。
WS-BPEL is a language for defining processes that can be executed on an orchestration engine.
WS - BPEL是一种用来定义可以在一个编制引擎中执行的过程语言。
The flow between processes and applications is better handled with a WSFL flow engine and even best with BPEL, not with a state diagram.
流程和应用程序间的流用WSFL 流引擎来处理更好，最好用 BPEL 来处理，尽量不要用状态图处理。
A first way to address this would be to use a common, well-known orchestration solution like full blown, externally deployed, BPEL-supporting orchestration engine [2].
解决这个问题的第一种方法是，使用一种常见、知名的编配解决方案，如成熟、外部部署、支持BPEL的编配引擎[2]。
A business process execution engine that understands BPEL will provide the resources to make all of this happen.
理解BPEL的业务流程执行引擎将提供实现所有以上任务的资源。
Once a process is described using the BPEL XML flow language, a business process engine must interpret the process description in order to execute and manage the business transaction.
一旦用BPELXML流语言描述了流程，业务流程引擎就必须解释流程描述以便执行和管理业务事务。
A model of a business process described using the BPEL XML grammar can be interpreted by a business process engine and executed.
使用BPELxml语法描述的业务流程模型可以由业务流程引擎来解释和执行。
However, the use of the coordination and transaction facilities will be managed by the business process engine based on the structure of the BPEL process description.
但协调工具和事务工具的使用将由业务流程引擎根据BPEL流程描述结构来管理。
Process container — provides engine that executes the (BPEL) business processes.
Process包容器——提供执行(BPEL)业务流程的引擎。
BPEL documents are executable scripts that can be interpreted using a business process engine to implement the described process. The steps for externalizing a system are as follows.
BPEL文档是可执行的脚本，可以使用业务流程引擎来解释它以实现所描述的流程。
The difference in this case are: there is only a single web-facing HTTP binding component and there are two different BPEL service engine components that each implement the same service (epB.)
这个示例中的不同点在于：这里只有一个面向Web的HTTP绑定组件和两个不同的BPEL服务引擎组件，每个引擎组件执行相同的服务（epB）。
SCA's conversational interfaces provide what BPEL refers to as engine-managed correlation, which removes the need for developers to specify correlating information explicitly.
SCA的会话接口提供了被BPEL称为“引擎管理的关联（engine- managed correlation）”的功能，这让开发者不必再显式指定关联信息。
应用推荐