Running sdgtw 2.28 ,the integration with Remedy was working fine until restarted the probe,
Tried downgrading to 2.25, reinstalling the probe, upgrading to 2.2 and re configuring it from scratch but it still fails to connect.
It now fails validation and not creating tickets.
Release : 20.4
Component :sdgw
BMC Remedy : 20.02
Can see below errors in sdgw logs
Jun 01 15:22:05:398 [Thread-58, sdgtw] ServiceDesk mdr_id :BMCRemedy
Jun 01 15:22:05:398 [Thread-58, sdgtw] In validateIntegration method :url is http://localhost:35891/ca-nim-sm/api/v2/config/integration/BMCRemedy/testConnection
Jun 01 15:22:05:398 [Thread-58, sdgtw] ::: going to call parseResponse ::: URL ::MDR http://localhost:35891/ca-nim-sm/api/v2/config/integration/BMCRemedy/testConnection :: BMCRemedy
Jun 01 15:22:05:418 [Thread-58, sdgtw] responseCode :: [200] response message :: [OK]
Jun 01 15:22:05:419 [Thread-58, sdgtw] Exception in making the connection to MDR:java.lang.NullPointerException
at com.nimsoft.probe.gateway.sdgtw.SDGtwProbe.initiateAlarmSynchronizer(SDGtwProbe.java:272)
at com.nimsoft.probe.gateway.sdgtw.SDGtwProbe.initializeAndConfigureNim(SDGtwProbe.java:172)
at com.nimsoft.probe.gateway.sdgtw.SDGtwProbe.access$000(SDGtwProbe.java:70)
at com.nimsoft.probe.gateway.sdgtw.SDGtwProbe$1.run(SDGtwProbe.java:132)
at java.lang.Thread.run(Thread.java:748)
If you are using BMC Remedy integration and upgrading the probe to version 2.0 or later, you must copy the BMC JAR files again in the lib folder to use BMC Remedy