RE: Re: Re: Re: EAR/WAR Deployment

> From: Buck
>
> > ...perhaps you might try deploying a few net changes
> > and see what happens.  On my model 270, deploying
> > a single-line fix ON A TRIVIAL APPLICATION took
> > 20 minutes, most of which time the application server
> > was unavailable.  If you think this is acceptable from a
> > production standpoint every time you need to deploy
> > a hot fix, then you come from a different environment than I do.
>
> I agree that this is unacceptable.  But I have deployed many hot fixes,
> similar to the one line oopsie you mention, and have never had to tear WAS
> or Tomcat down to do it.  Nor did I have to use a 3rd party tool
> to deploy:
> I wrote simple CL commands to MOV the objects from hither to yon.
>  It could
> also be done with DOS batch files or a *nix or QSH script.

Very few RPG programmers could do this, Buck.  Perhaps you'd like to publish
your tools open source to help some other folks?


> As you have mentioned in the past, one DOES need to understand
> the directory
> structure used by J2EE, which seems to be identical for WAS 4+ and Tomcat
> 4+.

And completely changes again for WAS5.  Which is my point.  You are
completely at the mercy of whatever the WAS team decides next.  And then
read Paul Nicolay's post on trying to redeploy existing applications.


> Discovering the file structure is not at all difficult in my opinion,
> even without looking at any documentation.  I advise beginners to create a
> teeny-tiny application, WAR it up and deploy it, then look at the
> results in
> the file system.

<laughing>  Yeah, a teeny-weeny WebFacing application.  In any event, Buck,
you actually prove my point.  You wrote CL commands to MOV objects around.
Me, my product generates stuff directly into the IFS.  It worked great with
WebSphere 3.5, but not with WAS4/Tomcat.  I changed it to work with
WAS4/Tomcat, and it didn't handle WAS5.  This idea of write once, run
anywhere is being completely trashed by the folks who think they should be
able to dictate our naming conventions.  Heck, I can'y even upgrade to V5R2
unless I rewrite my web applications.

This is not a good concept.  It's as simple as that.

Joe