WAS v8.5 > WebSphere applications > SCA composites
SCA composites
Find links to SCA resources for learning, including conceptual overviews, tutorials, samples, and "How do I?..." topics.
How do I?...
Conceptual overviews
| SCA overview (v8.5 adds OASIS support) | |
| SCA components | |
| SCA composites | |
| SCA application package deployment | |
| Security configurations for SCA applications (v8.5 adds OASIS support) | |
| SCA transaction intents |
Samples
| WAS v8.5 offers sample files that support SCA specifications. We can use these sample SCA files in business-level applications. The sample files are downloadable from the Samples information center. SCA services are packaged in JAR files that you import as assets to the product repository and then add as composition units to business-level applications. Samples include detailed deployment instructions in a readme.html file. |
Subtopics
- SCA components
A SCA component is a configured instance of an implementation, which is program code that implements one or more business functions such as Java classes. Components provide and consume services. The business functions provide services. Components consume services by referring to services provided by other components. The component configuration sets values for properties that are declared by the implementation and specifies references that point to services provided by other components. - SCA composites
A SCA composite is a composition unit within an SCA domain. An SCA composite can consist of components, services, references, and wires that connect them. A composite is the unit of deployment for SCA. - SCA domain
A SCA domain consists of the definitions of composites, components, their implementations, and the nodes on which they run. Components deployed into a domain can directly wire to other components within the same domain. On a single server, the domain is essentially the scope of the server. - SCA contributions
A SCA contribution contains artifacts that are needed for an SCA domain. Contributions are sometimes self-contained, in that all of the artifacts necessary to run the contents of the contribution are found within the contribution itself. However, the contents of the contribution can make one or many references to artifacts that are not contained within the contribution. These references might be to SCA artifacts, or to other artifacts, such as Web Services Description Language (WSDL) files, XSD files, or to code artifacts such as Java class files. - Security configurations for SCA applications
Security for SCA components and bindings can be configured using intents, SCA policy sets, web services policy sets, and WAS security configuration.
Related concepts:
SCA in WAS: Overview
Related
Samples, v8.5 information center
Example: Creating an SCA business-level application with the console
Example: Creating an SCA business-level application with scripting