Provide mapping UI for C8Y -> Hub Events (outbound)

[haraldmeyer]

UI currently only supports inbound (Hub Events -> C8Y):

There should be another menu entry "Events to Hub" and a page to configure the mapping. At the moment C8Y to ADAMOS Hub event processing is implemented in the Hub Connector Backend in a fixed way:

• Every 60s all events of type AdamosHubEvent are fetched
• Check if the device is a Hub-connected device, progress only if true
• Extract "adamos_hub_data" fragment from C8Y event
• Enhance extracted fragment with the HUB id of the device and timestamp
• Send event containing the enriched data to ADAMOS Hub

In the future the mapping should be configurable. A user should be able to select:

• The Cumulocity event type that should be the source of the mapping (free-text field)
• Optionally select one or multiple devices for which the event should be mapped. If no device is selected, rule should apply to all devices
• The ADAMOS Hub event code (=type) as a free-text field
• A list of fragments from the C8Y event that should be mapped 1:1 into the "attributes" array of the ADMOS Hub event. If the C8Y event fragment is an array, the elements of that array should be flattened into the "attributes" array.

See here for specification of ADAMOS Hub events: https://enablement.adamos.com/adamos-hub/fuer-entwickler/developer-handbook/event-service/?anchor=Event-definition

The microservice implementation here: https://github.com/SoftwareAG/c8y-adamos-hub-connector/blob/213e6499a24930ede4421272d68dbb96b241297f/ax-mm-hubconnector/src/main/java/com/adamos/hubconnector/services/EventRulesService.java#L118

needs to be extended to interpret the mapping rules and start separate listeners per mapping rule. Upon changes of mapping rules, the listeners should be updated. Listener logic should remain polling for the time being (change to Notification 2.0 is treated in #27). Probably best to have one repeated tasks that polls all "listeners".

[hnaether-c8y]

@haraldmeyer The list of fragments is optional I guess? The list of devices - should it contain all c8y devices of a tenant or just the devices which are connected with ADAMOS Hub?

[haraldmeyer]

• only Hub-connected devices
• all ADAMOS Hub Events at the moment, require a payload in the form of one or multiple fragment. It is conceivable that this might not be the case in the future though. So let us make it optional.

[hnaether-c8y]

In progress. Created UI part. Continuing with MS part.