search cancel

DX OnPrem Gateway fails.

book

Article ID: 215236

calendar_today

Updated On:

Products

CA Application Performance Management SaaS

Issue/Introduction

Trying to attempt to have 2 DX OnPrem Gateways connect to the same DX SaaS Tenant. It appears only 1 DX Gateway can get connected at 1 time. I can shutdown 1 DX Gateway and the other will work, so I know the configuration is correct.

Both DX Gateways are using the "dxsaas_username" : "SERVICE-ACCOUNT-USER" in the Tenant.

Environment

Release : SAAS

Component : APM SAAS ENTERPRISE

Resolution

In a customer call, the following was done:

Manually set the following two properties in onprem_gateway.properties on the 2nd DX OnPrem Gateway and restarted to get it up and running:

doi.alarm.lastExecutedDateTime=2021-05-17T00\\:00\\:26Z

doi.alarm.defaultDelayToTrigger=4

 

The doi.alarm.defaultDelayToTrigger property value determines the timeFrom value for the initial pool request on how many hours back from the current time, e.g. if doi.alarm.defaultDelayToTrigger=4, then timeFrom value would be 4 hours back from the current time.

The doi.alarm.lastExecutedDateTime property value logs the last executed datetime. 

Development also advised to use just one instance of DX OnPrem Gateway when having 2 webhook destinations instead of setting up 2 instances with one webhook destination in each configuration.  The customer could add the 2nd webhook url destination in the same webhook_gtw.cfg on one DX OnPrem Gateway instance inside the <netcool> xml element: e.g.

 

<netcool>
class = JsonPublisher
<filter> ... </filter>
<payload> ... </payload>
<1>
url = http://some_webhook_url_destination_here
auth_method = none
auth_key =
username =
password =
</1>
<2>
url = http://another_webhook_url_destination_here
auth_method = none
auth_key =
username =
password =
</2>
</netcool>