is a deployed business process archive (BPR), managed on the server as a unit of files. Rather than deploy and replace individual BPEL processes and resources, you deploy both current and updated files as a unit that is easily managed on the server.
If you are deploying one of the Process Developer sample projects, it should only have one sample-based contribution.
Each contribution has a project-location-based identifier. On the Contributions page of the Process Console, you see a list of
files. Each contribution is named according to your workspace project name. In the
file, you can view an attribute named
that is based on the project name:
. This location hint is a helpful way to track deployments on the server.
Contributions have the following states: online, offline, and offline pending.
Your first deployment is version 1.0 and is
. As you update and redeploy your files, older contributions go
and the new one comes online.
Only one version is online. The older versions become
when all running processes associated with the
version have completed.
Server Management of Contributions
Using contributions, it is easy to do the following tasks on the server:
Delete all old process instances and old resources by deleting the contribution.
Maintain your own resources that do not collide with those of other developers.
Rollback the current (online) contribution to an earlier version and vice versa.
Easily access the deployment log for the contribution on the Contribution detail page.
Contribution Deployment Tips
To maintain the ease of use for contributions, be sure to follow these deployment tips:
Always deploy a project reference contribution prior to deploying the parent contribution. For details, see
Using Project References
Maintain one BPR per project. Include all deployable files in the BPR. Use the Export Wizard to redeploy.
As you update project resources, re-deploy the entire project
As you add a new resource, re-deploy the entire project.
As you delete resources, re-deploy the entire project.