As we know the Enterprise Portal (EP) is utilized as a centralized means of access for our end-users to obtain access to a wide array of different business applications, information and data. WPC (Web Page Composer) compliments this business setup nicely through its underlying functional base. In itself WPC can be used as a means to generate both web based (dynamic) and static content. In turn this enables users to combine business application data alongside user generated web content.
Importance of Upgrades
As we know upgrades and SP implementations are common practice in modern day business environments backed by software setups.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.
A vital point to highlight and consider surrounding NW & EP Versions is that 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.
NW Upgrades & WPC Versioning
Let us take a sample scenario in which we imagine you have upgraded from an NW 7.X Version to a later NW 7.4 or NW 7.5 Version. NW 7.X Versions will be 15 years old by 2017 meaning they are missing a whole host of different code fixes hence the importance of upgrading.
In true essence this would represent quite a significant leap in terms of Product Versions and there have been a multitude of different functional enhancements within this time-frame.
An example of such functional changes applies directly to the Web Page Composer itself.
To clarify further an upgrade from NW 7.0 to NW 7.4 would represent a complete change in WPC Versions.
- WPC 1.0 (EP 7.0) to WPC 2.0 (EP 7.30 upwards)
NW Upgrades & TinyMCE
Regarding TINY_MCE this is provided by a third party and its utilization is not supported by SAP therefore I wouldint hold a position in terms of advisory consultation on the text-editor. Although the possibility is available to use TinyMCE editor in place of HTML Editor in WPC, TinyMCE is not provided by SAP and therefore it cannot be supported by SAP.
- Any issues, which occurs in conjunction with the use of TinyMCE in WPC, would not be supportable by SAP as a result.
- There has been quite a few issues pertaining to the use of TinyMCE in the past and as highlighted its utilization is not supported by SAP.
- If you are encountering issues I would firstly recommend reviewing the official guidance document SAP KBA: 2274004 – Integrating TinyMCE HTML Editor for Web Page Composer (WPC) within the SAP Portal
Alternatives to TinyMCE
With newer NW Versioning (7.3+) you do not need to do anything in order to integrate TinyMCE editor inside them. WPC as standard plays host to a wide array of new editors. Keep in mind that the new WPC editors cannot be customized, for instance the integrated editor cannot be replaced by another editor.
- Also as the new editors depend on the SAPUI5 and it must be available too.
- If you want to carry out further testing you should: Go to System Administration > System Configuration > Knowledge Management > Content Management > Web Page Composer > Editor >Editor Configuration and * the checkbox “New Web Form Editor”.
For more information about the new editors you could check this document: