Skip to Content
0
Dec 14, 2018 at 08:19 PM

Integrating Web Dynpro Application in SAP Cloud Portal

1208 Views

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

FLP: https://blogs.sap.com/2016/11/27/launch-classical-uis-from-hana-cloud-portal/

Portal Site: https://blogs.sap.com/2018/02/10/how-to-add-an-embedded-abap-webdynpro-in-freestyle-portal/

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.

Steps:

  • 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 "https://dak.company.int:8000" (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?

Thanks,

Robin

*) 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 (dak.company.com), 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.

Attachments

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)