These topics provide the concepts and step-by-step instructions
for creating modules, mediation modules, and libraries.
Modules and libraries
When building integrated business solutions with WebSphere® Integration Developer, you will create modules, mediation modules, and/or libraries to contain the resources and code.
Modules and libraries dependencies
When developing and deploying integration applications, you may need to declare dependencies for your modules, mediation modules, and libraries. Use the dependency editor to manage these required resources.
Business integration capabilities and roles
Through Eclipse, WebSphere Integration Developer provides a filtering function known as capabilities. With capabilities, you can choose to hide tools not used during business integration application development; at any time, you can choose to show those tools again.
Business Integration perspective and views
The Business Integration perspective provides simple, uncluttered views of essential resources so you can model and build business solutions. Unnecessary details and unused tools are hidden.
Documentation of resources
In addition to viewing resources, you may need to document the applications that you are building. WebSphere Integration Developer provides a tool to generate documentation for the resources in your modules, mediation modules, and libraries.
Business integration cheat sheets
WebSphere Integration Developer provides cheat sheets to guide you through some of its application development processes.
Tutorial: Work with modules and libraries
This tutorial teaches you how to create, view, and print modules, mediation modules, and libraries when working with the WebSphere Integration Developer tools.
Opening the Business Integration perspective
The Workbench window's title has the name of the perspective that you are using. Follow these instructions to open or switch back to the Business Integration perspective.
Creating a module for business services
A module is a WebSphere Business Integration project that is used for development, version management, organizing resources, and deploying to the runtime environment.
Creating a mediation module
A mediation module is a WebSphere Business Integration project that is used for development, version management, organizing resources, and deployment to the runtime environment. It contains flows that intercept and modify messages between service consumers (exports) and service providers (imports). Mediation modules can be deployed to the WebSphere Enterprise Server Bus or the WebSphere Process Server.
Creating the library
A library is a WebSphere Business Integration project that is used for the development, version management, and organization of shared resources. Only a subset of the artifact types can be created and stored in a library.
Adding dependencies to modules and libraries
Using the dependency editor, you can add dependencies on libraries and Java™ projects. For modules and mediation modules, you can also add dependencies on J2EE projects.
Changing default namespaces
Use Preferences to change the default template that will be used to create the namespaces of new artifacts that will be created.
Sharing your integration project
WebSphere Integration Developer provides the capability to develop applications in a team environment by allowing you to share resources with a central repository. Through eclipse, WebSphere Integration Developer provides a client for the Concurrent Versions System (CVS).
Enabling tools capabilities
Use capabilities to limit the functions that are available to the user. There are several ways you can enable and disable tool capabilities.
Showing all documentation in the information center
By default, only the WebSphere Integration Developer book is enabled in the Help. The product's capabilities support is used to hide documentation not related to the business integration tools.
Generating documentation
You can generate documentation for the resources in your modules and libraries.
Best practices: Modules and packaging for business services
When developing business integration applications, you may need to work with resources such as JSP files, JAR files, Web projects, Java projects, and J2EE projects. This topic provides information to help you set up your projects and resources so that they can be successfully built and deployed to WebSphere Process Server.
Best practices: Mediation modules and packaging
When developing mediation service applications, you may need to work with resources such as JSP files, JAR files, Web projects, Java projects, and J2EE projects. This topic provides information to help you set up your projects and resources so that they can be successfully built and deployed to WebSphere Enterprise Server or WebSphere Process Server.
Best practices: Changing an external service without interruption
When you are designing a system or developing modules, you sometimes gain advantages by placing an intermediary module between a module and an external service that it is invoking. You can only use the approach described here if you are using SCA bindings.