IBM WebSphere Application Server v8.5 Liberty Profile Developer Tools Beta 1,
IBM WebSphere Application Server v8.5 Developer Tools Beta 1,
IBM WebSphere Application Server v8.0 Developer Tools Beta 1,
IBM WebSphere Application Server v7.0 Developer Tools Beta 1.
But I cannot see WAS servers in run-time environment preferences. There is only Liberty Profile available.
Should I perform any additional configuration, to add WAS 7, 8 and 8.5 to run-time and server views?
This topic has been locked.
7 replies Latest Post - 2012-09-24T09:21:49Z by Jacek_Laskowski
Pinned topic Problem with WebSphere Application Server Developer Tools for Eclipse
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
SystemAdmin 110000D4XK590 PostsACCEPTED ANSWER
Re: Problem with WebSphere Application Server Developer Tools for Eclipse2012-01-09T19:26:54Z in response to mgn2009Hi Martin,
Which version of Eclipse based you are using? Only the Liberty Profile is supported on Indigo (Eclipse 3.7.1). The WebSphere Application Server Tools for WAS v7, v8 and v8.5 only runs on Helios, i.e. Eclipse 3.6.2. Make sure you are using Helios if you want to use those server types.
Also, there are some configuration steps required after the installation. You can refer to the "Configuring the installation" section of this documentation for details:
See if that helps.
EstherY 270000K8QE2 PostsACCEPTED ANSWER
Re: Problem with WebSphere Application Server Developer Tools for Eclipse2012-02-01T19:41:18Z in response to SystemAdminElson,
I am running Eclipse Indigo and have followed the instruction to add the -vm <WebSphere Application Server V8.0 or V7.0 installation directory>/java/jre/bin/java in the eclipse.ini file. It is all being asked to change. But I keep getting the IBM VM warning like this
"An attempt was made to use a WebSphere-specific function which is supported on the IBM JRE. Please use the IBM JRE from the product install image."
My JVM version in my windows XP is 1.6.0_30. The requirement for WAS 8 tool is 1.6.0_27 and above.
I got the same issue on Eclipse 3.6 with the 3.6 only WAS tool as well.
With this warning, when I start WAS v8 in Eclipse, the last output on the console is "XXX server open for e-business". The server status keep staying on "starting..." then the server boot timeout kicks in. The server status became "stopped". I am not able to stop the server either from Eclipse. I am setting the server start using generated script and run on workbench resource as same as it is done on Rational Application Developer.
The Rational Application Developer trial version is working fine to admin the same WAS server. So I believe the WAS installation is fine.
Any help would be greatly appreciated!
Roman@aformatik 100000GPCF3 PostsACCEPTED ANSWER
Re: Problem with WebSphere Application Server Developer Tools for Eclipse2012-02-02T10:12:29Z in response to EstherYHi Esther,
to make the WAS tools work with Eclipse and WAS you have to point and run your Eclipse with an IBM JDK. Just modify your eclipse.ini and use the -vm switch and point to the javaw of WAS 7 or
Hope this helps, it did to me :-)
EstherY 270000K8QE2 PostsACCEPTED ANSWER
Re: Problem with WebSphere Application Server Developer Tools for Eclipse2012-02-02T14:21:43Z in response to Roman@aformatikRoman,
Thank you for your response!
This is all I have in the eclipse.ini file. Do you see anything wrong here? It is still giving me the same warning. I installed WAS8.0.
PingWei 06000264S51 PostACCEPTED ANSWER
Re: Problem with WebSphere Application Server Developer Tools for Eclipse2012-03-07T08:30:10Z in response to EstherYTry put the path under the -vm
bjruddy 100000TBJT1 PostACCEPTED ANSWER
Re: Problem with WebSphere Application Server Developer Tools for Eclipse2012-09-20T16:50:41Z in response to PingWeiIm using the Spring Toolkit Eclipse Distribution. When I add the -vm path to my websphere install the client crashes. I think this is because the Spring Toolkit version wants the entire JDK and not just the JRE. Can anyone help on this? Ive been stuck for days.