Importing data from M3 BE

When importing data from M3, M3 CLM calls an MI program in M3 BE which reads a table and selects the records that belong to the same company and acts as the user who is running the MI program. The selected rows are then sent as events to the Event Hub, which passes them on to the subscribers.

Note: No events are created if there are no subscribers for them.

M3 CLM starts a subscriber which captures these events, does some checks, and writes them into the HubEvent table in the M3 CLM database. The HubEvent table is then read until no new records are found and the events are routed to the appropriate import or update programs.

The EventListenerNode starts the subscriber who listens for events from the EventHub. The TaskInitialLoadNode reads the HubEventTable until there are no more records to process. When importing data, the EventListenerNode and TaskInitialLoadNode should be started, but not the StandardIntegrationNode.