Persistent Internal Database w/ Container Gateway

[Austin Bieber]

Hi there,

We are attempting to run the provided docker image of CA API Gateway v9.4 using the internal Derby database. We would like to map a volume to the database files so that the data can persist if the container is destroyed. After doing some digging around, I came across the derby log file located at /opt/SecureSpan/Gateway/node/default/var/db/derby.log. When reviewing this file, it appears that the derby database runs in memory, based on the following line from the log:

Booting Derby version The Apache Software Foundation - Apache Derby ....... on database directory memory:/db/ssgdb

I have a few questions regarding this.

(1) Is it correct that the database is running in memory and is not persistent?
(2) Is there any way in the Container Gateway to make the Derby database persistent?
(3) If the data can be persisted, where in the container will that data be stored so that we may point a docker volume to it.

Thanks in advance for the help!

------------------------------
Austin
------------------------------