Overview of the application integration environment

A service application has an associated Service Component Architecture (SCA) module. You deploy service applications, to WebSphere Process Server, within EAR (enterprise archive) files.

The kind of SCA modules that enterprise service bus supports are called mediation modules. Mediation modules allow you to change the format, content or target of service requests.

Deploying a service application

The process of deploying an EAR file containing a service application is the same as the process of deploying any other EAR file. You can modify values for mediation parameters at deployment time. After you have deployed an EAR file containing an SCA module, you can view details about the following.
  • The service application.
  • The SCA module associated with the service application.
    • You can see how an SCA module is connected to service requesters and service providers. SCA modules are connected to service requesters through exports, and to service providers through imports.
    .

Viewing SCA module details

The SCA module details that you can view include some of the following. The precise details you can display depend upon the SCA module.
  • SCA module name.
  • SCA module description.
  • Associated application name.
  • SCA module imports.
    • Interfaces.
      • Import interfaces are abstract definitions that describe how an SCA module accesses a service.
    • Bindings.
      • Import bindings are concrete definitions. They specify the physical mechanism by which an SCA module accesses a service. For example, using SOAP/HTTP.
  • SCA module exports.
    • Interfaces.
      • Export interfaces are abstract definitions that describe how service requesters access an SCA module.
    • Bindings.
      • Export bindings are concrete definitions. They specify the physical mechanism by which a service requester accesses an SCA module, and indirectly, a service.
  • SCA module properties.

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)