Steps to enable new WCM features in WCM 7

Agenda : This article is to explain the steps required to enable new features of IBM WCM 7.
You may need to update your old web content to take advantage of the new Web Content Management features.

Web content configuration changes

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

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" ]

Note:

• 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 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=" " ]

Note:

• 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 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 WebSphere Application Server 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 your 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 your 7.0 system to maintain legacy systems by adding the following property in the WCM WCMConfigService service using the IBM WebSphere Application Server 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_root/ConfigEngine directory of your new system.

Windows

ConfigEngine.bat deploy-wcm-legacy-localrender-portlet -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password

Linux

./ConfigEngine.sh deploy-wcm-legacy-localrender-portlet -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password

iSeries

ConfigEngine.sh deploy-wcm-legacy-localrender-portlet -DPortalAdminPwd=password -DWasUserid=username -DWasPassword=password

To add the legacy 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.

Inserting links to remote content

           Web Content Management enables you to include links to remote content in other repositories, such as IBM Lotus® Quickr, 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, you must apply the Page Builder theme to any portal page that contains the authoring portlet.

Note: 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, you must also apply the Page Builder - No Skin skin to the reserved authoring portlet instance on that page.

Steps required to export WCM Library

IBM Workplace Web Content Management (WCM) 6 provides a way that you can export and import data from libraries. This can be useful as a way to backup data for safety - especially in the early days of development.
For example, before more robust data backup and restore procedures can be trusted, you might leverage this mechanism. It is also a way that you can get data from one server to another such as from a team DEV server to your local DEV server.

(Note that Syndication, not data export/import is the proper way to keep WCM content synchronized between servers on a regular basis. This describes a backup or data move procedure, not syndication for data synchronization.)

This procedure assumes that you have already configured the data export options in the WCM data export configuration file. This is intended to simply document a quick checklist style procedure for executing new data exports on a regular basis.

• Use PuTTY to login to the server (on SSH connection if necessary)
• Change directory: cd /usr/IBM/WebSphere/wp_profile/PortalServer/wcm/config
  • If you list the contents of this directory (ls -la), you should see a file called wcm60_conf.xml. This is the file where the WCM data export options are configured. We will need to modify this file, so let's make a backup for safety first.
• Backup the config file by making a dated copy. For example:
  • cp wcm60_conf.xml wcm60_conf_2009_09_24.xml
• Use VI to open the file:
  • vi wcm60_conf.xml
• The first thing we want to do is change the date in the name of the export directory (first config line in the file). We will change the following line, for example from:
  • <property name="ExportDir" value="/usr/IBM/WebSphere/wp_profile/PortalServer/wcm/config/22Sept2009export"/>
  • to...
  • <property name="ExportDir" value="/usr/IBM/WebSphere/wp_profile/PortalServer/wcm/config/24Sept2009export"/>
• Note that there is also a line in the file that defines the libary to export. It looks like this:
  • <property name="WebLib" value="Content"/>
• We can leave that alone for now and export the Content library first. But to export other libraries, we will need to change the library name and run the export command again.
• In VI, use [ESCAPE] to exit edit mode, then :wq (write, quit). If necessary, you can skip making changes to the file with :q! (quit, but ignore changes).
• Now that we've saved the file, we can execute the export command.
• cd /usr/IBM/WebSphere/wp_profile/ConfigEngine
• ./ConfigEngine.sh export-wcm-data
• The data will begin to export and you will get a lot of information on the console. Hopefully, the console messages will end with a BUILD SUCCESSFUL message. You will then have all the data exported from the library in the directory you specified and you can later import that data if necessary.
• Now you can cd back to the directory containing the config file, use VI to change the library name to export, and repeat the process for each library you wish to export.

Some Quick Tips for using the VI editor:
k = up
j = down
w = right or forward one word
b = left or back one word
l = right 1 char
h = left 1 char
x = delete 1 char
u = undo
i = insert
[ESCAPE] = get out of edit mode
:wq = write and quit
:q! = quite ignoring changes (do not write).

Hope this article will be useful...