The oks2coral is used to archive configuration databases and stores reference of used configuration into conditions database. The application should be integrated with online setup segment to be started automatically at the moment, when new run is configured or updated in running state.

The Sequence of Actions

After the oks2coral application is running, it does the following list of actions:

  1. Reads configuration data from oks xml files using oks library.
  2. Gets head version of configuration data from archive using roks library.
  3. Compares above configuration data. If they are different, the oks2coral tries to create new incremental version relative to last base version using roks library.
  4. Puts newly created or last data version of configuration data from archive into conditions database using CDI via information service.

Integration with Online Setup

The oks2coral is a resource application in the online segment. To disable the archiving of configuration data (e.g. for test purposes) put oks2coral resource into disabled relationship of the partition object.

Request for New Base Version

The oks2coral application creates incremental version. In case if the configuration databases have been significantly modified comparing with base version (i.e. size of changes exceeds some threshold) or the configuration schema has been modified, the oks2coral reports the problem via ers. In such case it is necessary to create new base version using utility oks-create-new-base-version.sh from oks package.

Reference in the Conditions Database

The oks2coral publishes reference on archived version in the Runparams.ConfigVersions object, that can be inspected at running state using Information Service monitors.