Extending Web Content Management

You can extend the standard features of IBM Lotus Web Content Management using the Web Content Management API and JSP files.

• The IBM Lotus Web Content Management API

  You can use the Web Content Management API to extend functions of Web Content Management.

• Use remote actions

  Remote actions are used in the query string of a URL to trigger actions from the IBM Lotus Web Content Management application.

• Creating a custom launch page

  You can configure an authoring portlet to use a launch page of your own design instead of the default user interface.

• Creating custom plug-ins

  A custom plug-in is a reusable Java class that you create to perform a task. You can create custom plug-ins such as custom workflow actions and plug-ins to run when a page is rendered.

• Display data from external sources

  You display data from external sources using the same methods as you would when creating a Web site.

• Creating Web sites for different localities

  Although Web sites that automatically display content for different localities or languages are not directly supported by Web Content Management, it is possible to maintain separate libraries and sites within IBM Lotus Web Content Management for different localities.

• Work with IBM Web Content Integrator

  The Web Content Integrator is a solution for integrating externally managed Web content with WebSphere Portal. Through the use of standard content syndication feed technologies based on RSS 2.0, the Web Content Integrator provides a loosely-coupled mechanism for transferring published content and meta data to the portal after they have been approved in the source system. Once the content and meta data have been transferred to the portal, it is possible to leverage the built-in content management features of WebSphere Portal to secure, personalize, and display the content to end users.

• Use WebDAV with Web content

  With WebDAV for WebSphere Portal, you can use standard operating system tools to create, modify, and delete Web content rather than the standard authoring portlet.

Parent topic:

Manage Web content

---