+

Search Tips   |   Advanced Search

Virtual Portal tasks

If we configured WebSphere Portal to use virtual portal, there are some additional steps needed to complete the migration.


Default virtual portal content

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

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


Person Tag

Your script can contain references to Dynamic Person Tag portlet. This portlet is no longer available and any reference to this portlet causes the script to fail.

Use the WAS console to update the virtual portal XML scripts to remove references to Dynamic Person Tag portlet.

  1. Go to the WAS console.

  2. Click...

      Applications | Application Types | Assets

  3. Select VirtualPortal.zip, and click Export.

  4. Remove the web-app sequence that includes the opening <web-app...> and the closing </web-app> tags, and everything in between.

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

  5. Remove the Person Tag page that includes the opening <content-node...> and the closing </content-node> tags, and everything in between. The object ids, portletrefs, sharerefs, and other references in the example might vary in the installation.

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

  6. Select VirtualPortal.zip, and click Update.

  7. Select the default value Replace entire asset.

  8. Locate the updated file and upload the file.


Deprecated CAI/TAI portlets

Your script can contain references to the CAI/TAI portlets. These portlets are no longer available and any reference to these portlets cause your script to fail.

Use the WAS console to update the virtual portal XML scripts to remove references to CAI/TAI portlets. For example, the portlets are defined in a web-app sequence like the following examples. 

<web-app action="locate" uid="com.ibm.workplace.community.portal">
  <portlet-app action="locate" uid="com.ibm.workplace.community.portal.1">
    <portlet action="locate" name="Community" objectid="Z3_CGAH47L0008270I7MOUHLP18C5"/>
  </portlet-app>
</web-app>
<web-app action="locate" uid="com.ibm.workplace.builder.parameterPortlet.ParamConfigPortlet.40b0885181fd00171b3b9587aea11c02">
  <portlet-app action="locate" uid="com.ibm.workplace.builder.parameterPortlet.ParamConfigPortlet.40b0885181fd00171b3b9587aea11c02.1">
    <portlet action="locate" name="Parameters" objectid="Z3_CGAH47L0008270I7MOUHLP18O5"/>
  </portlet-app>
</web-app>
<web-app action="locate" uid="com.ibm.workplace.policystatus.PolicyStatus">
  <portlet-app action="locate" uid="com.ibm.workplace.policystatus.PolicyStatus.1">
    <portlet action="locate" name="Policy Status Portlet" objectid="Z3_CGAH47L0008270I7MOUHLP18S5"/>
  </portlet-app>
</web-app>
<web-app action="locate" uid="com.ibm.workplace.builder.propertiesPortlet.portal">
  <portlet-app action="locate" uid="com.ibm.workplace.builder.propertiesPortlet.portal.1">
    <portlet action="locate" name="Properties portlet" objectid="Z3_CGAH47L0008270I7MOUHLP1845"/>
  </portlet-app>
</web-app>
<web-app action="locate" uid="com.ibm.workplace.builder.manageroles.ManageRoles.50047239651b0018123cdeae474aa5c4">
  <portlet-app action="locate" uid="com.ibm.workplace.builder.manageroles.ManageRoles.50047239651b0018123cdeae474aa5c4.1">
    <portlet action="locate" name="Roles portlet" objectid="Z3_CGAH47L0008270I7MOUHLP18K5"/>
  </portlet-app>
</web-app>

The pages that reference these portlets in sequences like the following examples. 

<component action="update" active="true" deletable="false" domain="rel" modifiable="undefined" objectid="Z7_CGAH47L0008270I7MOUHLP18M7" ordinal="100" skinref="undefined" type="control" width="undefined">
  <portletinstance action="update" domain="rel" objectid="Z5_CGAH47L0008270I7MOUHLP18E0" portletref="Z3_CGAH47L0008270I7MOUHLP18C5" shareref="Z5_CGAH47L0008270I7MOUHLP18E0"/>
