When Remedy consumes a 3rd-party Webservice, which is hosted on HTTPS &/or involves Proxy setup, it fails to either consider client-side keystore or proxy configuration (as set in arserver.config file). As a result, the Webservice call fails. |
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. To address it, please try following: 1. Open axis2.xml file in AR Server's conf\axis folder 2. Search for: transportSender name="http" 3. Change the class value: from: org.apache.axis2.transport.http.impl.httpclient4.HTTPClient4TransportSender to: org.apache.axis2.transport.http.CommonsHTTPTransportSender 4. Search for: transportSender name="https" 5. Change the class value: from: org.apache.axis2.transport.http.impl.httpclient4.HTTPClient4TransportSender to: org.apache.axis2.transport.http.CommonsHTTPTransportSender 6. Save the file & restart AR Server 7. Consume the WS & verify if it succeeds These changes rollback a 1908 implementation |