About the Service Component Architecture

IBM WebSphere Process Server and IBM WebSphere Enterprise Service Bus introduced a way to model services in an SOA, called the Service Component Architecture (SCA). SCA is designed to separate business logic from its implementation, so that you can focus on assembling an integrated application without knowing implementation details.

The Service Component Architecture is based on SCA modules and SCA components. An SCA module is made up of multiple SCA components. In ITCAM for SOA, SCA components are treated as Web Services Description Language (WSDL) service ports.

With additional support for IBM WebSphere Enterprise Service Bus and IBM WebSphere Process Server, ITCAM for SOA discovers information about messages flowing between SCA components.

The ITCAM for SOA data collector is installed and application servers are configured once in the IBM WebSphere Process Server or IBM WebSphere Enterprise Service Bus environment. The data collector does not require each SCA application to be configured separately. When you deploy new SCA applications into your monitored environment, they are automatically monitored as well.

The SCA data collector supports both synchronous and asynchronous interactions flowing through the application server runtime environment. Note that in the IBM WebSphere Process Server version 6.0 and IBM WebSphere Enterprise Service Bus version 6.0 environments, some asynchronous interactions between SCA components might result in requests or responses being reported multiple times or not at all. This is caused by thread switching in the SCA application server runtime environment and limitations of the data collector in tracking flows across these thread switches. Monitoring of asynchronous interactions is provided to give you a more complete picture of the services that exist in the environment, however you should not expect the metrics collected for asynchronous interactions to be precise. An improved monitoring interface in version 6.1 of these products provides for more reliable monitoring results.

Refer to your WebSphere Integration Developer documentation for more information about these synchronous and asynchronous interactions.

See Configuring managed SCA mediation primitive runtime support for more information on configuring your IBM WebSphere Process Server or IBM WebSphere Enterprise Service Bus runtime environment to support deployed SOA applications that contain managed SCA mediation primitives.

[ Top of Page | Previous Page | Next Page | Contents | Index ]