Solution : https://service.sap.com/sap/support/notes/1334956 (SAP Service marketplace login required)
Summary :
Using non-fully qualified domain names can lead to multiple issues in SAP environments as outlined in this SAP Note. Troubles range from JavaScript errors in browsers to failure in session management in DSM v1.0, issues with portal content display, authentication errors, and operational glitches with page features like Automatic Height adjustment. Moreover, backend application functionalities through the portal get affected, impacting user interactions such as button or link activations. The origin of many issues is linked to domain requirements crucial for seamless browser operations per Javascript's origin policy and optimal SSL and SSO cookie management. The solution emphasizes the necessity of using fully qualified domain names to avoid such operational disruptions, with clear guidelines provided for FPN configuration to ensure correct domain settings in producer portal registrations.
Key words :
/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset, htmwhen fpn problem issued, 'support desk' -> 'sap application', fully qualified domain names, org/en/same_origin_policy_for_javascript, fully qualified domain, wrong fpn configurations, set domain-wide, top-level domain, dsm log file
Related Notes :
| 1380993 | SAP NetWeaver Portal - Specific Component Note |
| 764773 | iView Automatic Height feature limitations |
| 677118 | SP31-> Fully Qualified Domain Names Check |
| 644377 | EP6 Iview/Page ClientSide communication doesn't work |