Business processes evolve over time. They need to reflect changing environments and business needs. These changes might be business-driven changes, such as changes in regulations, or optimizations of processes. Business-process applications can include long-running BPEL instances. These instances can run for weeks, months, or even years. This characteristic imposes specific requirements on the introduction of new versions of BPEL processes.
To create a new version of your BPEL process, you create a new version of a module in Integration Designer. Make the changes that you need to the new version of the process, give the new version a valid-from date if the process is not part of a process application or toolkit, and then deploy it to your runtime environment. If you want to enable the migration of existing process instances to the new version, you must also define a process migration specification in Integration Designer, and deploy it together with the new version of the process.
After the new version of the process is deployed, new process instances can be created from the new version of the BPEL process. Existing instances continue to complete using the version that they were created and started with, or depending on the nature of the changes to the process, they can be migrated to the new version. In some situations, for example, when you want to correct an error in the process, you might also want to migrate the running instances of a process to the newer version so that they complete using this version.
In process applications or toolkitsA BPEL process that is part of a process application or a toolkit is versioned through Process Center. In Process Center, BPEL processes are versioned as part of snapshots of the corresponding process application or toolkit. The following properties uniquely identify a process version on a deployment target.
For training on IBM Lombardi mail us at [email protected]
To create a new version of your BPEL process, you create a new version of a module in Integration Designer. Make the changes that you need to the new version of the process, give the new version a valid-from date if the process is not part of a process application or toolkit, and then deploy it to your runtime environment. If you want to enable the migration of existing process instances to the new version, you must also define a process migration specification in Integration Designer, and deploy it together with the new version of the process.
After the new version of the process is deployed, new process instances can be created from the new version of the BPEL process. Existing instances continue to complete using the version that they were created and started with, or depending on the nature of the changes to the process, they can be migrated to the new version. In some situations, for example, when you want to correct an error in the process, you might also want to migrate the running instances of a process to the newer version so that they complete using this version.
In process applications or toolkitsA BPEL process that is part of a process application or a toolkit is versioned through Process Center. In Process Center, BPEL processes are versioned as part of snapshots of the corresponding process application or toolkit. The following properties uniquely identify a process version on a deployment target.
- A process version that is part of the process application, or part of a toolkit that is referenced by a process application can be identified in one of the following ways:
- Process application acronym, process application snapshot name, and process name
- Process application snapshot ID and process name
- A process version that is part of a top-level toolkit (a top-level toolkit is not referenced by a process application), or part of a toolkit that is transitively referenced by the top-level toolkit can be identified in one of the following ways:
- Top-level toolkit acronym, top-level toolkit snapshot name, and process name
- Top-level toolkit snapshot ID, and process name
- Invoking different versions of a BPEL process
You can invoke a specific version of a process (early binding), or dynamically invoke the version of a process that is currently valid (late binding). - Migrating running process instances to a new version of the BPEL process
When you introduce a new version of a BPEL process, you might want this version to apply to both new process instances and to instances that have already started. This can be important in environments where changes to processes are needed frequently, but where an individual process instance can be relatively long-lived. In such cases you need to migrate the process instances that are running to the newer version.
For training on IBM Lombardi mail us at [email protected]
RSS Feed
