- This topic has 23 replies, 7 voices, and was last updated 19 years ago by
.
-
Posts
-
Hi,I have some problems with MyEclipse/WebSphere5.I deployed my Enterprise Application Project from the ‘MyEclipse->Deploy’ option.And I see my project under WebSphere_HOME\installedApps\myHost\.
When I start WS5, it does not start my app.
Any ideas?
Thanks!
Well, the short answer is we’re still working on our solution for WebSphere, but here’s what’s going on. WebSphere’s deployment model is a bit odd. It doesn’t have an “autodeploy” concept like all the other application servers, so the only way to deploy seems to be by manually deploying through its console. Also, manual deployment only accepts an archive file (EAR), not an exploded equivalent. When the app is deployed, however, it is saved in the standard exploded format and it will pick up changes to modified components. Given all this, here’s what we’re planning for WebSphere deployment.
-
1) The user will need to do a one-time export of the project as an EAR into WebSphere’s installableApps directory.
2) The user must then use WebSphere’s console to deploy the application.
3) Once installed, the user can then set up an exploded deployment on top of the one that WebSphere created in the ‘installedApps’ directory.
4) At this point, Sync-On-Demand will handle keeping your WebSphere deployment in sync with your workspace as you make modifications.For EA2, the EAR export wizard is not available yet so you’ll have to manually create your own EAR for step 1, probably by writing an Ant script.
For all you WebSphere pros, if any of you have a better idea than the process outlined here, that you’ve tested, please post it as a follow up. We want the deployment model for WebSphere to be best of breed. At present, the basics outlined above seem to be it.
–Scott
MyEclipse SupportI understand the solution but my only problem is that when I choose to deploy as an exploed archive with the intent of overwriting the war file from my initial install, the directory that myeclipse wants to install to is WebSphere_HOME\installedApps\server1 rather than WebSphere_HOME\installedApps\myHost\server1 and I can’t seem to modify the deploy location.
Is this an issue with the way I have set up websphere?
Thanks
loomis, as a temporary solution what happens when you adjust the home/temp/webapps directory for WebSphere from the Window->Preferences->MyEclipse-Application Server->Websphere preference panel?
I am not sure I follow what you are suggesting. In the preferences for websphere5 under application servers, I can enter the websphere home directory, the host name, the server name and output encoding as well as some optional arguments. The deployment tool for myeclipse tries to deploy an exploded archive into the server directory beneath the installedApps directory rather than beneath the hostname/servername directory.
I figured I would try one more time to see if anybody has a solution for this problem. I still haven’t been able to update a websphere web module without going through the admin web interface in websphere and it is a very slow process to update everytime I make a change. The deployment feature seems to deploy the war file to an incorrect directory beneath installedApps.
Hi,
I tried the workaround as described by Scott.
it does not work, sorry to say that.The reason: The deploy directory is not correct.
For example, my ear is named traveler.ear.
Websphere deploys it at <IBM>/AppServer/installedApps/[hostname]/traveler.ear
MyEclipse deploys it at : <IBM>/AppServer/installedApps/[server]/traveler.warUnfortunately, the ‘Deploy Location’ field is disabled in the Deployment window.
So we are left stranded at this point. I had to manually copy files that are modified.The fix for the MyEclipse team is simple: Let us specify the deploy location!!!
t nguyen//
Tom,
You are absolutely right, this is an enhancement that will make its way into MyEclipse in the 2.8 release. We are really focusing heavily on improving the deployment process and more people are bringing to our attention deployment and use cases we hadn’t planned for.Our ETA for 2.8 is a beta by early march.
This is the same problem as the bug identified here:
https://www.genuitec.com/forums/topic/websphere-config-and-console-output-closed/#post-203471It will be fixed in the next build (2.7 / 3.7 GA).
Is the procedure outlined below still state of the art for eclipse 3.1.1 / myeclipse 4.1.1 / Websphere 6?
If not, can someone please link me to better instructions for getting an app deployed correctly from myeclipse to websphere?
@support-scott wrote:
Well, the short answer is we’re still working on our solution for WebSphere, but here’s what’s going on. WebSphere’s deployment model is a bit odd. It doesn’t have an “autodeploy” concept like all the other application servers, so the only way to deploy seems to be by manually deploying through its console. Also, manual deployment only accepts an archive file (EAR), not an exploded equivalent. When the app is deployed, however, it is saved in the standard exploded format and it will pick up changes to modified components. Given all this, here’s what we’re planning for WebSphere deployment.
-
1) The user will need to do a one-time export of the project as an EAR into WebSphere’s installableApps directory.
2) The user must then use WebSphere’s console to deploy the application.
3) Once installed, the user can then set up an exploded deployment on top of the one that WebSphere created in the ‘installedApps’ directory.
4) At this point, Sync-On-Demand will handle keeping your WebSphere deployment in sync with your workspace as you make modifications.For EA2, the EAR export wizard is not available yet so you’ll have to manually create your own EAR for step 1, probably by writing an Ant script.
For all you WebSphere pros, if any of you have a better idea than the process outlined here, that you’ve tested, please post it as a follow up. We want the deployment model for WebSphere to be best of breed. At present, the basics outlined above seem to be it.
–Scott
MyEclipse SupportPatrick, we provide a doc for WebSphere here: http://www.myeclipseide.com/images/tutorials/quickstarts/websphere6/
The doc referred to in the link is for Websphere 6. Since the same procedure is not working for Websphere 5 am I to assume that WAS 5.x will never have this issue addressed?
Carlos
Actually I was under the impression from the dev team that the steps outlined in 6 for deployment work almost identically in 5.x.
The reason I asked was that I was unable to get auto-deployment to work using Eclipse 3.1, MyEclipse 4.1 and WAS 5.1.
I tried deploying an EAR that pointed to a WAR and WAS did not auto-deploy after MyEclipse deployed to the server.
Carlos
