Page Operations
Browse Space
Assembly Model
The SCA Assembly Model consists of a series of artifacts which define the configuration of an SCA system in terms of service components which implement and/or use services and the connections which describe how they are linked together. The assembly is defined in terms of a set of SCA composites, which define components and reference the implementation code that provide business function and which also describe services and references and the wires that link them.
 | Find out more The Assembly Model |
Policy Framework
The capture and expression of non-functional requirements such as security is an important aspect of service definition, and has impact on SCA throughout the lifecycle of components and compositions. SCA provides the Policy Framework to support specification of constraints, capabilities and Quality of Service (QoS) expectations, from component design through to concrete deployment. This specification describes the framework and its usage.
| Find out more The Policy Framework |
Bindings
SCA Bindings apply to services and references. Bindings allow services to be provided, and references to be satisfied, via particular transports. There is a binding available for each different access method.
| Find out more Bindings |
Java: Annotations, APIs and Component Implementation
The SCA Java Common Annotations and APIs specification define Java APIs and annotations which enable service components and service clients to be built in the Java programming language. There are closely related models describing how other Java-based frameworks and models can be used in the context of SCA, such as Spring and EJBs, which also use the common annotations and APIs defined here. In addition, the Java Component Implementation specification defines a simple Java POJO model for creating service components.
| Find out more Java Component Implementation |
Client & Implementation: C++
The C++ Client and Implementation model specifies APIs and annotations which enable the creation of service components and service clients built in the C++ language.
| Find out more C++ |
Client & Implementation: BPEL
The SCA WS-BPEL Client and Implementation (BPEL C&I) model specifies how WS-BPEL processes can be used as SCA components.
| Find out more BPEL |
Client & Implementation: PHP
The SCA Client and Implementation model for PHP defines how PHP scripts and objects can be used within an SCA assembly.
| Find out more PHP |
EJB Component Model
The SCA EJB Component model for EJB specifies how EJB components and EJB applications can be used within SCA.
| Find out more EJB |
Spring Component Model
The SCA Spring Component model specifies how the Spring Framework can be used with SCA.
| Find out more Spring |