S/4HANA FLP WebDynpro APP directly go to URL of backend server

[former_member182967]

Hi experts,

The My Account Bank Worklist Web Dynpro App is configured according to Fiori app reference library (LPD_CUST has been configuration to use HTTPS connection to the backend).

We use HTTPS connection to the backend server (central hub environment, S/4HANA OP1511 FPS 02). Whenever clicking this APP in FLP, I see an emtpy screen. In web consule of Google Chrome, the following error is shown:
https://backend_server_hostname:backend_HTTPS_port/url
Failed to load resouce: net: ERR_INSECURE_RESPONSE

I can open this backend url with new tab and adding exception for certicate in Google Chrome.

However, we only want to public web dispatcher hostname and its HTTPS port to end users not backend server related hostname and port, how to fix this issue?

Regards,

Ning

[former_member182967]

Hi Karan and Renan,

I get the following reply from SAP AGS which is reasonable:

In most cases, the webdynpro-applications are called in a backend-system. Hence with the navigation to the target application, a backend-call is made and the web-dynpro application is started in backend-system. The data is directly fetched form backend.

When you click on a tile on Fiori, the navigation target is evaluated from tile-definition and target-mapping. The target mapping contains often the reference to the backend-service. When the navigation is made, a url for the navigation target is evaluated and webdynpro application is started on backend (according to the specification of the target-system).

This is similar with transactions.

With SAP UI5 Fiori apps, you may also retrieve data from backend-systems using oData-Services. This services are published on the GW (frontend-server)

Regards,

Ning

[rribeiro]

Ning,

I'm able to fix this error.

In the Webdispatcher i configured PSE's files from/to backend and frontend.

RFC's was configured to connection HTTPS and "/nwbc".

How our development have 3 client's, i configured the appointments in FIORI DESIGN.

SSO isn't possible with USER kind of SERVICE, just DIALOG.

The connection E2E was configured as HTTPS.

[former_member190010]

Hi Ning,

We are having the same issue.

I understand the explanation you got from support, but have they provided any solution?

Best Regards,

Emanuel

[karanbahl]

Hi Ning,

Please check the following pointers and see if they help:

  The suffix at the end of the System Alias name is important, as it will determine which protocol to use. Always use the HTTPS to prevent mix-content mode.

The SAP_ECC_HTTPS destination is configured with the following Logon & Security options:

The Send Assertion Ticket for Dedicated Target Sys Is important, as it will prevent the NWBC logon screen in ECC since the user is already authenticated in the front-end system

Regards,

Karan

[former_member182967]

Hi Karan,

Still the same problem as according to the suggestion provided.

Regards,

Ning

[karanbahl]

Hi Ning,

Please share the screenshot of the LPD_CUST Transaction and Google Console error.

Regards,

Karan

[former_member182967]

Hi Karan,

LPD_CUST for this App.

(2235246 - SAP S/4HANA, on-premise edition 1511: Access to WebDynpro ABAP and SAP GUI functionality via Fiori Launchpad

2269272 - "Reference Lost" Error for FLP Tiles after applying new UI component version)

F12 web console information has been provided before. Not changed.

The problem has been reported to SAP AGS, I also wait for the answer from them.

Regards,

Ning

[karanbahl]

Hi Ning,

Can you check the ICF Profile Parameters for HTTP Re-direct and routing?

Regards,

Karan

[former_member182967]

Hi Karan,

What we have done in web dispatcher configuration is shown below (according to S/4HANA fiori fundation configuration):

wdisp/system_0 = SID=FE1, MSHOST=frontend1.xxx.com, MSPORT=8111, SRCSRV=*:44330, SRCURL=/sap/opu/;/sap/bc/;/sap/public/bc/;/ui2/nwbc/, CLIENT=100

wdisp/system_1 = SID=BK1, MSHOST=backend1.xxx.com, MSPORT=8111, SRCSRV=*:44330, SRCURL=/sap/es/, CLIENT=100

The URL https://<webdispater><webdispatcher_port>/sap/bc/ui2/nwbc/~...

will directly go to frontend not backend.

So I think the wdisp/system_x setting may cause this problem.

Regards,

Ning

[karanbahl]

Hi Ning,

The first setting points to the FES/Gateway:

wdisp/system_0 = SID=FE1, MSHOST=frontend1.xxx.com, MSPORT=8111, SRCSRV=*:44330, SRCURL=/sap/opu/;/sap/bc/;/sap/public/bc/;/ui2/nwbc/, CLIENT=100

The second system points to ECC/Backend

wdisp/system_1 = SID=BK1, MSHOST=backend1.xxx.com, MSPORT=8111, SRCSRV=*:44330, SRCURL=/sap/es/, CLIENT=100

For XSOData, we usually  use XSSRV/EXTSRV after the SID;

wdisp/system_1 = SID=BK1, XSSRV=backend1.xxx.com:8111, SRCSRV=*:44330, SRCURL=/sap/es/, CLIENT=100

wdisp/system_1 = SID=BK1, EXTSRV=backend1.xxx.com:8111, SRCSRV=*:44330, SRCURL=/sap/es/, CLIENT=100

Can you check this?

Regards,

Karan

[karanbahl]

Hi Ning,

Were you able to resolve this?

Regards,

Karan

[former_member182967]

Hi Karan,

Sorry for late reply, the case is forward to SAP developers and I'm waiting for the reply from them.

I will update ASAP.

Regards,

Ning

[rribeiro]

Hi ning,

You could solve?

[former_member182967]

Hi Renan,

Sorry, currently no.

Regards,

Ning