Webserver or Web Dispatcher

[Former Member]

Hi,

My customer is implementing EDI Interfaces in PI (using Seeburger).

In this regard, one of the requirement is to configure the certificates and the private/public keys thereon for secured communication.

The PI domain is within the firewall. The customer landscape already has a Web Server (IIS) in place which is open to the outside network. They do not have a SAP Web Dispatcher. The customer wants to know whether the web server will perform the role of web dispatcher.

Please provide your suggestions and best practice.

Appreciate your help.

Thanks.

Krishnan

[Former Member · Accepted solution]

Hi,

>The customer wants to know whether the web server will perform the role of web dispatcher

Strange question ! Does it mean that you and your customer don't know what are the capabilities of IIS and what you want to do with it ?

For security reasons, you need at least a reverse proxy for incoming access and a proxy for outgoing access.

The reverse proxy can be for example, Apache, IIS, the SAP web dispatcher.

For the same need : B2B access to PI from and to the internet, I have setup this architecure :

Incoming :

Internet --> Apache reverse proxy --> SAP Web dispatcher --> PI

Outgoing

PI --> Apache forward proxy --> Internet

Regards,

Olivier

[Former Member]

Depending on the scope of your project you could use the SAP .NET Connector or the older DCOM Connector. I use them both to establish RFC connections.