Importing data from M3

You must have configured EventHub and M3 access, and both EventListenerNode and TaskInitialLoadNode must be bound.

When importing data from M3, M3 Mobility Core calls an MI program in M3 BE which reads a table and selects the records that belong to the same company as the user that is running the MI program. The selected rows are then sent as events to the Event Hub, which passes them on to the subscribers that want them. Note that no events will be created if there are no subscribers for them.

M3 Mobility Core starts a subscriber which captures these events, does some checks and then it writes them into the HubEvent table in the M3 Mobility Core 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 that 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.