+

Search Tips   |   Advanced Search

Portal, V6.1

 

v6 to 6.1 post migration steps

You may need 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 WCM ConfigService.properties file has been moved to a new location. 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 now 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

 

Syndication items

Any syndicators or subscribers that were configured on your version 6.0 server will be migrated but will no longer be valid on your version 6.1 server. You must delete any migrated syndicators and subscribers and create new syndicators and subscribers for your new system.

 

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.

In previous versions, to access item type views in the authoring portlet the user required "contributor" access in a library's item types settings. "User" access on the library's item type settings did not give users access to anything in the authoring portlet. In version 6.1, the user only requires "user" access on the library's item type settings to access item type views in the authoring portlet. Therefore users with "user" access to the library's item type settings who don't require access to these views in the authoring portlet should have their "user" access removed from the library's item type settings.

 

The wcmadmins group

If you used the wcmadmins group in 6.0 you should be aware that wcmadmins does not automatically have administrator access in version 6.1. When you migrate from version 6.0 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.

 

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 and set this value to "false": 

cmpnt.htmlEncodeDefault=false

 

Caching

The default resourceserver.maxCacheObjectSize setting in the WCM ConfigService.properties file has been reduced from 10000 kilobytes to 300 kilobytes to maximize cache performance.

 

Menus

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.

 

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.

 

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.

 

Search Indexes

Rebuild your search indexes after migrating your version 6.1 system:

  1. Stop your server.

  2. Delete all the index directories under WP_PROFILE/PortalServer/jcr/search

  3. Restart the portal server

  4. The search indexes should be rebuilt the next time the index maintenance interval is reached.

  5. If the index directory is not built, edit a document and save it, and tray manually rebuilding the search index.

 

Remote rendering portlets

Remote rendering portlets on remote servers will still be configured to target the pre-migration server after you migrate the source server. You may need to edit the configuration of your remote rendering portlets to point to your migrated server.

 

Parent topic

Migrating version 6.0 Web content