If you are an existing Helix customer, the first time you log in and access the new Integration Hub, your previously configured Cloud Connect products and Sensors (Communication Brokers) will be migrated to the Integration Hub.
You should now use only the Integration Hub to manage all your configured Cloud Connect products and Sensors.
When an existing Cloud Connect product is migrated to the Integration Hub, it will have a unique name with the format of product name plus the identifier used to configure the integration. Only alphanumeric characters and certain special characters, for example dot (.) and semi-colon (;), are allowed, and any other special characters will be omitted from the integration name. For example, if the previously configured Cloud Connect integration for the product Microsoft Graph had the identifier sampleconfigure, it appears as Microsoft_Graph_sampleconfigure on the Integration Hub page.
When an existing sensor is migrated from Sensors to the Integration Hub, it will have a unique name with the format hostname plus sender_id(meta_cbid). If a sensor has the same sender_id as that of a Cloud Connect product, the sensor will not be shown on the Integration Hub. When you add a new sensor manually, you must provide a unique sender_id(meta_cbid).
To view previously configured sensors, go to Main Menu .png "Helix_MegaMenu.png")
> Integration Hub, and then select Forwarding under the Category filter option. The sensor name is displayed with the appended Communication Broker ID. For example, if the previously configured sensor hostname is samplesensor, it appears as samplesensor_1131181726553888 on the Integration Hub page.
Status mapping
Integration Hub uses different status names to Cloud Connect and Sensors. Products integrated with Sensors which had a status of Disconnect, will have the status Disabled in Integration Hub.