From a business standpoint, the task of performing an upgrade can be quite daunting due to the planning it entails along with validation of business requirements. Those who are familiar with utilizing the Netweaver (NW) Java Based Run-Time environment will most certainly be accustomed to the underlying tasks and processes associated with an upgrade. 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.
2017 & NW 7.0X
As we enter the latter stages of 2017 there are some very important points to highlight and consider surrounding NW Product Versioning. by the end of 2017, EP 7.0X versions will no longer be supported, and therefore we suggest to upgrade to a higher version now and not wait till the last moment. We suggest an upgrade to a Product Version of EP 7.5, which has the longest maintenance period, and moreover, you have many new features including the Fiori Framework Page and other features that are only available in the latest versions.
Existing bugs found will still be looked into and reviewed in accordance to the Product Availability Matrix (PAM) and the official SAP Documentation.
- To re-emphasize EP 7.0X versions will no longer be supported in their entirety by the end of 2017.
NW 7.0X – Why Will It No Longer Be Supported
- The Java stack in SAP NetWeaver 7.00, 7.01, 7.02, 7.03 is based on Java version 1.4.2. This Java version has reached its end of life and will be 15 years old by 2017.
NW 7.0X – My Version: Am I Still Supported?
The primary means of checking whether your present Platform version is supported is through the SAP PAM or Product Availability Matrix. On the PAM we are given insight into which different Product Versions maintain support. The PAM will also provide an informative outlined into the limitations (if any) which may exist which a potentially unsupported setup.
Why Should I Upgrade?
The following informative blog posting has been documented and put forward by my Development Colleagues as a means of outlining the important reasons behind EP-based upgrades. Within the blog posting you will find a comprehensive overview on the operational enhancements now available with new Product Versions and also the limitations which exist surrounding older releases (+ known issues).
In terms of strategic planning and preparation surrounding possible upgrades or any queries you might have the following documentation guide can be used as primary source of cross-referencing:
This document includes all relevant information, and is an entry point for many other documents\blogs.
Section (ii) – Portal Considerations (Frameworks & Themes)
As we touched on above there is a strong encouragement from SAP to upgrade to the latest Product Versioning with NW 7.5 the recommended platform. With NW 7.5 you are presented with access to a whole host of new features and functional features. It’s important to highlight an underlying change within the theming engine here. In terms of theming the UI Theme Designer is the newly released and newly available platform for both editing and generation. In terms of functional enhancements with the UI Theme Designer they key terms here are: CSS, LESS, SAP UI5, SAP NW AS ABAP, SAP NW Portal, Usability and Flexibility.
- NW 7.50 only supports the newer LESS Theming Engine.
- SAP NW 7.50 will only support the UI Theme Designer
As there is only supported for the newer LESS Theming Engine within new versioning it would be advised to move from the Classic Framework Page (CFP) to AJAX Standards Framework Page (AFP) for desktop scenarios.
- The reasoning for this is due to the conversion older Classic Framework Themes.
Within an organizational setup for NW 7.5 you can utilize any of the following Framework Setups to tailor the landscape to your business requirements:
- Fiori Framework Page (FLP@EP)
- Ajax Standards Framework Page (AFP Standards)
- Custom Standards Framework Page
If you are looking to use the Ajax Standards Framework Page then you may face issues with rendering applications.
With Ajax Standards Framework Page or a custom framework page based on this, you can run Standards/Edge applications fine inside the Portal Content Area. However, please do mind that if you have applications that require Quirks mode to run correctly, you will need to run them in the following properties configured:
- Application Parameters: add in sap-ie=EmulateIE8
- Default Document Rendering Mode: Quirks
- Launch in New Window: "Display in Separate Headerless Portal Window (standard mode)"
The reason for this is a Microsoft IE11 browser limitation. To clarify further, one page cannot simultaneously contain something of Quirks and something of Standards/Edge this is merely not possible in IE11 as it will cause rendering issues, cannot click buttons, iView is smaller than expected, and blank pages for example. It may not happen in other browsers such as Chrome/Firefox/Safari as they completely different rendering engines.
Once you have set your Framework page to Ajax Standards Framework Page, then you may wonder why HTMLB applications are not working.
Please follow 2249367 - Standards Mode Support - HTMLB in order to run Portal Based and Standalone HTMLB applications in Standards/Edge mode.
Additionally, a helpful blog regarding the use of Quirks and moving forward to Standards/Edge mode:
Section (iii) – Portal Considerations (Browsers)
With each different Web Browser Platform comes a set of different configurations which need to be maintained in order to ensure optimal performance. By performance here we are making reference to the actual display (rendering) of the Portal Setup and the navigation output (selectability).
Examples of the most commonly utilized browsers include: IE (Internet Explorer), Google Chrome and Mozilla Firefox.
A Point on IE (Internet Explorer): As of January 12, 2016 only the most recent version of Internet Explorer available for the supported operating system will receive technical support and security updates (see IE blog
http://blogs.msdn.com/b/ie/archive/2014/08/07/stay-up-to-date-with-internet-explorer.aspx). For Windows 7, 8.1 operating systems and server 2012 R2 this will be IE11. Older versions of IE are no longer supported by MS therefore it is of vital importance that you check the PAM.
Chrome: Lately 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
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.
I have a different issue -> Performance is slow
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.
This is a Live Blog Document and will be updated accordingly
