WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Service application features of the administrative interfaces

WebSphere® ESB allows you to use the administrative console to view and change aspects of service applications and service modules.

Service applications provide services, and have an associated service module (also called aService Component Architecture (SCA) module).

The only type of SCA modules that are supported by WebSphere ESB are mediation modules.

Viewable module details

After you have deployed an EAR (Enterprise ARchive) file containing an 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:
    • Interfaces.
    • Bindings.
  • SCA module exports:
    • Interfaces.
    • Bindings.
  • SCA module properties.

Modifiable 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:
    • 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 can be changed to interact with another 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.
  • Export and import bindings of types JMS, WebSphere MQ JMS, generic JMS, WebSphere MQ, and HTTP have attributes that you can modify.
  • Mediation module properties:
    • Mediation module properties belong to the mediation primitives with which they are associated. However, the WebSphere ESB 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 ESB.
    • 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. Mediation Module1 connects to Mediation Module2
MediationModule1 connects to MediationModule2

concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/concepts/cwesb_admininterfaceforserviceapps.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).