Key Components of IBM Lotus Web Content Management.
https://ibmwcmonlinetraining.blogspot.com/2016/05/key-components-of-ibm-lotus-wcm.html
IBM Lotus Web Content management is fully integrated with the WebSphere Portal Following are the key components of WCM:
IBM Lotus Web Content Management Server : All request for content are processed by the content server. The content server influences Virtual Member Manager as its user repository for authentication and group membership.
IBM Lotus Web Content Management Content Repository : WCM uses WebSphere Portal’s embedded Apache Derby database as its content repository. But if required you can switch to other supported databases. You can find the list of supported databases at As this list of supported databases is subject to change, refer to the WebSphere Portal Information Center for details on the latest supported versions and platforms.
IBM Lotus Web Content Management Authoring Portlet : The Authoring Portlet provides you the graphical user interface for interacting with IBM Lotus Web Content Management. Content creators use the portlet to author content. Content approvers use this same portlet for managing content.Developers use this portlet to create technical assets (for example, Presentation Templates, Workflows, Syndication components, and so forth). The Authoring Portlet allows for very granular user interface security controls.
IBM Lotus Web Content Management Connect Servlet : The Connect Servlet is used to fetch content outside the Portal env. Visior can request a content directly from the Connect Servlet.
IBM Lotus Web Content Management Rendering Portlets : IBM WCM provides two portlets to show your content on Websphere Portal:
1) Local Rendering Portlet: This portlet is used to show content locally on the portal server where the instance of WCM is also live. Hence this portlet can only be used to show content when deployed on Websphere Portal Server which also has WCM running on it.
2) Remote Rendering Portlet: This portlet is used to show content on portal other then instance where IBM WCM is installed. Hence it uses an HTTP connection to Remote WCM content server to fetch content at runtime.
