Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications
Develop SCA composites
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 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.
- Select the implementation type for an SCA composite
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 WAS environment, which is predominantly Java EE or Java-centric. SCA supports several service implementation technologies.
- Develop Service Component Architecture (SCA) services
To develop SCA service implementations, you can use either a top-down development approach starting with an existing WSDL file or you can use a bottom-up development approach starting from an existing Java interface or implementation. When using either the top-down or bottom-up development methodologies, you can develop service clients or use tools to map business exceptions on remotable interfaces.
- Specify bindings in an SCA environment
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.
- Create wire format handlers
We can use a wire format handler to transform data between a Service Component Architecture (SCA) application and the application binding.
- Use existing Java EE modules and components as SCA implementations
We can use the Service Component Architecture (SCA) programming model to invoke business services in Java EE components.
- Use OSGi applications as SCA component implementations
We can use an OSGi application as a Service Component Architecture (SCA) component.
- Use Spring 2.5.5 containers in SCA applications
We 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.
Learn about SCA composites