Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Name
    • A unique name for the bridge connection.
  • Enabled
    • Sets the enable state of the bridge connection.
  • Username
    • Optional username for connecting to the server.
  • Address
    • The server address.
  • Port
    • The server port.
  • Use TLS
      • Whether the bridge connection will be using SSL/TLS.

    Note
    • By default Chariot comes with an empty truststore file clientcerts.jks which overrides the JVM cacerts truststore. If TLS is enabled,
    remove
    • the following lines will need to be removed from the <Chariot_install_directory>/conf/com.cirruslink.chariot.system config file
    the following lines
    • :
      • trustStoreFile="security/clientcerts.jks"
      • trustStorePassword="secretpassword"
    • If the signer of the SSL/TLS cert installed on the remote MQTT Server is an external, commercial CA (e.g., DigiCert) the bridge client should successfully connect over TLS once you update the config file restart Chariot.
    • If the signer of the SSL/TLS cert installed on the remote MQTT Server is an internal, non-commercial, you will need to add your Root CA cert to the JVMs cacerts trust store and restart Chariot.


  • Client ID
    • The MQTT client ID to use for connecting to the server.
  • Keep Alive
    • The MQTT keep alive time in seconds.
  • Clean Session
    • Whether to connect with a clean session.
  • Allow Retained
    • Whether the retained message flag is allowed on messages published to the server.
  • Try Private
    • Whether the client should attempt to indicate to the server that it is a bridge client.
    • This feature helps to detect message loopback, but is only supported by some MQTT servers and may need to be disabled in order to connect.
  • Sub Topics
    • The topics filters that will be subscribed on by the bridge client.
    • The topic filters are of the form <topic>:<qos> or just <topic>.
  • Pub Topics
    • The topics filters that will be published on by the bridge client. These are used to restrict/filter which messages (flowing through Chariot) are published to the remote server,
    • The topic filters are of the form <topic>:<qos> or just <topic>.

...