Apama 10.3 | Apama Documentation | Connecting Apama Applications to External Components | Standard Connectivity Plug-ins | The MQTT Transport Connectivity Plug-in | Configuring the connection to MQTT (dynamicChainManagers)
Configuring the connection to MQTT (dynamicChainManagers)
You configure one or more dynamicChainManagers to connect to different MQTT brokers. For example:
transport: mqttTransport
brokerURL: tcp://localhost:1883
Connection-related configuration is specified in the managerConfig stanza on the dynamicChainManagers instance. The following configuration options are available for managerConfig:
Configuration option
URL for the MQTT broker.
For example, you can use the following URL for non-TLS connections:
To enable SSL/TLS, you simply indicate this in the broker URL. For example:
Type: string.
Prefix for dynamic mapping. If the prefix ends with a colon (:), it needs to be enclosed in quotation marks (see also Using YAML configuration files).
When the channel is mapped to an MQTT topic, the prefix is not used. For example, if the prefix is "mqtt:", then the channel mqtt:test/a maps to the MQTT topic test/a.
Type: string.
Default: "mqtt:".
Used with TLS. By default, connections to unrecognized certificates are terminated. Set this to true if non-validated server certificates are to be accepted.
Type: bool.
Default: false.
Used with TLS. By default, server certifications signed by all standard Certificate Authorities are validated. Optionally, you can set this option to provide a path to a CA certificate file in PEM format to authenticate the host with.
Type: string.
User name for authentication.
Type: string.
Password for authentication.
Type: string.
Used by TLS. Optionally, you can set this option to provide a path to a CA certificate file in PEM format to authenticate the client with.
Type: string.
Used by TLS. Optional password used to decrypt the client private key file, if encrypted.
Type: string.
Used by TLS. Optional path to a PEM file containing the private key, if not already included in the certificate file.
Type: string.
Important: If you provide a password for authentication via the configuration file, you must ensure to protect the configuration file against any unauthorized access, since the password will be readable in plain text.

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.