Activities performed within the context of a business process may have to execute application logic. This application logic is defined by a concept called application. For more details on applications, refer to chapter Applications in our Concepts documentation. Applications in our Concepts documentation.
The following sections describe how to work with applications in the Modeling perspective.
The following application types are supported in the Modeling perspective:
Chapter Using imported Plain Java Applications gives details on how to use imported Plain Java Applications, which are not supported for editing in the Modeling perspective, but can be imported to be used for modeling.
To create any of the application types listed above, perform the following steps:
Figure: Create Application
Now you can set application properties as described in the application type specific chapters.
If you add application parameters using a Firefox browser, it might happen that the parameter list is not updated. Please clear your browser cache in that case. Note that the whole cache should be deleted from beginning of time.
To rename an application, right-click the application name in the Applications node and select Rename .
Figure: Rename Application
You can rename applications either in the My Process Models panel, the property panel of the element or by simply double-clicking the element in the Process Diagram canvas.
To delete an application, right-click the application and select Delete in the Applications node.
Figure: Delete Application
To view and edit the properties of any application, select the application under the Applications node in the My Process Models panel.
Figure: Select Application
The property page of the selected application gets displayed with tabs for specific property settings. The following properties are common for most applications:
The following properties are available in the general properties section of an application:
Figure: Properties - UI Mashup Application
Note that the UUID and ID options are displayed only when you switch to the Integrator profile.
The configurable retry mechanism is available for all applications except UI Mashup and Decorator. It provides the facility to retry the operation in case the target service is temporarily unavailable.
For more information, please refer to section Retry Mechanism of Non-interactive Applications of chapter Applications. Retry Mechanism of Non-interactive Applications of chapter Applications in our Concepts documentation.
For example, you have added an application to the model. In the Property page of the application, you can enable the retry, specify number of retries and time between retries. However, note that a maximum of 10 retries and not more than 60 seconds between two retries are allowed. So, the application retries for the defined number of times with a pause of the defined number of seconds, until it has success. If the application still fails after the defined number, it no longer retries.
Optionally you can add comments for an application in the Comments tab. Enter a comment in the text field and click Submit.
All submitted comments are listed below the entry field. The newest comment gets displayed at the top.
To delete one or more comment(s), select it/them in the list and click the Delete icon.
Figure: Deleting a Comment
Note that only the user who has submitted a comment, can delete this comment. If one of the selected comments was created by another user or if no comment is selected, the Delete icon is disabled.
The Service Wrapper Process Wizard allows creating a process definition with SOAP and/or REST interface based on a service application, without the need to model it manually. It supports service definition with one IN and OUT access points on a structured data type only. The Request Data (any Structured Data Type in the same model) and Response Data (any Structured Data Type in the same model) are used as IN and OUT formal parameter of the process interfaces created. A Service Wrapper Process can be transient and/or persistent (default).
Figure: Create Service Wrapper Process Wizard
If the application has In and Out access points of types other than structured type or more than one In and one Out access point, an error message is displayed instead of the service wrapper dialog.
Figure: Error Message
If the Create Test Wrapper Process check box is selected, another test process is created. This process can be used as manual test process to invoke the original process from within the process portal and not via SOAP and/or REST.
Figure: Service Wrapper Process Wizard
Under the model node, the following elements get created:
Figure: Service Wrapper Process
Figure: Test Process - Service Wrapper Process as a Subprocess
In case you want to create a test process after the wrapper process is created, right-click the wrapper process and select the option Create Interface Test Process. The test process gets created.
Figure: Create Interface Test Process
This creates a test process to test your original process.
Figure: Interface Test Process
Specify the following details:
The created wrapper process becomes Auxiliary process, by default.
If the Public Visibility check box is selected in the application property page, then it can be referenced from a consumer model. To reference the application, drag and drop the application from the provider model to the consumer model.
Figure: Dragging and dropping the application to a Consumer model
Based on the application type, it gets converted to appropriate task types.
Figure: Referenced Application converted to Script Task
For more information, please refer to the section Dragging and Dropping of Elements of the chapter Swim Lanes Usage.