Here're are some of my results.
1) Using wrong jar leads to hours of useless diversion (see response to Enrique). They don't return Ready with Success = false. Not cool.
2) Using InitializeSync ignores parameters in JdbcUrl, which means there doesn't appear there is a way to set Integrated Security.
3) Using Initialize (no user/passward) doesn't see Integrated Security parameter in jdbcUrl and tries to login with blank user.
4) Using 'database' or 'databasename' in jdbcUrl are fine.
5) Using 'instance=' causes Jdbc to not return
Private jdbcUrl As String = "jdbc:sqlserver://192.168.0.233\SSE2017;Database=M4storeDSS;user=yourUser;password=yourPassword;"
So, Integrated Security doesn't seem to be supported. I use that feature because my mobile socket server runs on the server with the database, so I don't have to create Logins. 'jars' don't parse jdbcUrl parameters and return Ready with success = false if a parameter is invalid, just doesn't return at all!
Thanks to all that provided feedback. Now on to creating a database server for mobile devices like I had created with VB.NET.