- CWLAP0001E: The result of the transformation is null.
- Explanation: The binding got a result of null after the transformation.
- User Action: Make sure that the binding has been setup correctly to perform the transformation.
- CWLAP0002E: The JMS message must be of type BytesMessage or TextMessage.
- Explanation: The binding supports only BytesMessage or TextMessage.
- User Action: Please make sure that the JMS message sent to the binding is BytesMessage or TextMessage
- CWLAP0003E: Unable to locate the Websphere TX map file {0} in directory {1}.
- Explanation: The Websphere TX map file {0} is not present in the location {1}.
- User Action: Please make sure that the map file is in the specified location.
- CWLAP0004E: Error invoking Websphere TX map {0}: returnMessage {1}, Return Code {2}.
- Explanation: The following error {1} with error code {2} occurred when calling Websphere TX map {0}.
- User Action: Please lookup the error message and error code in Websphere TX documentation for further explanation and a solution.
- CWLAP0005E: Unable to load the Websphere Transformation Extender map file {0}.
- Explanation: The WTX data binding was not able to load the map file {0} because either the map file is in the wrong location or is incorrectly named.
- User Action: If using the default WTX data binding, please make sure that the map file is in the sca module in a directory called WTX. If using custom WTX data binding, please make sure the parameter map name passed into the method points to the correct map file.
- CWLAP0006E: A null binding configuration is passed by the export or import to the WTXDataBinding.
- Explanation: There has probably been an error in the export or import due to which it has not been able to setup the bidning context correctly on the data binding.
- User Action: Look at the logs and ffdc of the export and import has generated to see why the context is null.
- CWLAP0007E: The data binding descriptor {0} is not valid.
- Explanation: The WTX Data Binding uses the data binding descriptor property in the header to determine the WTX map name. The value of this property has to follow a certain format. This format is incorrect.
- User Action: Please look at the WPS documentation to figure out what the format of this property should be and to correct the format.
- CWLAP0008E: The HTTP headers are not set.
- Explanation: The WTX Data Binding uses the data binding descriptor in the header to determine the WTX map name. Because there are no http headers set, the property is also not set.
- User Action: Please add HTTP headers to this mesage and look at the WPS documentation to figure out what the format of this property should be and correct the format.
- CWLAP0009E: The input data is null.
- Explanation: The input data received by WTX Data Binding from the export or import is null.
- User Action: Please check the export or import configuration to make sure that it is able to read the input data.
- CWLAP0010E: The EIS record to be converted to data object sent to the WTX Data Binding is null.
- Explanation: The EIS binding has failed to send a valid record to the WTX Data Binding.
- User Action: Look at the logs and ffdc generated by EIS binding to see why the binding has sent a null record.
- CWLAP0011E: The MQ Binding sent a null data object to the WTX Data Binding.
- Explanation: The MQ binding has failed to send a valid data object to the WTX Data Binding.
- User Action: Look at the logs and ffdc generated by MQ binding to see why the binding has sent a null data object.
- CWLAP0012E: The {0} received a null data object from the binding.
- Explanation: The binding has failed to send a valid data object to the WTX Data Binding.
- User Action: Look at the logs and ffdc generated by the binding to see why the binding has sent a null data object.
- CWLAP0013E: The WTX Data Binding was unable to load the WTX map {0}.
- Explanation: Either the map does not exist in the project in the specified location or the classloader loading the map is unable to access the map.
- User Action: Make sure that the map is located in the correct directory.
- CWLAP0014E: The input data is null.
- Explanation: The input data received by WTX Data Binding from the export or import is null.
- User Action: Please check your export or import configuration to make sure that it is able to read the input data.
- CWLAP0018E: The type of the {0} property is not an object.
- Explanation: There is a mismatch between the data that is coming into the system and the XML schema that corresponds to the data object that is defined on the component interface. The data handler is trying to set a non-object value in the data object property, which is of the data object type.
- User Action: Make sure that the incoming data complies with your XML schema. Refer to the Troubleshooting guide and other information on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWLAP0019E: The business object name {0} and/or namespace {1} is null.
- Explanation: The business object name and namespace was not set in the properties.
- User Action: Set the business object name and namespace properties of the JSON data handler when the data handler is configured. Refer to the Troubleshooting guide and other information on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWLAP0100E: The {0} data object with the {1} namespace cannot be created due to missing schema file.
- Explanation: A likely cause of the problem is that the schema that corresponds to the data object is not in the module.
- User Action: In WebSphere Integration Developer, check that the XML schema that corresponds to the data object is in the module. If it is not, add it. Also, make sure that no other schema conflicts with this schema.
- CWLAP0101E: The {0} property in the {1} data object cannot be accessed or created.
- Explanation: Either the property does not exist, or it is set to a value that is not valid.
- User Action: In the business object editor of WebSphere Integration Developer, check the XML schema for the data object. If it does not exist, create it. If it is set to a value that is not valid, change the value.
- CWLAP0102E: The data contains headers and child objects.
- Explanation: The input data must not contain both headers and child objects.
- User Action: Remove the headers from your input data.
- CWLAP0103E: The expected type is not set by the binding.
- Explanation: The expected type should be set to the parameter type of the operation by the binding.
- User Action: The expected type should be set to the parameter type of the operation by the binding.
- CWLAP0200E: The type of the {0} property is not a list.
- Explanation: There is a mismatch between the data that is coming into the system and the XML schema that corresponds to the data object that is defined on the component interface. The data handler is trying to set a non-list value in the data object property, which is of the list type.
- User Action: Make sure that the incoming data complies with your XML schema. Refer to the Troubleshooting guide and other information on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.
- CWLAP0300E: The {0} token is larger than the {1} field width; the token length cannot be truncated.
- Explanation: The length of the token is larger than the width that is specified for the field. Also, the truncation property is set to false, which prevents truncation of the field value.
- User Action: In WebSphere Integration Developer, in the Binding Resource Configuration window, either increase the width of the field to the token size, or set the truncation property to true, which allows truncation of the value to the field width size.
- CWLAP0400E: A text qualifier cannot occur at location {0}.
- Explanation: The token has an incorrect number of text qualifiers.
- User Action: Modify the token value to comply with the delimited data format. Refer to the WebSphere Integration Developer information center at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp.
- CWLAP0401E: The token is invalid because the character {0} cannot occur at location {1}.
- Explanation: The delimited token is not valid because it does not comply with the delimited data format.
- User Action: Modify the token value to comply with the delimited data format. Refer to the WebSphere Integration Developer information center at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp.
- CWLAP0402E: The {0} token cannot be serialized because it contains an unescaped {1} delimiter.
- Explanation: Although the token contains a delimiter, it cannot be serialized because a text qualifier or escape character has not been configured on the data handler.
- User Action: In WebSphere Integration Developer, in the Binding Resource Configuration window, specify a text qualifier or escape character configuration property for the delimited data handler.
- CWLAP0501E: Cannot read from the Reader. Reason {0}.
- Explanation: The process of reading data from Reader has failed.
- User Action: Check the message thats been written on the queue and has to be processed.
- CWLAP0502E: The input of type {0} and output of type {1} is not supported by JAXBDataHandler. Check the java name {2} and corresponding BO type {3} {4}.
- Explanation: This data handler supports java bean as input and data object as output when transforming from native data to data object. It supports data object input and java output when transforming from data object to native data.
- User Action: When calling the transform API on this data handler, ensure that the input and output is either java bean or data object.
- CWLAP0503E: The transformation from {0} to {1} for JAXBDataHandler failed. Java name is {2}, BO Type is {3} {4}. Reason {5}.
- Explanation: Transformation from source object to target object has failed. The Java name and BO Type might be configured incorrectly.
- User Action: Check the java name configuration on DataHandler and input and output data type set on the method.
- CWLAP0504E: The input of type {0} and output of type {1} is not supported by JAXWSWrapperDataHandler.
- Explanation: This data handler supports java Object array as input and data object as output when transforming from native data to data object. It supports data object input and java Object array output when transforming from data object to native data.
- User Action: When calling the transform API on this data handler, ensure that the input and output is either java Object array or data object.
- CWLAP0505E: The request bean class for java class {0} method {1} cannot be created. Reason {2}.
- Explanation: The request bean class cannot be created for expected method in java class.
- User Action: Check the RequestWrapper annotation on the method. Make sure that the request bean class is in the class path.
- CWLAP0506E: The request bean {0} could not be read to build the object array. Reason {1}.
- Explanation: The request bean class cannot be read.
- User Action: Check the RequestWrapper annotation on the method. Make sure that the request bean class is in the class path.
- CWLAP0507E: The response bean class for java class {0} method {1} cannot be created. Reason {2}.
- Explanation: The response bean class cannot be created for expected method in java class.
- User Action: Check the ResponseWrapper annotation on the method. Make sure that the response bean class is in the class path.
- CWLAP0508E: The method name {0} is invalid. Corresponding method not defined on SessionBean {1}.
- Explanation: The method name on WSDL does not match with any of the methods defined on SessionBean.
- User Action: Check the annotations WebMethod if present on the SessionBean implementation. Make sure either the default name or one of the annotation name matches the method name in WSDL.
- CWLAP0509E: The DataObject with namespace {0} and name {1} cannot be created.
- Explanation: The DataObject with specified namespace and name cannot be created.
- User Action: Check if the respective XSD with specified namespace and name is present in the classpath.
- CWLAP0510E: The property {0} is incorrect for DataObject {1}.
- Explanation: The property does not exist in DataObject.
- User Action: Check if the XSD has the property name requested.
- CWLAP0511E: The exception for type {0} is not defined on EJB method {1}.
- Explanation: The exception type for DataObject is not defined on EJB Method.
- User Action: Check if the annotations on Exception types match the DataObject and the Exception classes are in classpath.
- CWLAP0601E: The input stream passed by the binding to the data handler is null.
- Explanation: The input send to the data handler is null. A valid input has to be passed to the data handler.
- User Action: Check to see if valid input has been passed to the binding.
- CWLAP0602E: There is no data handler configured for the content type {0}.
- Explanation: To parse an entry in the atom feed, the atom data handler has to be configured with a data handler for the content type specified on that entry. There is no such configuration specified for the content type.
- User Action: Add a configuration on the atom data handler for the content type in the entry in the atom feed and the corresponding qualified data handler name for that content type.
- CWLAP0603E: The business object {0} in the namespace {1} is not an ATOM feed ("http://www.w3.org/2005/Atom/feed") or entry ("http://www.w3.org/2005/Atom/entry") business object and hence it cannot be serialized by the ATOM data handler.
- Explanation: The ATOM data handler can serialize only an ATOM feed business object or an ATOM entry business object. The business object sent to it is neither one.
- User Action: Change the interface such that the parameters of the request/response type are either an ATOM feed or ATOM entry business object. The other option is not use the ATOM data handler but a propreitary data handler which can serialize the custom business object.
- CWLAP0701E: There are no configuration properties set on {0}.
- Explanation: This component needs configuration properties set up on it so it can operate correctly.
- User Action: Please create a binding resource configuration for this component and set it on the import or export.
- CWLAP0801E: Export with the following name {0} does not exist in any module in the server.
- Explanation: Export with the following name {0} does not exist in any module in the server.
- User Action: Please create an export with the given name or the binding is not sending the correct export name to the Constant function selector.
- CWLAP0802E: Export {0} has an interface with more than one operation on it. It should have exactly one operation on the interface.
- Explanation: This function selector requires that the interface on the export contain only one operation in it.
- User Action: Either select a different function selector which will work with multiple operations or change the interface on the export to have only one operation to use this function selector.
- CWLAP0803E: The export name is not set in the binding context by the export component.
- Explanation: The export component is required to set the export name in the binding context. This information is missing from the binding context.
- User Action: Please log a PMR.
- CWLAP0804E: The export type is not set in the binding context by the export component.
- Explanation: The export component is required to set the export type in the binding context. This information is missing from the binding context.
- User Action: Please log a PMR.
- CWLAP0900E: The simple type cannot be converted to XML data since the document root element name and namespace is not specified in the configuration.
- Explanation: To serialize simple XML element, the document root element name and namespace has to be specified for the XML data handler.
- User Action: Create a binding resource configuration for the data handler in Websphere Integration Developer and specify the root element name and namespace.