Public URL for Synchronous SOAP to RFC scenario

[former_member190358]

Hello Everyone,

I have synchronous SOAP to RFC scenario.

i have created the http URL for testing environment through sender agreement.

However, now the user wants a public URL and that too secured one ... means ( https ) in production.

i tried this blog, but Service registry is not configured in our landscape.

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23725

is there any other way ..?

Regards,

Ravi

[GabrielSagaya]

You can use HTTPS level authentication either HTTP with SSL (=HTTPS) without client authentication (NO certificate required) or HTTP with SSL (=HTTPS) with client authentication in sender side SOAP adapter

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3721

[former_member190358]

Hello Gabriel,

This is a Synchronous sceanrio. So i would have only one communication channel which would be sender SOAP Adapter.

There will be no receiver SOap Adapter. In this case will it take the same authentication that i set in sender SOAP Adapter.

Regards,

Ravi

[prateek]

The process of creating the wsdl will remain same. The url in your case will start with HTTPS instead of HTTP. Note that the port at which HTTPS data would be received will be different than HTTP port and thererfore you need to change that as well. You don't have to set any client authentication unless there is a business requirement. You may simply use certificates for SSL.

In some cases, if PI always receives data through web-dipatcher (ask your network team), then the data hostname and port of web-dispatcher should be used.

Regards,

Prateek Raj Srivastava

[baskar_gopalakrishnan2]

Service Registry is not a mandatory component. You can create webservice definition and share the wsdl to the customer. Use https communication (sharing the certificate with the customer) for the secured communiction. Service registry is to just publish the webservice.