Modify Portal URL

After installing WebSphere Portal you might want to change the default URI from say http://localhost:10040/wps/portal to http://localhost:10040/ibm/home. Changing the default portal URI is little more complicated because when you install portal, all the portlets get installed with the default path. Ex. Go to wp_profile/installedApps/<nodeName> directory, and go to one of the portlet directory say PA_Login_Portlet_App.ear/META-INF directory and open the application.xml file it should look something like this

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application id="Application_ID">
<display-name>login_war</display-name>
<module>
<web>
<web-uri>login.war</web-uri>
<context-root>/wps/PA_Login_Portlet_App</context-root>
</web>
</module>
</application>

As you can see the portlet application is installed at /wps/<portletname> url. If you want to change the portal url then all these portlets should be redeployed to start with say /ibm/ parth.

Please follow these path to change the portal URI

• First copy all of your own custom portlets to PortalServer_root/installableApps directory. As i said as of changing URI all the portlets have to be redployed. The configuration task for changing URI, takes care of this by redeploying all the portlets in PortalServer_root/installableApps directory. This directory has .war files for all the portlets that ship with WPS, you should copy the .war files for your custom portlets in this directory


• Stop the portal server if it is running already


• Edit the wkplc.properties file and change the value of wps
  

  WpsHostName=ibm

  
  


• Edit the wkplc_comp.properties file to change these two values the value of home is used for public pages and myhome for authenticated user pages. Change value of WsrpContextRoot if you want.
  

  
  WpsDefaultHome=home
  WpsPersonalizedHome=myhome
  WsrpContextRoot=wsrp
  

  
  


• Start the server1 by execute ./startServer server1 command


• Execute ./ConfigEngine.sh modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password Configuration task


• Restart the server1 and WebSphere_Portal server

Take a look at Changing Portal URL for further information

WebSphere Portal URL Requirements

WebSphere Portal (WP) has some specific requirements for the format and content of URL used by this application. Furthermore the WebSphere Portal URLs are not human decipherable or dependant on site taxonomy. One example of a typical WP version 6 URL might look like the following:

http://www.mycompany.com/wps/myportal/!ut/p/c1/04_SB8K8xLLM9MSSzPy8xBz9CP0os3hLRydHL1MjYwN3dyNXA6MAD3c_V2M_YwMDA30_j_zcVP2CbEdFAHUwnMg!/

The basic building blocks of this URL are defined as follows:

<protocol>://<hostname>:<port>/<portal-context>/<security-context>/[<virtual-portal-alias>]/[<portal-params>]

All elements of this URL are important to the portal server to ensure that the request is properly processed and it is very difficult to hide or manipulate any

<protocol> – This is the protocol used by the request in our case HTTP or HTTPS

<hostname> - This is the DNS resolvable host name of the entry point to our portal application

<port> - This is the port that the WebSphere Portal HTTP listener will be bound to and is often left off on a browser URL designating the port as either the default HTTP port 80 or HTTPS port 443. Any other port would need to be properly designated in the URL

<portal-context> - Portal Context is the part of the URL that determines which application on the WebSphere Server will service the request. The default for WebSphere Portal is wps

<security-context> - Security Context is the part of the URL that determines whether the user is request the anonymous or secure view of a given portal navigational element like a page. The default contexts are portal for the anonymous version and myportal for the secure version

<virtual-portal-alias> - Virtual Portal Alias (VP alias) is only relevant when the WebSphere Portal environment uses Virtual Portals. The Cisco Enterprise Portal (CEP) environment leverages the VP alias to do routing of requests to applications based on predefined service level agreement rules and