Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Managing Deployment Contributions

Managing Deployment Contributions

Add resources to deploy to the server.
A
contribution
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.
Contribution Name
Each contribution has a project-location-based identifier. On the Contributions page of the Process Console, you see a list of
project:/myProject
files. Each contribution is named according to your workspace project name. In the
.BPRD
file, you can view an attribute named
contributionURI
that is based on the project name:
project:/myProject
. This location hint is a helpful way to track deployments on the server.
Contribution States
Contributions have the following states: online, offline, and offline pending.
Your first deployment is version 1.0 and is
online
. As you update and redeploy your files, older contributions go
offline pending
and the new one comes online.
Only one version is online. The older versions become
offline
when all running processes associated with the
offline pending
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.


Updated March 30, 2020