Change the portal URI

 

+

Search Tips   |   Advanced Search

 

You can change the default URI for IBM WebSphere Portal and Web Services for Remote Portlets.

 

Before you begin

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

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
• WP_PROFILE/PortalServer/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 are already located in that directory, therefore you do not need to copy them.

• For changing the WebSphere Portal URI.

  When you specify the context root, do not specify a value that is the same as a directory existing in a portlet WAR. 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. 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 modify-servlet-path configuration task.

 

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 server.

2. Backup...
   • wkplc.properties
   • wkplc_comp.properties

3. Edit wkplc.properties file and enter the values that are appropriate for your environment.

   Property	Value
   PortalAdminPwd	The password for the WebSphere Portal administrator as defined in the PortalAdminId property. Recommended: Set this value according to your own environment.
   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. Recommended: Set this value according to your own environment.
   WasPassword	The password for WAS 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 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	The context root or base URI for WSRP Producer. Recommended: Set this value according to your own environment.
   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.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. Recommended: myportal
   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.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. Recommended: portal

6. Save and close the file.

7. Start server1.

8. Open a command prompt and change to the following.
   WP_PROFILE/ConfigEngine.

9. Perform the following steps if you are using an internal Web server:

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

      ./ConfigEngine.sh modify-servlet-path -DPortalAdminPwd=wpsadmin -DWasPassword=wpsadmin

      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_comp.properties files.

   2. Restart server1 and the WebSphere Portal server.

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

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

       ./ConfigEngine.sh modify-servlet-path -DPortalAdminPwd=wpsadmin -DWasPassword=wpsadmin

       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_comp.properties files.

    2. Regenerate the HTTP plug-in 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. 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 HTTP plug-in in WAS. If you are using 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 server.

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

    1. Open a command prompt and change to the directory where WebSphere Portal is installed, on the corresponding operating system:
       cd WP_PROFILE/ConfigEngine
       ConfigEngine.sh enable-http-basic-auth-tai-sitemgmt -DWasUserid=username -DWasPassword=wpsadmin -DPortalAdminId=username -DPortalAdminPwd=wpsadmin

    2. c. Restart server1 and the WebSphere Portal server.

12. Clustered environment only: Resynchronize the nodes and restart the cluster.

    1. Open the deployment manager console.

    2. Click...
       System Administration | Nodes | primary node | Full Resynchronize

    3. Click...
       Servers | Clusters | cluster | Stop

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

 

Parent topic

Configure security

---