messagegtw won't process alarms in secondary hub and data_engine dependency

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

You have the messagegtw probe running on a secondary hub and while the probe runs correctly on the primary hub, it is not processing any alarm when running on the secondary hub.

Is the messagegtw running secondary hubs dependent on the data_engine on the primary hub? 

Also, the primary hub has Windows Authentication set up on data_engine and primary hub service watcher is running as the same Windows User that has access to the DB, however, the messagegtw hub where the probe is deployed is running with local system account. 

Error: 

Jul 08 02:58:48:684 [/netcool_heartbeat, messagegtw] NisDBConnectionHandler.isConnected:118:    Failed to connect to database
java.sql.SQLException: Cannot create PoolableConnectionFactory (This driver is not configured for integrated authentication. ClientConnectionId:6d0f5973-9940-4e89-bd16-06288001bd81

Environment

• DX UIM 23.4.3
• Windows OS
• MS SQL Windows Auth
• messagegtw 1.48

Cause

• The messagegtw probe has a dependency on data_engine as it internally uses DB connection
  
  
• In case the messagegtw is installed on secondary hub, the data_engine key ponting to the primary hub data_engine address is required. Note: This key is mentioned to be "optional" in the documentation because it is not required if the messagegtw is installed on the primary hub. 
  
  
• Log on as a Service should be same as windows authentication service (Domain user).
  This is a documented requirement:
  Microsoft SQL Server

 

Resolution

If the messagegtw is deployed on a secondary hub, to resolve the issue: 

• The data_engine key must be configured (in the probe configuration) to point to the primary hub data_engine address
• if using Windows Authentication on the primary hub and data_engine DB connection, on the messagegtw hub set the Nimsoft Watcher Service to "log on as" as the same Service windows authentication service (Domain user) used on the primary hub. 

Additional Information

NOTE: As of September 2025, developments are ongoing to enhance the messagegtw probe to remove the probe dependency on the data_engine when running on secondary hubs. This will provide the flexibility of using messagegtw probe as a standalone gateway externally from network segregated hubs.