Regarding 'no suitable driver found'. I was receiving same message 'not a db2 database' and decided to switch to 'other db2 driver' as suggested in several posts. I noticed that when I did this, the error message switched to 'no suitable driver' from 'not a db2 database'. Then I noticed the 'db2' node in the connection url string had been dropped by the wizard when you select 'other db2 driver'. So I added it back in and BINGO Houston we have connection! jdbc

b2:SAMPLE
Hope this may help someone else. I've been struggling with this off and on for some time made all the more frustrtating as I was able to connect Visual Age for Java but wanted to migrate to WASD. This concept might also apply to newer versions of the WASD and database? Don't know but you might try.