eFix (APAR): PQ62502 WebSphere 4.0.2,4.0.3 Edition: WebSphere AE,AEs ContainerTypes: AEServer,AEsServer Operating System: All supported platforms for WebSphere AE Byte size of APAR: 8,66,347 Date: July 10, 2002 Abstract: XMLConfig changes not updated in a running wscp session.Description/symptom of problem: If WSCP session has already been open and XMLConfig deletes and recreates an application Server, the wscp session fails with: RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: ; nested exception is: javax.ejb.ObjectNotFoundException 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 NOTREMOVE AN EFIX UNLESS ALL EFIXES APPLIED AFTER IT HAVE FIRST BEENREMOVED. YOU MAY REAPPLY ANY REMOVED EFIX. Example: If your system has efix1, efix2, and efix3 applied in thatorder and efix2 is to be removed, efix3 must be removed first, efix2removed, and efix3 re-applied. 1) Change directory to the efix location: (/WebSphere/AppServer/efix/). 2) Shutdown WebSphere 3) Remove the Admin.config entry com.ibm.ejs.sm.adminServer.forceReconnect=true 4) Run the backup jar file with the following command: java -jar 5) Restart WebSphereDirections to re-apply an efix:Follow the instructions for applying an efix. If the backup filesstill exist (from the previous efix application), you will beprompted to overwrite. Answer "yes" at the overwrite prompts.