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. |
Explanation | This CDF step was completed unsuccessfully with exception. |
Action | Consult the error message associated with the exception created for detailed cause of failure. |
Explanation | The ConfigLoaderFactory cannot locate a suitable configuration loader for this configuration file type. |
Action | CSMG0002 |
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 |
Explanation | The CDRHelperUtil cannot find the specified configuration step. |
Action | CSMG0002 |
Explanation | Some validation errors exist. Correct these errors and redeploy the application. |
Action | Check the error logs for these validation errors and correct them. |
Explanation | The contribution dependencies are not recalculated even though the update is allowed and valid. |
Action | CSMG0002 |
Explanation | Do not update the composite file when the file is being used by a composition unit. |
Action | CSMG0002 |
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. |
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. |
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. |
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. |
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. |
Explanation | Bindings other than SCA binding are not supported on services in WAR composites. |
Action | Check the message for the reason |
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. |
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. |
Explanation | The specified enviroment variable cannot be found. |
Action | Verify that this script is being run within a valid profile scriping enviroment. |
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. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
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. |
Explanation | The specified output location is not valid or not writable. |
Action | Verify that the specified output location is a valid and writable directory. |
Explanation | The SCAWSDLArtifactCollector cannot set endpoints in the generated WSDL. |
Action | CSMG0002 |
Explanation | The CompUnitInfoLoader cannot determine the baseUri service endpoint. |
Action | CSMG0002 |
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. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |