+

Search Tips   |   Advanced Search

Portal, V6.1

 

V5.1 to 6.1 post migration steps

The IBM Lotus WCM migration process does not automatically update your Web content to use all the new features of the current release. The following steps are recommended to update your old Web content to take advantage of the new WCM features.

 

Install the Web content authoring portlet

When migrating an authoring server also install the Web content authoring portlet by running the configure-wcm-authoring task. Before you run this task, perform the following manual steps:

  1. Log in as administrator.

  2. Click Administration > Manage Pages .

  3. Search for a page with the unique name ibm.portal.Home. If you do not have a page with that unique name create one.

    1. Create a Label somewhere under ContentRoot .

    2. Click Custom Unique Names > Pages.

    3. Find the label that you just created and give it the unique name ibm.portal.Home.

You then run the configure-wcm-authoring to install the Web content authoring portlet:

  1. Open a command prompt.

  2. Run the configure-wcm-authoring task:

    • Windows and UNIX: Run the following command from the portal_server_root/config directory:

      • Windows:

        ConfigEngine.bat configure-wcm-authoring -DWasUserId=username -DWasPassword=wpsadmin

      • UNIX:

        ./ConfigEngine.sh configure-wcm-authoring -DWasUserId=username -DWasPassword=wpsadmin

    • i5/OS:

      Run the following command from the...

      WP_PROFILE/ConfigEngine

      ...directory:

      ConfigEngine.sh configure-wcm-authoring -DWasUserId=username -DWasPassword=wpsadmin

  3. Log out of the portal and log back in.

  4. Select Web Content from the main menu to access the Authoring portlet.

Installing the Authoring portlet in a clustered environment

If the authoring portlet does not display after installation, you may need to activate the portlet. See Manage portlets in your cluster for further information.

 

Web content configuration files

The Web content configuration files connect.cfg and aptrixjpe.properties have been deprecated and replaced by the WCM ConfigService.properties file. No configuration settings from your old system are migrated to this file. You will need to edit this file and update settings to match your old configuration if required. The WCM ConfigService.properties file is located under:

Configuration parameters required to support deprecated features have been moved to a section named "Legacy" at the end of the WCM ConfigService.properties file

The JDBC URL propertyDatabase driver URLs now need to contain escape characters. You will need to edit any JDBC URLs copied from an old connect.cfg file. For example:

 

Authoring portlet access changes

There are a number of authoring access control features which plan for and implement as part of your migration. Usage of these features depends on what pattern of authoring access control you require. In version 6.1 access permissions that are set on the library are by default automatically inherited by each new item created in the library. In previous versions, access permissions were not automatically inherited by new library items. When you migrate content to a version 6.1 server, the access permissions inheritance on migrated items will not have changed. If you decide that you want to enable automatically inherited access permissions, you will need to:

If you decide that you do not want to enable automatically inherited access permissions, you will need to:

IBM recommends that you use automatically inherited access, since this new feature greatly simplifies administrating library access.

You no longer assign access to the different views in the authoring portlet by configuring the authoring portlet. Access to the different views in the authoring portlet is now determined by the role assigned to users and groups. See Use item type roles within a library for further information. Item level access types have also changed:

 

The wcmadmins group

The wcmadmins group does not automatically have administrator access in version 6.1. When you migrate your WebSphere Portal users and groups from version 5.1 to 6.1, the wcmadmins group will be migrated, but the members of this group will not have administrator access to Web content. To grant the members of your old wcmadmins group administrator access to Web content either assign the wcmadmins group, or the individual members of wcmadmins, to the administrator role on your migrated Web content library.

 

Anchor tags and URLs

You should replace any anchor tags or URLs in presentation templates or element designs by using either a link element, or using the "add link" feature in HTML and rich text fields and elements. See the Link element and Inserting a link in an element topics for further information. To assist in this process, the following files are created under the summary path folder specified during data migration:

These files can be used as reference material as they list the old and new names and paths of content items, components (library components), elements (content components) and presentation templates.

 

Links to WCM content from external sites

During migration, some items will be merged, added or renamed. You may need to update links to WCM content from external sites. To assist in this process, the following files are created under the summary path folder specified during data migration:

These files list the old and new names and paths of content items, components (library components), elements (content components) and presentation templates.

 

Siblings with the same name

Unlike previous versions of WCM , you are no longer able to create two sibling Web Content items using the same name. For example, your old system may have the following site framework:

During migration, the second site area will be renamed as "MySiteArea_1". The site framework will now look like this:

Any references to the path "MySite/MySiteArea" will be left unchanged but will now only point to the site area named "MySiteArea". You will need to edit any paths that should now point to "MySite/MySiteArea_1" instead.

This example also applies to other siblings such as categories and content items.

 

Draft items

Any draft sites, site areas and taxonomies that have child items will be published during migration, as will their children. Any items that have had there status changed from draft to published are listed in published_draft_items.txt located under the summary path folder specified during data migration. You should review this file and check that any changes to these published items are valid.

If no items have had there status changed from draft to published, this file will not be created.

 

Expiring items

