Skip to Content


Introduction to our series


In this series of articles, we want to acquaint you with the architecture, functions and usage of the SAP Web Dispatcher.


In subsequent articles, you will find out about how the SAP Web Dispatcher for Hybris Marketing is configured. Our step-by-step instruction starts with a look at the parameters that need to be maintained. After this, you will learn how the configuration works when an ABAP application server (AS ABAP 7.50) is used. Although parts of Hybris Marketing will work without an XS engine, we consider a set-up with XS engine the default case. Note that without XS, important features like the CMO Dashboard won’t run. Our final topic will cover how configuration is done given the XS engine constellation.

What is the SAP Web Dispatcher and how does it work?


The SAP Web Dispatcher is an independent program run on an engine which is part of your corporate network. It serves as access point for HTTP or HTTPS requests directed to your system. The Web Dispatcher is capable of accepting and refusing connections and handles the steady distribution of requests and their way through the system. Acting this way, it fulfils three main functions: security, load balancing, and routing.


In addition to SAP systems, multiple systems (any combination of SAP and external systems) can be used with the Web Dispatcher.


But please consider: The Web Dispatcher is not only an auxiliary means but a mandatory device for running Hybris Marketing.

Diagramm_Web_Dispatcher_ohne_Zahlen.jpg  

In the diagram on the left, you can see the simple set-up with only one back end connection. The diagram on the right shows the default system design with two back end connections. You will find further explanations in the next article:


Using the SAP Web Dispatcher for Hybris Marketing, Part 2 Chapter 1

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply