WebSphere Process Server messages     Operating Systems: All supported
CWLAU0000E: The unsupported interaction type "{3}" resulted from using the interface map "{0}" with the source operation "{1}" and the target operation {2}.
Explanation: An internal error caused the interface map to be invoked in an unexpected manner. This usually happens if the source and target interfaces, operations and parameters are not bound correctly.
User Action: Verify that the source and target interfaces, operations, and parameters are bound correctly. Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.

 

CWLAU0001E: The interface map component "{0}" has either zero or more than one reference.
Explanation: The interface map component "{0}" must contain one and only one target reference.
User Action: Edit the interface map component to ensure that the specified component has one and only one target reference. If the invocation style is asynchronous one-way, use multiple wires in the reference.

 

CWLAU0002E: The interface map "{0}" cannot retrieve the ticket from the database (target component: {1} with operation {2}).
Explanation: The interface map uses a database that is installed during the WebSphere Process Server installation. A likely cause of the problem is that the database is not running
User Action: Please go to the System Administration Console. Look under the Data Sources and test the connection to jdbc/WPSDB database to ensure that the database is running. Once you have verified that the database is running, please also verify that the Mediation_Tickets table exists. This table stores the mediation tickets.

 

CWLAU0003E: The interface map file "{0}" cannot be loaded.
Explanation: The specified file is either missing or it is not in the correct location.
User Action: Please verify in the System Administration console that the application you are using has been installed and running. PLease check whether the .ifm file is part of the insstalled application/module by looking under the "InstalledApps" directory under the specific WAS profile you are running. If you cannot find it, please create the .ifm file and re-deploy the module to the server.

 

CWLAU0004E: The interface map file "{0}" cannot be loaded. The following exception was thrown: {1}.
Explanation: Examine exception {1}. Possible reasons for the error are that the interface map file is missing or it is not in the correct directory.
User Action: PLease look at the Systemout.log file and look for the specific exception thrown while loading the file. If the file could not be loaded, please edit the component to make sure that the file has not been misspelt.

 

CWLAU0005E: The following error occurred with the interface map "{0}" (source operation "{1}" and target operation "{2}") when it invoked the map "{3}" in the calling context {5}.
Explanation: During Business object transformation parameter interface mapping, business object map {3} is invoked.
User Action: Ensure that the map is deployed without errors, that it has valid inputs, and that it is running properly. Please verify that the interface map inputs/outputs match those of the data map inputs/outputs.

 

CWLAU0006E: The following unexpected exception occurred while using the interface mapping "{1}" with the source operation "{2}" and the target operation {3}: {0}.
Explanation: This exception might be caused by incorrect artifacts created during design-time, incorrect runtime data, or a problem within IBM WebSphere Process Server. Possible reasons are 1) Target could not be invoked 2) A correlation ticket could not be stored in the Mediation Tickets table during the target invocation 3) A correlation ticket could not be retreieved from the Mediation Tickets table during the response.
User Action: Please look at the Systemout.log for specific exceptions that might have occurred during this asynchronous invocation. Possible reasons are 1) Target could not be invoked 2) A correlation ticket could not be stored in the Mediation Tickets table during the target invocation 3) A correlation ticket could not be retreieved from the Mediation Tickets table during the response. Please take a re-llok at the profile installation and/or the application installation and see if all the steps have been correctly followed.

 

CWLAU0007E: The interface mapping {0} (source method {1}, target method {2}) caused the following exception while calling the Java snippet {3}: {4}.
Explanation: An exception occurred while calling the Java snippet. This might happen because the java class to be invoked was missing or was not spelled correctly.
User Action: Please look at the Systemout.log for specific exceptions that might have occurred during java snippet invocation. Please edit the interface map file uing the interface map editor, and choose an existing java class implementing com.ibm.wbiserverspi.mediation.JavaMediationDataObject class.

 

CWLAU0008E: The interface mapping {0} (source method {1}, target method {2}) does not recognize the class type "{3}" when mapping with the Java snippet.
Explanation: The specified interface mapping does not implement the correct Java snippet class/interface com.ibm.wbiserverspi.mediation.JavaMediationDataObject.
User Action: Please edit the "java" interface parameter mapping so that the chosen java snippet implements either JavaMediation or JavaMediationDataObject.

 

