Virtual Portal post migration steps
If you configured WebSphere® Portal to use virtual portal, there are some additional steps needed to complete the migration.
Virtual Portal Manager portlet
About this task
Procedure
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.
- <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
Procedure
Web Content Manager WCI pages
About this task
Procedure
- Log in to Portal as an administrator.
- Navigate through .
- Create two new pages, one named Feed Configurations and the other Feed Jobs.
- Edit Page Layout of the Feed Configurations page, add the portlet named Feed Configurations and click OK.
- Edit Page Layout of the Feed Jobs page, add the portlet named Feed Schedules and click OK.