Enable new Web Content Manager features
You might need to update the 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 WCM. Instead, you now use the WCM WCMConfigService service to update configuration settings using the WAS admin console. For more information, see Set service configuration properties.
Web content tag format changes
Web content tags now use brackets, enabling you to enter web content tags directly into rich text fields.
For example, in previous versions the component tag was written as:
<component name="componentname" />The component tag now uses brackets:
[component name="componentname" ]
- All web content tags are converted to the new format during migration.
- After migration, if a user enters a web content tag using the old format, it will be converted to the new format when saved.
New web content property tag
The IDCmpnt, HistoryCmpnt, ProfileCmpnt, WorkflowCmpnt, and SecurityCmpnt tags are no longer supported. These features are 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=" " ]
- These tags are converted to the new property tag during migration.
- After migration, if a user enters one of the deprecated tags, it will be converted to the new property tag when saved.
Autofill parameter in web content tags
The behavior of the autofill parameter used in some web content tags is updated. If used in an item where autofill is not applicable, the tag instead uses the context of the current item.
If you do not want this behavior to be used, we can set the renderAutoFillTagsAsCurrent to false in the WCM WCMConfigService service using the WAS admin console.
Federated content component and element
The federated content component and element are no longer supported in version 8.0. To reference federated content in the website, use one of the following features:
- The ECM window
- The Web Content Integrator
- The federated document feature of Personalization
Federated content components and elements are migrated from previous versions and are visible in the authoring portlet. These items can still be rendered in web pages, but we cannot create new federated content components or elements unless you enable this functionality.
To maintain older systems, enable federated content components and elements in the new system by adding the following property in the WCM WCMConfigService service in the WAS admin console:
federatedcontent.enabled=true
Local rendering portlet
The traditional local rendering portlet is no longer supported and is replaced with the web content viewer portlet, which is based on the JSR 286 API. If required, we can enable the IBM API local rendering portlet by running the deploy-wcm-legacy-localrender-portlet of the new system.
./ConfigEngine.sh deploy-wcm-legacy-localrender-portlet -DPortalAdminPwd=foo -DWasUserid=username -DWasPassword=foo
To add the traditional local rendering portlet to a page:
- Go to the Edit Layout view of a page and click Add portlets.
- Search for "Web Content Viewer".
- Select the portlet and click OK.
To use the inline editing function of WCM with the traditional local rendering portlet, ensure that Dojo 1.6 or higher is available to the portlet:
- Apply the Portal 8.0 theme to pages containing the portlet.
- Add the following metadata to the Advanced settings in the Page Properties window:
- Key: resourceaggregation.profile
- Value: profiles/profile_full.json
Links and metadata for remote content
The federated documents feature of WCM enables you to insert links to content that resides in a remote content system or document repository. Examples of supported repositories include Lotus Quickr , IBM Content Manager, IBM FileNet Content Manager, and Microsoft SharePoint. This capability is provided by the rich text editors in v8.0:
- The default and advanced rich text editors include a toolbar button named Insert Link to Remote Document.
- In addition to the toolbar button, the advanced rich text editor includes a menu item named Insert Link to Remote Document.
We can also use the federated documents feature with Personalization to create selection rules. Personalization enables you to retrieve metadata about documents stored in external content management systems or document repositories. With personalization components in Web Content Manager, we can display the metadata and create links to the documents in the web content. To select remote content in the Personalization Editor, the federated documents feature provides a wizard.
In v8.0, the capabilities of the portal theme determine whether the user interface features for WCM and Personalization are available.
To enable the Insert Link to Remote Content function after migration, ensure that the wp_federated_documents_picker theme module is available on the migrated portal. Any page containing the authoring portlet must use a theme that integrates this theme module. In addition, to ensure that the module is loaded, the module profile used by the page must include the wp_federated_documents_picker theme module. If the feature is disabled when using inline editing of web content, complete these steps:
- Apply a theme to the hidden authoring page containing the wp_federated_documents_picker theme module.
For example, we can apply the Portal 8.0 theme.
- Apply a module profile to the hidden authoring page containing the wp_federated_documents_picker theme module.
For example, we can apply the full profile of the Portal 8.0 theme.
- Apply a skin without decorations to the reserved authoring portlet instance on the hidden authoring page.
For example, we can apply the "Portal 8.0 - No Skin" skin.
To enable the folder selection wizard in Personalization, ensure that the wp_federated_documents_picker theme module is available to the page containing the Personalization Editor.
Parent: Deploy new functionality in a migrated portal
Related:
Convert an IBM API web content viewer to the JSR 286 API
Related:Configure the reserved authoring portlet
Supported specifications for inserting links to remote content