CWLAU0009E: The interface mapping {0} (source method {1}, target method {2}) cannot use the parameter type "{4}" when calling a Java snippet with the class {3}.
Explanation: The specified class implements JavaMediationDataObject, so it must have a parameter of type DataObject.
User Action: Edit the parameter mapping in the interface map file so that the source of the parameter mapping is a complex type, instead of a simple/primitive type. This will make sure that at run time, the parameter passed to the Java snippet is of type DataObject.

 

CWLAU0010E: The interface mapping {0} (source operation {1}, target operation {2}) includes the type {3}, which is unsupported when running setValue parameter mapping with the value {4}.
Explanation: "{3}" must be of the type boolean, byte, double, float, int, long, or string. These are the only supported types which can be assigned a value using interface mediation. All primitive types are not supported becuase only some of them can take a freeform string value for assignment.
User Action: Change the setValue parameter for constants to one of the following types: boolean, byte, double, float, int, long, or string.

 

CWLAU0012E: The interface mapping {0} (source operation {1}, target operation {2}) has an unexpected fault: {3}.
Explanation: The fault happened even though the specified fault is not declared in the source operation. This is possibly due to an incorrect integration solution design by the user. If it was an expected fault,the fault should be added to the list of specified faults on the source side of the mapping.
User Action: There are three possible solutions: First, if the specified fault should not be raised, make sure that it is not raised again. Second, include a parameter mapping from the specified fault to a fault declared in the source operation. Third, add the specified fault to the declared list of faults in the source operation.

 

CWLAU0013W: The duplicate key "{0}" was found during business object transformation or Java snippet mapping.
Explanation: When multiple maps are called, multiple Java snippets are invoked, or a combination of at least one map and one Java snippet is invoked. In this scenario, duplicate keys might be generated for relationships.
User Action: Please edit the .ifm file using the interface map editor and ensure that the map variable name and parameter names in the .ifm file are unique.

 

CWLAU0014E: The source operation "{1}" cannot be found in the interface {0}.
Explanation: Either the specified source method is not in the specified interface, or the .ifm file has validation errors due to an incorrect operation specified in the mapping.
User Action: Check the .wsdl interface file for the presence of the specified source method and add it if it is not there.

 

CWLAU0015E: The target operation "{1}" in "{0}" cannot be found.
Explanation: Either the target method {1} is not in interface {0} or the .ifm file has validation errors due to an incorrect operation name specified in the mapping.
User Action: Check the .wsdl target interface file for the presence of the specified target method and add the missing method using the Interface Editor.

 

CWLAU0016E: The interface mapping {0} (target reference {1}) has multiple wires.
Explanation: Multiple wires can be used only for asynchronous one-way invocations. The specified mapping must have only one wire.
User Action: Edit the interface map component qualifiers from the Assembly editor properties page so that invocation style is always asynchronous one-way or remove the other wires so that the target reference has only one wire.

 

CWLAU0017E: The interface mapping {0} (source operation {1}, target operation {2}) has caught an unexpected runtime exception: {3}.
Explanation: Target operation {2} produced an unexpected exception {3}. Interface mapping wraps the unexpected exception in a MediationRuntimeException and retries. Please look at ther Systemout.log or SystemOut.err log files to determine why the target component invocation has failed. Possible reasons are 1)The target service is not responding 2)The target service was misspelled when the target reference was wired to in the assembly editor.
User Action: Examine the scenario that caused the target Service Component Architecture (SCA) component invoking the specified target operation to produce the exception. Please look at ther Systemout.log or SystemOut.err log files to determine why the target component invocation has failed.

 

CWLAU0018E: The value "async" of the PreferredInteractionStyle attribute on the interfaces of the target component "{0}" was ignored during an {1} interaction using the interface map {2} (source operation {3}, target operation {4}). This interaction was handled as a synchronous-to-synchronous call.
Explanation: The specified interface map is being invoked in an interaction where the target component interface PreferredInteractionStyle attribute is set to "async". This value is ignored and the interaction defaults to a synchronous call on the target component.
User Action: Change the value of the PreferredInteractionStyle attribute on the target component interfaces to "any or "synchronous" in the properties page after selecting the component in the assembly editor.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009