Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

This is an issue that I saw happening several times, when the incorrect load balancing mechanism was used!

It is quite common, even though it is not recommended, to use the Message Server to have load balancing when calling Portal iViews (SAP transaction iView). The ITS Host Name (in the Portal System Landscape configuration) will contain the HTTP (or HTTPS) message server port number:

The port number must match the one from the backend (ms/http_port or ms/https_port):

The iView will call a backend transaction via WEBGUI (SAPGUI for HTML), e.g. SU01:

But when previewing the iView, the following screen is displayed:

What happened? Why SU01 is not displayed? An important clue is present in an HTTP trace:

The call to SU01 was sent to the message server (port 8100 can be seen in the first row of the trace) and the POST method was used:

However, HTTP code 301 was used to redirect to the available application server. Code 301 means Moved Permanently; the subsequent call is using a GET method: the POST data is lost! So this is causing the SAP Easy Access Menu appearing. How can this problem be solved?

Simple! Setting ms/redirect_version = 1 via transaction code RZ11 will solve the problem; the profile file should be changed as well (so the correct setting will be available after a system restart).

After the change a new test will display the transaction:

The HTTP trace will also display different entries:

At last, but not least, as the profile parameter name indicates, this is not a problem in the ITS or in the Portal, this is an issue in the message server configuration; SAP notes 1055324 and 857596 can provide additional information.

Learn more about the ITS (and the WEBGUI) at the ITS Wiki.