I have a RAD 7.5 with WAS TE 7.0.0.15 installed on my windows XP 32 bit machine.
I used to be able to open my EAR project and deploy onto the server directly i.e. right click on EAR > Run on server > and then point to my server.
The EAR URL looked like this: http://localhost:9080/myContext/Login.action
When I deploy the EAR (export as and EAR file first and then install the EAR from admin console) I am able to work with the application just fine.
However, after trying to use the profiling feature of RAD, this feature has simply stopped working. I am no longer able to run the application from with in the IDE. I simply get the 404 error. I am not able to understand the difference between why it works when deployed as an enterprise application from admin console.
I have uninstalled the server assuming something might have corrupted the server. But it did not help at all.
Is this a known problem? Please help.
Thanks, Ayusman
I had problems of similar nature with RAD 7.5 and WAS 7 runtime. I used it to install, configure and test several our corporate applications. Sadly, sometimes exceptions thrown by these applications caused the server profile, in which they were executed, to corrupt inadvertently, and no cache cleaning/redeploying helped. Deploying via admin console is more stable, as it does not use Eclipse/Websphere integration, which is probably the problem here.
My general advice for working with RAD is this:
[yourprofiledir]/temp
and [yourprofiledir]/wstemp
, then restart the server;If you set up your configuration by scripts, then you probably don't need the archive, as it is not costly then to remove and recreate a server profile — as it's the profile that often gets corrupted.