IBM BPM, V8.0.1, All platforms > Programming IBM BPM > Enterprise Service Bus programming

Service Component Architecture

SCA is a model to define and implement SOA based solutions. This section details the IBM implementation of SOA within WebSphere ESB, and its associated tooling, Integration Designer.

There are two defined sections within SCA:

1. Service assembly, which details the service definitions and relationships of the export, import, components and interfaces
2. Service implementation, which details the construction of the service definition and the transport of information through defined protocols (web services, JMS, MQ, adapters).

In an SOA framework, high-level business components are exposed as services. SCA provides a model for how the services in an SOA framework are structured.

• Module
  A module is a unit of deployment, where services are packaged together. Components within a module are assembled for performance, and can pass their data by reference. A module can be seen as a scoping mechanism; it sets an organizational boundary for services.
• SCA implementation in Integration Designer
  

  You can build SCA modules within Integration Designer. Modules contain all the artifacts required to create a complete SCA application and they can be organized into projects. Additionally SCA libraries can be created in Integration Designer. You can build libraries to store artifacts, and you can share them between multiple SCA modules. Libraries are detailed later on in the chapter.

• Library
  A library is a project used to store resources and artifacts, so that the resources or artifacts can be shared by multiple modules defined in the library. The usage of libraries is good practice where interfaces are shared across multiple mediation modules.

Enterprise Service Bus programming