I have set the JVM with -Dhttp.proxyHost and -Dhttp.proxyPort (same as what I have in IE which can get through). With PRPC, I cannot get through? The article is about set up or change proxy server on the fly.
Why IE, SOAPUI, Chrome can get through with both https and http uisng the same internet proxy above.
With Pega given the proxy host/port above, I can only get through with http.
Will check with the network team if the gateway drop the connection when it come from PRPC? (wild guess here)
I believe it's a limitation with the SOAP wizard that it doesn't honor proxy settings. We have proxy support at runtime, but not for the wizard. Could you please raise an enhancement request for the same.
I think this could be a known issue. Your post says "- PRPC 717 719 72." Are you getting these results on the 7.2 system? I see this code in step 5 of the ValidateInfrastructure Activity for Rule-Connect-SOAP in Pega-IntegrationArchitect 07-10-23 which seems like it is fixing the issue:
// create the scheme for connection
com.pega.apache.http.conn.scheme.SchemeRegistry sr = new com.pega.apache.http.conn.scheme.SchemeRegistry();
I am unfamiliar with the SR process, but someone from that department (Kevin Zheng ?) should be able to help you through this.
I think you may have marked this post as "answered," which may get confusing for people, as you seem to still need assistance. For instance, the SOAP Connector Invoke activity may also need modification in order to make the runtime work, if it does not have the "fixed" code in it.