Daniel Nashed's Blog

Configure the Domino container wait for OTS

The Domino container image always waited a bit at first start until a OTS file showed up.
This was due to the expansion of the notes data tar file.

But it wasn't an explicit feature to let the server wait for a longer time for a OTS.
If no OTS was present when starting the server binary, it falls back to the legacy Java based listener for remote Domino setup.

A new variable DOMINO_WAIT_FOR_OTS=1 can now be used to always wait for OTS.

This would work for any kind of container where the admin wants to provide OTS JSON thru a trusted channel like docker cp / kubectl cp.
In case of an additional server setup this approach could also copy the server.id into the container before copying the OTS which triggers the setup to continue.
The two trigger files are the following two possible json files in the Domino's server data directory:

• DominoAutoConfig.json
• DominoAutoConfigTemplate.json
   

It is now formalizing the wait to be a feature which works also when the configuration does not happen immediately.
This isn't replacing any other setup method and is another way to add more flexibility to avoid a remote listener only using a trusted channel.

Here is an example how it looks like in the container log:

Waiting for OTS JSON in /local/notesdata

... waiting 10 seconds for OTS
... waiting 20 seconds for OTS
... waiting 30 seconds for OTS

OTS configuration found: /local/notesdata/DominoAutoConfig.json

• Comments [1]