CWLAU0000E: An unsupported interaction type, {3}, occurred using an interface map {0} with source operation {1} and target operation {2}.
Explanation: The interface map is being invoked in an unexpected manner due to an internal error.
User Action: Contact IBM Technical Support.

 

CWLAU0001E: {0} has either zero or more than one reference.
Explanation: {0} must contain only one target reference.
User Action: Ensure that {0} has one target reference. If the invocation style is asynchronous oneway, use multiple wires within the reference.

 

CWLAU0002E: The interface map {0} could not 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.
User Action: Ensure that the database is running.

 

CWLAU0003E: {0} cannot be loaded.
Explanation: The {0} file is either missing or not in the correct location.
User Action: Ensure that the {0} file is present.

 

CWLAU0004E: {0} cannot be loaded because of {1}.
Explanation: Examine exception {1}. Perhaps {0} is missing or not in the correct location.
User Action: Determine why {1} has occurred and then correct the situation.

 

CWLAU0005E: Interface mapping {0} with source operation {1} and target operation {2} experienced an unexpected error {4} when invoking map {3}. The calling context is {5}.
Explanation: During BOTransform parameter interface mapping, map {3} is invoked.
User Action: Ensure that the map is deployed without errors, has valid inputs, and is running properly.

 

CWLAU0006E: Unexpected exception {0} occurred while using interface mapping {1} with source operation {2} and target operation {3}.
Explanation: An unexpected exception can be caused by incorrect artifacts created during design-time, incorrect runtime data, or a problem within IBM WebSphere Process Server.
User Action: Review the logs for more details.

 

CWLAU0007E: Interface mapping {0} with source method {1} and target method {2} has exception {4} while calling Java snippet {3}.
Explanation: An exception occurred while calling the Java snippet.
User Action: Review the exception for more details.

 

CWLAU0008E: Interface mapping {0} with source method {1} and target method {2} does not recognize class type {3} when mapping with the Java snippet.
Explanation: {0} does not implement the correct Java snippet class interface.
User Action: {0} must implement either JavaMediation or JavaMediationDataObject.

 

CWLAU0009E: Interface mapping {0} with source method {1} and target method {2} cannot use parameter type {4} when calling a Java snippet with class {3}.
Explanation: {3} implements JavaMediationDataObject and thus should have a parameter of type DataObject.
User Action: At run time, ensure that the parameter passed to the Java snippet is of type DataObject.

 

CWLAU0010E: Interface mapping {0} with source operation {1} and target operation {2} has an unsupported type {3} while running setValue parameter mapping with part name {4} and value {5}.
Explanation: {3} must be of type boolean, byte, double, float, int, long, or string.
User Action: Ensure that setValue for constants is one of the types mentioned in the explanation.

 

CWLAU0012E: Interface mapping {0} with source operation {1} and target operation {2} has an unexpected fault {3}.
Explanation: Interface mapping received {3} but this fault is not declared in {1}.
User Action: There are three possible solutions. First, {3} should not be raised. Ensure that {3} will not be raised again. Second, ensure there is a parameter mapping from {3} to a fault declared in {1}. Or, third, add {3} to the declared list of faults in {1}.

 

CWLAU0013W: The duplicate key {0} was found during BOTransform or Java snippet mapping. Ensure that the map variable name and parameter names in the .ifm file are unique.
Explanation: When multiple maps are called, multiple Java snippets are invoked, or a combination containing at least one map and one Java snippet occurs, duplicate keys might cause problems for relationships.
User Action: Ensure that the map variable name and parameter names in the .ifm file are unique.

 

CWLAU0014E: Source operation {1} cannot be found in {0}.
Explanation: Either the source method {1} is not in {0} or the .ifm file has validation errors.
User Action: Run the validator on the .ifm file and ensure that the method is in the .ifm file.

 

CWLAU0015E: Target operation {1} in {0} cannot be found.
Explanation: Either the target method {1} is not in {0} or the .ifm file has validation errors.
User Action: Run the validator on the .ifm file and ensure that the method is in the .ifm file.

 

CWLAU0016E: Interface mapping {0} with target reference {1} should have one wire, unless the invocation style is asynchronous oneway.
Explanation: Multiple wires can only be used for asynchronous oneway invocations.
User Action: Ensure that {1} has one wire unless the invocation style is always asynchronous oneway.

 

CWLAU0017E: Interface mapping {0} with source operation {1} and 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.
User Action: Examine the scenario causing the target SCA component invoking operation {2} to produce an exception {3}.