Complete the context root change started during installation

If we changed the context root on the Configuration for HCL WebSphere Portal: Profile configuration details: Advanced pane during installation, there are more steps to take to complete the change.

HCL WebSphere Portal and Web Services for Remote Portlets are installed with a default URI. We can change this URI after installation to better suit the requirements of our organization.

When specifying the context root for a Portal URI, do not specify a value that is the same as a directory that exists in a portlet WAR directory. For example, we set the HCL WebSphere Portal context root to /images. There is a portlet with the directory structure /myPortlet.ear/myPortlet.war/images. This issue might 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. HCL WebSphere Portal looks for the image resources according to its own context root path instead of the directory path specified by the portlet WAR file.

If we use Syndication, the Syndicators and Subscribers servers that refer to this Portal instance must be updated with the modified URI. Log on to the HCL WebSphere Portal syndicating to this instance and click...

Administration menu icon > Portal Content > Syndicators > Syndicator > edit icon

Update the URL with the new context root information. Then, log on to the HCL WebSphere Portal subscribing to this instance. Click...

Administration menu icon > Portal Content > Subscribers > subscriber > edit icon

Update the URL with the new context root information.

Change Portal URI

1. Start the WebSphere_Portal server in a stand-alone environment or the deployment manager and node agent in a clustered environment.

2. Complete the following steps for an external web server, such as an HTTP Server:
   1. Choose one of the following options:

      HCL WebSphere Portal environment	Steps
      Stand-alone configuration	Copy the following script from plugin_root/bin of the web server to the wp_profile_root/bin directory on the HCL WebSphere Portal server: ./configurewebservername.sh where webservername is the web server definition name defined when we configured the HTTP Server for HCL Run... cd wp_profile_root/bin ./configurewebservername.sh
      Clustered configuration	Copy the following script from plugin_root/bin of the web server to dmgr_profile/bin on the Deployment Manager server: ./configurewebservername.sh where webservername is the web server definition name defined previously when we configured the HTTP Server for HCL From the Dmgr server run: ./configurewebservername.sh

   2. Regenerate the web server plug-in in WebSphere Application Server. For a remote web server, copy the generated plugin-cfg.xml file to the remote server.

      Important: Do not complete these steps if we are changing only the WSRP Producer URI

   3. Restart the web server.

   4. Restart the WebSphere_Portal server.

3. Required if we use HCL Web Content Manager: Manually change the JSP components in the Web Resources v70 Library:

   Cluster note: In a clustered environment, complete these steps on the primary node only.

   1. Log on to HCL WebSphere Portal.

   2. Go to...
      Applications > Content > Web Content Authoring > Preferences > Edit Shared Settings > Library Selection

      ...and add Web Resources v70 to the Selected Libraries list.

   3. Click OK.

   4. Under Item Views, select...
      All Items > All > Components > JSP

   5. Select every JSP component from the Web Resources v70 library and then click Edit.

   6. Update the Path field for every JSP component with the new context root path.

      The JSP path includes two parts, which are separated by a semi-colon. The first part is the context path to the HCL Web Content Manager extensions web application and then the second part is the path to the JSP. Update the path to the web application.

      For example, the other path might be:

      /wcmextension;/jsp/html/general/UpdateItem.jsp

      If we changed the context root to mynewcontext, change the old path to...

      /mynewcontext/wcmextension;/jsp/html/general/UpdateItem.jsp

4. Edit the context root for every existing search collection:Attention.
   1. Log on to HCL WebSphere Portal as the administrator.

   2. Ppen the Manage Search portlet...
      Administration menu icon > Search Administration > Manage Search > Search Collections search collection > Edit Content Source icon

   3. Edit the URL listed in the Collect documents link from the URL with the new context root.

   4. Click Save.

   5. Edit the URL in each remaining content source and then save your changes.

   6. Start the HCL WebSphere Portal crawler content source for each collection:

      • If the documents are not stored in the search collection but a schedule is defined for the crawler, the crawler automatically runs at the scheduled time. We can also start the crawler manually.

      • If the documents are already collected, select Regather documents to update the documents with the new context root information.

   7. Click Collections from All Services in the breadcrumb trail and select the next search collection to modify.

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

   Cluster type	Steps
   Static cluster	For a static cluster on an idle standby environment: Open the deployment manager WebSphere Integrated Solutions Console. Click... System Administration > Nodes, > primary node > Full Resynchronize Click... Servers > Clusters cluster Stop After the cluster stops, restart it by selecting the cluster. Then, click Start.
   Dynamic cluster	Complete the following steps if we have a dynamic cluster: Open the deployment manager WebSphere Integrated Solutions Console and click... System Administration > Nodes > primary node > Full Resynchronize Click... Servers > Dynamic Clusters > dynamic cluster > Dynamic cluster members > member name > Stop Select the member name that we want to start and then click Start.

WSRP Producer Portal

For changing the URI of a WSRP Producer portal: Changing the WSRP Producer context root does not require that you redeploy all portlets. Run the modify-servlet-path configuration task only. With v8, the URI of the context root for the WSRP Producer is /wps/wsrp. Before v8, this context root was /wsrp. If we migrated from an earlier version, we still might have WSRP Consumers that attempt to access the WSRP Producer with the previous context root (/wsrp). We can correct this issue in one of the following ways:

• Modify the context root for the WSRP Producer to /wsrp. This change enables the Consumers to access the Producer without requiring further changes to the Consumers.
• Update the configuration of the WSRP Consumers to use the new context root (/wps/wsrp).