You can install a Eclipse plugin that works with IBM WebSphere Application Server 7.0 from the Eclipse Marketplace. Yes, In addition to supporting WebSphere Application Server v8.5 Alpha Liberty Profile, v8.0, it also supports the v7.0.
http://marketplace.eclipse.org/node/131344
If you don’t have Eclipse Marketplace installed, Add a new site/repository for software updates – http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/V8.5/
See screen shot below:

Advertisement
You mean IBM put out a plugin and they are not charging you for it?
Comment by Daniel Frey (@dmfrey) — October 10, 2011 @ 2:36 pm
@dmfrey, yep!
Comment by Davanum Srinivas — October 10, 2011 @ 3:02 pm
Hi have a problem in starting WAS7.0 after doing above steps, I am using helios version of Eclipse, when I try to start the server, the process bar always stuck at 23%, but in actual server is starting completed because I could see ‘java’ process running in ‘Task Manager’ and also I can open admin console, could you please suggest if you have ever faced similar issues.
Many Thanks
Ganesh
Comment by ganesh — December 3, 2011 @ 3:04 am
But we can not enable JRebel for this WAS 7.0
Comment by Le Duc Tho — October 10, 2011 @ 11:48 pm
Any chance we’ll see a plugin for WPS7 too?
Comment by Carsten — October 11, 2011 @ 6:32 am
unfortunatelly it is not working. After trying to install the plugin for WAS 7 I get the error message: The software items you selected may not be valid with your current installation. I am using Ganymede. Does it not work with it? Thanks
Comment by ciccio — October 21, 2011 @ 11:27 am
hello, I really appreciate that this plug-in appears, but I have a problem with it, I tried to connect to remote server, but It always show me “stopped” condition.
Comment by Boris Shestakov — November 8, 2011 @ 12:02 pm
Hi srinivas, i dont this is appropriate place for posting my issue or not. sorry if its wrong location. i am facing a serious problem in WAS6.1 server for personal certificcate.
please read below issue.
1. we are consuming/calling web service (https), by apache axis 1.4 frame work , by configuring the signer certificate in NodedefaultTrustStore.
this is working absolutely fine for the past 2 years.
2. recently we got new requirement to connect SSL based MQ from the WAS6.1 . We received personal certificate (installed on NodeDefaultKeyStore), root,intermediate,actual signers (we installed these 3 on NodeDefaulttrustStore) from our client manager. and we changed to transport chain as MQ secured link, and provided appropriate chiper suite as top in the list.
Now, the new MQ connectivity is working, but existing web service request is failing. basically, web service request is using the mq personal certificate, which should not happen
please help us asap..
roopa
Comment by roopa — November 19, 2011 @ 6:58 am