IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing business processes > Building BPEL processes > Versioning BPEL processes

Late binding using a partner link extension

When you late bind one process to another one, the connection is resolved dynamically in the runtime environment. In that situation, the calling process will always pick up the currently valid version of the process that it is invoking. New instances will always use the latest version of the process, and if you use the migration verification tools you can also migrate running instances to the latest version.

These instructions assume that you have already created a process that is the caller and another process that is being invoked.

If your BPEL process is under control of a process application or toolkit, read the topic, Invoking different versions of a process, in the related link section.


Procedure

  1. Open the caller process in the BPEL process editor.

  2. Create a new Reference Partner in the caller process and name it Inventory.

  3. In the Description tab for this Reference Partner:

    1. Click Browse next to the Namespace field to select the namespace.

    2. Click Browse next to the Target process field to select the invoked BPEL component for the target process.


Results

This late binds the caller process to the invoked process. It can also generate a CWSCA8015W warning. You can ignore this warning because this target is dynamically selected in the runtime environment.

Versioning BPEL processes


Related concepts:
Process Migration Specification


Related tasks:
Create a new version of your process - migrate running instances
Create a new version of your process - running instances use old version
Create versions of your process to be used with SCA components and exports

Invoking different versions of a process