Re: WebSphere 5.0 Express Questions

[<Matt.Haas@xxxxxxxxxxx>]

Mike,

Probably the best way to do this with one HTTP server and one App server
is to use virtual hosts. You'll have to set this up in both the HTTP
server and in the App server. You'll have to call the test and
production applications something different in the App server but they
can answer to the same context name as long as they are defined in
different virtual hosts. The big draw back to this is that you're
running in the same JVM so if your test application does something that
takes out the JVM, production goes down as well.

Matt 

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Mike Wills
Sent: Monday, February 13, 2006 2:38 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] WebSphere 5.0 Express Questions

Maybe I didn't describe what I wanted good enough.

I want to go to one WAS instance and and one apache instance on the
iSeries
for live and test. The vendor recommends one set for live and one set
for
test. If I could even go to two WAS instances and one apache, that would
work as well. Is this possible, or is it best to keep them seperate?

On 2/13/06, Dave Odom <Dave.Odom@xxxxxxxxxxxx> wrote:
>
> Mike, et all,
>
> As an aside, it always baffles me how PC server technology or at least
> application designed to run thereon, in their current form, ever got
to
> be something businesses would take seriously as a mission critical
> environment with most vendors requiring an EXCLUSIVE server for their
> application.    One application per server!!!   How early man!!
>
> When was the last time you ever saw a real computer, i.e., mainframe
or
> midrange (iSeries for instance) require only one application per
> server???   Maybe around the late 1950's or early 1960's.   That
should
> show the world how primitive are PC applications, except for their
GUI.
> Certainly not something to 'bet the farm on".
>
> Take care,
>
> Dave
>
> >>> colinwilliams007@xxxxxxxxx 2/13/2006 11:54:08 >>>
> Mike as others have said, it depends how the vendors app is
> configured.
>
> Running on seperate websphere instances is certainly the cleanest way
> to do
> it, less chance of accidentally knocking out the production systems!
>
>
> On 13/02/06, Dave Odom <Dave.Odom@xxxxxxxxxxxx> wrote:
> >
> > Of course making sure you have the "horsepower" on your PC to run
> more
> > than one, you can run two copies (Production and Test) in the same
> > server IF your vendor or you have created the application in such a
> way
> > as the two don't "bump heads" going after the same resources and
> each
> > wants it exclusively and the like.
> >
> > Also, you can put more than one different application on the same PC
> as
> > long as the two aren't created in such a way they won't play well
> > together.   One example of them not playing well together is each
> > wanting to use a different version of Java and neither can tolerate
> the
> > other version.
> >
> > Dave
> > Arizona.
> >
> > >>> koldark@xxxxxxxxx 2/13/2006 10:03:10 >>>
> > My vendor recommends running a seperate webserver and application
> for
> > our
> > live and test systems. If possible, I would like to at least run
> only
> > one
> > web server if not one application server as well. Is this possible?
> Or
> > is it
> > best to run seperate web servers and application servers?
> >
> > --
> > Mike Wills
> > koldark@xxxxxxxxx
> > http://mikewills.name
> > http://theriverbendpodcast.com
> >
> > "There are 10 types of people in the world: those who understand
> > binary, and
> > those who don't." -Unknown
> > --