This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to
Article Number 000385088 for more information about troubleshooting BMC products in containers.
NOTE: This article applies to AR Server 9.1.03 or earlier.
We need to make sure the certificate is being used by the ar server
Step 1:
Identify the JRE path in being used for ARS. This can be checked in the armonitor.cfg/armonitor.conf
Step 2:
Execute the below command :
keytool –import –v –alias {new alias for the certificate} -file {full path to the certificate} –keystore {Path from the JRE being used by ARS \lib\security\cacerts}
If you are having problems loading the wsdl in dev studio, you may need to add a parameter in Dev Studio
> Open {DevStudioInstallPath}\devstudio.ini and add:
-Djavax.net.ssl.trustStore={Path from the JRE being used by the ARS\lib\security\cacerts}
To actually test if the current certificate works as expected please check the utility from this article:
Remedy - Server/Web - Checking SSL connection out of remedy using SSL Poke utility