Re: [WDSCI-L] EAR/WAR Deployment

[MEovino@xxxxxxxxxxxxxxxxx]

> some require you to stop and start the application

That doesn't sound so bad.

> and a few require you to stop and start the server.

That sounds bad.  Guess we'll have to quit writing bugs!

But seriously, how do you get around that?  If I'm running just a single
appserver instance, I'm pretty much screwed.  I have to take down all of my
apps to fix one.  If I'm running clustered appservers, can I take each one
down individually and deploy the fix while the others are handling incoming
requests?

Mike E.






MEovino@xxxxxxxxxxxxxxxxx
Sent by: wdsci-l-bounces+markp=softlanding.com@xxxxxxxxxxxx
07/06/2003 11:08 PM
Please respond to Websphere Development Studio Client for iSeries

        To:     Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
        cc:
        Subject:        Re: [WDSCI-L] EAR/WAR Deployment



Joe,

Go ask Bob Cancilla what he thinks of the EAR/WAR concept.

;-)

Seriously, this stuff looks crazy to an old (at least in Internet years)
Net.Data/RPG guy.  No way to deploy a fix to a broken app without taking
down the server?  Well, now WAS-E running on a single node looks really
attractive -- as long as we never deploy an app with a bug in it.

We usually only deploy apps late at night, but every so often we do have
to
put in a fix ASAP.  Now I have to take down the entire app server?  Ugh, I
can't wait.

Mike E.




> From: David Gibbs
>
> There are other tools available that are more robust than ANT ...
> but they aren't free.

"Tools"?  As in deployment tools?  Some sort of add-on tool that will
deploy
applications?  I don't understand how that would work with WAS.  The only
way I know to deploy to WAS is via an EAR file (or, to a limited degree,
with a WAR file).  There are no other tools, because the WAS folks insist
that they are following the "J2EE standard" and that's all they need to
do.

Unfortunately, the more I look into it, the more I realize that J2EE isn't
really standard for business applications.  No concept of net change
deployment, no ability to hot install without bringing down the server,
and
now I find that there's no way to run a post-installation script.

As far as I can tell, the J2EE deployment model is pretty much just a way
to
occasionally install a tool.  It certainly is no model for business
application deployment.

Joe





_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.