The underlying purpose behind the Enterprise Portal is to provide our organizational end-users with a means of gaining centralized access to business information. Such information can stem across various data sources and application setups. As we known the environment landscape in which such information is presented can be heavily tailored and customized to suit organizational preference. Perhaps one of the overlooked elements of importance here is that of the Web Browser Platform which we use (as end-users) to access the Portal. In the modern world of information flow across the web there are several core browser platforms that we may utilize on a daily basis.
- Internet Explorer (IE)
- Google Chrome
- Mozilla Firefox
- Safari (Apple Mac)
Since January 2016 Microsoft has stopped its support for any Internet Explorer (IE) lower than IE11. SAP can’t support a browser that isn’t being supported by its manufacturer, as a result SAP doesn’t support older IE either. In accordance to SAP Note: 1672817 Internet Explorer 11 is the recommended Browser Version
From the perspective of IE11 I would firstly recommend reviewing the following Blog Posting from my Development Colleagues to ensure the correct parameters are maintained in the setup.
The following blog posting is the core comprehensive guideline for the correct settings (kindly see the IE11 section):
- IE and Portal – Standards/Quirks Mode Evolution (or Love-Hate Relationships) : http://scn.sap.com/community/enterprise-portal/blog/2014/09/03/ie-and-portal-standardsquirks-mode-evolution-or-love-hate-relationships
You can utilize this development document to cross-reference your current Browser Configurations to ensure they are maintained without any discrepancies.
From the core aspect of the Portal itself the following documentation is of direct relation:
- SAP Note: 1903267 – Browser: Internet Explorer 11 Release Notes
- SAP Note: 2398889 – Internet Explorer support for Enterprise Portal
The only 2 modes that are officially supported in portal are IE=5 for quirks and IE=Edge for standards. Hybrid solutions like IE=EmulateIE8/IE=8 can’t be supported.
- Enterprise Mode is not supported
Firstly with reference to Chrome in itself indeed there has been several noted issues with the latest versions. There has been an influx of Incidents surrounding Google Chrome 54+ Versions and these are known and documented issues. Customers are encountering a whole host of different issues pertaining to rendering and layout access.
The main point of reference here is that of SAP Note: 2372722 – Portal is not loaded on Chrome 54 and above
Additionally to the loading issues, subsequent performance degradation has been noted in some scenarios surrounding Chrome 56 and the main point of reference here is:
SAP Note: 2422288: Chrome Issue: Performance decrease of Unified Rendering / Lightspeed based applications after upgrade to Chrome version 56.
SAP highly encourages both the application and deployment of the latest Patch Level Releases & SP’s (Support Packages). The reasoning behind such encouragement is not solely based on accessibility to new features but also the avoidance of errors. Applying the latest documented fixes is a “clean” means to ensure “easily avoidable” issues do not arise in the first place.
If you are encountering the issues covered within SAP Note 2372722 then the above the concept of Patching is just as important.
- Make sure you apply the patch with all its dependencies
- It is mandatory to mention that all dependencies are applied accordingly
Make sure to apply also SAP Note 2382773 to make sure portal will be accessible after applying the first SAP Note.
- The SAP Note 2382773 is a recommendation and only relevant to newer versions of portal.
- If you are operating on a version not within Note 2382773 then the primary point of reference is that of 2372722.
You can utilize the SWDC Dependencies guidance tool (on the page) alongside SAP Note: 1974464 – Information on SCA Dependency Analysis for Java download objects for formal guidance.
Additionally the SAP Support Launchpad incorporates (on the actual page) a dependencies tool when you select a Patch or SP for download.
There is also the option of using the NW Java Dependency Analysis Tool as this is indeed a good means of guidance surrounding the dependencies and their implementation.
Firefox & Safari Issues & Fixes
- SAP Note: 2049690 – DSM pop-up window is not hidden
- SAP Note: 2228379 – DSM termination in Chrome, Safari and Firefox is not sent
- SAP Note: 1116118 – Portal DSM not working with Firefox 220.127.116.11 or higher
- SAP Note: 1480290 – Error message is displayed when login off in Fire *
- SAP Note: 1089062 – FireFox Limitations for Unified Rendering and ACF
- SAP Note: 1828529 – Excess space causes scrollbars in Firefox browser in NW7.0x
- SAP Note: 1705067 – Known issues for Portal on Device
- SAP KBA: 2396661 – Problems with web dynpro on mobile using FFP
A key source of refernece in scenarios that highlight web browser platforms as a critical source of interest is that of the PAM. The PAM stands for Product Availability Matrix and provides us with insight into which browser platforms support various NW versions and vice versa. The PAM also provides a listing of the limitations which may exist in such combinations.
The primary means of checking whether or not your present Web Browser Platform version is supported is through the SAP PAM or Product Availability Matrix.
On the PAM navigate to “Technical Release Information” & Web Browser Platforms”.
- Access the PAM: https://support.sap.com/pam