Store-and-forward mode for gateways

If there is a problem with the gateway target, the ObjectServer and database writers can continue to run using store-and-forward mode.

When the writer detects that the target ObjectServer or database is not present or is not functioning (usually because the writer is unable to write an alert), it switches into store mode. In this mode, the writer stores everything it would normally send to the database in a file named:

$OMNIHOME/var/writername.destserver.store

In this file name, writername is the name of the writer and destserver is the name of the server to which the gateway is attempting to send alerts.

When the gateway detects that the destination server is back on line, it switches into forward mode and sends the alert information held in the .store file to the destination server. After all of the alerts in the .store file have been forwarded, the writer returns to normal operation.

Store-and-forward mode only works when a connection to the ObjectServer or database destination has been established, used, and then lost. If the destination server is not running when the gateway starts, store-and-forward mode is not triggered and the gateway terminates.

If the gateway connects to the destination ObjectServer and a store-and-forward file already exists, the gateway replays the contents of the store-and-forward file before it sends new alerts.

Store-and-forward mode is configured using the attributes STORE_AND_FORWARD and STORE_FILE.