Fix (APAR):  PK66602

Status:  Fix

Release:  6.1.0.9,6.1.0.7,6.1.0.5,6.1.0.3,6.1.0.17,6.1.0.15,6.1.0.13,6.1.0.11,6.1.0.1

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

Supersedes Fixes:  

CMVC Defect:  PK66602

Byte size of APAR:  13374

Date: 2008-06-03

Abstract:  Virtual member manager fails to migrate the external id attribute configuration from websphere member manager.

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

ERROR DESCRIPTION:                                              
VMM doesn't migrate extId configuration from WMM if it's        
configured as DN.  This is working as design because of these   
design considerations:                                          
                                                                
a. DN is not the recommended extId for VMM since there're some  
known issues about its usage, such as uppercase problem in some 
locales.                                                        
b.  VMM uses the default extId configurations for each supported
LDAP servers, which works well instead of DN.                   
                                                                
Although customers can customize the extID to be what ever they 
want in WMM and VMM.  Therefore the value should not be         
restricted to the default value VMM uses, and migration tool    
should migrate the extId from WMM to VMM as it is.  In addition,
VMM also supports configuring DN as extId.                      

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere Application Server
6.1 who use federated repositories of
virtual member manager.

PROBLEM DESCRIPTION:
Virtual member manager fails to migrate
the external id attribute
configuration from websphere member
manager.

RECOMMENDATION:
None

Virtual member manager is not able to migrate external id
attribute configuration if it is configured as
distinguishedName.

PROBLEM CONCLUSION:                                             
The problem has been fix. The external id attribute             
distinguishedName can be migrated correctly.                    
                                                                
The fix for this APAR is currently targeted for inclusion in    
fixpack 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-IFPK66602.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-IFPK66602.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-IFPK66602.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: