Enabling Https in SAP PI 7.31

[vinaymittal]

Hello All,

We need to enable https for all calls coming to PI for ex via WS adapters/SOAP etc.

SMICM

NWA

I checked certificates for ssl icm in certificates and keys they are valid till 2027

PI Netweaver portal opens in https(not by default)

Can you tell me  what can be done to have the HTTPS in the <SOAP:Address> tag for ex

<soap:address location="http://pi-xyz.dd/XISOAPAdapter/MessageServlet?....."

by default when i generate wsdl for sender soap i get only http in the tag i should get https also to be able to allow it to be accessed by https...

OR

i have to redirect the http call to https by using...java system properties->http->Proxy settings (if yes ?) what is the parameter

Are there any settings missing which i can check...

Please help

Regards

Vinay

[former_member186851 · Accepted solution]

Hello Vinay,

In WSDL there will usualy 2 end points one with HTTP and other with HTTPS.

Usualy I have seen this while generating WSDL in ICO..Guess you can use the same as HTTPS endpoint.

See if the below link helps you

[vinaymittal · Accepted solution]

I am using the classical configuration not the ICO(though we have ICOS's in 20% configs) i dont see the Https endpoint in the generated WSDLs.

I will check the link but we don't have SOAP senders with client authentication. Is it mandatory to modify sender soap channels with client authentication setting if using Https?

[former_member186851 · Accepted solution]

Hello Vinay,

Am not much aware in Classical configurations,But in ICO yes there will two endpoints which I see one for HTTP and one for HTTPS.

You can select HTTPS without client authentication option in which certificates will be ignored.

[former_member182412 · Accepted solution]

Hi Vinay,

It looks like secureURL is blank as shown in this sap note 1678104 - PI Adapter Engine Cache URL shows incorrect host name

Regards,

Praveen.

[vinaymittal · Accepted solution]

Hi Praveen

where do i see this screenshot in my PI system

Regards

Vinay

[vinaymittal · Accepted solution]

Hi Raghu,

1) If i select Https without client authentication in the soap sender channel and then generate wsdl will it have the https endpoint too?

2)Do i need to regenerate the wsdl with https endpoint and provide it to the sender or it is not required and i can ask the senders to just add https in the soap urls they have?

Regards

Vinay

[former_member186851 · Accepted solution]

Hello Vinay,

1) If i select Https without client authentication in the soap sender channel and then generate wsdl will it have the https endpoint too?

As I told I can see  the WSDL having both the endpoints . Did you try the setting mentioned by Praveen or something mentioned in the link?

2)Do i need to regenerate the wsdl with https endpoint and provide it to the sender or it is not required and i can ask the senders to just add https in the soap urls they have?

Guess regeneration is required as the channel has been updated.

[former_member182412 · Accepted solution]

Hi Vinay,

Go to SLD->CIM Instances and select XI Adapter Framework and then click on association tab and then click on SOAP adapter service

Under the association click on Port for SOAP service

You will find under the properties tab.

Regards,

Praveen.

[vinaymittal · Accepted solution]

Hi Praveen/Raghu

yes the secure url parameter has that https in SLD checked it .

just to make it clear i am not saying i have any problem i want to know what action is required from my side in order to enable the sender to call soap by https...

I checked display wsdl from ICO it has two endpoints http and https

the SOAP scenarios using classical config have only http endpoint so for those do i need to give the url in https format while generating wsdl from menu options in ID...

also do i just need to give the updated wsdl to the senders so that they are able to call PI by https

or even then by default the soap will be called by http and to ensure that it is called by http i do Https without authentication in the SOAP sender channel.

Regards

Vinay

[former_member186851 · Accepted solution]

Hello Vinay,

Enable the option HTTPS without authentication with in the soap channel.

And share the HTTPS endpoint to client,it should work.

You can even test once with SOAP UI before sharing the WSDL.

[vinaymittal · Accepted solution]

Even the WSDL generated by ICO which has two endpoints when i test that wsdl in SOAP UI i see http url being called in the header....why not Https by default?

[former_member182412 · Accepted solution]

Hi Vinay,

select https end point url from the drop down and test from soap ui.

Regards,

Praveen.

[vinaymittal · Accepted solution]

i tested the ico config with http in header i got response back than changed the channel config to https without authentication and tested with https it takes forever but still didnt get response back

[vinaymittal · Accepted solution]

I dont get any response when i use https i get soap timed out exception

[former_member186851 · Accepted solution]

Hello Vinay,

Check that Link once.

In case of HTTPS did you maintain username/password in the SOAP UI?

[vinaymittal · Accepted solution]

In case of https without authentication i maintained username password in soap ui

[vinaymittal · Accepted solution]

I was using the wrong port for https earlier now i get the connection refused error....

[former_member186851 · Accepted solution]

Vinay check once with the parameters mentioned in the link.

[vinaymittal · Accepted solution]

Hi Raghu ,

Can you help me know when i was testing in soap ui with the https url and https port from smicm the request met an error connection refused but when i removed the port and gave just https i got the response back.....same for http request i was able to get the response back both by removing port for http and with port for http same happened in browser too...do you know why?

Regards

Vinay

[former_member186851 · Accepted solution]

Hello Vinay,

This one am not sure, We use same port for http and https.

My guess would the port your using is http enabled not https that why no response is thrown back.