Websphere JDBC Adapter Conclusions

A few months ago, before changing the project, my team took the decision of using JDBC Adapter for a Bridge application.

The conclusion was that it is not trivial to use and does not have enough documentation for complex cases.

1. the main problem was that the Inboud (from the DB towards application) was not always working, sometimes we had to restart the servers 5-10 time to make it work. The solution was to update the process server to a higher version;

2. We did some tricks to make the relations one child table with two parents work (see previous post);

3. Bottom line is that if you're using Websphere Application Server instead of Websphere Process Server you have more chances to have it run smoothly concerning this topic; don't use this solution unless you have pretty straight forward schema design and you're not goiing to modifiy it too often, because the manual modifications might not cover all the Websphere Integration Development wizard for Adapters generates and you'll end up swearing.