WebSphere Portal , WCM, Connections Notes

Recently, I applied CF02 latest Portal fix pack to my local Portal 8.5 (with CF01) using Installation Manager. Was able to apply the fix pack without any issues. . Was able to verify most of the functionality of the Portal and WCM with latest fix pack CF02 a fter the upgrade, but noticed that I was not able to create any new “Site Area” in WCM Authoring Portlet and so quickly checked the SystemOut.log, I noticed following error - java.lang.NoSuchMethodError: com/aptrix/children/ParentValidator.isValidParent(Lcom/aptrix/identity/IdentityReference;) at com.ibm.workplace.wcm.app.ui.portlet.command.object.AbstractNewCommand.isAcceptableLocation(AbstractNewCommand.java:668) at com.ibm.workplace.wcm.app.ui.portlet.command.object.AbstractNewCommand.getPresetFolderLocation(AbstractNewCommand.java:641) at com.ibm.workplace.wcm.app.ui.portlet.command.object.AbstractNewCommand.getLocationForNewItem(AbstractNewCommand.java:465) at com.ibm.workplace.wcm.app.ui.portlet.command.obje...

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. Stop the WebSphere_Portal server. Open the the wkplc.properties and wkplc_comp.properties files in the /wp_profile_root/ConfigEngine/properties directory in some text editor. Open the wkplc.properties file and enter the value for your environment in the WpsContextRoot property. Save and close the file. 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. Re Start the WebSphere_Portal server. 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...

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...

I wanted to install Script Portlet into my local WebSphere Portal instance to explore this further and so I followed following steps. To work with Script portlet, you should have the WebSphere Portal 8.0.0.1 CF11 or Portal V8.5. 1. Download the Script portlet paa archive file from Green house catalog from the link - https://greenhouse.lotus.com/plugins/plugincatalog.nsf/assetDetails.xsp?action=editDocument&documentId=DDB5C467D991413285257C67002476E0 2. Un-archive the above downloaded file locally and this should contain the “ scriptportlet-app-x.x-SNAPSHOT.paa” paa file . 3. Go to your Portal profile ConfigEngine directory <WAS_HOME>/<wp_profile>/ConfigEngine and execute following ConfigEngine install-paa command – In Linux or AIX: ./ConfigEngine.sh install-paa -DPAALocation=< paa_file_location> -DWasPassword= password -DPortalAdminPwd=< password> Once above install-paa command executed successfully, then execute deploy-paa comma...

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...