Modeling considerations
When you are developing a model into a Business Process Execution Language (BPEL) process that can be used as an application, you can perform certain tasks to simplify the process.
Short-running and long-running processes
If you want the model to generate a BPEL process and your client is not persistent, avoid modeling short-running and long-running processes as parallel branches of a fork in a single process.
Business processes that are exported as BPEL can be used with a short-running client, for example, a JavaServer Pages (JSP) client. The processes are divided in two BPEL processes: a short-running BPEL process from which the JSP gets a quick response, and a long-running BPEL process that fulfills the requirements of the application. If this is the architectural pattern to be used in your implementation, enforce the technical pattern in the modeling to ensure that developers or integration developers can use the generated BPEL process. You can avoid modeling short-running and long-running processes as parallel branches of a fork by structurally separating the processes that require immediate completion (short-running processes) from processes that might not require a response or might take time to respond (long-running processes). If you separate processes in this manner, you can use a short-running process that calls a long-running global process. If you model the long-running process as a one-way process, the short-running processes do not wait for a reply.
Artifact transformation from IBM WebSphere Business Modeler to IBM Integration Designer
IBM Integration Designer works with artifacts that follow the Business Process Execution Language (BPEL) specification. A model intended for further development must be imported as a set of BPEL artifacts.
To make the artifact transformation from IBM WebSphere Business Modeler to IBM BPM artifacts as smooth as possible, see the related topic "IBM Integration Designer export reference" and its subtopics, in the IBM WebSphere Business Modeler documentation, particularly about the mapping elements and details. The topics in this section explain how artifacts in the process model will be transformed for use with IBM Integration Designer and IBM BPM.
The business analyst and process architect should agree on the names of the interfaces, inputs, outputs, and namespace so that both people can work comfortably with the application. To aid cooperation, the business analyst should work in IBM BPM mode.
Export a clean project
Resolve errors before you export the model for use in IBM Integration Designer. Errors will disrupt the merging of the model changes into the development application, because some references will be unresolved.
Export using the IBM Integration Designer option
The IBM Integration Designer export option provides a project interchange file that divides business logic from implementation details. In effect, this structure divides the process into a project that should be controlled by the business analyst and another project that should be developed by the integration developer. The structure also places shared resources in a library and, most important, provides mapping metadata that can be used by synchronization tools to merge model changes into anIBM Integration Designer application.