For the notifications there are two transport layers available that can be configured independently. These settings can be made in the current domain object.
If the settings are modified, it takes a short moment to ensure that the modifications are distributed to other Fabasoft Folio COO Services (synchronization threads run in periodical intervals).
After a restart of Fabasoft Folio COO Services the new settings are active. Starting the Fabasoft Folio COO Services the used settings are written to the event log (see chapter “Event Log”).
For UDP multicast you need to configure the multicast address and the port number.
Performing a Fabasoft Folio update or a reinstallation, the “UDP multicast transport” is activated by default and the multicast address and the appropriate port are initialized with default values. These default values are dependent on the installed Fabasoft Folio Domain. The assigned multicast address stays between 18.104.22.168 and 22.214.171.124.
The event queue transport requires a RabbitMQ broker be installed within the network. In addition, the broker address or host name, port number, routing key, username, and password can be configured.
The event queue transport is disabled by default. For the use of containers, the use of RabbitMQ is recommended as UDP might not be available.
It is possible to have a configuration where both the UDP multicast and the event queue transport are enabled. In this case the Fabasoft Folio COO Service generates both types of events.
In this case an override should be used in the process hosting the Fabasoft Folio Kernel to enable just one of the transports. To configure the event listener set the environment variables EVENTQUEUELISTENERENABLED to 0 or 1 and MULTICASTLISTENERENABLED to 0 or 1 to override the “Enabled” setting in the corresponding configuration.
Note: If both protocols are enabled, the Fabasoft Folio Kernel will receive notifications twice that may slow down the system.