Portal V6.1.x on application server V6.1: Updating portlets URL

After migrating your portal environment, you must verify and update as needed the portlets URLs. In some cases, portlets have the incorrect URL after migration. URLs can be easily corrected using the XML configuration interface to export, update, and import the configurations.

About this task

Perform the following steps in the newly migrated environment.

Procedure

Export the portlet configuration.

  1. Change directory where the WebSphere® Portal tools are contained:
  2. Export the configuration using the provided sample file named ExportAllPortlets.xml by entering the following command:
    • Windows: xmlaccess.bat -in PortalServer_root\doc\xml-samples\ExportAllPortlets.xml -user wpsadmin -password wpsadminpwd -url http://server.example.com:port/wps/config -out Server_config.xml
    • AIX IBM i Linux Solaris: ./xmlaccess.sh -in PortalServer_root/doc/xml-samples/ExportAllPortlets.xml -user wpsadmin -password wpsadminpwd -url http://server.example.com:port/wps/config -out Server_config.xml

    The exported configuration is stored in the XML file named Server_config.xml.

Verify output XML file and update URLs as needed.

  1. Open the Server_config.xml file and verify that all URLs are valid. This means that all the files that are listed in the XML file must be present and accessible in the specified locations.
    1. If the URLs do not match the actual location in your environment, update those entries according to the actual location of the files.
    2. If the files specified in the URL field do not exist in the migrated environment or are no longer needed in the configuration, remove those entries.
    Note: If you are making the updates on a clustered environment, modify the XML file to remove the global-settings and services-settings entries if available in the file.

Import XML file with the updated URLs.

  1. Change directory where the WebSphere Portal tools are contained:
  2. Run the following command to import the updated configuration using the Server_config.xml file that you just updates:
    • Windows: xmlaccess.bat -in Server_config.xml -user wpsadmin -password wpsadminpwd -url http://Server.example.com:port/wps/config
    • AIX IBM i Linux Solaris: ./xmlaccess.sh -in Server_config.xml -user wpsadmin -password wpsadminpwd -url http://Server.example.com:port/wps/config
  3. After the request has been processed, make sure that the import process has given the following return message: 
    <status element="all" result="ok">

For clustered environments only.

  1. Resync the cluster from the Deployment Manager console.
  2. Restart the Enterprise Applications from the Deployment Manager console.
  3. Run the following command on the cluster primary node to activate the deployed portlets:
    • Windows: ConfigEngine.bat activate-portlets -DWasPassword=password
    • AIX Linux Solaris: ./ConfigEngine.sh activate-portlets -DWasPassword=password
    • IBM i: From the UserData directory, ConfigEngine.sh activate-portlets -DWasPassword=password
  4. Restart the portal.

What to do next

Change the portal URI. Your migrated portal URI has the following format: http://host_name:port_number/original-context-root_migrated/portal. If you have changed the context root of the MigratedTheme.ear or if MigratedTheme.ear is not installed in your environment then you should set the Portal URI to a format like http://host_name:port_number/original-context-root/portal. For information on how to change the portal URI, see Changing the portal URI.