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 -

  1. Open the command prompt and go to <WP_PROFILE>/ConfigEngine directory.
  2. Run the wp-la-install-ear ConfigEngine tasks-
    1. In Linux env -
./ConfigEngine.sh wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name
    1. In Windows env -
ConfigEngine.bat wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name

  1. Restart the Portal Server profile.

  1. 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 wkplc.properties file before modifying this file.

  1. Modify the following parameters in the wkplc.properties file and save the file.
  • la.providerURL
  • la.propertyName
  • la.entityTypes
  • la.dataType
  • la.multiValued
 Note: You can find documentation about the above required parameters inside the wkplc.properties file..

  1. Now lets go back to <WP_PROFILE>/ConfigEngine in Command Prompt again and run the
    1. In Linux env -
./ConfigEngine.sh wp-add-property -DWasPassword=password
    1. In Windows env -
ConfigEngine.bat wp-add-property -DWasPassword=password
Note -  When you run this wp-add-property ConfigEngine, depending on the your env setup in the sas.client.props file, you might challenged with user identity and password. Enter the WebSphere Application Server user ID and password.

  1. Restart the Portal server again and then you should have the extended attributes in your Portal.
Note -  When you are adding more than one attributes, then step 1 -3 you just need to execute once only, you need to follow step 4 and further to add other attributes.

   
  1. Also you can verify the newly added LDAP attribute inside the wimxmlextension.xml file under  the directory /<WAS_HOME>/<WP_PROFILE>/config/cells/<WP_PROFILE>/wim/model/

Comments

Post a Comment

Popular posts from this blog

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