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

Converting Legacy Deployments to Contributions

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:
  • 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.


Updated March 30, 2020