[halkasimi]

I know the topic of automated Websphere deployment has come before on the forum, but I haven’t been able to find a clear answer on one question. Specifically, Is it possible to use MyEclipse to automatically deploy a new EAR and start the application in Websphere without using the Websphere admin console ?

I have been able to use MyEclipse to deploy the EAR into the insallable/installed directories, and to start/stop Websphere. But I have to use the Websphere admin console to insall the applicaiton. If anyone has been able to fully automate this using MyEclipse, please let me know.

Thanks

[Riyad Kalla]

Is it possible to use MyEclipse to automatically deploy a new EAR and start the application in Websphere without using the Websphere admin console ?

No, you must do the Admin console step because it builds out all the EJB stubs and enabled your server to host/run that ent app.

I think you might be mistaking what you are asking for what is typically asked about, hot syncing changes out to WebSphere while you work. This is supported and we have a quickstart guide comming out any day now that covers this with WebSphere 6.0.

[Riyad Kalla]

Actuallly guide is up, just not linked to our doc section yet: http://www.myeclipseide.com/images/tutorials/quickstarts/websphere6/

[halkasimi]

Thanks for the quick reply. I have a followup question regarding hot synch : So after I install my EAR using admin console, will hot synch take care of all changes including adding/removing EJBs, adding new remote methods, changes to the deployment descriptor … Are there any limitations to hot synch ? I’m trying to find out if there’s any point when changes to my app force me to reinstall using admin console ?

Also, do you know roughly what date WAS 6 will be supported ?

Thanks

[Riyad Kalla]

will hot synch take care of all changes including adding/removing EJBs,

No

adding new remote methods

Possibly, the spec doesn’t support hot syncing classes whose “shape” has changed, however some app servers (like Tomcat) will simply reload the context so if you just wait a bit the new class will be loaded. I’m not sure how WS will support this. Give it a try.

changes to the deployment descripto

Again, depends on app server, give it a try.

Are there any limitations to hot synch ?

Yes. It is basically intended to changes to the implementation details of methods for class files and unlimited for JSP files and other runtime-compiled resources.

I’m trying to find out if there’s any point when changes to my app force me to reinstall using admin console ?

General rule of thumb, anything major will need a reinstall. Hot sync is for smaller changes.

[halkasimi]

I tried to setup hot sync in Websphere V5.1 according to what I’ve read in the forum but it doesn’t seem to work for me. After successfully deploying my EAR as a Packaged deployment and testing my EJBs I did the following:

1. Stopped the server
2. Removed the “Packaged Arhive” deployment
3. Added an “Exploded Archive” deployment and redeployed my EAR
4. Restarted the server

After 4, I noticed that my application failed to restart. I believe the reason for this is MyEclipse deployed an exploded directory that is missing the required generated EJB files. What am I doing wrong and what do I need to fix it ?

Thanks in advance

[Riyad Kalla]

We are adding a new feature to the deployer in 4.0 Milestone 3 due out in about a week that allows you to “Overwrite” when deploying, instead of deleting, and I think this would fix the problem you are experiencing. Please hang in there until Milestone 3 is out and then give the “overwrite” feature a try when deploying.

[Author]

Posts