cancel
Showing results for 
Search instead for 
Did you mean: 

Only HTTPS requests are working for SOAP Sender and HTTP not working

Former Member
0 Kudos

wHi Experts,

We have enabled our HTTPS port ( SSL ) in NWA -- >> Security -- >> SSL and Key stores. So understanding is HTTPS port is now enabled on top of HTTP. So PI should be able to cater requests at both ports.

Now, we have developed a synchronous SOAP to RFC scenario and downloaded WSDL file. This file has both links -

a. http:<host>:<port>

b. https:<host>:<port>

We intend to make a PI system where both ports can work. Now questions.

1. When we test web service exposed from PI using SOAPUI tool, only HTTPS works fine and gets the response back. If we try HTTP URL, an error is encountered - HTTTPS scheme is required.

2. Is this whole understanding that both ports  ( HTTP, HTTPS ) should be able to operate simultaneously correct ? Or this is not at all possible ?

3. In SOAP Sender, we tried selecting all 3 options - 1. HTTP 2. HTTPS without client authentication 3. HTTPS with client authentication.

   None of the options have any effect on testing, Each time, only HTTPS request works and HTTP doesn't.

Can anyone please provide some hints for troubleshooting ?

Thanks..

regards,

Rajagopal.

Accepted Solutions (0)

Answers (1)

Answers (1)

chrismills
Explorer
0 Kudos

The error "HTTPS scheme is required" is normally returned when the HTTP Security Level on the SOAP adapter is not set to "HTTP". I can see you have mentioned you have tried all these, maybe a cache refresh has gone wrong? Could try recreating the channel with just HTTP specified as security level and this should allow HTTP or HTTPS

I assume you are using a different port number for  your HTTP and HTTPS requests from SOAP UI. Normally the HTTPS port is the same as the HTTP port number but the final zero changed to a 1 i.e. https://<host>:50001 instead of http://<host>:50000.

You should be able to confirm both HTTP and HTTPS work OK by loading some of the system webpages in a browser over HTTP and over HTTPS i.e. http://<host>:<port>/nwa and https://<host>:<port>/nwa

Chris

Former Member
0 Kudos

Hi Chris,

Thanks for your reply, let me try to do cache refresh with new sender agreement.

Regards

Rajagopal D

Former Member
0 Kudos

Hi Chris,

I did full CPA Cache Refresh and created new Sender agreement for HTTP, still same error is coming.

when i check in other (i.e DEV server) where only http port is enabled , no https enables.

http is working fine in SOAPUI.

Regards

Rajagopal D