Change the WebSphere Portal and WSRP Producer URI

 

+
Search Tips   |   Advanced Search

 

Overview

  1. Copy your custom portlet .WAR files to...

    wp_root/installableApps

    This step is required because after changing the portal URI all portlets must be redeployed.

  2. Verify whether wcm WAR files ilwwcm-authoring-portlet.war, ilwwcm-localrendering-portlet.war and ilwwcm-remoterendering-portlet.war are present in...

    wp_root/installableApps

    If the WAR files are not present, copy the files from...

    wp_root/wcm/installableApps

    ...to...

    wp_root/installableApps

  3. When specifying the context root (WpsContextRoot property), do not specify a value that is the same as a directory existing in a portlet WAR directory. For example, if you set the context root for WebSphere Portal to be /images (/wps is the default value) and there is also a portlet with the directory structure...

    /myPortlet.ear/myPortlet.war/images

    ...this could cause a conflict if the portlet encodes URI references to resources in its own /images directory. In this situation, the portlet would be unable to display images because WebSphere Portal would look for the image resources according to its own context root path instead of the directory path that is specified by the portlet WAR file.

  4. Go to...

      WAS_HOME/AppServer/bin

    ...and stop WebSphere Portal

  5. Make a backup of $PORTAL_HOME/config/wpconfig.properties

  6. Edit...

    $PORTAL_HOME/config/wpconfig.properties

    ...and change any or all of the following...

    Property Value
    PortalAdminPwd The password for the WebSphere Portal administrator, as defined in the PortalAdminId property.

    Recommended value: No recommended value for this property

    Default value: None

    WpsContextRoot The context root or base URI for the portal. All URLs beginning with this path will be reserved for the portal. The value of this property is part of the URL that is used to access WebSphere Portal from a browser. For example,

    http://hostname.setgetweb.com:9081/wps/portal

    Recommended value: None

    Sample value: home

    Default value: wps

    WsrpContextRoot The context root or base URI for WSRP Producer.

    Recommended value: None

    Sample value: wsrp

    Default value: wsrp

    WpsDefaultHome The default portal page. This is the page for users who are not logged in. The value of this property is part of the URL that is used to access WebSphere Portal from a browser. For example, http://hostname.setgetweb.com:9081/wps/portal

    Recommended value: portal

    Sample value: ibm

    Default value: portal

    WpsPersonalizedHome The portal page for users who have already logged in to the portal. This page cannot be accessed by anonymous users. The value of this property is part of the URL that is used to access WebSphere Portal from a browser. For example,

    http://hostname.setgetweb.com:9081/wps/myportal

    Recommended value: myportal

    Sample value: myibm

    Default value: myportal

  7. Save the file.

  8. Open a command prompt and change to the following directory.

      wp_root/config

  9. Perform the following steps, depending on whether you are using an internal or external Web server with WebSphere Portal.

    • Internal Web server

    • External Web server (such as IBM HTTP Server)

      1. Configure the WebSphere Portal URI...

        ./WPSconfig.sh modify-servlet-path

        Check the output for any error messages before proceeding with the next task. If any of the configuration tasks fail, verify the values in the wpconfig.properties file.

      2. Regenerate the HTTP plugin in WAS. If you are using a remote Web server, copy the generated plugin-cfg.xml file to the remote server.

      3. Restart the Web server.

      4. Perform these steps only if you are changing the WebSphere Portal URI or if portlets are installed. The next steps should not be executed if only the WSRP Producer URI is being changed or if no portlets are installed:

        1. Update the portlets with the new context root information...

          WPSconfig.bat action-update-portlets -DPortalAdminPwd=<password>

        2. Regenerate the HTTP plugin in WAS. If you are using a remote Web server, copy the generated plugin-cfg.xml file to the remote server.

        3. Restart the Web server.

  10. Start Portal

    cd was_root/bin
    startServer WebSphere_Portal

 

Next steps

You have completed this step. Continue to the next step by choosing one of the following topics:

 

See also

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.