ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

messagegtw webhook subject not displayed as an option in the hub queue dropdown


Article ID: 199955


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


Why do I not see the SUBJECT webhook as an option under our hub when creating an attach queue?

I see documentation that talks about it but when I go in and look at ours, webhook is not an option in the dropdown that we can choose.


- documentation unclear


Release : 20.1


messagegtw v1.44


As per the official help doc:

You can deploy the messagegtw on the Primary, Secondary (remote) or a robot.

Regarding the webhook queue:

The queue 'name' you create must be webhook, but the Subject/Queue can be anything you choose, e.g., probe_messagegtw, Msgs_to_SNOW, etc.,

messagegtw log extract:

Sep 21 17:41:57:505 [Timer-0, messagegtw] UimMessageListener.attachToQueue:88: Reinitializing UIM queue subscription
Sep 21 17:41:57:505 [Timer-0, messagegtw] UimMessageListener.attachToQueue:101: Subscribing for queue webhook
Sep 21 17:41:58:059 [Timer-0, messagegtw] (4) not found, Received status (4) on response (for sendRcv) for cmd = 'subscribe' name = 'null'
 at com.nimsoft.nimbus.NimSessionBase.sendRcv(
 at com.nimsoft.nimbus.NimSessionBase.sendRcv(
Sep 21 17:49:11:005 [main, messagegtw] stderr: SLF4J: See for an explanation. 
Sep 21 17:49:11:008 [main, messagegtw] stderr: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

>>>THIS IS THE POINT AT WHICH I CREATED THE WEBHOOK QUEUE...but note I dont have it 100% configured, just operating without config.

Sep 21 17:49:11:571 [main, messagegtw] UimMessageListener.readConfig:402: UIM Message Listener '/webhook' initializing
Sep 21 17:49:11:571 [main, messagegtw] UimMessageListener.readConfig:403: UIM Message Queue Name: webhook 
Sep 21 17:49:11:571 [main, messagegtw] UimMessageListener.readConfig:404: UIM Message Queue Bulk read size: 10 
Sep 21 17:49:11:571 [main, messagegtw] UimMessageListener.readConfig:405: Outgoing bulk serialization key: null 
Sep 21 17:49:11:571 [main, messagegtw] UimMessageListener.readConfig:406: UIM ThreadPool size: 20 
Sep 21 17:49:11:572 [main, messagegtw] PublisherFactory.createPublishers:32: Publisher class for outgoing communication: 
Sep 21 17:49:11:572 [main, messagegtw] PublisherFactory.createPublishers:34: Looking for configured publishers in configuration section: listeners/webhook/publishers 
Sep 21 17:49:11:573 [main, messagegtw] UimMessageListener.initEndpoints:184: Listener /webhook has 0 configured endpoints 
Sep 21 17:49:11:617 [main, messagegtw] UimMessageListener.attachToQueue:88: Reinitializing UIM queue subscription 
Sep 21 17:49:11:619 [main, messagegtw] UimMessageListener.attachToQueue:101: Subscribing for queue webhook 
Sep 21 17:49:12:422 [main, messagegtw] ****************[ Starting ]**************** 
Sep 21 17:49:12:423 [main, messagegtw] 1.44 
Sep 21 17:49:12:423 [main, messagegtw] CA Technology 
Sep 21 17:49:12:424 [main, messagegtw] port=48036 
Sep 21 17:49:12:459 [main, messagegtw] Login to NimBUS is OK 
Sep 21 17:49:12:471 [main, messagegtw] found queue name probeDiscovery with matching subject probe_discovery and type attach 
Sep 21 17:49:12:471 [main, messagegtw] The probe messagegtw should be able to publish discovery results. An attach or post queue for the subject probe_discovery on the hub /lvxxxxxxxxx23_domain/lvxxxxxxxxx23_hub/lvxxxxxxxxx23/hub has been configured. If the hub is not the primary hub and an attach queue is being used, a get queue is also needed on an upstream hub to forward the data.