Enable new Web Content Manager features

You may need to update old web content to take advantage of the new Web Content Manager features.


Web content configuration changes

You no longer use the WCMConfigService.properties file to update configuration settings for Web Content Manager. Instead, you now use the WCM WCMConfigService service to update configuration settings using the IBM WebSphere Application Server administration console. See Set service configuration properties for further information.


Web content tag format changes

Web content management tags now use square brackets. This means web content tags can now be entered directly into rich text fields.

For example, in previous versions the component tag was written as:

<component name="componentname" />

The component tag now uses square brackets:

 [component name="componentname" ]


New web content property tag

The IDCmpnt, HistoryCmpnt, ProfileCmpnt, WorkflowCmpnt, and SecurityCmpnt tags have been deprecated. All deprecated tag features have been retained and consolidated into a new property tag.

 [Property field=" " context=" " type=" " name=" " key=" " format=" " link=" " separator=" " 
htmlencode=" " awareness=" " ifEmpty=" " include=" " restrict=" " resolve=" "
start=" " end=" " ]


Autofill parameter in web content tags

The behavior of the autofill parameter used in some web content tags has been updated so that if used in an item where autofill is not applicable, the tag will instead use the context of the current item.

If you do not want this behavior to be used, you can set the renderAutoFillTagsAsCurrent to "false" in the WCM WCMConfigService service using the IBM WAS administration console.


Federated content component and element

The federated content component and element have been deprecated in version 7.0. You can instead use features such as the new ECM dialog, the Web Content Integrator or the federated document feature of Personalization to reference federated content in website.

Federated content components and elements are migrated from previous versions and will be visible in the authoring portlet and can still be rendered in web pages, but you cannot create new federated content components or elements unless you enable this functionality.

You can enable federated content components and elements in 7.0 system to maintain legacy systems by adding the following property in the WCM WCMConfigService service using the IBM WAS administration console:

federatedcontent.enabled=true


Local rendering portlet

The local rendering portlet has been deprecated and replaced with the new JSR 286 web content viewer portlet. If required, you can enable the IBM API local rendering portlet by running the deploy-wcm-legacy-localrender-portlet task from the WP_PROFILE/ConfigEngine}}} directory of new system.
Windows™


UNIX™


i

To add the legacy local rendering portlet to a page:


Inserting links to remote content

Web Content Manager enables you to include links to remote content in other repositories, such as IBM LotusQuickr®, IBM DB2 Content Manager, or IBM FileNet Content Manager through the use of rich text fields. The rich text editors in version 6.1.5 (standard and extended rich text editor) and in version 7.0 (default and advanced rich text editor) support this function with the Insert Link to Remote Content button, and, in the case of the extended or the advanced rich text editor, with an additional Insert Link to Remote Content menu item.

In version 7.0 the availability of the button and the menu item depend on capabilities of the portal theme. In particular, the theme applied to a page containing the authoring portlet must support Dojo 1.4.x and must include the theme.capability.dojo property in its metadata.properties file (for example, theme.capability.dojo=1.4.3).

To enable the Insert Link to Remote Content function after migration, ensure that the Page Builder theme is available on the migrated portal. In addition, apply the Page Builder theme to any portal page that contains the authoring portlet. The web content page containing the reserved authoring portlet for inline editing is hidden from the portal navigation. You can locate the portlet using the Manage Pages portlet by searching for the page with the unique name com.ibm.wps.hiddenpage.wcm.Authoring_Portlet. For inline editing, in addition to setting the Page Builder theme for that hidden authoring page, also apply the Page Builder - No Skin skin to the reserved authoring portlet instance on that page.


Parent

Deploy new functionality in a migrated portal
Reserved authoring portlet


Related tasks


Add the Page Builder theme
Defining rich text options
Manage pages
Converting an IBM API web content viewer to the JSR 286 API
Set service configuration properties


Customize pages

  Sep 5, 2011 11:50:03 PM Minor change Sep 5, 2011 11:48:36 PM Added link to Converting an IBM API web content viewer to the JSR 286 ...


+

Search Tips   |   Advanced Search