Fix (APAR): PK18574 Status: Fix Release: 6.0.2.3 Operating System: AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: PK18574 Byte size of APAR: 13722 Date: 2006-02-06 Abstract: The adminClient's caching could not be previously disabled Description/symptom of problem: PK18574 resolves the following problem: ERROR DESCRIPTION: Rollup of PQ86926 (V5 APAR) to V6 all platforms LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server version 6 users who do not want to cache their AdminClient. PROBLEM DESCRIPTION: The adminClient's caching could not be previously disabled RECOMMENDATION: None Because of non-configurable adminClient caching, customers would sometimes run into problems when running custom code as part of a server process. In SystemOut.log you see 000003b RoleBasedAuth A SECJ0305I: The role-based authorization check failed for admin-authz operation Server: getProcessType. The user saUser (unique ID: user:t51.austin.ibm.com:389/cn=sauser,o=ibm,c=us) was not granted any of the following required roles: administrator, operator, configurator, monitor. 0000003b AdminServiceI A ADMN0007I: The getAttribute method results in exception com.ibm.websphere.management. exception.AdminException: javax.management. JMRuntimeException: ADMN0022E: Access is denied for the getProcessType operation on Server MBean because of insufficient or empty credentials. at com.ibm.ws.management.AdminServiceImpl. getAttribute(AdminServiceImpl.java:628) at com.ibm.ws.management.connector. AdminServiceDelegator.getAttribute (AdminServiceDelegator.java:117) at com.ibm.ws.management.connector.rmi. RMIConnectorService.getAttribute(RMIConnectorService.java:124) at com.ibm.ws.management.connector.rmi. _RMIConnectorService_Tie.getAttribute (_RMIConnectorService_Tie.java:209) at com.ibm.ws.management.connector.rmi ._RMIConnectorService_Tie. _invoke(_RMIConnectorService_Tie.java:97) at com.ibm.CORBA.iiop.ServerDelegate. \dispatchInvokeHandler(ServerDelegate.java:610) at com.ibm.CORBA.iiop.ServerDelegate. dispatch(ServerDelegate.java:463) PROBLEM CONCLUSION: This APAR allows customers to turn off & on caching for the admin client.PQ86926 took care of this problem in Version 5. This APAR has made same changes as PQ86926 in Version 6: Changes in PQ86926: In AdminClient.java the CACHE_DISABLED property was defined. In AdminClientFactory.java, if the CACHE_DISABLED property is set, then we create a new admin client every time. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.9 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: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ 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.0.2.2 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 PKxxxxx.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 (PKxxxxx.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 (PKxxxxx.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: