Project structure exported from IBM WebSphere Business Modeler
In order to use the tools that support iterative development between the model and the application, projects should be imported into IBM Integration Designer in a specific format, consisting of two modules and a library.
A model that is developed in IBM WebSphere Business Modeler should be exported in a particular structure if it will be further developed in IBM Integration Designer. The pattern is generated by selecting IBM Integration Designer from the IBM WebSphere Business Modeler export wizard. If the two products are operating in a shell-sharing environment, you can use Recommended Export Option to export directly to the development workspace. Using either of those options, IBM WebSphere Business Modeler generates the following project structure for use with IBM Integration Designer:
- Business logic module
- This module will contain the artifacts describing the business logic.
- The artifacts that are placed in this module are the main BPEL process, inline human tasks (TEL files), BPEL artifacts, exports, and imports.
- Shared library
- The library will contain all supporting artifacts shared by the business logic and the implementation modules.
- The artifacts that are placed in the library are business objects and WSDL interfaces for all components.
- Implementation module
- This module will contain the artifacts that are to be implemented by the integration application developer.
- The artifacts that are placed in this module are components, exports, imports, and component implementation skeletons (BPEL, Java™, TEL, BRG, SACL, and WSDL bindings).
Most of the artifacts owned by the business analyst are in the business logic module. Most of the artifacts that would be developed by the integration developer are in the implementation module. Both would work with libraries.
You should inspect the imported projects. In some cases, you might need to do some customizing.