[HH#618312] Getting access to my DB from another tool

[HelioHost]

Username: jimkosloskey, Server: Tommy, Main domain: jim-kosloskey.com.helioho.st

Hi,



I have been successfully using DB-Visualizer to work in my DB.



The goal of this effort was to construct a simple table; a simplistic Stored
Procedure to extract from the table; and successfully invoke the Stored
Procedure.



I have accomplished that,



The final goal now is to invoke that same Stored Procedure form another tool
which uses JDBC.



What do you need to know to allow this other tool access?



My Db is called jimkosloskey_test_mule, username=jimkosloskey_whosis.



The name of the tool is Cloverleaf (it is a commercial Data Integration
Engine toolset).



Thank you for your consideration,



Jim Kosloskey

[wolstech]

If it's connecting using the same database name and database user that was previously approved for remote access, the software used on your side to make the connection doesn't matter. It should just work.

Is it not working for some reason?

[HelioHost]

When I attempt the connection, here is what I get:



An error occurred while attempting to retrieve the table/view list from
current database connection.



And.



Cannot create PoolableConnectionFactory (The connection attempt failed.)



Not very helpful I am afraid.



Thanks,



Jim

[Krydos]

Can you post your JDBC resource? Make sure to censor out the password.

[HelioHost]

Here is the connection URL:

jdbc:postgresql://65.19.154.94 :5432/jimkosloskey_test_mule



Here is the User Name:



jimkosloskey_whosis

[Krydos]

What is the driverClassName that you are using?

[HelioHost]

Ummm - that information is hidden from me by the Cloverleaf tool. Since it
is using jdbc, is there a file I would find that in?

[Krydos]

Here is a sample cloverleaf config I found

jdbc.driverClassName=org.postgresql.Driver
jdbc.url=jdbc:postgresql://localhost/clover_db?charSet=UTF-8
jdbc.username=clover
jdbc.password=clover
jdbc.dialect=org.hibernate.dialect.PostgreSQLDialect

If you are using the wrong driverClassName on the first line it would explain that error.

Another possibility is your driver version may not match the PostgreSQL version on the server.