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

Importing a Visio XML Drawing File

Importing a Visio XML Drawing File

The Visio drawing used in your workspace can be based on BPMN shapes. You import it into a workspace project.
You can import a Visio XML drawing from Visio 2010 Premium (or later) that is created with the BPMN template or flowchart using BPMN shapes. Other types of Visio drawings cannot be converted to BPEL.
To import the file:
  1. Save it as an XML drawing with the .vdx extension.
  2. Select
    File > Import > Orchestration > Visio XML Drawing
  3. Select a Visio file from your workspace or the file system. The file must have the .vdx extension.
  4. Select a project folder location for the file. For example, select the "bpel" folder of an orchestration project.
  5. If needed, type in a name (or keep the default) for the files being converted to BPEL. You may need to supply a name if the file includes multiple pools. If a Visio file contains multiple pools, each pool is converted to one BPEL file. Multiple pools are not supported in one BPEL file. Process Developer automatically adds the .bpel extension.
  6. If needed, you can overwrite an existing BPEL file.
Tips on converting Visio files:
  • The Visio file is not imported into your project. The import wizard converts the Visio file to BPEL.
  • The Scale factor creates the BPEL process with a default amount of space between activities. The scale factor is a Visio measure unit (by default in inches) to convert to pixels in Process Developer. If the default of 150 creates a BPEL process that displays too much space between activities, try setting the value to 100. Alternately, in Process Developer, select
    Auto Layout
    to improve the placement of activities on the canvas.
  • Messaging data that exists between pools is not supported. In Process Developer, you must create a process-to-process or process-to-subprocess invoke handler in the Process Deployment Descriptor.
  • Be sure to view the Errors and Problems views to see messages generated from the conversion


Updated March 30, 2020