The problem is in the sdgtw.cfg file.
Instead of providing a queue name for the alarms to be processed by the sdgtw probe, you listed the alarm subjects:
queue_name = alarm_assign, alarm_update, alarm_close
By default the probe uses tickets for the queue name. They need to either continue using tickets for the queue name, or manually create a queue from the hub Configure GUI which subscribes to the 3 alarm subjects they are currently using for the queue_name, then use the name of the new queue in the sdgtw.cfg file.
The error message recorded in the sdgtw.log is telling you that the probe is failing to connect to any of the 3 queue names that they configured in the sdgtw.cfg file for the queue_name:
Got NimException connecting to queue alarm_assign, alarm_update, alarm_close: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'subscribe' name = 'null'
Step #3 in the "(Optional) Configure General Properties" section of the sdgtw AC Configuration document provides instructions for configuring the queue name.