Forum Discussion
richie
Community Hero
failed to initialise the driver? did you download the correct .jar files for the connection and stick them in the bin/ext directory?
also - as I said before - it's easier (or at least I find it easier) if I setup a connection first in a DB Interrogation tool.
If you do this first, it at least takes most of the headache out of diagnosing the problem - cos if you can connect using a db interrogation tool it means that it's the config in soapui that is the problem.
have you tried this yet?
cheers,
richie
Arunsrs
6 years agoOccasional Contributor
Yes , i hav taken azure-documentdb-2.1.0 jar and placed in bin/ext directory.
DB Interrogation tool , can u pls elaborate as i am not much familiar on this
- richie6 years agoCommunity HeroHey
Sorry for the delay in responding. What i mean by db interrogation tool is software that allows the user to generate and submit queries using sql to retrieve/insert/delete/update data im the database tables.
The trouble with connecting to a database in soapui is that there are two parts, 1. Making sure your connection to db is setup correctly and 2. The additional overhead of configuring the connection in soapui.
Soapui is a cracking tool but its not specifically built to connect to database, whereas a db interrogation tool (e.g. db visualiser, etc....there are hundreds out there) is built specifically to connect to a database and so it abstracts out some of the headache.
Hence the reason im saying install dbvisualiser and configure your connection there. Once weve confirmed you have the corrwct drivers, java version and jdbc thin driver connection string, we can then set it up in soapui knowing we have the config detail confirmed as correct.
Essentially if we have a working db connection in db visualiser and we copy those connection details across to soapui, we can more easily diagnose the error responses coming back
Has that helped?
Cheers,
Richie