WebSphere MQ Telemetry - Middleware News
WebSphere MQ Telemetry supports the connection of telemetry devices to WebSphere MQ. Telemetry devices include, but are not limited to, sensors and actuators, mobile phones, smart meters, medical devices, vehicles, and satellite locations. The connection is made possible by the WebSphere MQ Telemetry Transport (MQTT) protocol.
MQTT is an open message format and protocol that you can use to transfer messages from telemetry devices to a message server or vice versa. It can run on constrained devices and across constrained networks. Constraints on devices include low memory and processing capability. Constraints on networks include low bandwidth, high latency, high cost, and fragility. MQTT has been successfully deployed in various industries, including energy, utilities, and the retail sector.
This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...
Comments
Post a Comment