SOAP Sender exposed to public internet

[matt_austin]

How can I expose a webservice via the SOAP sender adapter to the public internet without exposing my entire XI server?

The default URL for a SOAP sender adapter is http://server:port/XISOAPAdapter/MessageServlet?channel=p:s:c&version.

I do not want my server name and port known to the public. I would like to use an alias for the soap adapter.

I could use a reverse proxy to map an external hostname to our internal server (like http://www.external.host.com to http://server, then I could use http://www.external.host.com/XISOAPAdapter/MessageServlet?channel...), but this would expose the entire XI server as I could access the administration interface via http://www.external.host.com/nwa).

How can I expose just the interfaces available through the SOAP adapter without exposing the entire XI server? I know everything is protected by username and password, but we require an additional layer of security. Is it possible to create a virtual host or something similar for just the SOAP adapter?

[Former Member]

Hi Matt,

You are on right path. That is the correct approach using reverse proxy or Web Dispatcher.

In SAP, I have not found/saw some other solutions in any EP/XI implementation.

Piyush

[Former Member]

Hi Matt !

Using a proxy you don't need to map everything. You could filter which URLs to forward and which not, to only allow /XISOAPADAPTER....URLs. Also remember to state the user in the Sender Agreement to only allow specified users to log in an use the service.

Regards,

Matias.

[matt_austin]

Thanks Matias, this is the solution we are going for. After reviewing the requirements with the network administrator, he suggested a similar approach using the SAP Dispatcher.