Virtual Portal Manager portlet

About this task

If you are migrating from WebSphere Portal 6.1.x and you use the Virtual Portal Manager portlet, you need to update the shared setting for this portlet.

Procedure

  1. Access the Virtual Portal Manager portlet, by clicking Administration > Virtual Portals > Manage Virtual Portals.
  2. Click Edit Shared Settings of this portlet
  3. Note the XML file in the Xml script to create virtual portal content tree: field. This value must be edited to point to the migrated script. For example, if the value is MyVirtScript.xml the new value would be WebSphere:assetname=MigratedVirtualPortal.zip:MyVirtScript.xml.
    Note: As part of the migration process the virtual portal scripts are removed from the wps.ear and moved to a compressed file asset named MigratedVirtualPortal.zip.

Default Virtual Portal Content

About this task

To create new virtual portals with the same content as in your system you migrated from, you need to pre-configure the default content for virtual portal creation. This configuration is done by registering your filename.xml file you used in the system you migrated from. Be aware of the fact that the name of the file might change based on the release and editions of portal you are using.

Here are some examples of the used names:"InitVirtualContentPortal.xml, InitAdminVirtualPortal.xml, .."

Manage Seed List portlet

If you migrate from WebSphere Portal 6.1.x, your script can contain references to Manage Seed List portlet. This portlet is no longer available and any reference to this portlet will cause your script to fail.

Use the WebSphere Integrated Solutions Console to update the virtual portal XML scripts to remove references to Manage Seed List portlet. For example:
  • <portlet action="locate" name="Manage Seed List" objectid="3_CGAH47L008DE402BK8543I1G63"></portlet>
  • <portletinstance action="update" domain="rel" objectid="5_CGAH47L008DE402BK8543I18D4" portletref="3_CGAH47L008DE402BK8543I1G63" shareref="5_CGAH47L008DE402BK8543I18D4"></portletinstance>

Make sure to remove those lines. Note that the object ids, portletrefs, sharerefs and other references in the example may vary in your installation.

Person Tag

After migrating, your script can contain references to Dynamic Person Tag portlet. This portlet is no longer available and any reference to this portlet will cause your script to fail.

Use the WebSphere Integrated Solutions Console to update the virtual portal XML scripts to remove references to Dynamic Person Tag portlet. For example the portlet is defined in a web-app sequence like this:

<web-app action="locate" uid="com.ibm.wkplc.people.portal.portlet.dynamicpersontag.web.app">
  <portlet-app action="locate" uid="com.ibm.wkplc.people.portal.portlet.dynamicpersontag.portlet.app">
    <portlet action="locate" name="Dynamic Person Tag" objectid="3_CGAH47L008DE402BK8543I1O47"></portlet>
  </portlet-app>
</web-app>

And the page defined in the content-node sequence like this:

<content-node type="page" uniquename="ibm.portal.Person.Tag">
  <supported-markup markup="html" update="set"></supported-markup>
  <localedata locale="en">
<title>Person Tag</title>
<description>Person Tag portlet, which enables live names and information for names in IBM Portal</description>
  </localedata>
</content-node>

Make sure to remove the web-app sequence including the opening <web-app...> and the closing </web-app> tags, and everything in between. Also remove the Person Tag page including the opening <content-node...> and the closing </content-node> tags, and everything in between. Note that the object ids, portletrefs, sharerefs and other references in the example may vary in your installation.

Migrated Virtual Portal pages with old features

When you migrate a virtual portal, WebSphere Portal treats all pages in the portal as custom, customer-created content. As a result, if the virtual portal contains pages that are associated with features that are not available in the new installed version, WebSphere Portal migrates those pages regardless.

For example, if you migrate a virtual portal that contains a Document Libraries page, WebSphere Portal preserves that page even though document libraries were removed from WebSphere Portal starting with Version 6.1. You can remove these pages manually, after migrating the virtual portal.

Update Web Content Manager pages theme

About this task

You must change the theme of the hidden Web Content Manager authoring portlet to Portal 8.0 theme, otherwise Web Content Manager related portlets do not work properly.

Procedure

  1. Log in to Portal as an administrator.
  2. Navigate through Administration > Manage Pages.
  3. Locate the hidden Web Content Manager authoring portlet.
    1. In the Search by menu select Unique name contains.
    2. In the Search field enter com.ibm.wps.hiddenpage.wcm.Authoring_Portlet and click Search.
  4. Click the Edit Page Properties button for the Web Content Manager page.
  5. On the Theme field, select Portal 8.0.
  6. Click OK.

Web Content Manager WCI pages

About this task

If you plan to use WCI portlets after migration, you must add WCI pages and portlets manually.

Procedure

  1. Log in to Portal as an administrator.
  2. Navigate through Administration > Manage Pages > Content Root > Administration > WebSphere Portal > Portal Content.
  3. Create two new pages, one named Feed Configurations and the other Feed Jobs.
  4. Edit Page Layout of the Feed Configurations page, add the portlet named Feed Configurations and click OK.
  5. Edit Page Layout of the Feed Jobs page, add the portlet named Feed Schedules and click OK.

Sharing Web Content Manager libraries between virtual portals

About this task

When you created Web Content Manager libraries in the base portal of earlier versions of WebSphere Portal, these libraries were available in the virtual portals. In WebSphere Portal Version 8.0 or later versions with managed pages enabled, a Web Content Manager library that you create in the base portal is not available in the virtual portals. If you have managed pages enabled and want to share a Web Content Manager library between virtual portals, use syndication to replicate the library to the virtual portals.