Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The SCA composite failed to start correctly for the specified Web application. |
Action | Check your SCA composite for errors and review the server log files. |
Explanation | The embedded SCA Runtime failed to start correctly. |
Action | Check the server log files for errors. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The SCA composite failed to stop properly for the specified Web application. |
Action | Please check your SCA composite for errors and review the server logs. |
Explanation | Matching dependent assets cannot be located for the unresolved imports. |
Action | Check your SCA asset and make sure the dependent assets are imported. |
Explanation | Web Applications may not contain references with callbacks using the Web Services Binding. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The Service Component Architecture (SCA) Runtime cannot determine the Java Implementation Class for wsdlElement. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The SCA Codegen directory failed to be created. Check server logs for more details. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The ConstrainingType is an unsupported specification scenario. |
Action | Do not set the ConstrainingType on either composites or components. |
Explanation | Conversations on service interfaces and callback interfaces is not supported. |
Action | Do not set the conversation on service interfaces and callback interfaces. |
Explanation | The implementation type is not supported. |
Action | Use one of the supported implementation types. |
Explanation | The binding type is not supported. |
Action | Use one of the supported binding types. |
Explanation | The service is unavailable for reference target. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The service is not installed for reference target. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Unable to determine the destination endpoint from Service Registry for reference target. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Cannot handle mixed payloads betweem OMElements and other types. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Unable to determine Endpoint URI for reference. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Unable to determine wsPolicy for reference. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This service is available on secure channels only. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Unable to register service with the Service Registry. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Unable to stop service with the Service Registry. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Absolute URI cannot be specified as the location to host this service: |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Unable to obtain CompUnitInfoLoader. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The Service Component Architecture (SCA) Runtime cannot obtain the CompUnitInfoLoader URL prefix for a service. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The Service Component Architecture (SCA) Runtime cannot determine the wsPolicy for the service. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The component names must be unique across all of the applications. |
Action | Ensure that the component names are unique across all of the applications. |
Explanation | we do not support user defined uri on binding.sca. The URI should be calculated by runtime in the form of component's uri/service name. |
Action | Make sure not defining default binding URI. |
Explanation | we do not support user defined uri on binding.sca. The URI should be calculated by runtime in the form of component's uri/service name. |
Action | Make sure not defining default binding URI. |
Explanation | The component names must be unique across all of the applications. |
Action | Ensure that the component names are unique across all of the applications. |
Explanation | Authorization & runAs identity policy for impl.jee is handled by the implementation. Policy sets cannot be used to perform authorization checks and set runAs identity. |
Action | Detach the policy set and specify the roles and security constraints in the EAR file. |
Explanation | check the message for the reason |
Action | check the message for the reason |
Explanation | check the message for the reason |
Action | check the message for the reason |
Explanation | The create attribute is set to 'always', but the resource can not be created because the resource already exists. |
Action | Delete the existing resource, or change the create attribute to 'ifnotexist' |
Explanation | The create attribute is set to 'always', but the resource can not be created because the resource already exists. |
Action | Delete the existing resource, or change the create attribute to 'ifnotexist' |
Explanation | The create attribute is set to 'always', but the resource can not be created because the resource already exists. |
Action | Delete the existing resource, or change the create attribute to 'ifnotexist' |
Explanation | A destination resource was not specified, but is required for the binding |
Action | Specify a destination resource JNDI name |
Explanation | The service's JMS binding uses an existing resource that is associated with the bus named in the message. The JMS binding does not provide an existing activation specification. An activation specification with the default JNDI name cannot be created for this bus name. |
Action | Specify an activation specification JNDI name. An activation specification can be created in this situation if it is given a different JNDI name. |
Explanation | The service's JMS binding uses an existing resource that is associated with the bus named in the message. The JMS binding does not provide an existing connection factory. A connection factory with the default JNDI name cannot be created for this bus name. |
Action | Specify a connection factory JNDI name. A connection factory can be created in this situation if it is given a different JNDI name. |
Explanation | The reference's JMS binding uses an existing resource that is associated with the bus named in the message. The JMS binding does not provide an existing connection factory. A connection factory with the default JNDI name cannot be created for this bus name. |
Action | Specify a connection factory JNDI name. A connection factory can be created in this situation if it is given a different JNDI name. |
Explanation | The create attribute is set to 'never', but the resource does not exists. |
Action | Make sure to create the resource. |
Explanation | The create attribute is set to 'never', but the resource does not exists. |
Action | Make sure to create the resource. |
Explanation | The create attribute is set to 'never', but the resource does not exists. |
Action | Make sure to create the resource. |
Explanation | The propagatesTransaction intent is not supported on binding.atom. |
Action | Remove the propagatesTransaction intent from the binding.atom element. |
Explanation | The propagatesTransaction intent is not supported on binding.jsonrpc. |
Action | Remove the propagatesTransaction intent from the binding.jsonrpc element. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider. |
Action | Update the JMS binding to refer to an existing activation specification for the appropriate JMS provider. |
Explanation | JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider. |
Action | Update the JMS binding to refer to an existing connection factory for the appropriate JMS provider. |
Explanation | JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider. |
Action | Update the JMS binding to refer to an existing connection factory for the appropriate JMS provider. |
Explanation | JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider. |
Action | Update the JMS binding to refer to an existing destination for the appropriate JMS provider. |
Explanation | JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider. |
Action | Update the JMS binding to refer to an existing destination for the appropriate JMS provider. |
Explanation | The Java EE applications associated with SCA component implementation must be unique across all of the applications. |
Action | Ensure that the Java EE application names are unique across all of the applications. |
Explanation | The CU referred via implementation.jee must be targeted to all servers in which the CU using implementation.jee is targeted. |
Action | Change targets of composition units to match when using implementation.jee. |