Migration Guide to Thingshub 8: Old ThingPark/Swisscom to New ThingPark/Swisscom Network Connector
Due to changes to the API of Actility and Swisscom, we have recently updated our network connectors. As of now, both the ThingPark and Swisscom are now under the same Network connector name: Actility ThingPark
Below are the changes that we need to take into account during the upgrades:
Pre-Upgrade:
Routing Profile ID: Please make sure that an appropriate Routing Profile ID value is set in the network connector config. As of now, this is now called as Direct Association Connection ID in the new updated implementation. So, make sure you updated this field to the appropriate value before doing the upgrade. If not, below are the consequences during and after the upgrade:
A new direct connection will be created in Actility or Swisscom server
That connection ID will be used for the Direct Association Connection ID
The field will be read-only, so you won’t be able to change it afterwards (easily)
Connectivity Plan: Take a look into what connectivity plan you want to use for the devices during registration. You can easily find it from the Connectivity Plans page in the respective network servers page. Note it down
Post-Upgrade:
Direct Association Connection ID: Check that it is populated from the Routing profile ID. If not, let the team know and find a way forward here
Connectivity Plan: Put the connectivity plan you noted down into the network connector config page’s connectivity plan field. It must adhere to this format:
for ThingPark, example connectivity plan would be something like
drei-cs/h3a_cp_conn_pilotfor Swisscom LPN, the value isswisscom-cs/swisscom-cp-trial, both of them are prefixed by their network server type likedrei-csandswisscom-cs, which is mandatory)
Please refer to the documentation of the respective network server for more details. For example Actility ThingPark
With this changes, the network connectors should be up and running with the updated changes.