Defining rich text options

You can configure IBM® Lotus Web Content Management to use different rich text editors.

There are three options available when configuring the default rich text editor for your authoring portlet:

Standard
Select this to use the standard ODC editor used by previous versions of Web Content Management.
Extended
Select this to use the EditLive! rich text editor.
Custom

Selecting Custom allows you to use a third-party rich text editor as your 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 Management solution.

When configuring a third-party rich text editor, you will need to copy a JSP file supplied by the third-party rich text editor. This will be 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 will be used.

Note: Storing JSP Files

JSP files can be located:

  • within the was_profile_root/installedApps/node-name/wcm.ear/ilwwcm.war directory of your 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 Management 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