Troubleshooting
Problem
If you add a Service Component Architecture (SCA) composite asset to a business-level application and select a deployment target that is not a Feature Pack for SCA-enabled server such as a Web server, the SCA composite does not start. You must deploy SCA assets to servers or clusters that are enabled for the feature pack.
Symptom
When you attempt to start an SCA application that is deployed to a non-SCA server or cluster, the product displays messages, which indicate that the composite did not start. For example:
10/31/08 15:28:35:822 EDT] 0000001a SCARuntimeImp E CWSAM2000E:
The PricechgLoggingServiceComposite composite did not start successfully.
[10/31/08 15:28:35:824 EDT] 0000001a CompositionUn E WSVR0194E:
Composition unit WebSphere:cuname=PricechgLoggingServiceComposite in
BLA WebSphere:blaname=PricechgLoggingServiceComposite failed to start.
[10/31/08 15:28:35:828 EDT] 00000000 ContainerHelp E WSVR0501E:
Error creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl@308d308d
com.ibm.ws.exception.RuntimeWarning:
org.apache.tuscany.sca.core.assembly.ActivationException:
java.lang.IllegalArgumentException
Cause
The product does not validate targets for SCA applications. On the Map composition unit to a target page, the administrative console allows you to select deployment targets that are not enabled for the Feature Pack for SCA.
Resolving The Problem
When you add an SCA composite asset to a business-level application, select only servers or clusters as deployment targets that are enabled for the feature pack.
Related Information
Was this topic helpful?
Document Information
Modified date:
06 June 2019
UID
swg21327862