WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Change the portal URI

This section describes how you can change the default portal URI after installation. This includes information about how to change the URI for a Producer portal.

Although IBM® WebSphere® Portal Express and Web Services for Remote Portlets are installed with a default URI, you can change this URI after installation to better suit the requirements of your organization.

 

Before you begin

Copy all a custom portlet application .WAR files that you deployed after the initial installation into the directory portal_server_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 the directories portal_server_root/installableApps and portal_server_root/deployed/archive. Therefore copy your custom WAR files into that directory so that they are included in the redeployment. The portlet WAR files that are provided with WebSphere Portal Express are already located in that directory, therefore you do not need to copy them.

Notes:

 

Steps for this task

To change the URI, complete the following steps.Cluster note: If you are modifying 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.

  1. Stop the WebSphere Portal Express server.

  2. Locate the wpconfig.properties file and create a backup copy before you change any values.

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

    Notes:

    1. Do not change any settings other than those that are specified in these steps. For instructions on working with these files, see Configuration properties reference for a complete properties reference, including default values.

    2. Use forward slashes ( / ) and not backward slashes ( \ ) for all platforms.

    3. Some values that are shown here in italics might need to be modified to your specific environment.

     

    Section of properties file: IBM WebSphere Application Server properties

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

    Recommended: Set this value according to a environment.

    Default: 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 Express from a browser. For example, http://hostname.example.com:10038/wps/portal, where hostname.example.com is the fully qualified host name of the machine where WebSphere Portal is running and 10038 is the default transport port that is created by WebSphere Application Server.

    Recommended: Set this value according to a environment.

     

    Sample value: home

    Default: wps

    WsrpContextRoot The context root or base URI for WSRP Producer.

    Recommended: Set this value according to a environment.

     

    Sample value: wsrp

    Default: 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 Express from a browser. For example, http://hostname.example.com:10038/wps/portal, where hostname.example.com is the fully qualified host name of the machine where WebSphere Portal is running and 10038 is the default transport port that is created by WebSphere Application Server.

    Recommended: portal

     

    Sample value: ibm

    Default: 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 Express from a browser. For example, http://hostname.example.com:10038/wps/portal, where hostname.example.com is the fully qualified host name of the machine where WebSphere Portal is running and 10038 is the default transport port that is created by WebSphere Application Server.

    Recommended: myportal

     

    Sample value: myibm

    Default: myportal

    WasPassword

     

    Description: The password for WebSphere Application Server security authentication.

    If a value is specified for WasPassword, a value must also be specified for WasUserid. If WasPassword is left blank, WasUserid must also be left blank.

    Type: Alphanumeric text string

    Recommended: Set this value according to a environment.

    Default: ReplaceWithYourWASUserPwd

  4. Save the file.

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

  6. Perform the following steps, depending on whether you are using an internal or external Web server.

    • Internal Web server

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

        • Linux:

          ./WPSconfig.sh modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

        • Windows:

          WPSconfig.bat modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

        • i5/OS:

          WPSconfig.sh -profileName profile_root modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

          where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed, for example, wp_profile.

        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.

        Version 6.0.1 only Spell Checker does not work if the context root is not the default /wps/ . To enable Spell Checker, administrators must set the value of the SpellCheck_Portlet_Context property in the SpellCheckConfig.properties file, which is located in portal_server_root/shared/app/com/ibm/wps/odc/spellcheck/util directory, to the current context root value.

      2. Enter the following command to configure the WebSphere Portal Express or the WSRP URI:

        • Linux:

          ./WPSconfig.sh action-update-portlets -DPortalAdminPwd=password -DWasPassword=password

        • Windows:

          WPSconfig.bat action-update-portlets -DPortalAdminPwd=password -DWasPassword=password

        • i5/OS:

          WPSconfig.sh -profileName profile_root action-update-portlets -DPortalAdminPwd=password-DWasPassword=password

          where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed, for example, wp_profile.

        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.

      3. Restart server1 and the WebSphere Portal Express server.

    • External Web server (such as HTTP Server)

      1. Enter the following commands to configure the WebSphere Portal Express URI:

        • Linux:

          ./WPSconfig.sh modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

        • Windows:

          WPSconfig.bat modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

        • i5/OS:

          WPSconfig.sh -profileName profile_root modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password

          where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed, for example, wp_profile.

        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 plug-in in WebSphere Application Server. 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 Express URI or if portlets are installed.

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

        1. Update the portlets with the new context root information. Enter the following command to configure the WebSphere Portal Express URI:

          • Linux:

            ./WPSconfig.sh action-update-portlets -DPortalAdminPwd=password -DWasPassword=password

          • Windows:

            WPSconfig.bat action-update-portlets -DPortalAdminPwd=password -DWasPassword=password

          • i5/OS:

            WPSconfig.sh -profileName profile_root action-update-portlets -DPortalAdminPwd=password -DWasPassword=password

            where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed, for example, wp_profile.

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

        3. Restart the Web server.

      5. Restart server1 and the WebSphere Portal Express server.

  7. Perform the following steps if you are using the Resource Manager portlet to manage your site and you changed the portal URI:

    1. Use a text editor to open the wpconfig.properties file:

    2. Edit the BasicAuthUrlBlackList and BasicAuthUrlWhiteList parameters to match the new URI.

    3. Save the wpconfig.properties file.

  8. Clustered environment only: Resynchronize the nodes and restart the 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.

 

Related information

 

Parent topic:

Configuring

 

Related concepts
Configuring security Configuration tools