MID Server MySQL connectivity

servicetrout
Tera Expert

Upgrading to Helsinki we are getting an error that indicates the MariaDB/J Connector needs to be added to our MID server, as described here:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0565069

I was not the person who set up with MID Server, will the following be sufficient to update the MID server to use the new driver ?

1) Download mariadb-java-client-1.5.6.jar file off web.

2) Add file to ~/servicenow/midserver/agent/lib directory (which is where our current mysql-connector-java.jar file resides.

3) I see there is a dependencies.txt file that has this line in it, not sure what the role of the file is?

  |   +- com.snc:mysql-connector-java:jar:5.1.21-snc4:compile

4) Followed the instructions on this page, which indicate the driver will be available to any

http://wiki.servicenow.com/index.php?title=Adding_JDBC_Drivers_for_Unsupported_Data_Sources#gsc.tab=...

5) Restart the server

1 ACCEPTED SOLUTION

Sashi K1
Kilo Guru

Hi Glenn


With the link provided above, it talk about deprecating MySQL driver starting from Helsinki. So all scripts that uses MySQL required to be updated MariaDB driver. That mean Helisnki has default support with MariaDB driver.



Alternatively, if we insists to use same code for MySQL driver, we have to manually download MySQL drive and add that to MID server.



Why are you downloading MariaDB driver to add to a MID?



Thanks


View solution in original post

6 REPLIES 6

Sashi K1
Kilo Guru

Hi Glenn


With the link provided above, it talk about deprecating MySQL driver starting from Helsinki. So all scripts that uses MySQL required to be updated MariaDB driver. That mean Helisnki has default support with MariaDB driver.



Alternatively, if we insists to use same code for MySQL driver, we have to manually download MySQL drive and add that to MID server.



Why are you downloading MariaDB driver to add to a MID?



Thanks


Thank you, Sashikanth.     This was good advice.   It was unnecessary to download the MariaDB driver.   Changing the MID server to use MariaDB worked fine.


Hi Glenn, we are having a similar issue after upgrading to Helsinki in our Dev environment where we are getting the following error:



          java.sql.SQLException: java.sql.SQLException: JZ001: User name property 'servicenow-svc%26password=xxxxxxxxxx' too long. Maximum length is 30.



Is this the same error that you were getting? Can you confirm what the Mid Server changes were that you made to fix this?



For info, I have added further details on the Community of the issue we are having here: JDBC Connection not working following Helsinki upgrade



Thanks



Steve


I posted my reply under your other posting.   Hope that helps.