Changing the WebSphere Portal URI to custom URI


I just updated my local WebSphere Portal env to Portal V8.5 and wanted to change the Portal URL from 'wps' to some custom uri. To make this happen I followed following steps in my local Portal.

  1. Stop the WebSphere_Portal server.


  1. Open the the wkplc.properties and wkplc_comp.properties files in the /wp_profile_root/ConfigEngine/properties directory in some text editor.

  1. Open the wkplc.properties file and enter the value for your environment in the WpsContextRoot property. Save and close the file.

  1. Open the wkplc_comp.properties file and enter the appropriate value for your environment in the following properties:
WsrpContextRoot
WpsPersonalizedHome
WpsDefaultHome
Note : Do not enter the same value for WpsPersonalizedHome and WpsDefaultHome.
  1. Re Start the WebSphere_Portal server.
  2. Once again go to the /wp_profile_root/ConfigEngine directory using Command prompt and run the following task:

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

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

Note: Check the output for any error messages before you proceed with the next task. If any of the configuration tasks fail, verify the values in thewkplc.properties and wkplc_comp.properties files.

  1. Again from the Comand prompt Run the following task to change the context root for the portlets:

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

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

  1. Restart the WebSphere_Portal server.


  1. Verify the Portal URL now, should be pointing to the new custom URL.




Comments

Post a Comment

Popular posts from this blog

Extending LDAP attributes to WebSphere Portal

I wanted to extend the Portal VMM attributes by adding new attributes from LDAP to our Portal env. Out of the box WebSphere Portal VMM is configured with a default attribute schema. You can extend the VMM attribute by adding new attributes that you can map between WebSphere Portal and your user registry. I followed below steps to extend the VMM attributes from the LDAP - Open the command prompt and go to <WP_PROFILE>/ConfigEngine directory. Run the wp-la-install-ear ConfigEngine tasks- In Linux env - ./ConfigEngine.sh wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name In Windows env - ConfigEngine.bat wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name Restart the Portal Server profile. Go to <WP_PROFILE>/ConfigEngine/properties directory in your Portal installation and open the wkplc.properties file in amy text editor. For safer side take a back of...
Read more

Installing and Un-installing Portal Application Archive (PAA) file

Basically .paa file installation process consists of two steps, install and deploy. 1. Copy the .paa file into some temp directory in your Portal box in case of installing the portal application archive file. 2. Open a command prompt and navigate to Portal profile ConfigEngine directory <WAS_HOME>/<wp_profile>/ConfigEngine and execute following ConfigEngine install-paa command – a) Installation of the .paa file In Linux or AIX ------------------- ./ConfigEngine.sh install-paa -DPAALocation=<paa_file_location> -DWasPassword=<password> -DPortalAdminPwd=<password> ./ConfigEngine.sh deploy-paa -DappName=<paa_app_name> -DWasPassword=<password> -DPortalAdminPwd=<password> In Windows: ---------------- ConfigEngine.bat install-paa -DPAALocation=<paa_file_location> -DWasPassword=<password> -DPortalAdminPwd=<password> ConfigEngine.bat deploy-paa -DappName=<paa_app_name> -DWasPassword=...
Read more

WCM Syndication issue in WebSphere Portal V 8001 with CF06 or CF07

Last week we faced issue while creating new syndication in WebSphere Portal 8001 with CF06 in one of Production deployment.  In WebSphere Portal CF6 there is an issue while creating new Syndicator and Subscriber pair with having two different domain name of Subscriber and Syndicator. Once you create syndication, in Syndicator side subscriber url get updated with the fully qualified domain name.  Basically, Syndication will be created perfectly fine, but when you execute the update WCM library , you will see following error in Portal SystemOut log -  IWKWC0004I: Code #405, phrase: Unrecognized sender, detail: Failed to retrieve subscriber. Cause: com.ibm.workplace.wcm.services.content.ItemNotFoundException: Failed to find controllable{746aeb11-629d-4759-9865-aeb754e094ea, com.aptrix.pluto.control.Controllable}in vp instance: 0 with context pathnull and hostname: null ) To fix this issue, we have to manually edit the syndicator and correct the subscriber ur...
Read more