Skip to Content

This documents explains how to figure out ( in an ABAP FES landscape) to what ABAP server one is trying to connect.

Presume someone sends you an url:

https://wdciw24.wdf.sap.corp:6021/ui

or

https://ldciuv2.wdf.sap.corp:44355/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=120

an you need to figure out the ABAP Server / Client you are working in.

Determining system during login dialogue


Solution: On the logon screen, Open Developer tools:

analyseSystem2016-07-01_10-32-44.jpg

The logon prompt sets cookies, which indicate SAP System name ( UXV ) and (in some cases) default sap-client=395

Determining system after login

Once you are connected, different cookies appear:

/wp-content/uploads/2016/07/afterlogincookies_987544.jpg

The Session cookie indicates System ID and Client.

/wp-content/uploads/2016/07/afterlogincookies_987544.jpg

Note that when navigating further one may open multiple sessions (on different servers)

/wp-content/uploads/2016/07/mulitplesessions_987549.jpg

If there are doubts, which server is the Frontendserver, this information can also be evaluated from the startupConfig.

(in 1.28 this is part of the start_up request response, in higher releases part of the FioriLaunchpad.html:

Set a breakpoint in the FioriLaunchpad source ( in this case the source appears as ui? to the browser).
controlO.jpg

Set a breakpoint below the parsing of the oServerSideConfig:
Refresh and analyze the content of oServerSideConfig in the debugger.
serverConfig2016-07-01_10-54-39.jpg

This identifies the Frontendserver system as UXV , client 395.

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