Based on comments in https://folio-org.atlassian.net/browse/EDGDEMATIC-9#icft=EDGDEMATIC-9, it seems like this is working well enough for UAT. Closing this issue.

Thanks, Slava. That does not work the same as the other edge modules, however (which accept the single dash -D options as program arguments), so it still requires special configuration. But I've updated the build script to allow for more flexibility. In my testing on folio-snapshot-test, I get the following response to the request https://folio-snapshot-test.dev.folio.org:8000/asrService/asr/lookupNewAsrItems/12345?apikey=eyJzIjoidDJFZTU0a2s5bCIsInQiOiJkaWt1IiwidSI6ImRpa3UifQ==:

So it seems like at least the module is responding as expected. The Docker container log shows that the institutional user is logged in and able to complete requests.

Just a note – you may want to tune down the default logging from DEBUG to INFO.

Putting this issue in review. After the overnight reference environment builds, the module should be available in folio-testing and folio-snapshot.

Hi @Wayne Schneider,

now it works with VM options (before -jar):

as well as with Program arguments (after -jar):

or

The only one difference - two dashes in case of Program arguments. 

Thanks,

Slava

In our testing, we found that edge-dematic requires the -D options to be before the -jar option, rather than processing them as command arguments after -jar. But otherwise the new Dockerfile seems to work well.

We should be able to accommodate this by putting the -D options in the JAVA_OPTIONS environment variable. Once the PR is merged, we can build a test environment.

Hi, Slava. I believe with the changes to the Dockerfile, you should get the same command-line as above. I will test.

And, probably, you can provide useful remarks how to provide support of $JAVA_OPTIONS on our ens.

The base container image you are using should support the JAVA_OPTIONS environment variable. Do you need options passed to the container? We can set environment variables if needed.