Terry, Yes, it's because the Web server is only http, but the value in that is only 'arbitrary'...meaning that it's just how the web server knows to reference itself....so, if you turn it into a wsdl file, or once you load it into SoapUI, or some other tool, you can simply manually add the s, or point to individual nodes, or really...whatever you want without issue, as long as it can connect.
In short, I'm not sure how to get the web server to know that the client is using an https, but what the WSDL thinks is irrelevant as long as you are using the proper one to actually connect. On Tue, Aug 5, 2014 at 9:43 AM, Terry Bootsma <[email protected]> wrote: > ** > > > > Hi everyone: > > > > I was wondering if anyone came across this before when developing and > consuming Remedy Web Services: > > > > ARSystem - 8.1.01 > > ITSM – 8.1.01 > > > > Here is the configuration: > > > > I have two mid-tiers running on port 8080 (tomcat) front-ended by a > load-balancer that has a virtual-IP and hostname that is running on port > 8443. I have the certificate associated to port 8443 on the load balancer > and it does a “least connection” selection of which mid-tier to use. It > also “decrypts” the data from a secure connection (https) to a non-secure > connection (http) when passing to the mid-tiers. I am using this method as > I can freely add new mid-tiers without requiring additional certificates > from my certificate authority (CA) . I am using a Citrix Netscaler to > perform the load balancing. These mid-tiers are used only for web-services > and no concurrent user sessions. However, to test it, I can log into > Remedy via the load-balancer and have verified that it works just fine. > > > > To give you a clearer picture, the web service consumer connects like the > following: > > > > https://loadbalancerfqdn:8443 > > > > and it load-balances to the midtiers as follows: > > > > http://midtier1:8080 > > http://midtier2:8080 > > > > The issue I have is this. > > > > If I look at the WSDL associated to my webservice (let’s call it > MYWEBSERVICE), I can get the WSDL to display via the following: > > > > > https://loadbalancerfqdn:8443:/arsys/WSDL/public/remedyservername/MYWEBSERVICE > > > > If I look inside the web service WSDL, the port binding to the actual web > service is : > > > > <soap:address location=”http > ://loadbalancerfqdn:8443:/arsys/WSDL/public/remedyservername/MYWEBSERVICE > ””/> > > > > (notice above it is http not https! ). When I try to call it, I obviously > get errors. > > > > I am wondering, how do I get the remedy-provided WSDL to indicate https > instead of http in the binding ? Is this because I am front-ending this > via a https-based load balancer ? Can I do this ? > > > > Any ideas ? > > > > Terry > > > > > > > > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
