Fix (APAR):  PK63375

Status:  Fix

Release:  6.1.0.17,6.1.0.15,6.1.0.13

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK63375

Byte size of APAR:  20200

Date: 2008-04-17

Abstract:  When adding Domino LDAP into virtual member manager configuration, the default RDN property for PersonAccount will be changed in error.

Description/symptom of problem:  
PK63375 resolves the following problem:

ERROR DESCRIPTION:                                              
RDN property changed when configuring Domino LDAP, even if      
file repository still exists                                    
                                                                
                                                                
                                                                
The rdn attribute of the supported entity type PersonAccount in 
wimconfig.xml is modified when adding an LDAP repository.  This 
only happens when calling createIdMgrLDAPRepository with        
ldapServerType DOMINO(5/6/65), and it only happens if no other  
LDAP repository already exists in wimconfig.xml (the file       
repository still exists).                                       
                                                                
<config:supportedEntityTypes                                    
defaultParent="o=defaultWIMFileBasedRealm"                      
name="PersonAccount">                                           
      <config:rdnProperties>cn</config:rdnProperties>           
</config:supportedEntityTypes>                                  
                                                                
This is not acceptable for portal, since the supported entity   
type is independent of the LDAP repository. When an LDAP        
repository is added, we still use the file repository (rdn      
attribute should be 'uid') until the administrator edits the    
supported entity type manually.                                 

LOCAL FIX:                                                      
N/A                                                             

PROBLEM SUMMARY

USERS AFFECTED:
 All users of IBM Websphere Application
Server V6.1 who use federated repositories
(virtual member manager - VMM).

PROBLEM DESCRIPTION:
When adding Domino LDAP into virtual
member manager configuration, the
default RDN property for PersonAccount
will be changed in error.

RECOMMENDATION:
None

The RDN property for PersonAccount will be changed to 'cn' in
error, even if there is a file repository in  the VMM
configuration using the RDN property "uid".

PROBLEM CONCLUSION:                                             
The problem has been fixed. Virtual Member Manager will not     
modify the RDN property for PersonAccount if there is still     
another repository in the VMM configuration.                    
This fix is included with PK63375 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.1
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 <was_root>/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-IFPK63375.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-IFPK63375.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-IFPK63375.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: