[J.C. Hamlin]

Last week I read the New & Noteworthy information about MyEclipse 7.5 on the home page (which says “WebSphere 7 support”). I was very excited since that is one of our target platforms (in fact, the only one that MyEclipse 7.1, the version I was using, didn’t have). So I spent a day rebuilding my dev environment incudling downloading and installing 7.5 Professional edition. We use Flex Builder, multiple app servers, and bunch of other things, so it actually takes quite a bit of time to get the environment setup and running.

Much to my dismay, when I got it all setup back up and was ready to deploy I went to MyEclipse->Servers->WebSphere, to configure my WebSphere 7.0 installation, it shows 4.x, 5.x, 6.0, 6.1, and Community Edition. No mention of 7.0 in the list!

Then I found a post in another forum on this topic: https://www.genuitec.com/forums/topic/websphere-7-support/. It appears that only the Blue edition, that costs 3x as much as the regular per person per year, has support for WebSphere 7.0. Of course the Blue edition also has lots of other WebSphere features: RAD Project Support, Web Services, Connectors, Remote Servers, etc. However, what if you need to test and debug your application on WebSphere 7.0 but don’t need all those tools for features?

Our software engineering group does not need all the extra Blue features and this small little feature isn’t worth tripling the cost for 100 engineers. What we would like is just the basic support for WebSphere 7.0 that has always been there for the other app servers (38 of them and counting now). I think the basic features are: deploying, undeploying, starting, stopping, debugging, and capturing its output and sending it to the console window.

The WebSphere 6.1 settings don’t work (it has been tried and has issues).

So, we would like to request that a basic level of support for WebSphere 7.0 be added to the Professional and/or Standard version of MyEclipse.

Thanks!

-J.C.

[Riyad Kalla]

JC,

I’ll bring this up to the management team to discuss — as an immediately workaround see if you can go to the WebSphere 6.1 connector, set it up, hit Apply THEN go to the “Launch” tab and click “Create Custom Launch Configuration”. Then go under the Run or Debug dialogs and tweak the actual launch configuration to try and get WAS 7 working — it’s usually just an issue of making sure you are calling the right main class and have the right classpath set.

You will have to use custom location deployments to handle deploying to that custom setup, but it should allow you to manage launching and deployments from inside ME still. Also if run in Debug mode, the debugger should still auto-connect for you.

[nerimichael_abat]

This message has not been recovered.

[viswamy2k]

This message has not been recovered.

[Author]

Posts