There is a database called SQLite.
It comes with a JDBC driver.   ITX has a JDBC adapter in V10 but I don't remember which version.  You can give it a try.
https://www.sqlitetutorial.net/sqlite-java/sqlite-jdbc-driver/

Thanks Rex!  We have considered SQLite for this use case.  The only issue is where the db locks during writes to that single user.  Multiple reads are allowed though, so it's really more of a design consideration.  If we presume this is for lookup data that does not change often then it would likely work very well as a per-server local db.

There is a database called SQLite.
It comes with a JDBC driver.   ITX has a JDBC adapter in V10 but I don't remember which version.  You can give it a try.
https://www.sqlitetutorial.net/sqlite-java/sqlite-jdbc-driver/

Did a little more research and need to understand how SQLite would work in Launcher.  I'm guessing the SQLite JDBC jar file needs to be named in the Launcher dtx.ini to be loaded in the classpath at Launcher startup.  The JVM and maps running in Launcher that call SQLite JDBC will then have access to the driver.  Am I missing anything?

Thanks Rex!  We have considered SQLite for this use case.  The only issue is where the db locks during writes to that single user.  Multiple reads are allowed though, so it's really more of a design consideration.  If we presume this is for lookup data that does not change often then it would likely work very well as a per-server local db.

There is a database called SQLite.
It comes with a JDBC driver.   ITX has a JDBC adapter in V10 but I don't remember which version.  You can give it a try.
https://www.sqlitetutorial.net/sqlite-java/sqlite-jdbc-driver/

In V10, there should be a /data/extra folder.   You can simply put your jar there.  If not, specifying it in dtx.ini should work.

Did a little more research and need to understand how SQLite would work in Launcher.  I'm guessing the SQLite JDBC jar file needs to be named in the Launcher dtx.ini to be loaded in the classpath at Launcher startup.  The JVM and maps running in Launcher that call SQLite JDBC will then have access to the driver.  Am I missing anything?

Thanks Rex!  We have considered SQLite for this use case.  The only issue is where the db locks during writes to that single user.  Multiple reads are allowed though, so it's really more of a design consideration.  If we presume this is for lookup data that does not change often then it would likely work very well as a per-server local db.

There is a database called SQLite.
It comes with a JDBC driver.   ITX has a JDBC adapter in V10 but I don't remember which version.  You can give it a try.
https://www.sqlitetutorial.net/sqlite-java/sqlite-jdbc-driver/

Just confirming where the JDBC jar file goes on RHEL ITX installs.  The itx1010/data/extra isn't working, neither is the itx1010/extjar (which already has the javamail.jar file in it, so I though it would be a good alt to data/extra.

On our Windows systems with Design Studio the /extjar location worked fine.

On RHEL I'm not even getting a JDBC trace file so it's not finding anything at all.

I'm going to try the dtx.ini approach, but was hoping I could just put the JDBC file somewhere already known to ITX.

Any other suggestions?

In V10, there should be a /data/extra folder.   You can simply put your jar there.  If not, specifying it in dtx.ini should work.

Did a little more research and need to understand how SQLite would work in Launcher.  I'm guessing the SQLite JDBC jar file needs to be named in the Launcher dtx.ini to be loaded in the classpath at Launcher startup.  The JVM and maps running in Launcher that call SQLite JDBC will then have access to the driver.  Am I missing anything?

Thanks Rex!  We have considered SQLite for this use case.  The only issue is where the db locks during writes to that single user.  Multiple reads are allowed though, so it's really more of a design consideration.  If we presume this is for lookup data that does not change often then it would likely work very well as a per-server local db.

There is a database called SQLite.
It comes with a JDBC driver.   ITX has a JDBC adapter in V10 but I don't remember which version.  You can give it a try.
https://www.sqlitetutorial.net/sqlite-java/sqlite-jdbc-driver/

I partially outsmarted myself - we use a trimmed down config/adapters.xml file.  We found that performance on RHEL 8 with the full adapter list was sluggish so we cut out ones we don't use, and JDBC was one.

I added the JDBC adapter back in and now get a different error message:

libjvm.so preloadLibrary(/itx1010/libomrsig.so): cannot open shared object file: cannot open shared object file: no such file or directory
libjvm.so failed to load: omrsig

That file does exist but under the /itx1010/java dirs.  I created a symlink to it in the root install dir /itx1010 and got a different error message:

libjvm.so preloadLibrary(/itx1010/libj9vm29.so): cannot open shared object file: cannot open shared object file: no such file or directory
libjvm.so failed to load: j9vm29

That libj9vm29.so file does not exist in my itx1010 install.

Why is the location of the "missing" so files directly under the /itx1010 install dir?

Just confirming where the JDBC jar file goes on RHEL ITX installs.  The itx1010/data/extra isn't working, neither is the itx1010/extjar (which already has the javamail.jar file in it, so I though it would be a good alt to data/extra.

On our Windows systems with Design Studio the /extjar location worked fine.

On RHEL I'm not even getting a JDBC trace file so it's not finding anything at all.

I'm going to try the dtx.ini approach, but was hoping I could just put the JDBC file somewhere already known to ITX.

Any other suggestions?

In V10, there should be a /data/extra folder.   You can simply put your jar there.  If not, specifying it in dtx.ini should work.

Did a little more research and need to understand how SQLite would work in Launcher.  I'm guessing the SQLite JDBC jar file needs to be named in the Launcher dtx.ini to be loaded in the classpath at Launcher startup.  The JVM and maps running in Launcher that call SQLite JDBC will then have access to the driver.  Am I missing anything?

Thanks Rex!  We have considered SQLite for this use case.  The only issue is where the db locks during writes to that single user.  Multiple reads are allowed though, so it's really more of a design consideration.  If we presume this is for lookup data that does not change often then it would likely work very well as a per-server local db.

There is a database called SQLite.
It comes with a JDBC driver.   ITX has a JDBC adapter in V10 but I don't remember which version.  You can give it a try.
https://www.sqlitetutorial.net/sqlite-java/sqlite-jdbc-driver/