In previous versions, items that had no expire date specified would never expire. In the version 6.1 this has been changed so that items with no expire date will be expired as soon as an expire action is triggered. You can configure your version 6.1 server to use the behavior available in previous versions by setting expire.blankdate.immediately to "false" in the WCM ConfigService.properties file.

 

Navigator elements

Paging is now supported in the design of navigator elements. After migration, the maximum number of items to be displayed per page is set at one hundred by default. If any or your navigators display more than one hundred items, edit this figure. You can also add a paging element to your navigator design. See Define navigator element design options for further information.

 

Menu elements

A "no result" design has been added to menu elements. You must edit all your menus and enter appropriate text in the "no result" design. Otherwise, nothing will be displayed when a menu finds no results. See Define menu element formatting options for further information.

In version 6.1, menus will return no search results if you select a search criteria but don't enter any search parameters. For example, if the menu is configured to return results based on categories, but no categories are specified in the menu form, then no matches will be found. In previous versions, menu searches would ignore any selected search criteria without search parameters. You need to fix any migrated menus that contain search criteria without search parameters. You can also configure menus to use the search behavior available in previous versions by setting menu.executeWhenCriteriaEmpty to "true" in the WCM ConfigService.properties file.

 

Authoring tool component tag

You no longer need to use an authoring tool component tag to reference authoring tool components in menu or navigator designs. Instead, use a component tag with a parameter of compute="always". For example: 

<Component name="authoringtoolname " context="autofill" compute="always" />

Existing authoring tool component tags will still function correctly in your migrated data.

 

Name and title fields

A title field has been added to the identification section of all items. The title is the text displayed to end-users when viewing a list of items in the authoring portlet. Unlike the name, titles can use double-byte and non-ASCII characters. When migrated, the current name is also copied to the title field. You will need to edit any items where you would like to use a different title than one created during migration.

Any Web content tags that use the field="name" attribute, such as the placeholder tag, can be changed to use field="title" as well.

When migrated, any invalid characters in the name field will be replaced by an underscore: "_". If more than fifty percent of the characters in a name are invalid, the name is replaced with the value of "$$!!". If this name already exists, then an integer will be added. For example, "$$!!01".

 

HTML encoding

In version 6-1, reserved HTML characters stored in some elements are converted into character entities. For example, '<' will be converted to '&lt;'. This is useful if you would like to prevent users adding malicious code, or if you want to prevent users changing the look and feel of their text using HTML. This behavior is enabled by default. To disable this behavior you edit the WCM ConfigService.properties file in was_profile_root/PortalServer/wcm/config directory and set this value to "false": 

cmpnt.htmlEncodeDefault=false

 

Connect tags

The use of "connect" tags has been deprecated, with the exception of component caching. Content that uses "connect" tags will still work, but IBM recommends that "connect" tags be replaced with other standard Web content features. See Displaying data from external sources for further information.

Configuration parameters required to support deprecated features have been moved to a section named "Legacy" at the end of the WCM ConfigService.properties file

 

WCM search

The WCM search module is no longer supported. The WebSphere Portal search features are now used to search for Web Content.

Any search forms that use the WCM search module must be replaced or updated with search forms using the WebSphere Portal search features. See Searching Sites for details on using the WebSphere Portal search features with Web content.

 

Moving objects to new libraries

The WCM migration process will only create a single library. To implement multiple libraries, create new libraries and move items from the migrated library into the new libraries. See Copying and moving items for further information.

 

API code

After migration, any WCM API code should still function as normal. The API will, by default, use the library specified in the WCM ConfigService.properties file.

Once you create new libraries and add items to those libraries, you will need to update your API code to be library-specific by using the setCurrentDocumentLibrary method. See the Javadoc HTML files located under the WP_PROFILE/installedApps/node/wcm.ear/ilwwcm.war/webinterface folder for further information on using this method.

 

JSP files

Any JSP files used on your old system will need to be manually copied to your new system. See JSP elements for details on where to store JSP files.

 

Referential integrity

Referential integrity features have been added in this release. See Collaborative authoring and Delete items for further information.

These features are not applied to a migrated items that contain element or component tags until the item is opened and saved in the authoring portlet.

 

Authoring portlet pages

Although authoring portlets are not migrated, any portal pages that previously displayed an authoring portlet on your old system are migrated as blank pages. You can either delete these pages, or add a new authoring portlet to the blank page.

 

Presentation templates

Migrated presentation templates may contain additional HTML header information not present in the original presentation template. The additional header information will not affect any content rendered in the presentation template and can be deleted.

 

Migrate data a second time

If you plan to perform more than one migration, such as when you plan to perform an initial migration, test it, and then update your migrated server with the latest data from your old server, do the following:

Please note that you will need to also re-migrate your local and remote portlets after migrating your data a second time. All your data migrated a second time will appear in a new library. The old library will not be deleted. It is advisable to re-initialize your JCR database to prevent the accumulation of unneeded data.

 

Post migration database tuning

You should review your data repository settings post migration to ensure your database is optimized for storing your Web content. See Database considerations and your database documentation for further information.

 

Removing the migration tool

To remove the migration tool, run the remove-wcm-migration task from the WP_PROFILE/ConfigEngine directory of your new system.

 

Parent topic

Migrating version 5.1 Web content