- CWSXA0200E: The {0} bus name cannot be found.
- Explanation: The bus name that was supplied to the command cannot be matched to a bus object.
- User Action: Make sure that the specified bus name is spelled correctly and fix the spelling if it is not. Also verify that a bus with that name exists in the configuration. The Administrative Console>Service Integration> Buses, shows the bus names.
- CWSXA1500E: The application does not contain a Service Component Architecture (SCA) module.
- Explanation: The SCA application must contain a .module file.
- User Action: return to the WebSphere Application Developer and generate a valid SCA application.
- CWSXA1501E: The {0} application does not exist.
- Explanation: The specified application cannot be found in the cell.
- User Action: Check that the specified application has been installed. You can find a list of installed applications in the administrative console in Applications > Enterprise Applications. Install the application if it does not appear in the list.
- CWSXA1502E: A Service Component Architecture (SCA) module cannot be found in the {0} application binaries.
- Explanation:
- User Action: Check that the correct application is specified. You can find a list of installed applications in the administrative console in Applications > Enterprise Applications.
- CWSXA1503E: The {0} module does not exist in the {1} application.
- Explanation: The specified Service Component Architecture (SCA) module is not found in the specified application.
- User Action: Check that the correct module and application are specified. You can find a list of installed applications in the administrative console, in Applications > Enterprise Applications or return to the WebSphere Integration Developer to display the modules within the application.
- CWSXA1504E: The {0} module does not exist.
- Explanation: The specified module cannot be found in any application in the cell.
- User Action: Check that the correct module has been specified. You can find a list of installed applications in the administrative console in Applications > Enterprise Applications or return to the WebSphere Integration Developer to display the modules within the application.
- CWSXA1509E: The {0} destination cannot be created.
- Explanation:
- User Action: Reinstall the application to retry the destination creation. If reinstalling the application does not fix the problem, refer to the troubleshooting information on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWSXA1510E: The {0} destination cannot be deleted.
- Explanation:
- User Action: Delete the specified destination manually. You can find how to do this at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.soacore.610.doc/doc/tadm_deletingsibusdest.html
- CWSXA1511E: The Enterprise JavaBeans (EJB) reference mappings for the module cannot be resolved.
- Explanation: The EJB reference supporting the synchronous Service Component Architecture (SCA) import binding cannot be found in the application.
- User Action: Verify that the application is correctly formed. You can find how to to do this at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp.
- CWSXA1512E: The {0} command cannot be loaded.
- Explanation: The user does not have the correct privileges to call the specified command.
- User Action: Verify that the correct privileges have been specified. You can check this in the Information center at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp.
- CWSXA1700E: Module properties cannot be found for the {0} module.
- Explanation:
- User Action: In the sca-module-properties.xml file in the application, check that the module includes some promoted module properties. If there are no promoted properties, return to WebSphere Integration Developer to create promoted properties
- CWSXA1701E: A module property with the {0} identifier cannot be found in the {1} module.
- Explanation:
- User Action: Call the AdminTask command to show SCAModuleProperties. Make sure you have specified the correct identifiers for the module property and that you have specified a module that contains the property.
- CWSXA1702E: The {0} value for the module property has the {1} type, which is not correct.
- Explanation:
- User Action: Specify a new value of the correct data type for the specified module property. Call the command with the parameter -showPropertytypes set to true to show the types that are expected for each property.
- CWSXA1703W: The mediation flow Enterprise JavaBeans (EJB beans) cannot be found.
- Explanation: The specified EJB beans might have been deleted. Without it, this application does not function correctly.
- User Action: Rebuild and republish the application. If the problem persists, refer to the troubleshooting information on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWSXA2000E: The {0} bus cannot be found.
- Explanation: The bus name that is specified in the command cannot be resolved to a bus object.
- User Action: In the administrative console, in Service Integration > Buses, check that the bus name is spelled correctly and that a bus with that name exists in the configuration.
- CWSXA2001E: The {1} server cannot be found on the {0} node.
- Explanation: The node and server names that are specified in the command do not match a server object.
- User Action: In the administrative console, in Servers > Application servers, verify that the node and server names are spelled correctly and that the server exists in the configuration.
- CWSXA2002E: A messaging engine for the {0} bus cannot be found on the {1} server.
- Explanation: The bus and server names that are specified in the command do not match a messaging engine object.
- User Action: In the administrative console, in Service Integration > Buses > myBusName > Bus members, check that the bus and server names are spelled correctly and that the server is a member of the bus.
- CWSXA2003E: The {0} cluster cannot be found.
- Explanation: The cluster name that is specified in the command does not match a cluster object.
- User Action: In the administrative console, in Servers > Clusters, verify that the cluster name is spelled correctly and that the cluster exists in the configuration.
- CWSXA2004E: The {1} server on the {0} node is not a member of the {2} cluster.
- Explanation: The node and server that are specified in the command do not match a member of the specified cluster.
- User Action: In the administrative console, in Servers > Clusters > myClusterName > Cluster members, verify that the the node, server, and cluster names are spelled correctly and that the server is a member of the cluster.
- CWSXA2005E: The {0} cluster is already a member of the {1} bus. Messaging engine migration is not supported in this scenario.
- Explanation: To migrate a server messaging engine to a cluster, the cluster cannot already be a member of the same bus.
- User Action: In the administrative console, in Service integration > Buses > mybusName > Bus members, verify that the cluster is not a member of the same bus to which the server belongs. For details of how to do this you can refer to the information Centre at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp.
- CWSXA2006E: The {1} server on the {0} node is not a member of the {2} bus.
- Explanation: The node and server specified in the command do not match a member of the specified bus.
- User Action: In the administrative console, in Service integration > Buses > mybusName > Bus members, verify that the node, server, and bus names are spelled correctly and that the server is a member of the bus.
- CWSXA2007E: No messaging engine names are available for the cluster.
- Explanation: A valid messaging engine name cannot be created because the maximum number of messaging engines has been reached for this cluster.
- User Action: Specify different configuration data when creating the messaging engine.For details of how to do this you can refer to the information Centre at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp.
- CWSXA2008E: The combination of the {0} node name, the {1} server name, and the {2} cluster name is not valid.
- Explanation: The specified parameters do not make up a valid bus member configuration.
- User Action: To correctly identify a bus member, specify either, node name and server name, or cluster name. Do not specify all three (node name, server name and cluster name).
- CWSXA2009E: The specified server does not have a service integration bus service.
- Explanation: An exception occurred while retrieving the service integration bus service for the messaging server.
- User Action: Ensure that a SIB Service exists for the messaging server. In the administrative console, in Servers > Application Servers > myServerName > SIB service, verify that a service integration bus service exists for the messaging server. If it does not, enable uisng the checkbox on the console page.
- CWSXA2010E: The scope specification is not valid.
- Explanation: The specified details do not represent a valid scope specification.
- User Action: In the administrative console, in Servers> Application Servers, verify that the node name and server name details are valid for the scope. In Servers > Clusters, verify that the cluster name details are valid for the scope.
- CWSXA2011E: Event sequencing is not supported on a WESB node.
- Explanation: Event sequencing is not supported on a node not running WPS.
- User Action: Try to install the application on a node that supports event sequencing.
- CWSXA2200E: The {0} command did not return a result.
- Explanation:
- User Action: Check the FFDC log files for an indication of the cause and refer to the troubleshooting information on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.