You can develop service applications that, when deployed onto WebSphere ESB, enable message-based
communication between services and can operate on and manipulate messages
in flight between interaction endpoints.
Why and when to perform this task
WebSphere Integration Developer is
the development environment for
WebSphere ESB.
You can use
WebSphere Integration Developer to
graphically model and assemble mediation components from mediation primitives,
and assemble mediation modules from mediation components.
- If the interface for SCA mediation components are not imported, you can
use the Simplified Interface Editor to create the interface. You can use this
editor to specify and edit interfaces (operations and parameters) of mediation
modules.
- You can use the Mediation Flow Editor to map between operations on the
end points of a mediation, to define the set of mediation flows needed for
this application. You can use a set of predefined mediation primitives to
visually compose a mediation flow.
- When developing a service application that is to be deployed into a secure
environment, use the service component architecture (SCA) qualifiers for security:
- SecurityPermission to secure access to interfaces or methods.
- SecurityIdentity if the SCA component is to run under an identity defined
in the runAs role.
WebSphere Integration Developer simplifies
the task of declaring services and defining their interconnections. You can
also use WebSphere Integration Developer to
create and edit message descriptors through a set of business-oriented visual
editors. You can use the Business Object Editor to construct the messages
that are used in mediations.
After developing a service application,
best practices state that you should deploy the application onto a test server
for testing before committing it to the production requirement. To deploy
the applications into a test environment, you can use WebSphere Integration Developer.
To
deploy the applications into a production environment, you use WebSphere ESB.