Fix (APAR): PK71757 Status: Fix Release: 7.0 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries Supersedes Fixes: CMVC Defect: 547736 547717 548970 Byte size of APAR: 75042 Date: 2008-09-18 Abstract: There are multiple problems fixed by this APAR. Description of each follows: a) For users of WebSphere Administrative ThinClient 7.0 on distributed, the client fails to connect to Description/symptom of problem: PK71757 resolves the following problem: ERROR DESCRIPTION:? Admin thin client on distributed environment does not work for RMI/JSR160RMI with security on. LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: All users of WebSphere Application Server 7.0 PROBLEM DESCRIPTION: There are multiple problems fixed by this APAR. Description of each follows: a) For users of WebSphere Administrative ThinClient 7.0 on distributed, the client fails to connect to the server if security is turned on when using RMI or JSR160RMI connector. b)A nested business-level application cannot be started as part of its parent business-level application. c) Using wsadmin in local mode (conntype NONE option) and assigning resources to AuthorizationGroup, the addResourcesToAuthorizationGroup command fails with an Exception "Invalid type" RECOMMENDATION: None A summary of each problem follows: a) When using wsadmin in the thinclient environment to connect to a secured server with RMI connector, it may fail with the error below: WASX7023E: Error creating "RMI" connection to host "localhost"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableExce ption: javax.naming.NamingException: Error during resolve [Root exception is org.omg.CORBA.UNKNOWN: Unexpected exception found while rethrowing pending exception after processing client-side response interceptor: com/ibm/ws/Transaction/client/NonRecoverableTranManagerSet vmcid: IBM minor code: EA3 completed: Maybe] b) A business-level application can be added to another (parent) business-level application. When a parent business-level application is started or stopped, all members of the business-level application are started or stopped, including all nested business-level applications that were added to it. The start or stop operations on nested business-level applications fail, yielding a "partially successful" result on the parent start or stop operation. A nested business-level application can be started and stopped directly with successful results, however. The error message depends on whether the operation is executed from wsadmin or the Adminstrative console. The error message displayed in wsadmin for start and stop operations has this general form: WASX7015E: Exception running command: "$AdminTask startBLA {-blaID ParentBLA}"; exception information: com.ibm.wsspi.management.bla.op.OpExecutionException com.ibm.wsspi.management.bla.op.OpExecutionException java.lang.NullPointerException: java.lang.NullPointerException: name cannot be null The error message displayed in the administrative console for start operations is: ParentBLA failed to start. and the administrative console message for stop operations is: An error occurred while stopping Parent BLA. In the above messages, ParentBLA is the BLA being started or stopped. c) Cannot use addResourcesToAuthorizationGroup command from wsadmin using local mode. For example: When running the following command $AdminTask addResourceToAuthorizationGroup {-authorizationGroupName ag1 -resourceName Server=server1} The following error occurs: ERROR: Caught Exception: com.ibm.ws.scripting.ScriptingException: com.ibm.websphere.management.cmdframework.CommandValidationExcep tion com.ibm.websphere.management.cmdframework.CommandValidationExcep tion: Invalid Type. Server PROBLEM CONCLUSION:? For each problem: a) Added the missing classes that need to be in administrative client com.ibm.ws.admin.client_7.0.0.jar. b) Enabled a nested business-level application to be started and stopped successfully as part of a start or stop operation on its parent business-level application. c) Changed the code to properly use the resource type validation code that is required to validate resource types in a wsadmin process running in local mode. The fix for this APAR is currently targeted for inclusion in fixpack 7.0.0.1. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. 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-1.ibm.com/support/docview.wss?rs=180&uid=swg24020212 1) The fix is delivered as a single file with a .pak extension (such as 7.0.0.1-WS-WAS-IFPK12345.pak). Copy the .pak file directly to the maintenance directory, /maintenance. 2) Shutdown WebSphere 3) For IBM i users, use the update command to install and uninstall the interim fix. The IBM Information Center can provide additional details, if needed, on the use of this command. http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update. For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. To determine why some maintenance packages have been identified as not applicable, see description in log found in /logs/tmp*/updatelogs.txt 8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance. Correct any file permissions before clicking next to start the install. 9) Restart WebSphere Directions to remove fix: 1) Shutdown WebSphere 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) Select 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: