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.
Find links to Service Component Architecture (SCA) resources for learning, including conceptual overviews, tutorials, samples, and "How do I?..." topics, pending their availability.
Explore the key concepts pertaining to Service Component Architecture (SCA) composites. SCA composites consist of components that implement business functions in the form of services. You can develop components that use Web services and Enterprise JavaBean (EJB) sessions and define bindings that enable the components to run on product servers. 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 then add the assets to business-level applications.
IBM® WebSphere® Application Server V7 Feature Pack for SCA delivers critical technology that enables adoption of key Service-Oriented Architecture (SOA) principles.
The IBM Feature Pack for Service Component Architecture (SCA) supports deployment of many types of SCA artifacts as composition units of business-level applications. Typical artifacts include Java™ archive (JAR) files, compressed (ZIP) files, and Web application archive (WAR) files.
This topic lists the sections of Service Component Architecture (SCA) specifications not supported in Feature Pack for SCA.