eFix (APAR): PQ60657 Status: efix Release: WebSphere 4.0.4 Supersedes eFixes(server): none Supersedes eFixes(client): none CMVC defect: PQ60657 Byte size of APAR: 1,180,287 bytes Date: 09/10/2002 Abstract: In multi-node environment using remote console, EAR files fail to expand yet console indicates successful installation. Error Description: In multi-node environment When using a remote admin console to install an Ear file that is local to the adminserver the adminclient is connecting to, the final screen informs the user that the file is local to the install node and will be expanded in the installedApps directory. This however does not occur. The application is visible in the console, but will not run properly because the code has not been expanded into the installedApps directory. The error "CNTR0020E" appears when trying to start or access info on the i nstalled application. Customer receives feedback that the instal l was successful, without being told that the EARexpander has to be ran against the EAR file before the application is fully installed. This is a false positive. With this fix, expanding the EAR file will be determined only by: node on which EAR file resides and node on which EAR file is to be expanded are same, node on which admin server is running will not be a factor! As a result customer can have local console connect to local adminserver and install EAR on remote nodes in the multi-node cluster without needing to manually expand the EAR. If EAR file resides on a node other than the one intended to install on, user will need to manually expand the EAR on the intended node. This is the expected behavior of WebSphere. A console provides message to inform customer. ************************** NOTE: ************************** This fix applies to both the admin server and GUI console, as a result instances of WebSphere with eFix PQ60657 will introduce client/server incompatibilities with instances WITHOUT eFix PQ60657 when installing EAR. When applying this eFix, it is recommended customer apply it to all instances of WebSphere AE 4.0.4 in the environment. Behaviors customers can expect to see between NEW (PQ60657 applied) and OLD (no PQ60657) client/server: - NEW client remote-connect to OLD server: - install EAR on appserver located on OLD server: -> console msg indicates auto expansion, but exceptions thrown, console popup critical error - install EAR on appserver located on NEW server: -> correct console msg, installation succeeds - old client remote-connect to new server: - install EAR on appserver located on NEW server: -> console indicates success, yet no expansion - install EAR on appserver located on OLD server: ->console msg indicates manual expansion necessary, however expansion succeeds - OLD client local-connect to OLD server: - install EAR on appserver located on NEW server: -> console indicates success, yet no expansion - install EAR on appserver located on OLD server: -> working as before - NEW client local-connect to NEW server: - install EAR on appserver located on OLD server: -> console indicates auto expansion, however popup critial error, installation fails - install EAR on appserver located on NEW server: -> working as before ************************************************************ Directions to apply efix: 1) Create temporary "efix" directory to store the jar file: AIX: /tmp/WebSphere/efix Solaris/Linux: /tmp/WebSphere/efix Windows: c:\temp\WebSphere\efix 2) Copy jar file to the directory 3) Shutdown WebSphere 4) Run the jar file with the following command answering questions/prompts as they appear: java -jar 5) Restart WebSphere 6) The temp directory may be removed but the jar file should be saved. Do not remove any files created and stored in the /WebSphere/AppServer/efix/ directories. These files are required if an efix is to be removed. Directions to remove an efix: NOTE: EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE AN EFIX UNLESS ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED EFIX. Example: If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be removed, efix3 must be removed first, efix2 removed, and efix3 re-applied. 1) Change directory to the efix location (/WebSphere/AppServer/efix/). 2) Shutdown WebSphere 3) Run the backup jar file with the following command: java -jar 4) Restart WebSphere Directions to re-apply an efix: Follow the instructions for applying an efix. If the backup files still exist (from the previous efix application), you will be prompted to overwrite. Answer "yes" at the overwrite prompts. Additional Information: ------------------------------------------------------------------ This is a cumulative efix. In addition to the description above, applying this efix solves the following problems: none ================================================================= Cumulative from client eFixes: none