Defining rich text options
You can configure IBMWeb Content Manager to use either the standard rich text editor, an advanced rich text editor, or a third-party rich text editor in rich text fields.
There are three options available when configuring the default rich text editor for authoring portlet:
DefaultSelect this option to use the standard JavaScript editor.
AdvancedSelect this option to use the advanced editor. This editor has more features than the default editor but requires a working Java runtime environment in the browser on the client computer.
CustomSelect Custom allows you to use a third-party rich text editor as default editor. Before using a compatible third-party rich text editor, you should read the installation and configuration instructions of the third-party rich text editor. These should include instructions for enabling the third-party rich text editor to be used in a Web Content Manager solution.
When configuring a third-party rich text editor, you need to copy a JSP file supplied by the third-party rich text editor. This file is used to launch the third-party rich text editor. You enter the name of this JSP file in the Rich Text Options section of the authoring portlet configuration.
If the third-party rich text editor is not available the standard rich text editor is used.
Storing JSP Files:JSP files can be located:
- within the was_profile_root/installedApps/node-name/wcm.ear/ilwwcm.war directory of server.
The JSP page is also stored in the client war directory of the local rendering portlet or of the servlet or portlet that calls the JSP, if using the Web Content Manager API. For example, to render a JSP page on a local rendering portlet, you would also need to store a copy of the JSP file under was_profile_root/installedApps/node-name/PA_WCMLocalRendering.ear/ilwwcm-localrende.war
- within any other web application running on portal. When referencing JSP files in another web application, use the following path: contextPath;jspPath
For example: /wps/customapplication;/jsp/editor.jsp