Event Hub administration tasks
Event Hub and Event Analytics is an M3 system that is used to monitor events for related M3 applications.
Event Hub and Event Analytics are managed by Tenant Administrators and are not used by end users. Event Hub is used for outbound M3 Cloud BODs such as EDI BODs, outbound M3 Cloud FBMs, Data Lake Publisher, and M3 Function Search. Event Analytics is used for filtering of events for outbound M3 Cloud BODs and FBMs.
Event Hub uses the Apache Kafka® engine instead of JBoss HornetQ or Apache ActiveMQ® Artemis, which is used in Event Hub for on-prem version. Event Analytics uses the Apache Kafka® Streams engine instead of JBoss Drools, which is used in Event Analytics for on-prem version. Apache Kafka® persists events on disk in directories called partitions. Partitions are grouped by a name which is called a topic. For Event Hub, the tenant ID plus one or more subscriptions (without the operations) are mapped to topics.
You can specify which partition within a topic stores the event using the "keyValue" element. The element keyValue contains the primary key for the event. The element keyValue is set for all database events published by M3. You can also set it using rules in Event Analytics.
Events are only ordered within their partitions. If you create item A and then update item A two times, these three events are always delivered to subscribers in the correct order. This is because they all have the same keyValue. If you update item B before item A is updated, the event for the item B update may be delivered in a different order because it has another keyValue and is stored in another partition.
Each event is identified by an offset. The offset is an index of the event within its partition. Offsets for the latest consumed event within each partition are stored per subscriber. Several subscribers can consume events from the same partition.
Both consumed and unconsumed events are persisted for a five-day retention period. You can browse events within the retention period, by selecting one or more subscriptions and specifying a start time. You cannot purge events in Kafka® but you can skip unconsumed events by not delivering them to the subscriber application.
See Processing skipped events.
To access Event Hub, select from the M3 menu in Infor OS Portal. The EVENTHUB-Administrator or EVENTHUB-User Security role is required to access the Event Hub page.