Troubleshooting Adapters : WBI adapter fails to process outbound requests
Vinod_Valecha 270002HC72 Visits (1807)
We are starting a new series of blog posts where we shall discuss on the commonly faced issues by the users while working with the WebSphere Adapters and the ways to resolve them. This series is going to be your one-stop troubleshooting guide while using adapters.
Today's post deals with a commonly faced issue while using the legacy WebSphere Business Integration (WBI) Adapters.
Many users of WBI JDBC adapter (a legacy adapter prior to the JCA counterpart) have encountered this issue of the adapter failing to process the message from the queue.The scenario involved here is a WBI JDBC adapter picking up messages from the intergration broker's (WMB) queue and then performs a create/update operation to the database(SQL server) i.e. WMB --> JDBC adapter -->SQL Server database.
The Database and broker mentioned above is one of the examples. The same can apply for all the other databases like DB2, Oracle, Sybase, etc and other brokers like Interchange Server.
When the JDBC adapter picks up the message from the queue and attempts to process it, it errors out with the error message "received message cannot be converted to BO Message. The message is not valid and is NOT processed".
Below is a snippet of the message that you will see in your logs when this issue arises:
[MsgID: 0] [Mesg: Unable to find version "*.*.*" of business object
[Time: 2012/03/05 10:21:07.880] [System: ConnectorAgent] [SS:
JDBCConnector] [Thread: EAI2
(#21217085)] [Type: Error] [MsgID: 9068] [Mesg: The received message
cannot be converted to BO Message. The message is not valid and is NOT
processed. The response will be sent to the ReplyToQueue if it is set.
Otherwise, the message will be sent to the fault queue. Message ID:
[Time: 2012/03/05 10:21:07.968] [System: Server] [Thread:
After encountering this exception, the adapter will be unable to process the messages from the queue and the outbound operation to the database stops.
Solution to the Problem:
This exception is generally seen for any WBI adapter if the Business Object (BO) is not included in the list of the supported business objects in the configuration (.cfg) file. Thus make sure that the business object is included in the list of the supported BOs in the .cfg file.
This error is also seen if the input message is not matching exactly the format needed by the business object schema. Make sure that the element names in XML input message are exactly same as that defined in the business object.
Using the above solution should solve the issue for you.
You can always get help regarding any adapter issues by posting on the Adapter developerworks forum.