Change the portal URI


Overview

You can change the default portal Uniform Resource Identifier (URI) after installation for the following applications:

For the context root, do not specify a value that is the same as a directory existing in a portlet WAR directory.

For example, if you set the WebSphere Portal context root as /images 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 specified by the portlet WAR file.

Changing the WSRP Producer context root does not require that you redeploy all portlets. You only need to run the task...

To modify the URI in a clustered environment, perform the steps described here only on the primary node. It is not necessary to complete the steps on secondary nodes in the cluster.


Procedure

  1. Stop the WebSphere Portal server.

  2. Create backup copies of...

      profile_root/ConfigEngine/properties/wkplc.properties
      profile_root/ConfigEngine/properties/wkplc_comp.properties

  3. edit wkplc.properties and enter values...

    Property Value
    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.example.com:10040/wps/portal, where hostname.example.com is the fully qualified host name of the machine where WebSphere Portal is running and 10040 is the default transport port that is created by WAS; the port number may be different for your environment. In the example wps is the WpsContextRoot.

    Recommended value:

    Set this value according to your own environment.

  4. Save and close the file.

  5. After making a backup, use a text editor to open the wkplc_comp.properties file and enter the values that are appropriate for your environment.

    Property Value
    WsrpContextRoot Context root or base URI for WSRP Producer.

    Recommended value:

    Set this value according to your own environment.

    WpsPersonalizedHome 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.example.com:10040/wps/portal, where hostname.example.com is the fully qualified host name of the machine where WebSphere Portal is running and 10040 is the default transport port that is created by WAS; the port number may be different for your environment.

    Recommended value:

    myportal

    WpsDefaultHome 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.example.com:10040/wps/portal, where hostname.example.com is the fully qualified host name of the machine where WebSphere Portal is running and 10040 is the default transport port that is created by WAS; the port number may be different for your environment.

    Recommended value:

    portal

  6. Save and close the file.

  7. Start server1 in a stand-alone environment or start the deployment manager in a clustered environment.

  8. Open a command prompt and change to profile_root/ConfigEngine.

  9. To change the WebSphere Portal URI:

    1. To change the context root of WSRP Producer or WebSphere Portal, enter the following command:

        UNIX: ./ConfigEngine.sh modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

        Windows: ConfigEngine.bat modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

        i5/OS: ConfigEngine.sh modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

      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 wkplc.properties and wkplc_dbdomain.properties files.

    2. Restart server1 and the WebSphere_Portal servers.

  10. Perform the following steps if you are using an external Web server, such as an HTTP Server:

    1. Choose one of the following options based on your WebSphere Portal environment:


      Table 1. configurewebservername command options

      WebSphere Portal environment Steps
      Standalone configuration Perform the following steps in a standalone configuration:

      1. Copy the following script from the plugin_root/bin directory to the wp_profile/bin directory on your WebSphere Portal server:

          UNIX: ./configurewebservername.sh

          Windows: configurewebservername.bat

          i5/OS: configurewebservername.sh

        where webservername is the web server definition name you defined previously when configuring the HTTP Server for WebSphere Portal, for example: configurewebserver1.bat.

      2. Execute the following command, from the wp_profile/bin directory:

          UNIX: ./configurewebservername.sh

          Windows: configurewebservername.bat

          i5/OS: configurewebservername.sh

      Clustered configuration Perform the following steps in a clustered configuration:

      1. Copy the following script from the plugin_root/bin directory to the dmgr_profile/bin directory on your Deployment Manager server:

          UNIX: ./configurewebservername.sh

          Windows: configurewebservername.bat

          i5/OS: configurewebservername.sh

        where webservername is the web server definition name you defined previously when configuring the HTTP Server for WebSphere Portal, for example: configurewebserver1.bat.

      2. Execute the following command on the Deployment Manager server:

          UNIX: ./configurewebservername.sh

          Windows: configurewebservername.bat

          i5/OS: configurewebservername.sh

    2. Regenerate the Web server plug-in in WAS.

      For a remote Web server, copy the generated plugin-cfg.xml file to the remote server.

    3. Restart the Web server.

    4. If you are changing the WebSphere Portal URI or if portlets are installed, perform the following steps.

      These steps should not be performed if you are only changing the WSRP Producer URI.

      1. Regenerate the Web server plug-in in WAS.

        For a remote Web server, copy the generated plugin-cfg.xml file to the remote server.

      2. Restart the Web server.

    5. Restart server1 and the WebSphere_Portal servers.

  11. Perform the following steps if you changed the portal URI and you are using the Resource Manager portlet to manage your site and/or you are using the Mashup Integration features:

    1. Open a command prompt and change to the directory where WebSphere Portal is installed, on the corresponding operating system; for example, in profile_root/ConfigEngine.

    2. Enter the following command:

        UNIX: ConfigEngine.sh enable-http-basic-auth-tai-sitemgmt -DWasPassword=password

        Windows: ConfigEngine.bat enable-http-basic-auth-tai-sitemgmt -DWasPassword=password

        i5/OS: ConfigEngine.sh enable-http-basic-auth-tai-sitemgmt -DWasPassword=password

    3. Restart server1 and the WebSphere_Portal servers.

  12. Clustered environment only:

    Resynchronize the nodes and restart the cluster.

    Option Description
    Static cluster Perform the following steps if you have a static cluster:

    1. Open the deployment manager administrative console.

    2. Click System Administration > Nodes, select the primary node from the list, and click Full Resynchronize.

    3. Click Servers > Clusters.

    4. Select the cluster and click Stop.

    5. After the cluster has stopped, restart it by selecting the cluster and clicking Start.

    Dynamic cluster Perform the following steps if you have a dynamic cluster:

    1. Open the deployment manager administrative console.

    2. Click System Administration > Nodes, select the primary node from the list, and click Full Resynchronize.

    3. Click Servers > Dynamic Clusters.

    4. Click on the required dynamic cluster that you want to stop and restart.

    5. Click Dynamic cluster members.

    6. Select the member name that you want to stop and then click the Stop button.

    7. Select the member name that you want to start and then click the Start button.


Parent topic:

Configure WebSphere Portal


Related concepts


Configuration task properties
Configure WebSphere Portal with the configuration wizard
Configure portal behavior
Configure IBM Tivoli License Compliance Manager
Manage the user registry
Configure Web Content Management
Set up a remote spell checker
Enable Document Conversion Services
Connect to existing database domains
Add features to an administration installation
Activate SSL and FIPS
Additional security features