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.
Details about deployment of SCA artifacts in the Feature Pack for SCA follow.
One specification requirement is that the names of top-level components must be unique. Thus, the product validates top-level component name uniqueness.
The product validates all composite files in a JAR or ZIP file, regardless of the file location in the archive or whether the sca-contribution.xml file references the composite file. The product does not validate all services and references.
The product writes warning and error messages resulting from the validation tests to the SystemOut.log file. Read the log file to learn about inconsistencies with specifications in your SCA composites.
Deployable composite files must have name and targetNamespace values. The name and targetNamespace values are combined to form the QName of a composite file.
However, you can place other composite files in directories other than META-INF/sca-deployables, and reference those composite files in the top-level composite under the META-INF/sca-deployables directory.
For example, suppose your Contribution A imports a JAR file from Contribution B. You might need to import Contribution B and then Contribution A as assets. Contribution A depends on Contribution B so you must import Contribution B before importing Contribution A.