Basic Configuration

Events

The SEF app communicates with SCO stations over the Kafka message system. The connection to this service is configured within services.json. The <host> placeholder must be replaced by the actual host address of a server running a Kafka instance.

"EVENT_SERVICE": {
  "eventServiceHost": "<host>",
  "eventServicePort": 61613
}

Additionally, the following configurations must match to have the events propagated between the systems correctly. In Event Service configurations, the internal topic prefix must be set up in the file event-service.properties. This property is used when multiple event-services have to use the same broker instance (e.g. Kafka). In such cases, a separate set of required Kafka topics (store.events, store.commands, store.states) exists for each event-service instance and has the prefix added to it - for example qa25.store.events, qa25.store.commands, qa25.store.states. Such naming is then used for the internal processing between Event Service and Kafka only and has no effect on the external STOMP topics and subscriptions.

Since Self Scanning is communicating with Kafka in the same multi-broker environment, the same prefix must be configured for correlated environments in Self Scanning Service configuration, specifically in the file self-scanning-service.properties.

Logs

The SEF app stores its own logs on a central Log Service instance. The connection to this service is configured within services.json. The <host> placeholder must be replaced by the actual host address of a server running the Log Service. <username> and <password> define the credentials to access this service.

"LOG_RECEIVER": {
    "logReceiverHost": "<host>",
    "logReceiverPort": 9200,
    "logReceiverUsername": "<username>",
    "logReceiverPassword": "<password>"
}

Managed SCO Stations

The SEF app can be configured to support only a subset of SCO stations. This subset must be identifiable by the "deviceGroup" property within the STOMP messages sent over Kafka. The SEF app will use this to filter the messages accordingly. The list of assigned SCOs is defined within assignedscos.json. This file contains an array with each array element defining a deviceGroup that should be filtered. The default value "defaultGroup" fits any SCO with a default configuration.

[
  {
    "deviceGroup":"defaultGroup"
  }
]