Administration Console > Catalog, Reports, and Custom Faults > Catalog
  

Catalog

Enter a short description of the concept here (required).
This is the start of the concept.

Understanding Contributions

The Contributions page lists all business process archive (BPR) deployments. Their names are based upon the Process Developer project from which they were deployed.
Contribution Page
Just as Process Developer keeps together all files in an orchestration project, a contribution is a unit of the deployable processes and resources from a project. It is a unique deployment to the server catalog. As developers update their projects, they can deploy new contributions while maintaining earlier ones on the server.
Here is some information about contributions:
For details, see Contribution Detail.
What Happens When a Contribution is Updated
When a BPR contribution is deployed for the first time, Process Server tags the contribution and every file in the deployment as version 1.0, and the contribution is online. Subsequently, as developers make changes, they may update, add, or delete files and then repdeploy the same BPR. Tthe new version becomes the online version and the old version is offline pending, eventually becoming offline when all executing processes complete.
The following scenarios illustrate what happens in the Process Server catalog when a contribution is updated.
Contribution changes from V1 to V2 -- Process1 is modified, Process2 is removed
Deployment 1
project:/MyProject V1
Deployment 2
project:/MyProject V2
Changes on the Server
process1.bpel
process1.bpel (modified)
V2 is online, V1 is offline or offline pending, if it has associated process instances.
process.private.wsdl
process.public.wsdl
not modified
V1.01 is online. V1 is offline. With each deployment, WSDL and XSD are incremented to avoid cache issues.
process2.bpel
(not included)
The process is no longer in the catalog.
Contribution changes from V1 to V2 -- All original files are removed, a new one is deployed
Deployment 1
project:/MyProject
Deployment 2
project:/MyProject V2
Changes on the Server
(myAVOS.avcconfig does not exist)
myAVOS.avcconfig
This file is deployed as an "Additional Resource" and is the only file deployed in the same BPR as previous deployment. V1 is online. This is the only file online because it is the only file in Contribution V2. To get all files back online, redeploy the BPR and include all files.
process1.bpel
(not deployed)
BPEL file is removed
process.private.wsdl
process.public.wsdl
(not deployed)
WSDL files are removed
For each contribution, basic version information is displayed, as shown in the table.
Item
Description
Contribution
The base URI, usually the Process Developer project name, such as project:/myProject
Version
Deployed version
State
By default, online state is displayed; for information, see the description of all states below this table
Date
Date the contribution was deployed
Group
Group this contribution belongs to, if any, as added in the Export Business Process Wizard in Process Developer
Deployer
Name of person (or system) who deployed, if authentication is required for deployers. The default is anonymous.
Contribution Versions
Contribution versions can have one of the following states:
Selection Filters
You can select the following Selection Filters to view a subset of contributions:

Contribution Detail

The Contribution Detail page displays a selected contribution version. You can change the state of the contribution or delete the contribution.
Contribution Detail page
Setting the State to Offline or Online
If the contribution state is online, it is the current version, and you can select Set to Offline. If there are other contribution versions, the next higher or lower version is set to online. If process instances are running against the BPEL files in the contribution, the contribution is set to Offline Pending. When all process instances complete, the state changes to Offline.
If the contribution state is offline, select Set to Online. The contribution’s files become the current version. If any BPEL was deployed with an online (effective) date, the process state is online pending.
Note that the state of BPEL processes within a contribution is the same as the state of the contribution itself, but you can individually select a BPEL process from an online contribution and change its state. For example, if three processes are included in an online contribution, you can take one, two, or all three processes offline.
Deleting a Contribution
Select Delete to remove the entire unit of files from the catalog. If running processes exist, the contribution goes to the offline pending state until the processes complete.
When you delete a contribution, the following events occur:
Contribution Detail Information
The information within this page is grouped into sections, and these are described in the following list:

Converting Legacy Deployments to Contributions

Process Developer 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 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 Process Developer, note that all BPR deployments prior to Version 8 are preserved as legacy contributions. On the Contributions page of the Process 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:
Note that as you redeploy your BPEL processes and associated resources, they are removed from the legacy:bpr.deployment and added as contributions.