IBM Websphere MQ - Creating and configuring a telemetry channel - Middleware News

IBM Websphere MQ - Creating and configuring a telemetry channel - Middleware News

A telemetry channel connects a number of MQTT clients to WebSphere® MQ. Create one or more telemetry channels on a queue manager. Each of these telemetry channels might have different configuration settings, making it easier to manage the clients attached to them.

Procedure

Create and configure a new telemetry channel by completing the following steps:

1. Right-click the telemetry Channels folder and click New > Telemetry channel. The New Telemetry Channel wizard opens.
2. Type the name of the channel in the Channel name field.
   The names of telemetry channels are restricted to 20 characters. The characters that can be used in a telemetry channel name, as with all WebSphere MQ names, are:
   

   • Uppercase A-Z
   • Lowercase a-z
   • Numerics 0-9
   • Period (.)
   • Underscore (_)
   • Forward slash (/)
   • Percent sign (%)
   Leading or embedded blanks are not allowed.
3. Type the port number in the Port number field. The default port number for a telemetry channel without SSL security is 1883.
4. Optional: If you choose to secure your new telemetry channel using SSL, select Secure channel using SSL. The port number changes to 8883, which is the default for a channel secured using SSL.
   1. Click Next.
   2. Type the name of the SSL file to use in the SSL Key File field.
   3. Type the password to unlock the key file in the SSL Passphrase field.
   4. Select Identify client using digital certificate to force all clients to send their privately signed digital certificate for authentication, or select Allow anonymous clients to stop the telemetry channel from authenticating the client using SSL.
5. Click Next.
6. Select one of the following options for client authentication:
   • Don't check client supplied username and password: Select this option if you want your program to either perform its own authentication, or you do not need any clients authenticated.
   • Check client supplied username and password (using JAAS): Select this option to verify the identity of the client using JASS. Select the name of the JAAS configuration you want to implement from the JAAS config name menu.
7. Click Next.
8. Select from one of the following menu options:
   • Select MQTT Client ID to use the supplied MQTT client ID.
   • Select Fixed user ID to disregard whatever user ID is supplied by the client. Type your preferred user ID in the User ID field. The default value is Guest on Windows® systems, andnobody on Linux® systems.
   • Select Username provided by client to use the user name supplied in by the client. If no user name is supplied, the client fails to connect to WebSphere MQ.
9. Click Next.
10. Optional: Select Launch MQTT client utility to launch the graphical utility to test the MQTT protocol.
11. Review the list of actions to be performed and click Finish.