This page provides a starting point for finding information about Service Component Architecture (SCA) composites, which consist of components that implement business functions in the form of services. You can develop components to run on a product server that interact with web services and Enterprise JavaBeans™ (EJB) StatelessSessionBeans by defining SCA bindings.
You typically do not deploy SCA composites directly onto a product server. To deploy SCA composites, you import SCA composites as assets to the product repository and add the assets to business-level applications.
A benefit of Service Component Architecture (SCA) is that you can use existing assets in an application, without having to change the asset implementation. Many enterprises have application assets developed using a variety of technologies and frameworks, including assets previously deployed in a WebSphere® Application Server environment, which is predominantly Java Platform, Enterprise Edition (Java EE) or Java-centric. SCA supports several service implementation technologies.
After you develop an Service Component Architecture (SCA) component, you can use bindings to specify how SCA services and references enable the component to communicate with other applications.
You can use a wire format handler to transform data between a Service Component Architecture (SCA) application and the application binding.
You can use the Service Component Architecture (SCA) programming model to invoke business services in Java Platform, Enterprise Edition (Java EE) components.
You can use an OSGi application as a Service Component Architecture (SCA) component.
You can use the Service Component Architecture (SCA) programming model to invoke beans that follow the Java 2 Platform, Standard Edition (J2SE) programming model in a Spring 2.5.5 container. The product supports components implemented with Spring Framework that use <implementation.spring> in composite definitions.