Upgrading WebSphere Commerce
Mojca 1200008G2Y Visits (4112)
WebSphere Commerce V7.0 Feature Pack 5.0 was recently released and many clients rushed to upgrade to the new environment so they could play with the new features. One of the prerequisites is to upgrade WebSphere Commerce to 220.127.116.11 fixpack, and as usual, while already one is at these maintenance tasks, it is good to upgrade also the underlying SW (software) stack, such as the WebSphere Application Server (WAS) fixpack level, to the latest.
While running upgrades for WebSphere Commerce underlying SW stack such as WAS fixpacks, it's good to be attentive to run it as recommended. For a UNIX® environment, where the environment is setup as non-root, it is recommended to use a non-root user to install upgrades as well, otherwise one might get into trouble when you start the server after a fixpack has modified the files and their permissions under the WAS_
Normally, there is a script wcnonroot.sh that takes care of files permissions, but this will take care of permissions of Websphere Commerce files and not for the runtime jars under profiles, as this document describes: Troubleshooting: Returning to use a non-root user to run WebSphere Commerce
A problem that I recently worked on was for an error during WebSphere Commerce server startup, after WAS has been upgraded, and pointed to some jar not found, for example:
[06/07/12 11:27:14:487 BST] 00000000 ComponentMana E WSVR0501E: Error creating component class com.
Running wcnonroot.sh didn't solve this problem, however the following steps did help to get the server started, and then we were able to continue with the WebSphere Commerce fixpack 18.104.22.168 and Feature Pack 5 install.
Complete the following tasks: