Rodrigo -The best way to determine why the connection to your CA SDM is failing from the sdgtw probe is to activate the NIM API debug traces, then check the Nim.log to see why the connection is failing with the configured connection parameters. Here is how you would do this:
1. Deactivate the sdgtw probe
2. Navigate to the <installPath>\Nimsoft\probes\gateway\sdgtw\NIMSM_WORKSPACE\webapp\WEB-INF\config directory, make a backup copy of the log4h2.xml file, them modify the log4j2.xml file replacing all occurrences of the following 2 strings:
level="ERROR"level="INFO"with the string:level="ALL"Save the changes.3. Activate the sdgtw probe, wait about 30 seconds, then open the probe's Configuration Page from the Admin Console and Validate the connection for your CA SDM connection profile.4. Navigate to the <installPath>\Nimsoft\probes\gateway\sdgtw\NIMSM_WORKSPACE\webapp\WEB-INF\logs directory then check the Nim.log file to see what error is reported when the NIM API attempts connecting to the configured CA SDM Service Desk application using the configured connection parameters.
pdm_log4j_config -f REST -l DEBUG -a -s 100MB
Wait a few minutes and logging goes to jrest.log.Some other tests we can try:1- Does this load in a browser?https://awisdmp01.ilg.ad:9443/caisd-rest/2- Can we try to getAccessKey using this tool?https://community.broadcom.com/communities/community-home/librarydocuments/viewdocument?DocumentKey=58614e13-f420-4245-b120-72e3700fa682#commentThanks,Shawn
NX_ROOT/bopcfg/CATALINA_BASE_REST/logs/localhost*** This will show us what happened to the call from UIM.Thanks,Shawn