This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Deployment of BPEL processes and human tasks

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-01-20 10:38
Draft comment:
This topic was viewed 7 times since its publication
Use Integration Designer or the serviceDeploy command to package process components or task components in an enterprise application (EAR) file. Each new version of a model that is to be deployed must be packaged in a new enterprise application.

When you deploy an enterprise application that contains BPEL processes or human tasks, then these are stored as BPEL process templates or human task templates, as appropriate, in the Business Process Choreographer database. Newly deployed templates are, by default, in the started state. However, the newly deployed enterprise application is in the stopped state. Each deployed enterprise application can be started and stopped individually.

You can deploy many different versions of a process template or task template, each in a different enterprise application. The versions are differentiated by their valid-from dates. When you deploy a new enterprise application, the version of the template that is deployed is determined as follows:
  • If the name of the template and the target namespace do not already exist, a new template is deployed
  • If the template name and target namespace are the same as those of an existing template, but the valid-from date is different, a new version of an existing template is deployed
Note:
  • The template name is derived from the name of the component and not from the BPEL process or human task.
  • If your EAR file was created for a WebSphere® Process Server version earlier than 7.0, you must pre-process it by using the serviceDeploy command. This action is particularly important if you migrate process applications you haven't accessed for years. For more information about this command, see serviceDeploy command-line utility.
If you do not specify a valid-from date, the date is determined as follows:
  • If you use Integration Designer, the valid-from date is the date on which the human task or the BPEL process was modeled.
  • If you use service deployment, the valid-from date is the date on which the serviceDeploy command was run. Only collaboration tasks get the date on which the application was deployed as the valid-from date.