When Fiori Launchpad is accessed directly, Web Dynpro applications work, but when the Fiori Launchpad is accessed via Web Dispatcher or other reverse proxy, the Web Dynpro application is not found.
- When viewed in a network trace, the Web Dynpro address contains a colon and port number in the Web Dynpro's name.
- Alternately, when viewed in a network trace, the Web Dynpro address contains the port as a part of the path:
e.g.: https://<Web Dispatcher FQDN>:8443/8443/sap/bc/ui2/nwbc/~canvas;window=app/wda/SUI_TM_MM_APP
When viewed in the start_up request, the URL contains a port and a relative path, but no server or protocol: :8443/sap/bc/ui2/nwbc/~canvas;window=app/wda/SUI_TM_MM_APP
- When accessing a Solution Manager Web Dynpro app via Fiori Launchpad, the following text may appear instead of the app:
SAP Solution Manager Work Centers
Select a work center from one of the tabs above.
You can also access Solution Manager content from the Fiori Launchpad: Open the SolutionManager Fiori Launchpad
SAP Fiori Launchpad
WDA, SAP Solution Manager: My Home , KBA , 404 , CA-FLP-ABA , SAP Fiori Launchpad ABAP Services , BC-WD-ABA , Web Dynpro ABAP , BC-FES-BUS-RUN , Runtime , BC-FES-BUS-HTM , HTML , CA-FLP-FE-AI , Fiori Launchpad Application Integration , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.