IBM support for the asset production workflow.
IBM为资产生产工作流程所提供的支持。
Defining variables for the merged production workflow.
为合并的生产工作流程定义变量。
Hosting task layer for the merged production workflow.
托管合并的生产工作流程的任务层。
You're now all set to try your merged production workflow.
现在已经一切就绪，您可以尝试您的合并生产工作流程了。
Defining an XML schema for the merged production workflow.
为合并的生产工作流程定义XML模式。
Now I present the XML schema for the merged production workflow.
接下来，我将介绍合并的生产工作流程的XML模式。
I'll refer to this five-step sequence as a bulk-production workflow.
我将称这个五步的序列为批量生产工作流程。
The tag describes the service provided by your merged production workflow.
标记描述了合并生产工作流程提供的服务。
Each one describes a partner service that the merged production workflow invokes.
每个标记描述一个合并的生产工作流程所调用的合作伙伴服务。
Once again I will try to keep my post production workflow simple as possible.
再次申明，我将尽量简化后期制作的工作流程。
ProductionOrder holds the production order received by the merged production workflow.
productionOrder用于保存合并生产工作流程收到的生产指令。
You have defined variables to be used in your BPEL file for the merged production workflow.
您已经为合并生产工作流程定义了用于BPEL文件的变量。
The BPEL client will also display the response received from the merged production workflow.
BPEL客户机还会显示从合并的生产流程收到的响应。
The tag contains several tags, one for each variable you define for your production workflow.
标记中又包含了几个标记，它们分别对应您为生产工作流程定义的每个变量。
Now you know how to use BPEL to express the business logic of your merged production workflow.
现在您已经知道如何使用BPEL来描述合并的生产工作流程的业务逻辑。
You are now all set to start learning how to configure your merged production workflow in a BPEL file.
您现在已经准备就绪了，可以开始学习如何在BPEL文件中配置合并的生产工作流程了。
For example, compare Step 2 of the large-variety workflow with Step 2 of the bulk-production workflow.
例如，比较多种工作流程的第2步和批量生产工作流程的第2步。
Response holds the final response of the merged production workflow after execution of all tasks in the task layer.
response用于在执行任务层的所有任务之后，保存合并生产工作流程的最终响应。
Step 2 of the bulk-production workflow performs only one task (extracts a list of items from the production order).
批量生产工作流程的第2步只执行一个任务(从生产指令中提取需要生产的产品清单)。
The first simple production workflow would suit a production house that manufactures only a large variety of products.
第一个简单的生产工作流程适合于制造多种产品的生产工厂。
I'll refer to this three-step sequence of tasks as large-variety production workflow or simply large-variety workflow.
我将称这个三步的任务序列为多种生产工作流程或者简称为多种工作流程。
The better granularity of Step 2 in the bulk-production workflow allows it to fit directly into the merged workflow.
批量生产工作流程的第2步的粒度更细，这使得它可以直接融合到合并的工作流程中。
There is only one service that merged production workflow provides; that is, it receives and processes a production order.
合并的生产工作流程提供的服务只有一个，即接收并处理生产指令。
Provide multimedia object libraries, video footage, background music and sound effects as part of the production workflow.
提供多媒体物体图书馆、电影片段、背景音乐和音响效果作为制作流水线的一部分。
This production workflow is therefore quite different from the large-variety workflow. Consider its five-step sequence of tasks.
因此该生产工作流程与多种工作流程有很大差异。
The second tag imports a WSDL file named ProductionManagementSystem.wsdl, which represents the complete merged production workflow.
第二个标记导入了一个名为ProductionManagementSystem .wsdl的wsdl文件，这个文件代表整个合并的生产工作流程。
Part 2 will discuss the production-management schema and the WSDL that you require to implement your merged production workflow.
第2部分将论述实现合并的生产工作流程所需要的生产管理模式和WSDL。
Now I'll show how to define the sequence of tasks in your merged production workflow using the tag that you saw in Listing 2 of Part 1.
接下来，我将展示如何用第1部分清单2中的标记在合并的生产工作流程中定义任务序列。
The BPEL file and the deployment descriptor for the merged production workflow are included in this article's source code (see Download).
合并的生产工作流程的BPEL文件和部署描述符都包含在本文的源代码中(参见下载)。
After receiving the production order, the BPEL engine executes all the steps of the merged production workflow, which I discuss in a moment.
收到生产指令之后，BPEL引擎就会执行合并的生产工作流程的所有步骤，我稍候再对此进行讨论。
应用推荐