Fix (APAR): PK63020 Status: Fix Release: 6.1.0.17,6.1.0.15 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: PK63020 Byte size of APAR: 15236 Date: 2008-04-06 Abstract: An exception is thrown when adding property "ibm-primaryEmail" as the loginProperty of repository. Description/symptom of problem: PK63020 resolves the following problem: ERROR DESCRIPTION: Abstract: if ibm-primaryEmail is added as loginProperty via the updateIdMgrLDAPRepository AdminTask, the following exception was thrown: Update LDAP repository - result: [com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5015E Login properties are not valid: [ibm-primaryEmail].] [wplc-update-federated-ldap-repository] com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5015E Login properties are not valid: [ibm-primaryEmail]. [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.ConfigValidator.validateLoginProperties(Co nfigVali dator.java:522) [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.ConfigValidator.validateRepositoryParams(C onfigVal idator.java:157) [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.LDAPRepositoryConfigHelper.updateIdMgrLDAP Reposito ry(LDAPRepositoryConfigHelper.java:170) [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.commands.LDAPRepositoryConfig.updateIdMgrL DAPRepos itory(LDAPRepositoryConfig.java:68) [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.commands.IdMgrRepositoryConfigCommandsProv ider.upd ateIdMgrLDAPRepository(IdMgrRepositoryConfigCommandsProvider.jav a:167) [wplc-update-federated-ldap-repository] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Description: The above behaviour is wrong as ibm-primaryEmail is a valid VMM attribute and it is also existing in the according LDAP . LOCAL FIX: No work-around. PROBLEM SUMMARY USERS AFFECTED: All users of IBM WebSphere Application Server V6.1 users who use federated reposito ies (virtual member manager, VMM). PROBLEM DESCRIPTION: An exception is thrown when adding property "ibm-primaryEmail" as the loginProperty of repository. RECOMMENDATION: None If "ibm-primaryEmail" is added as loginProperty via the updateIdMgrLDAPRepository task, the following exception is thrown: Update LDAP repository - result: [com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5015E Login properties are not valid: [ibm-primaryEmail].] [wplc-update-federated-ldap-repository] com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5015E Login properties are not valid: [ibm-primaryEmail]. [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.ConfigValidator.validateLoginProperties (ConfigValidator.java:522) [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.ConfigValidator.validateRepositoryParams( ConfigValidator.java:157) [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.LDAPRepositoryConfigHelper.updateIdMgrLDAP Repository(LDAPRepositoryConfigHelper.java:170) [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.commands.LDAPRepositoryConfig.updateIdMgrL DAPRepository(LDAPRepositoryConfig.java:68) [wplc-update-federated-ldap-repository] at com.ibm.ws.wim.config.commands.IdMgrRepositoryConfigCommandsProv ider.updateIdMgrLDAPRepository(IdMgrRepositoryConfigCommandsProv ider.java:167) [wplc-update-federated-ldap-repository] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) PROBLEM CONCLUSION: The problem has been fixed. The exception will not be thrown if "ibm-primaryEmail" is configured as the loginProperty. This fix is included in PK63020 and targeted for fix pack 6.1.0.19. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: Fix applies to Editions: Release 6.0 x_ Application Server (Express or BASE) x_ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer x_ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes x_ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.1.0.13 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy 6.1.0.0-WS-WAS-IFPK63020.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (6.1.0.0-WS-WAS-IFPK63020.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (6.1.0.0-WS-WAS-IFPK63020.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: