Im trying to integrate a SQL Anywhere db with IdentityNow. When I try to test the connectivity, the conntection works, the problem came when we try to run the accounts aggregation, we obtain: no dbjdbc17 in java.library.path
We check that the SQL Anywhere server has defined the path variable to dbjdbc17, but not lucky.
Hello @Beatriz
Did you upload the JDBC driver for SQL Anywhere?
At the bottom of the source page, there is a “upload” button to select your jar file and upload it.
I did not manage to make it work with the JDBC driver.
However, I manage to make work the JDBC connector with the jConnect JDBC Driver (cf. SAP Help Portal)
My parameters:
URL: jdbc:sybase:Tds:<myhost>:2638
Driver: com.sybase.jdbc4.jdbc.SybDriver
I have only uploaded jconn4.jar.
A query like select * from users; is working for the aggregation.
Hello @Beatriz
Try to upload the jconn4.jar or wait a few minutes or restart the CCG service.
It probably means that the VA did not receive the driver. It takes a few minutes for the VA to get the file.
If you have the proper jconn4.jar, the class com.sybase.jdbc4.jdbc.SybDriver is present in it.
I see you are using parameters in the connection string. At least, it would ensure that you are targeting the proper host, the proper server and the proper database.
You can also try to a simpler password. Mine was not using any special character.
I guess that testing the credentials with an administration tool is excluding the case where “user requires a new password to be specified at next login”.
The problem is that they dont see any info on the trace, is like the tenant is not capable of reach the DB. About the password, its a simple one, it doesnt contain any special character. The JDBC URL is correct, DB team confirm it.
This SO post and this one are referencing charset issues for instance.
Also, can you ensure that the port 2648 is opened from the VA (with a telnet command) for instance.
If you do not see anything in the DB logs, it might be a network issue.
Again, the analysis of the full stacktrace may help eventually.
Sorry for the delay. I did the check and I can confirm that the VA is able to stablish the connection via telnet command. So I guess there is not a network related issue. Do you have any documentation about the compatibility between IDN and SQL anywhere.