WebSphere Process Server allows
you to view and change aspects of service applications using the administrative
console.
Service applications provide services, and have an associated Service Component Architecture (SCA) module.
The type of SCA modules that
are supported by enterprise service bus are mediation modules.
Viewable SCA module details
After
you have deployed an EAR (Enterprise ARchive) file containing an Service Component Architecture (SCA) module,
you can view SCA module details.
You can list all your SCA modules,
and their associated applications, and you can view details about a particular SCA module.
The
SCA module details you can
view include some of the following.
- SCA module name.
- Associated application.
- SCA module imports.
- SCA module exports.
- SCA module properties.
Modifiable SCA module details
After
you have deployed an EAR file containing an
SCA module you
can change the following
SCA module details
using the administrative console, without having to redeploy the EAR file.
- Import bindings of
type SCA and Web service.
- Changing import bindings lets
you change service interactions.
- SCA bindings connect SCA modules to
other SCA modules.
- One SCA module can
interact with a second SCA module,
and be changed to interact with a third SCA module.
- Web service bindings connect SCA modules to external services using SOAP.
- Import bindings of type Web service (WS).
- Changing import bindings lets you change service interactions.
- WS import bindings allow SCA modules to access web services. A WS import
binding calls a service located at a specified endpoint. You can change the
end point such that the binding calls the service at an alternative end point,
or even an entirely different service with compatible interfaces.
- Mediation module properties.
- Mediation module properties
belong to the mediation primitives with
which they are associated. However, the WebSphere Process Server administrative
console displays some of them as Additional Properties of
an SCA module. The integration
developer must flag a mediation primitive property
as Promoted in order for it to be visible from WebSphere Process Server.
- Changing mediation module properties
lets you change the behavior of your mediations. The mediation changes that
you can make depend upon the properties that have been promoted.
Note: An export with no binding specified is interpreted
by the runtime as an export with an SCA binding.
Figure 1. Example
showing one mediation module interacting with another mediation module.
MediationModule1 connects to MediationModule2
Figure 2. Example showing one mediation module interacting with another
mediation module.
MediationModule1 connects to MediationModule3
Last updated: Wed 06 Dec 2006 07:08:08
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)