Figure: Eclipse-based Modeler - Convert Gateways
This chapter covers the following:
The Business Process Modeling perspective supports Web-based modeling. However, when it comes to importing models created in Stardust's Eclipse-based modeler to the Web-based modeler and vice versa, some restrictions are encountered. To ensure smooth deployment of models, you need to alter some of the elements in the model before you import. Following elements need special treatment either in Eclipse-based modeler or Web-based modeler:
Gateways need to have correct interpretation when you import the Eclipse-based model with gateways in the Business Process Modeling perspective. In the Business Process Modeling perspective, gateways are first class elements (you can drag-and-drop gateway symbol from the toolbar). However, there is no first class diagram element for gateways in the Eclipse-based modeler. That's why models created in Stardust's Eclipse-based modeler and to be imported in Web-based modeler should use the Convert Gateways functionality in Eclipse-based modeler.
If the model contains gateways, then right-click the process definition in Outline view and select Convert Gateways.
Figure: Eclipse-based Modeler - Convert Gateways
A route activity is created as first class element to represent the gateway, which can be imported in the Business Modeler.
Figure: Eclipse Model after Gateway Conversion
The control flow in this route activity is set to the type of the split or join control flow of the activity the gateway is referring to.
Figure: Route Activity - Control Flow
Once you convert gateways, you can import the model in the Web-based Modeler.
Figure: Gateways interpreted in Web-based Modeler
For more information on Convert Gateways functionality, please refer to the chapter Converting Gateways to a Business Modeler-compliant Format Converting Gateways to a Business Modeler-compliant Format of the Modeling Guide. Modeling Guide in the Stardust Documentation.
Gateways added in Web-based modeler are displayed in Eclipse-based modeler as route activities. The control flow property of the route activity is set according to the following rules:
Figure: Gateways interpreted in Eclipse-based Modeler
However, note that the route activity used for gateway in Web-based modeler acts as an auxiliary activity and hence, is not displayed anywhere in Stardust Portal.
Models created in the Eclipse-based modeler should support BPMN drawing mode (pools and lanes). When imported, only those models are displayed properly in the Business Process Modeling Perspective.
The Web-based modeler allows only:
In case multiple data mappings exist between a structured data and an activity, only the first data mapping is displayed.
The Web-based modeler supports setting conditional sequence flow only from gateways to activities. However, if you import a model created in Eclipse and it has conditional sequence flow from activity to activity. In that case, you can edit the transition condition in Web-based modeler. Also, you can save, deploy and execute the model in Web-based modeler.
In cross modeling, to maintain the references between the models, the imported referenced model should be kept in the same project folder. If the imported model resides at any other location then the references are not resolved by the Eclipse-based modeler and Web-based modeler.
The Eclipse-based models having IDs that are not Java conform identifiers may cause problems when imported to Web-based modeler. Currently, Web-based modeler cannot handle IDs that are not Java conform identifiers.
For compatibility issues with read-only models, refer to the section Eclipse Compatibility of Read-only Models of the chapter Model Properties.
Input access points are parameters of the completion method and output access point is the return value of the completion method. Only these access points are displayed in the Web-based modeler.
Models containing intermediate events may cause inconsistency warnings and errors when opened in the Eclipse-based modeler which may prevent direct deployment from the Eclipse-based modeler.
Only one event action can be defined per event in Web-based modeler.
| Eclipse Action Type | Handler Types | Web-based Modeler Action Type | Web-based Modeler Alternative |
|---|---|---|---|
| Abort Process | Timer, On Exception | Follows Exception Flow. A validation is performed whether a connection exists and a warning message is displayed in the UI. Also, on model deployment a warning/error message is displayed. | Create a model with exception flow to an End Event. |
| Abort Activity | Timer, On Exception | Follows Exception Flow | Set the Interrupt flag on the Event General Properties. |
| Delegate Activity | Timer, On Exception, On Activity State Change, On Assignment | Not supported | Delegation should be modeled with a Sequence Flow to another Task executed by a different Participant. |
| Send Mail | Timer, On Exception, On Activity State Change, On Assignment | Follow Exception Flow | Create a model with exception flow to a Mail Application |
| Process Trigger | Timer, On Exception, On Activity State Change, On Assignment | Follow Exception Flow | Create a model with exception flow to a subprocess. |
| Set Data | Timer, On Exception, On Activity State Change, On Assignment | Follow Exception Flow | This can be modeled with Route Activities or Message Transformation Applications |
| Activate Activity | Timer, On Exception, On Assignment | Not supported | No Alternative |
| Complete Activity | Timer, On Exception, | Follow Exception Flow | No Alternative |
| Schedule Activity | Timer, On Exception, On Activity State Change | Not supported | No Alternative |
| Exclude User | On Assignment, | Not supported | No Alternative |
The Stardust supports creation of workflow models in two ways. Firstly, you can create models in the Stardust's Eclipse-based modeler and secondly, in the Business Process Modeling perspective of Stardust. However, when you import model created in Eclipse-based modeler, some of the model elements are not supported in Web-based modeler. For those unsupported elements, you should use Stardust's Eclipse-based modeler.
Following is the list of supported elements. That means, you can add, edit, delete and rename these elements.
| Element | Type |
|---|---|
| Manual Trigger | Lifecycle |
| Scan Trigger | Lifecycle |
| Camel Message Event | Lifecycle |
| Camel Timer Event | Lifecycle |
| End Event | Lifecycle |
| Document Data | Data |
| Primitive Data | Data |
| Structured Data | Data |
| Structure Type | Data |
| Message Transformation Application | Application |
| Camel Application | Application |
| UI Mashup Application | Application |
| Web Services Application | Application |
| None Task | Activity |
| Manual Task | Activity |
| User Task | Activity |
| Service Task | Activity |
| Script Task | Activity |
| Send Task | Activity |
| Receive Task | Activity |
| Subprocess Activity | Activity |
| Role | Participants |
| Organization | Participants |
| Conditional Performer | Participants |
Unsupported elements are displayed in My Process Models panel and Process Diagrams view but you can only edit General Properties of these elements.
Following table summarizes the operations for unsupported elements:
| Function | Supported | Not Supported |
|---|---|---|
| Create | - | Not Supported |
| Edit | Only General Properties are editable | Other specific properties such as, class name for Java application type are not editable |
| View | Only General properties are displayed | Other specific properties such as, class name for Java application type are not displayed |
| Rename | Supported | - |
| Delete | Supported | - |
Also, the message is displayed for each unsupported element in its General Properties page.
Figure: Unsupported Model Element
Following is the list of unsupported model elements.
| Element | Type |
|---|---|
| Document List | Data |
| Folder | Data |
| Folder List | Data |
| Entity Bean | Data |
| Hibernate Data | Data |
| XML Document | Data |
| Serializable Data | Data |
| DMS Application | Application |
| JMS Application | Application |
| Mail Application | Application |
| Message Parsing Application | Application |
| Message Serialization Application | Application |
| Plain Java Application | Application |
| Session Bean Application | Application |
| Spring Bean Application | Application |
| XSL Message Transformation Application | Application |
| JFC Application | Application |
| JSF Application | Application |
Following pre-defined primitive data are not supported.
Note that the Default Diagram is also not supported.
The following functionality, which is available in the Eclipse modeler, is not yet available n the Business Process Modeler: