Changing the portal URI after an installation in websphere portal server 8.5

•           Stop the WebSphere_Portal server.
•            Locate the wkplc.properties and wkplc_comp.properties files in the wp_profile_root/ConfigEngine/properties directory and create backup copies before you change any values.
•       Change the WpsContextRoot property in wkplc.properties            WpsContextRoot=wps                                                                                                    to                                                                                                WpsContextRoot=wp85
•        Change properties in wkplc_comp.properties                        WsrpContextRoot=wps/wsrp to WsrpContextRoot=wps85/wsrp          WpsPersonalizedHome=myportal to WpsPersonalizedHome=wp85myportal   WpsDefaultHome=portal  to  WpsDefaultHome=wp85portal                     Attention: Do not enter the same value for WpsPersonalizedHome and      WpsDefaultHome.
•         Start the WebSphere_Portal server.                                                                              
•          To change the context root for the values that you entered in the WpsContextRoot, WsrpContextRoot, WpsPersonalizedHome, and or WpsDefaultHome properties ,run the following command                                                                           ConfigEngine.bat modify-servlet-path -DPortalAdminPwd=password -DWasPassword=password 

•       Restart the WebSphere_Portal server.    
•       To change the context root for the values that you entered in the WpsContextRoot, WsrpContextRoot, WpsPersonalizedHome, and or WpsDefaultHome properties ,run the following command                                                                              ConfigEngine.bat modify-servlet-path-portlets-DPortalAdminPwd=password -DWasPassword=password

•              Navigate to C:\IBM\WebSphere\PortalServer\wcm\prereq.wcm\config\nodetypes,in ibmcontentwcm.registernodetypes , Update all lines that contain the         <ApplicationURI name="wps/mypoc/?view=auth&uri=wcm:oid:"/>                                  to                                                                                                                 <ApplicationURI name="wp85/mypoc/?view=auth&uri=wcm:oid:"/>

•         Run the following ConfigeEngine:                                                                  ConfigEngine.bat action-register-wcm-nodetypes -DWasPassword=passw0rd_123 -DPortalAdminPwd=passw0rd_123 
  
• ·      Run SELECT * FROM "JCR"."ICMSTJCRNODEREGISTER" to confirm:
  
                                                                                                                               
•         Log on to WebSphere Portal.Go to Applications > Content > Web Content Management. Under Preferences, select Edit Shared Settings. Under Library Selection, add Web Resources v70 to the Selected Libraries list. Click OK. Under Item Views, select All Items > All > Components > JSP. Select every JSP component from the Web Resources v70 library and then click Edit. Update the Path field for every JSP component with the new context root path.Change                                              /wcmextension;…
        to
         /wps85/ /wcmextension;……   
  
  
  
•         Log on to WebSphere Portal as the administrator. Click the Administration menu icon in the toolbar. Click Search Administration > Manage Search. Click Search Collections. Click the search collection that you want to update. For example: Default Search Collection.
  
  
  
            
•     Click the Edit Content Source icon for the first content source in the list. Edit the URL listed in the Collect documents link from the URL with the new context root. Click Save. Edit the URL in each remaining Log in to the WebSphere Integrated Solutions Console. Go to Applications > Application Types > WebSphere enterprise applications. Click the Seedlist_Servlet application link. Click Context Root For content source and then save your changes.
  
•       Web Modules.Change the context root and then click OK.
  
•      Run the following task to create the WebSphere environment variables for Web               Content  Manager:                                                                             

        ConfigEngine.bat create-wcm-servletpath-variables          DServerName=WebSphere_Portal -DWasPassword=passw0rd_123                

  
  

   Please refer wkplc.properties, for ServerName property.

Default URLs of WebSphere Portal Server 8.5

Use the following default URLs to access IBM® WebSphere Portal, the WebSphere Integrated Solutions Console, and theConfiguration Wizard:

IBM WebSphere Portal

http://localhost:10039/wps/portal

https://localhost:10042/wps/portal

WebSphere Integrated Solutions Console

http://localhost:10038/ibm/console

https://localhost:10041/ibm/console

Configuration Wizard

http://localhost:10200/ibm/wizard

https://localhost:10202/ibm/console

How to find Port numbers using ConfigEngine in WebSphere Portal8.5

 Run the following commands

ConfigEngine.bat list-server-ports -DWasPassword=passw0rd_123

After running this command, WebSphere_Portal_PortMatrix.txt is generated in wp_profile_root\ConfigEngine\log\

New Features of WebSphere Portal Server 8.5 CF3

Theme analyzer for portlet modules

You can see what resources are coming from the theme and what resources are coming from the portlets on the page. Support for pages was also extended to the export theme data function, so your output includes page, theme, and profile information.

Resource Aggregation for portlets

The system resource aggregator automatically loads dependencies on capabilities for portlets, if the theme metadata resourceaggregation.autoLoadPortletCapabilities is set to true. These capabilities and modules load automatically regardless of the profile on the page, if the capabilities and modules are installed and active anywhere on the system. The resource aggregator for portlets:

• Reduces the profile size
• Reduces the number of profiles that are required
• Reduces the need to modify the theme (a profile) or page (which profile assigned) to use certain portlets on a page
• Makes the system overall simpler and easier to use.

This feature requires configuration if your custom theme was created from the Portal 8.5 theme on a system before CF03. Connect to your WebDAV and edit the local copy of your metadata.properties file. Set the theme metadata resourceaggregation.autoLoadPortletCapabilities to true.

Public ResourceCombinerService API

Use the ResourceCombinerService public API for portlets that must link multiple resources on a page. The ResourceCombinerService public API links these resources in a combined, optimized way to keep the number of requests to a minimum.

Web Application Bridge Mobile support

Mobile support is provided for web applications that were developed and tested for rendering inside mobile device browsers.

SmartCloud for Social Business HTTP Outbound

You can now activate outbound HTTP connections to remote resources with IBM Connections in SmartCloud for Social Business by using SAML 2.0 tokens.

 Windows Mobile Support

Device detection has been added for Windows Mobile devices. Windows smart phones can render the mobile theme instead of the full desktop version of the theme.