Skip to Content

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

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

pastedImage_0.png (49.6 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Aug 30, 2016 at 02:00 AM

    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

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      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

  • Jun 13, 2016 at 09:47 AM

    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


    Add comment
    10|10000 characters needed characters exceeded