Converting Legacy Deployments to Contributions

ActiveVOS Designer User’s Guide

Converting Legacy Deployments to Contributions

ActiveVOS Version 8.0 introduces contributions. A contribution is a deployed business process archive (BPR), managed 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. For details, see Managing Deployment Contributions.

If you are upgrading to a new version of ActiveVOS, note that all BPR deployments prior to Version 8 are preserved as legacy contributions. On the Contributions page of the Administration Console, you will see one or more entries named legacy:/bpr.deployment The newest deployment has the status of online. Previous deployments have the status of offline pending.

We highly recommend that you delete old BPRs and redeploy your processes and resources to take advantage of contribution features.

Here are some recommendations for converting your old deployments:

Delete old BPRs and BPRDs from a project. You will create just one new BPR/BPRD per project. The BPR treats all deployable project files as a unit that is easily managed on the server.
(Recommended). In your project, create a folder to hold all non-deployment files, such documentation files and unused resources. This is recommended, but is not required. You can add this folder to a list of excluded folders for deployment. See Contribution Preference for details.
(Recommended). If your project is using WSDLs from another workspace project, you can specify that project as a project reference to manage those WSDLs in a separate contribution. For advantages to this approach, see Using Project References.
Create and export a new project-based business process archive. Notice that the new Export Wizard automatically includes all deployable resources in your project and excludes test and sample data files.
Be sure to deploy all deployable files each time you redeploy, even if you have only updated one or two files. Deploying an updated individual resource creates an undesirable version of a contribution.

Note that as you redeploy your BPEL processes and associated resources, they are removed from the legacy:bpr.deployment and added as contributions.