Completing the context root change started during installation | HCL Digital Experience
If you changed the context root on the Configuration for HCL Digital Experience: Profile configuration details: Advanced pane during installation, there are more steps to take to complete the change.
About this task
If you are on Combined Cumulative Fix 7 or earlier, go to CF07 and earlier: Completing the portal URI change started during installation.
HCL Digital Experience 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.
Notes:
- To change the HCL Digital Experience URI: When you specify the context root, do not specify a value that is the same as a directory that exists in a portlet WAR directory. For example, you set the HCL Digital Experience 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 Digital Experience looks for the image resources according to its own context root path instead of the directory path that is specified by the portlet WAR file.
- 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.Important: With Version 8, the URI of the context root for the WSRP Producer is
/wps/wsrp
. Before Version 8, this context root was/wsrp
. If you migrated from an earlier version, you still might have WSRP Consumers that attempt to access the WSRP Producer with the previous context root (/wsrp
). You 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
).
- Modify the context root for the WSRP Producer to
- If you use HCL Web Content Manager Syndication, the Syndicators and Subscribers servers that refer to this Portal instance must be updated with the modified URI. Log on to the HCL Portal syndicating to this instance. Click the Administration menu icon. Then, click . Click the edit icon of the Syndicator you want to edit. Update the URL with the new context root information. Then, log on to the HCL Portal subscribing to this instance. Click the Administration menu icon. Then, click . Click the edit icon of the subscriber you want to edit. Update the URL with the new context root information.
Procedure
- If necessary, start the HCL Portal server in a stand-alone environment or the deployment manager and node agent in a clustered environment.
- Complete the following steps if you
are using an external web server, such as an HTTP Server:
- Required if you use HCL Web Content Manager: Complete the following
steps to 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.
- Complete the following steps to edit the context
root for every search collection:Attention: Edit the context root for each existing search collection.
- Clustered environment only:Idle standby only: Resynchronize the nodes and restart the
cluster.
Table 2. Steps to resynchronize the nodes and restart the cluster. Cluster type Steps Static clusterIdle standby Complete the following steps if you have a static clusteran idle standby environment: - Open the deployment manager WebSphere® Integrated Solutions Console.
- Click Full Resynchronize. , select the primary node from the list, and click
- Click .
- Select the cluster and click Stop.
- After the cluster stops, restart it by selecting the cluster. Then, click Start.
Dynamic cluster Complete the following steps if you have a dynamic cluster: - Open the deployment manager WebSphere® Integrated Solutions Console.
- Click Full Resynchronize. , select the primary node from the list, and click
- Click .
- Click the dynamic cluster that you want to stop and restart.
- Click Dynamic cluster members.
- Select the member name that you want to stop and then click Stop.
- Select the member name that you want to start and then click Start.