--- schema_version: "1" id: 4e04e64bd625180253ed93d55dbce12ca543a4d7b480840352b0968bbcbeb47a title: Set a Client ID with MQTT Connector collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mqtt3-connector/latest/mqtt3-connector-client-id.md canonical_url: https://docs.mulesoft.com/mqtt3-connector/latest/mqtt3-connector-client-id source_site: docs.mulesoft.com content_type: documentation content_hash: a26b416c78dc9830aab0cd4bc233fddcdf939bee7e877d7ac2425cc7c38d8060 description: MuleSoft Documentation Site release: "1.1" latest: true --- --- product: MQTT Connector version: 1.1 is-latest-version: true --- # Set a Client ID with MQTT Connector > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Client IDs are important for MQTT because they identify a connection to an MQTT broker. Moreover, they identify a specific device or client, and it can be useful in terms of traceability to set a client ID that clearly identifies a device’s connection to the broker. MQTT brokers usually implement a mechanism that closes an old connection if a new connection request with the same client ID as the existing (old) connection is received and then accepts the new connection. MQTT brokers employ this mechanism to prevent situations such as TCP connections reaching a half-open or invalid state due to a crash in one of the communication ends, which is undesirable. The broker assumes the new incoming connection to be valid, closes the older connection, and continues using the newly established connection. The client takeover mechanism can become a problem if you want to deploy an application in a cluster, and still provide an explicit client ID that identifies the client. Anypoint Connector for MQTT (MQTT Connector) provides client ID generators that help you set a static client ID, set a client ID with a dynamic component to adjust to different deployment scenarios, or define your custom client ID generator. ## Configure the Client ID Custom Expression Generator This generator enables you to set a static string prefix and an expression as a suffix. Both parameters are optional but you must provide at least one of them in order to generate a client ID. If you do not provide any parameter, an `INVALID_CLIENT_ID` exception is thrown. In the following example, you configure the client ID string to include the current date at the end, generating a client ID similar to `principality-123-2020-09-03`: 1. In Studio, navigate to the **Global Elements** tab. 2. Click **Create**. 3. In the filter box, type `mqtt` and select **MQTT3 Config**. 4. Click **OK**. 5. In **MQTT3 Config** > **Connection**, select **MQTT3 URL Connection**. 6. For **Client id generator**, select **Client id custom expression generator**. 7. Set the following fields: - **Client ID**: `principality-123-` - **Custom Client ID Suffix**: `#[%dw 2.0 output text/plain --- now() as String {format: 'y-MM-dd'}]"` - **Username**: `mosquitto` - **Password**: `password` - **URL**: `tcp://broker.hivemq.com:1883` 8. Click **OK**. ![Client ID Custom Expression Generator configuration in Global Element Properties window](/mulesoft/current/en-us/mqtt3-connector/latest/_images/mqtt3-custom-generator.png) In the **Configuration XML** editor, the `` and `customClientIdSuffix` configurations look like this: ```xml ``` You can also specify an expression as a client ID. In the following example, dynamic configurations generate new connections for each new expression value: ```xml ``` In the following example, you configure a simple string as the client ID, which generates a static client ID `principality-123`: ```xml ``` ## Configure the Client ID Random Suffix Generator This generator enables you to set an optional static string prefix and adds a random UUID as a suffix. If you provide a static prefix, it is separated from the random UUID suffix with a `-` character. In the following example, you configure the generator to generate a client ID similar to `smart-bentley-123-0f321a85-fddf-429f-ba89-26d201db9777`, but each new connection has its own randomly generated UUID suffix: 1. In Studio, navigate to the **Global Elements** tab. 2. Click **Create**. 3. In the filter box, type `mqtt` and select **MQTT3 Config**. 4. Click **OK**. 5. In **MQTT3 Config** > **Connection**, select **MQTT3 URL Connection**. 6. For **Client id generator**, select **Client id random suffix generator**. 7. Set the following fields: - **Client ID**: `smart-bentley-123` - **Username**: `mosquitto` - **Password**: `password` - **URL**: `tcp://127.0.0.1:${mosquitto.port1}` 8. Click **OK**. ![Client ID Random Suffix Generator configuration in Global Element Properties window](/mulesoft/current/en-us/mqtt3-connector/latest/_images/mqtt3-random-generator.png) In the **Configuration XML** editor, the `<` configuration looks like this: ```xml ``` You can also omit the client ID prefix, in which case the generator assigns a random UUID as your client ID. In the following example, you configure the generator to generate a client ID similar to `0f321a85-fddf-429f-ba89-26d201db9777`: ```xml ``` ## Configure a Custom Client ID Generator If you want to supply your own custom client ID generator, you must be familiar with the Mule SDK subtypes, and the import and export annotations. In the following example, you configure your own client ID generator: 1. Create your own Java connector project. 2. In the `pom.xml` file of your connector project, add MQTT Connector as a dependency, for example: ```xml 4.0.0 org.example mqtt3-extended-connector 1.0.0-SNAPSHOT mule-extension MQTT Extended Connector org.mule.extensions mule-ee-core-modules-parent com.mulesoft.connectors mule4-mqtt3-connector 1.0.0 mule-plugin ``` 3. Create your connector’s definition class, for example: ```java @Xml(prefix = "mqtt3-extended") @Extension(name = "MQTT3Extended", category = SELECT) public class MQTT3ExtendedConnector { } ``` 4. In your custom extension, define your implementation for the `ClientIDGenerator` interface, exposed by MQTT Connector. MQTT Connector exposes the `ClientIDGenerator` interface, which requires only that you implement the method `generateClientID()`. At this point, you import this interface using the `@Import` annotation, which is then exported by MQTT Connector. ```java @Xml(prefix = "mqtt3-extended") @Extension(name = "MQTT3Extended", category = SELECT) @Import(type = ClientIDGenerator.class) public class MQTT3ExtendedConnector { } ``` 5. Define an implementation for the `ClientIDGenerator` interface: ```java @Alias("custom-client-id") public class MyClientIdGenerator implements ClientIDGenerator { /** * Client id to be used to identify the connection to the MQTT broker. */ @Parameter @DisplayName("Client ID") @Optional(defaultValue = "") @Expression(NOT_SUPPORTED) @ClientId protected String clientId; private String suffix = "my-custom-suffix"; /** * @return a client ID that results from concatenating the clientId and a randomly generated UUID string. */ @Override public String generateClientID() { return clientId + (clientId.isEmpty() ? "" : "-") + suffix; } } ``` 6. Define the subtype in your connector definition and export your custom implementation: To do so, make the previously defined implementation available to MQTT Connector by defining your custom implementation as a `ClientIDGenerator` subtype in your connector class. Also, export your `MyClientIdGenerator` class using the `@Export` annotation: ```java @Xml(prefix = "mqtt3-extended") @Extension(name = "MQTT3Extended", category = SELECT) @Import(type = ClientIDGenerator.class) @Export(classes = {MyClientIdGenerator.class}) @SubTypeMapping(baseType = ClientIDGenerator.class, subTypes = {MyClientIdGenerator.class}) public class MQTT3ExtendedConnector { } ``` After you set up your custom connector project, you are ready to access the new implementation from your application using MQTT Connector. 7. In Studio, import both your custom connector and MQTT Connector in your application’s `pom.xml` file, for example: ```xml com.mycompany mqtt-custom-id-generator 1.0.0-SNAPSHOT mule-application mqtt-custom-id-generator UTF-8 UTF-8 4.3.0-20210719 3.5.2 org.apache.maven.plugins maven-clean-plugin 3.0.0 org.mule.tools.maven mule-maven-plugin ${mule.maven.plugin.version} true org.eclipse.paho org.eclipse.paho.client.mqttv3 org.mule.connectors mule-http-connector 1.5.25 mule-plugin org.mule.connectors mule-sockets-connector 1.2.1 mule-plugin org.eclipse.paho org.eclipse.paho.client.mqttv3 1.2.5 org.example mqtt3-extended-connector 1.0.0-SNAPSHOT mule-plugin com.mulesoft.connectors mule4-mqtt3-connector 1.0.0 mule-plugin ``` When you subsequently create a new MQTT Connector configuration in your application, your custom client ID implementation appears in the list of available client ID generators. 8. To use your custom ID generator in an MQTT Connector configuration, navigate to the **Global Elements** tab. 9. Click **Create**. 10. In the filter box, type `mqtt` and select **MQTT3 Config**. 11. Click **OK**. 12. In **MQTT3 Config** > **Connection**, select **MQTT3 URL Connection**. 13. For **Client id generator**, select **Custom client id**. 14. Set the following fields: - **Client ID**: `123` - **Username**: `mosquitto` - **Password**: `password` - **URL**: `tcp://broker.hivemq.com:1883"` 15. Click **OK**. ![Custom Client ID Generator configuration in Global Element Properties window](/mulesoft/current/en-us/mqtt3-connector/latest/_images/mqtt3-custom-generator.png) In the **Configuration XML** editor, the `` and `` configurations look like this: ```xml ``` ## See Also - [MQTT Connector Examples](https://docs.mulesoft.com/mqtt3-connector/latest/mqtt3-connector-examples) - [Salesforce Help](https://help.salesforce.com)