Pre Rendering WCM site

Pre Rendering WCM sites in your portal environment will improve performance drastically.
Recently I just did pre rendering of WCM content for our portal environment and performance improved a lot.

I will briefly talk about Concepts, Limitations/Restrictions.

For further information and detailed configuration, I would strongly recommend to go through the info center and perform configuration as per your business needs.

Concept:- 

Pre rendering allows you to cache your wcm content as static html files and save it to disk.
The pre rendered sites or static html can then be moved to web server and delivered to end users from web server.
It generates a static Web site as a set of HTML pages. Users requesting a page will get the pre-generated HTML page rather than a dynamic page from the Web Content Management connect servlet.
Web Content Management Caching, Servlet Caching (DynaCache), and pre-rendering are used to improve the performance of Workplace Web Content Management Web sites.
Although pre-rendering is the fastest option, its various limitations mean that most users will choose Web Content Management Caching or Servlet Caching over pre-rendering.

Limitations/Restrictions:-

Sites, site areas, and content items cannot contain characters that are considered invalid in file names by the operating system on which you are pre-rendering. For example, on a machine running Windows, these characters are invalid: / \ : * ? " < > |.

The pre-rendering feature cannot be used to pre-render JSP components and few more....

Here are the info center article for the same,

Pre-Rendered WCM Sites


Configuring Pre-Rendering


Accessing the pre-rendered site

EPhox EditLive Customization - Update

Latest article on EPhox Edit Live might be useful for those who are using EditLive tool for managening their WCM contents in their Portal environment.

Exporting and importing a WCM library

While working with WCM, you may come to a scenario where you have created WCM library in one environment and want to export the same library to other environment.

For example:-  You have WCM library created for staging environment and want to create the same library for you preprod or production environment.

You can easily do this by exporting library from one environment and import it to other environment.

There are certain rules and procedures that you should be aware of and also need to consider the limitations.

For detailed description, please follow steps described in article Exporting and importing a WCM library

WCM Repository Cloning Procedure

Syndicating items from one server to another either after migration or to roll out a new WCM environments can take a long time.

Database backup/restore can be used to speed up the initial set up, ready for syndication to be used from then on for incremental updates.

This article talks about Cloning a WCM repository procedure.

Download your copy from WCM Repository Cloning Procedure Guide

Editing WCM content on the fly with Edit Live

Edit Live provides rich editing experience for users of IBM Lotus Web Content Management.
This browser-based, rich content HTML editor has a Word-like interface that is easy for business users who know nothing about HTML and want to keep it that way.

Here you go,  EditLive! for IBM Lotus Web Content Management

                  Edit Live Demo

EditLive! OEM Edition is available to all licensed users of IBM's Lotus Web Content Management 6.1 or above. EditLive! Enterprise Edition adds advanced capabilities that increase productivity and content quality and is can be obtained by contacting Ephox.

WCM Best Practices: naming conventions

In one of my assignment, I got a chance to work with WCM team partially.
At the initial stage, we had been looking for some best practice to have good
naming conventions for WCM components and on of the mentioned blog article helped us to provide very useful information.

I just thought of sharing here with you all.

If you are also in the early stage of WCM, and looking for naming conventions for WCM compoents, i would suggest to have a look here before


WCM Best Practices: naming conventions

40 sites that use IBM Lotus WCM in production

Here you will find a resource relating to a list of 40 public web sites that use IBM Lotus Web Content Management (LWCM) in production. Some of them are entirely implemented with LWCM, others are built on WebSphere Portal, where pages contains Local (or Remote) Rendering Portlets, linked to a WCM content
The resource is a french blog entry:

Recommended fixes and updates for WPS and WCM

I came across to this documentaion while searching for fixes for my wps and wcm environment, hope this might be useful others...
Recommended fixes and updates for WebSphere Portal and Web Content Management

New JSR 286 WCM Rendering Portlet

I just came across with new JSR 286 WCM rendering portlet and thought of sharing here
Few of the benefits and features are.
1)You can attach Web Content Management sites and site areas to portal pages.
2)The JSR 286 Web Content Viewer does not need to be configured on Web content pages because it renders the default content attached to the page.
3)The portlet supports the portal Web 2.0 theme
4)Sessions are no longer required for rendering Web content for both anonymous and authenticated portal users.

For detailed article and list of complete features, have a look at
New JSR 286 WCM Rendering Portlet

Importing large files and images in WCM

If you have any large files or images to imported in WCM...
this article might be helpful for you...

Importing large files and images in WCM