Updating .ear file on websphere (6.1) still runs old code

Question

I have a question regarding updating a application on websphere application server. The application is already up and running and I just want to update the code which is packaged in a .ear file. Here is what I thought I should do:

1. stop the application server.
2. go to my enterprise application, select the one I am updating, and click update.
3. point to my .ear file in replace the entire application radio button option.
4. restart my application server.

After doing this and trying out my application, it is still running the old code, which makes me really confused. The only way I managed to get it to work is to use WinSCP, manually go to the cell directly/installedapps and replace the whole .ear folder. I dont think this a viable solution moving forward.

Answer 1

To update existing enterprise application we do not have to stop the application since WAS stops the application before updating the code .

Based on the update you gave i am assuming this is a network deployment manager setup , so possibly problem is with sync is not taking place after updating the app and save .

Are you explicitly invoking sync operation after application update ? If not , i would recommend that.

Still problem persists then most likely for what ever reason nodeagent process is not invoking app expansion into installedApps folder but you can take a quick look at nodeagent systemout.log file or ffdc files to see if there is any clue about expansion process.

As a work-around you can also use EARExapnder.sh/bat tool available /profile_home/bin directory to expand the application into installedApps when the app is really updated in config/cells/cell_name/applications but not under installedApps folder.

I hope this helps. Thanks VT These opinions are my own.

Answer 2

I solved it. After some intense digging it seems the binary files were expanded into dmgr profile but not my correct node. After finishing the update instead of clicking save I click review and there is a checkbox to synchronize the nodes, which then did the trick.