</component>
<component action="update" active="true" deletable="false" domain="rel" modifiable="undefined" objectid="Z7_CGAH47L0008270I7MOUHLP18I0" ordinal="100" skinref="undefined" type="control" width="undefined">
  <portletinstance action="update" domain="rel" objectid="Z5_CGAH47L0008270I7MOUHLP18I4" portletref="Z3_CGAH47L0008270I7MOUHLP18O5" shareref="Z5_CGAH47L0008270I7MOUHLP18I4"/>
</component>
<component action="update" active="true" deletable="false" domain="rel" modifiable="undefined" objectid="Z7_CGAH47L0008270I7MOUHLP18U4" ordinal="100" skinref="undefined" type="control" width="undefined">
  <portletinstance action="update" domain="rel" objectid="Z5_CGAH47L0008270I7MOUHLP18U2" portletref="Z3_CGAH47L0008270I7MOUHLP18S5" shareref="Z5_CGAH47L0008270I7MOUHLP18U2"/>
</component>
<component action="update" active="true" deletable="false" domain="rel" modifiable="undefined" objectid="Z7_CGAH47L0008270I7MOUHLP18Q6" ordinal="100" skinref="undefined" type="control" width="undefined">
  <portletinstance action="update" domain="rel" objectid="Z5_CGAH47L0008270I7MOUHLP18Q1" portletref="Z3_CGAH47L0008270I7MOUHLP1845" shareref="Z5_CGAH47L0008270I7MOUHLP18Q1"/>
</component>
<component action="update" active="true" deletable="false" domain="rel" modifiable="undefined" objectid="Z7_CGAH47L0008270I7MOUHLP1865" ordinal="100" skinref="undefined" type="control" width="undefined">
  <portletinstance action="update" domain="rel" objectid="Z5_CGAH47L0008270I7MOUHLP1863" portletref="Z3_CGAH47L0008270I7MOUHLP18K5" shareref="Z5_CGAH47L0008270I7MOUHLP1863"/>
</component>

The portletref attribute of the portletinstance tag matches one of the objectid attributes from the portlet tags in the web-app section. 

<portlet action="locate" name="Roles portlet" objectid="Z3_CGAH47L0008270I7MOUHLP18K5"/>
<portletinstance portletref="Z3_CGAH47L0008270I7MOUHLP18K5" ... />

Make sure to remove the web-app sequence that includes the opening <web-app...> and the closing </web-app> tags, and everything in between. Also, remove the components that reference the portlets. It includes the opening <component ...> and the closing </component> tags, and everything in between. The object ids, portletrefs, sharerefs, and other references in the example might vary in the installation.


Migrated virtual portal pages with old features

When we 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 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 containing a Document Libraries page, WebSphere Portal preserves that page. We can remove these pages manually after you migrate the virtual portal.


Update Web Content Manager pages theme

Before using WCM in virtual portals created after migration using default portal content from an older release, update the theme to Portal 8.5 theme. Otherwise, Web Content Manager related portlets do not work properly.

  1. Run the following configuration task from the WP_PROFILE/ConfigEngine:

      Windows
      ConfigEngine.bat update-wcm-pages -DWasPassword=foo -DPortalAdminPwd=foo

      AIX Linux Solaris
      ./ConfigEngine.sh update-wcm-pages -DWasPassword=foo -DPortalAdminPwd=foo

      IBM i
      ConfigEngine.sh update-wcm-pages -DWasPassword=foo -DPortalAdminPwd=foo

  2. Change the following pages to use Portal 8.5 Theme:

    • .ibm.wps.hiddenpage.wcm.Authoring_Portlet
    • .portal.Web.Content.Management
    • .portal.Portal Content

    1. Log in to Portal as an administrator.

    2. Click... '

        Administration | Portal User Interface | Manage Pages

    3. In the Search by menu select Unique name contains.

    4. In the Search field, enter the unique name of the page and click...

        Search | Edit Page Properties | Theme field | Portal 8.5 | OK


Share Web Content Manager libraries between virtual portals

When creatingd 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 v8.0 or 8.5, a Web Content Manager library created in the base portal is not available in the virtual portals. If we 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.


Parent Portal tasks

Related tasks:

Remove Person Tag hidden pages


Related information


Administer virtual portals
Tasks for administering virtual portals