Change the WebSphere Portal URI

 

+
Search Tips   |   Advanced Search

 

Overview

Although WebSphere Portal is installed with a default URI, you can change this URI after installation to better suit the needs of the organization.

If you are using an external Web server with WAS, regenerate the Web server plug-in settings after modifying the WebSphere Portal URI.

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.

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

Copy all the own custom portlet application .WAR files that you deployed after the initial portal installation into...

wp_root/installableApps

This step is required because after changing the portal URI all portlets must be redeployed. The redeployment is done by a configuration task in a step listed further below. The configuration task redeploys all portlet WAR files that are located in...

wp_root/installableApps

Therefore copy the custom WAR files into that directory so that they are included in the redeployment. The portlet WAR files that are provided with WebSphere Portal are already located in that directory, therefore you do not need to copy them.

Do not run the modify-servlet-path task after portlets have been deployed.

You cannot set the WebSphere Portal server's context root to only /. WebSphere Portal always looks for a URI. For example, /wps/portal. The URI cannot be only / .

 

Steps for this task

To change the URI, do the following steps:

  1. Stop WebSphere Portal...

    STRQSH
    cd /qibm/proddata/webas5/pme/bin
    stopServer -instance <instance> <app_server>

  2. Make a backup copy of...

    /qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties

  3. Edit the file...

    EDTF '/qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties'

    ...and enter the values that are appropriate for the environment.

    Some values, shown here in italics, might need to be modified to the specific environment.

     

    WAS properties

    Property Value
    WpsContextRoot

    Description: 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.yourco.com:9081/wps/portal

    Recommended value: None

    Sample value: home

    Default value: wps

    WpsDefaultHome

    Description: 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.yourco.com:9081/wps/portal

    Recommended value: portal

    Sample value: ibm

    Default value: portal

    WpsPersonalizedHome

    Description: 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.yourco.com:9081/wps/myportal

    Recommended value: myportal
    Sample value: myibm
    Default value: myportal

  4. Save the file.

  5. Enter the following to configure the WebSphere Portal URI:


    STRQSH
    WPSconfig.sh modify-servlet-path
    cd /qibm/proddata/webas5/pme/bin
    startServer -instance <instance> <app_server>

 

Results

You have now successfully changed the URI of the portal. Verify that the URI was changed successfully by typing the new URI in a browser.

  http://<hostname.yourco.com>:<port_number>/<WpsContextRoot>/<WpsDefaultHome>

...or...

  http://<hostname.yourco.com>:<port_number>/<WpsContextRoot>/<WpsPersonalizedHome>

For example, if you performed the previous steps using the sample values, the resulting WebSphere Portal default URI would be:

  http://<hostname.yourco.com>:<port_number>/home/ibm  

The personalized URI for users who are logged in would be:

  http://<hostname.yourco.com>:<port_number>/home/myibm  

 

Next steps

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

 

See also