引入的请求能够路由到外部伙伴链接。
BPEL称这些链接为合作伙伴链接。
WSDL文件定义了合作伙伴链接类型。
用于BPEL文件中的合作伙伴链接名。
伙伴链接绑定。
您也将会发现他们被引用在BPEL流程内部生成的伙伴链接中。
You will also find them referenced in the generated Partner Links inside the BPEL process.
如果是一个伙伴发生操作调用，则合作伙伴链接类型就必定只有一个角色。
If invocations of operations from one partner occur, the partner link type must have one role.
稍候我将在链接到您的服务合作伙伴部分详细论述合作伙伴链接。
I'll discuss partner links in detail later, in Linking to your service partners.
举例来说，正如我们前面已经提及，用于伙伴链接的所有绑定信息将必须指定。
For instance, as we mentioned already, all the binding information will need to be specified for the Partner Links.
与伙伴链接中BPEL过程角色相对应的服务会在部署过程的时候发布。
The service that corresponds to the BPEL process role of a partnerlink is the one that will be published during deployment of a process.
单击browse…来指定包含服务合作伙伴链接类型的WSDL文件。
Click Browse... to specify the WSDL file that contains the service partner port type.
您最后需要做的事情就是，为用于调用活动的合作伙伴链接分配服务端点。
The last thing you need to do is assign the service endpoint to the partner link you use for your invoke activity.
还需要在BPEL文件中定义相同的合作伙伴链接，如清单5 所示
The same partner link also needs to be defined in your BPEL file, as shown in Listing 5
这个流程部署步骤为通过合作伙伴链接使用的真实服务和流程本身创建绑定。
This process deployment step creates the bindings for actual services used through the partner links and the binding for the process itself.
伙伴链接在部署时被捆绑在一起，因而可以在不改变流程结构的条件下替换服务供应者。
Partner links are bound at deployment time, therefore service providers can be substituted without changing the process structure.
例如，对于Process组件，变量视图显示BPEL变量和合作伙伴链接。
For example, in the case of the Process components, the variables view shows the BPEL variables and Partner Links.
只在使用非静态的服务绑定时使用这两个lob；可选伙伴链接，代表到外部服务的连接。
Both LOBs are used only if a non-static binding of services is used; optional Partner links, which represent connections to external services.
从BPEL过程到伙伴的服务调用和伙伴对BPEL过程的调用都关联到伙伴链接。
Both service invocations from the BPEL process to a partner and invocations by a partner to the BPEL process are associated with partner links.
伙伴链接(partner links)用来标识那些参与BPEL过程通信的外部团体。
Partner links identify external parties with which the BPEL process is able to communicate.
如果两个合作伙伴互相对话，也就是说，双方都调用各自伙伴的操作，此时伙伴链接类型就有两个角色。
If two partners are talking to each other, that is, both are invoking operations of their partner, the partner link type has two roles.
伙伴链接类型(请参见下一部分)进一步定义了合作伙伴链接，并且有别于业务流程中其他元素的名称。
A partner link type (see next section) further defines the partner link, and has a name which distinguishes it from other elements in the business process. It looks as follows.
除了要对活动进行排序，流程的BPEL描述包含服务端口类型、操作和通过合作伙伴链接引用的消息类型。
In addition to the ordering of activities, the BPEL description of a process includes service port types, operations, and message types which are referenced through partner links.
因此，您需要为每一个合作伙伴服务在BPEL和WSDL文件中定义合作伙伴链接(BPEL -WSDL链接)。
Therefore, you need to define partner links (BPEL-WSDL links) in your BPEL file and in WSDL files for each partner service.
BPEL文件和合作伙伴链接：BPEL文件是一个XML文件，您要在该文件中配置流程执行层的业务逻辑。
BPEL file and partner links: the BPEL file is an XML file in which you configure the business logic of your process-execution layer.
BusinessProcess Choreographer进一步加强了此限制，因为无法基于相关集和伙伴链接区分传入消息。
Business Process Choreographer tightens this restriction further, since it cannot distinguish incoming messages based on correlation sets or partner links.
因此，WS-BPEL 要求，在任何给定时间，对于每个端口类型、操作、相关集和伙伴链接，每个流程实例只能有一个请求-响应操作。
Therefore, WS-BPEL claims that only one request-response operation per process instance may be active at any given time for each port type, operation, correlation set, and partner link.
并且每一个伙伴链接都定义了很多操作，这些操作可以是在内部实现的操作，甚至可以是映射到为执行任务而调用的外部服务中的操作的操作行为。
A partner link defines operations that may be implemented internally or may even map to operations in external Web services that may be invoked in order to fulfil the task.
然后您应该在运行时计算端点引用，并且在运行时将这些分配给合作伙伴链接引用(本系列的下一篇文章将包含更多这方面的详细信息)。
Then you should compute the endpoint reference at runtime and assign that with the partner link reference during run-time (the next paper in this series will include more details on this).
将新的InvokeOrderValidation活动连接到上面创建的合作伙伴链接和操作以及输入和输出流程变量，如图15所示。
Wire the new InvokeOrderValidation activity to the partner link and operation and to the input and output process variables you created above, as shown in Figure 15.
我如何在WebSphereProcessServer中的BPEL流程内跨多个合作伙伴链接调用保留soapHeader字段？
How do I preserve SOAP header fields across multiple partner link invocations within a BPEL process in WebSphere process Server?
应用推荐