RE: Re: EAR/WAR Deployment -- WDSCI-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

> From: Mark Phippard
>
> In your case I imagine that you have a command that does the
> updates.  For
> your command to work correctly now, the user must have to provide
> the name
> of their WAS instance as well as their WAS version, otherwise you
> would be
> hard-coding and we know you do not like that.

No, Mark.  You just don't get it.  Last post.

My directory structure is constant.  It defaults (thought can be changed) to
install in '/user/psc400'.  Everything lives there.  Small, simple folder
names.  Then I simply create a WAS instance to point to those folders, using
a very simple script.  The WAS instance information needs to be identified
at that initial installation time ONLY.

>From that point on, I always deploy to the /user/psc400 hierarchy and never
worry about it again.  This makes debugginng, support, and so many other
issues so much easier.  I have fixed Tomcat to be able to do this as well,
and now I plan to fix WAS5X.

Anyway, this is my last post on the subject.

Joe

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.