Updating from IoTC v1.2 to IoTC v1.3¶

IoTC v1.3 introduces a new system health capability and MQTTS. The system health capability reports on IoTC system status for confirmation of proper operation and detection of issues. While MQTTS enables sure communication between IoTC and application. To introduce these features, it’s been necessary to extend the docker-compose as described below. These parameters must be added to the IoTC v1.2 docker-compose file before updating to IoTC v1.3

1. The following environment variables must be added to “engine” to accommodate for system health.

   engine: 
       ... 
       environment: 
           ... 
           # newly added variables 
           - INGRESS_HOST=ingress 
           - INGRESS_PORT=7070 
           - INGRESS_USERNAME=  #enter engine user name e.g. user1 
           - INGRESS_PASS= #enter engine password e.g. pass1
           - API_URL=http://api:1887/api.beta/v1 
           - HEALTH_PUBLISH_INTERVAL=600 
   

2. The following environment variables must be added to “secrets” and “integration” to enable MQTTS. This may be skipped if MQTTS is not used.
   

   secrets: 
       ... 
       mqtt-ca-cert: 
           file: ./mqtt/config/certs/ca.crt   # Point your CA Certificate 
       mqtt-client-cert: 
           file: ./mqtt/config/certs/client.crt  # Point your Client Cert 
       mqtt-client-key: 
       file: ./mqtt/config/certs/client.key  # Point your Client Key
   

   integration: 
       ... 
       environment: 
           ... 
           - MQTT_CONNSTRING=mosquitto:8883 
           - MQTT_AUTH=0 
           - MQTT_LOCAL_EGRESS_ENABLE=1 
           - MQTT_USE_TLS=True 
           - MQTT_USE_TLS_VERIFY=True 
           ... 
       secrets: 
           - source: mqtt-ca-cert 
               target: /mqtt-ca.crt 
           - source: mqtt-client-cert 
               target: /mqtt-mqtt_client.crt 
           - source: mqtt-client-key 
               target: /mqtt-mqtt_client.key