MID Server JDBC doesn't work

[Yadin]

We're trying to pull in data from a source using JDBC.  This appears to not work for some reason, possibly due to custom JAR.  The MID is configured, the JAR is loaded and on the MID, everything seems in order.  However, it does not work, and per log:

MID Server reported error: java.sql.SQLException: com.snc.automation_common.integration.exceptions.InvalidConnectionParameterException: JDBC connection string not specified

Well that's a peculiar message as it would indicate the software doesn't work.  There is no place to specify a connection string, the assumption is the MID should be building that from the information in the Data Source configuration (server, port, etc etc).  Any ideas why this would be?

[Tony Chatfield1]

Hi, have you reviewed your node logs for additional information regarding the issue and validated your JDBS connection configuration?

https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/credentials/reference/connection-information.html

https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/credentials/task/create-JDBC-connection.html

https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/credentials/reference/r_JDBCCredentialsForm.html#r_JDBCCredentialsForm

[Yadin]

Those second two articles aren't relevant for Data Sources.  If those are what you're referring to for validating the configuration they don't apply in this case.  If there is some method to validate a Data Source JDBC configuration please advise, I see no such function in the form.

The log on the MID shows nothing more than the log in the instance that I quoted.  Or do you mean something else by "node logs"?

[Jeffrey Siegel]

Were you able to figure this out? im having a similar issue.

[Yadin]

We abandoned the idea of using a Mid server years ago as it simply was not possible to make function and SN support was frankly non existent.  We use a scheduled CSV import as that was the only viable option.  Pity to hear 3 years later they have not fixed it, but that is pretty typical of the platform in my experience.