Network Deployment (Distributed operating systems), v8.0 > Applications > SCA composites > Learn about SCA composites


SCA contributions

A Service Component Architecture (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 WSDL files, XSD files, or to code artifacts such as Java class files.

The following graphic shows composites in an sca-contribution.xml file in an SCA domain.

An SCA contribution is typically described in a contribution file, named sca-contribution.xml in the META-INF directory. The contribution file for a helloworldws composition unit follows:

<?xml version="1.0" encoding="ASCII"?>
<contribution xmlns="http://www.osoa.org/xmlns/sca/1.0" xmlns:ns="http://helloworld">
<deployable composite="ns:helloworldws"/>
</contribution> 

The product supports contributions, as described in Chapter 1.10 of SCA Assembly Specification 1.0. The assembly specification defines the contribution metadata model to describe the runnable components for a given contribution, as well as the exported definitions and imported definitions to help resolve artifact dependencies across multiple contributions. See "Unsupported SCA specification sections" for information on parts of Chapter 1.10 that the product does not support.

Information about support for SCA contributions follows:



Preconditions or inputs

One SCA contribution, including multiple deployable composites, and with import or export definitions.


Postconditions or outputs for JAR packaged applications



Postconditions or outputs for WAR packaged applications

Successful installation of a WAR module with a single deployable composite in the contribution.


Contribution scenarios



Scenarios for mapping multiple deployable composites to a composition unit



Notes and limitations

Currently this topic focuses on JAR-packaged SCA applications. For WAR-packaged applications support is provided for only a single deployable composite in the contribution.
Unsupported SCA specification sections
SCA components
SCA in WAS: Overview
Specify bindings in an SCA environment Concept topic

+

Search Tips   |   Advanced Search