If I use this in my server yaml, I can publish monitoring events to a remote queue manager using ccdt.
BusinessEvents: # Monitoring events
MQ:
policy: '{MQEventLogPolicy}:MQCCDT' # Specify a {policy project}:policy if not using 'defaultQueueManager'
enabled: true # Set true or false, default false
format: '' # Set string or none
outputFormat: 'xml' # Set comma separated list of one or more of : json,xml. Defaults to 'xml'
but when I change the format to json, I get the error.
BusinessEvents: # Monitoring events
MQ:
policy: '{MQEventLogPolicy}:MQCCDT' # Specify a {policy project}:policy if not using 'defaultQueueManager'
enabled: true # Set true or false, default false
format: '' # Set string or none
outputFormat: 'json' # Set comma separated list of one or more of : json,xml. Defaults to 'xml'
An error occurred publishing integration node event on topic '$SYS/Broker/integration_server/MonitoringEvents/JSON/is2/EIL_Loopback_APP/HTTP_LoopBack_Monitoring_Flow' using the 'MQ' transport.
: BIP2666E: Unable to open queue '$SYS/Broker/integration_server/MonitoringEvents/JSON/is2/EIL_Loopback_APP/HTTP_LoopBack_Monitoring_Flow' on IBM MQ queue manager '*LOGSVCS': completion code 2; reason code 2035.
What could be the reason??
subscription are defined for topicstring - $SYS/Broker/integration_server/MonitoringEvents/JSON/is and $SYS/Broker/integration_server/Monitoring/is, pointing to different queues.
------------------------------
Pankaj Gupta
------------------------------