Show Table of Contents
5.4. Importing Existing Processes
5.4.1. Importing Existing BPMN2 Processes
To import existing BPMN2 processes into the designer, select the import icon on the top menu in the Process Designer and select Import from BPMN2. The import menu provides two options:
- Upload an existing file from the local filesystem.
- Copy and paste the BPMN2 XML directly into the import dialogue box.
If a BPMN2 process has already been imported and a change to the process is required, the process should be edited in the process designer. Do not attempt to import the same process twice as the original process will not be overwritten.
When importing processes, it is important to note that the designer provides visual support for Data Objects, Lanes, and Groups. If the BPMN2 file being imported does not include positioning information for these nodes, they will need to be added manually.
(To import processes designed in JBoss Developer Studio, please refer to the BRMS Getting Started Guide).
5.4.2. Migrating jPDL 3.2 to BPMN2
Important
The migration tool for jPDL 3.2 to BPMN2 is an experimental feature and must be enabled by the user. Red Hat does not support the jPDL 3.2 migration tool.
Procedure 5.2. Enabling the jPDL 3.2 Migration Tool
- Stop the server.
- Locate jbpm.xml in the
server/profile/deploy/designer.war/profiles/directory. - Remove the comment tags around the JPDL migration plugin tool entry:
<!-- plugin name="ORYX.Plugins.JPDLMigration"/ --> - Save the file with the comment tags removed:
<plugin name="ORYX.Plugins.JPDLMigration"/> - Restart the server.
- Log onto the JBoss BRMS user interface and navigate to the process designer. The jPDL migration tool button has now been added to the process designer user interface.
Figure 5.1. jPDL Migration Tool
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.