CWSAM

CWSAM0002I: The SDO feature has not been enabled for this profile.
Explanation It is possible that the SDO feature has not been installed on this system or the SDO feature has not been enabled for this particular profile.
Action Install the SDO feature and augment this profile with the SDO template.
CWSAM0101E: {0} step ended with exception.
Explanation This CDF step was completed unsuccessfully with exception.
Action Consult the error message associated with the exception created for detailed cause of failure.
CWSAM0102E: The ConfigLoaderFactory cannot locate a suitable configuration loader for the {0} configuration file type, causing the {1} step to fail.
Explanation The ConfigLoaderFactory cannot locate a suitable configuration loader for this configuration file type.
Action CSMG0002
CWSAM0103E: The Service Component Architecture (SCA) SCDL file cannot be validated because a duplicate component, service or reference names exist, which causes the {0} step to fail.
Explanation The SCA SCDL file cannot contain component, service, or reference names that are used by any of the existing SCA modules within the same cell.
Action CSMG0002
CWSAM0104E: The CDRHelperUtil cannot find the {0} configuration step.
Explanation The CDRHelperUtil cannot find the specified configuration step.
Action CSMG0002
CWSAM0105E: The following Service Component Architecture (SCA) Validation errors caused the {1} step to fail: {0}
Explanation Some validation errors exist. Correct these errors and redeploy the application.
Action Check the error logs for these validation errors and correct them.
CWSAM0106W: Updating the contribution file is allowed in the {0} asset. However, the dependencies are not recalculated.
Explanation The contribution dependencies are not recalculated even though the update is allowed and valid.
Action CSMG0002
CWSAM0107W: Ensure that the {0} composite file is not in use.
Explanation Do not update the composite file when the file is being used by a composition unit.
Action CSMG0002
CWSAM0108E: The {0} step ended with an exception. The Application Server found the META-INF/sca-contribution.xml file within the Web archive (WAR) file, which is not supported.
Explanation The META-INF/sca-contribution.xml file is not supported for Service Component Architecture (SCA) WAR files.
Action Remove the META-INF/sca-contribution.xml file within the WAR file before deploying the application.
CWSAM0109E: The {0} step ended with an exception. The Application Server found multiple composites in the META-INF/sca-deployables directory under the Web archive (WAR) file. For the Service Component Architecture (SCA) WAR file, the product supports only a single composite in the META-INF/sca-deployables directory.
Explanation Multiple composites are not supported in the META-INF/sca-deployables directory within the WAR file. For an SCA WAR file, only a single composite in supported in the META-INF/sca-deployables directory.
Action Remove additional composites from META-INF/sca-deployables directory and redeploy the application.
CWSAM0110E: The JEE Archive specified by the composite file for {1} cannot be found in BLA {0}.
Explanation An instance of a JEE application cannot be found for at least one of the JEE Archives specified in an implemetation.jee tag for the Service Component Architecture (SCA) composite currently being deployed.
Action Deploy at least one instance of each JEE Archive specified by implementation.jee tags in the composite file for the asset being deployed.
CWSAM0111E: The JEE Application {1} cannot be found in BLA {0}.
Explanation The JEE Application that was specified during deployment does not exist in the target BLA.
Action Deploy the JEE Archive specified by implementation.jee tag in the composite file under the application name specified.
CWSAM0112E: No JEE Application mapping was specified for Service Component Architecture (SCA) component {1} in BLA {0}.
Explanation Every implementation.jee tag used in the composite file must have a matching JEE Application argument during deployment configuring which instance to wire to.
Action Specify a valid JEE Application name to the wsadmin addCompUnit command when deploying this Composition Unit.
CWSAM0113W: Multiple bindings were found in service {0}. Only SCA Binding is supported for services in WAR composites.
Explanation Bindings other than SCA binding are not supported on services in WAR composites.
Action Check the message for the reason
CWSAM0114E: SCA Binding was not found configured on service {0}. Only SCA Binding is supported for services in WAR composites.
Explanation Bindings other than SCA binding are not supported on services in WAR composites.
Action Please remove all bindings on services, configure the services using SCA Binding and redeploy the WAR.
CWSAM0115E: SDO application is being deployed in a profile where the SDO feature has not been enabled.
Explanation Improper user of SDO in an SCA application. It is possible that the SDO feature has not been installed on this system or the SDO feature has not been enabled for this particular profile.
Action Install the SDO feature and augment this profile with the SDO template before deploying this application.
CWSAM0501E: The scripting environment is not valid. The Variable is not found.
Explanation The specified enviroment variable cannot be found.
Action Verify that this script is being run within a valid profile scriping enviroment.
CWSAM0502E: The export process for the Web Service Definition Language (WSDL) Artifacts failed.
Explanation The export process for the WSDL Artifacts failed.
Action Review the error message, which is associated with the exception that has been created, for a detailed cause of the failure.
CWSAM0503I: The Web Service Definition Language (WSDL) Artifacts have been exported successfully.
Explanation This message is for informational purposes only.
Action No action is required.
CWSAM0504E: The meta-data source directory for the composition unit is not valid.
Explanation The meta-data directory path for the composition units is not valid.
Action Verify that the Service Component Architecture (SCA) composition unit name is specified correctly.
CWSAM0505E: The specified output location is not valid.
Explanation The specified output location is not valid or not writable.
Action Verify that the specified output location is a valid and writable directory.
CWSAM0506E: The SCAWSDLArtifactCollector cannot set endpoints in the generated Web Service Definition Language (WSDL).
Explanation The SCAWSDLArtifactCollector cannot set endpoints in the generated WSDL.
Action CSMG0002
CWSAM0507E: The CompUnitInfoLoader cannot determine the baseUri service endpoint.
Explanation The CompUnitInfoLoader cannot determine the baseUri service endpoint.
Action CSMG0002
CWSAM2000E: The {0} composite did not start successfully.
Explanation A failure occurred in one of the handlers when the SCA Runtime attempted to start the composite.
Action Verify that the composite is deployed properly and that all of the configurations are valid.
CWSAM2001I: The {0} composite started successfully.
Explanation This message is for informational purposes only.
Action No action is required.
Reference topic    

Terms and conditions for product documentation | Feedback

Last updated: Apr 17, 2017 8:10:18 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.soa.sca.admin.logger.Messages.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)