Author: yuval

If you ever uninstalled an application from RAD 6’s embedded WebSphere using its admin console (http://localhost:9060/ibm/console), you may encounter a bizarre situation in RAD.

If RAD was used to install the application into WebSphere, it will now fail to ‘recognize’ that WebSphere started up even when it does, and will keep the ‘Starting…’ state going for the server status. The only way I could find to cure this ill is to reinstall the application – again from the admin console – and then try to start the server from RAD.

How do you start and stop the server from outside of RAD?

Go to {WEBSPHERE_HOME}/bin/startServer.(bat or sh) server1 (or whatever name your server uses).

Early on when working with WebSphere, I made the mistake (out of frustration and other momentary elements) of removing applications by force, simply deleting them from the server’s directory structure.

Ever since, the beast that is WebSphere was angry: no matter what I tried, it kept attempting to load the missing applications. Finally, I seem to have found the place where the application references were hiding:
cells\ENYZHLNode01Cell\nodes\ENYZHLNode01\serverindex.xml is the file that among other things, tells WebSphere which applications to load. In short, remove the missing applications from it, and you get a nicer, cleaner startup from WebSphere.