Skip to Content

Integrating Web Dynpro Application in SAP Cloud Portal

Hey Experts,

I try to integrate an existing Web Dynpro Application into a SAP Cloud Portal of a SCP Trial Account during a Proof of Concept for a customer.

There are two great Blogs on this, describing how to integrate into


Portal Site:

While we got the Fiori Launchpad Scenario running (besides inspecting there is a bug within the Cloud Connector *) , the Cloud Portal Freestyle Scenario does not, and a really strange behaviour occurs.


  • Creating App Descriptor in Backend using Mass Maintenance Tool for Web Dynpro Applications
  • Create Destination to Backend System, e.g. ERP_Backend, pointing to lets say "" (Internal Network Address)
  • Creating App within the Freestyle Portal Site, pointing to Destination ERP_Backend in System Alias Field as required

  • Assigned the App to a Menu Item

But when I start the App the Browser states that the IP Address of the Server was not found. When I open F12, there is a request directly pointing to the Backend Server, which from my point of view should never ever occur. This is an external Portal Site, and the Backend Servers shall be hidden from any Frontend.

When perform the same Configuration steps for a classic Launchpad, the Scenario works fine (even if a desired Error message is shown below):

Is there anything else which I should consider when setting up this scenario?



*) Cloud Connector Bug:

The Header Parameter "host" is not set correctly while forwarding the Web Dynpro request to the Backend System. If the Virtual Hostname (e.g. DAK) differs from the actual Hostname (, a Runtime Error in the Backend CX_FQDN occurs. So we changed the Virtual Hostname and set it identically to the Internal Hostname - after this modification the scenario worked.

imgscn.png (72.5 kB)
imgscn2.png (71.3 kB)
imgscn3.png (113.1 kB)
imgscn4.png (27.3 kB)
imgscn5.png (40.3 kB)
Add comment
10|10000 characters needed characters exceeded

3 Answers

  • Best Answer
    Posted on Jan 21, 2019 at 09:54 AM


    If someone encounters the same issue:

    I assume that this scenario is only working if the Destination is set to Authentication with Principal Propagation. In my first tests this worked as expected - the request is now routed through an SCP Destination and not directly to the Backend system. I suggested SAP to update their Help Info on this here:

    Best regards,


    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 30, 2018 at 06:44 PM

    Hello ,

    Please expose the full path /sap/bc/ui2/nwbc or make sure you have exposed the /sap/bc subpath also.


    Meghal Shah

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Meghal,

      in the Cloud Connector the full path is exposed ("/").

      As we can see in the Fiori Launchpad Example, the Web Dynpro Application is launched correctly - but not if running in the Cloud Portal Runtime Environment.



  • Posted on Jan 01, 2019 at 07:53 AM

    I suggest to open an OSS message (feel free to post here the message number and I will try to route it to the right component).


    Add comment
    10|10000 characters needed characters exceeded