Installing new application

[Webobjects Developer]

If I have a running server, what is the suggested way of updating an
application on the server?
Here is my current technique (below). I run one instance at once and this
technique works consistently for me, but requires me to shut down the web
server.

It seems like if I skip any of the steps, webobjects keeps using some cached
version of the old application. The sequence of steps (below) works, but it
is tedious and has more downtime than I'd prefer.

Is there an easier way to do this?


Installing new webobjects application.

- Using monitor, stop my instance(s) from running.

- Using server admin, turn off monitor, save.

- Using server admin, stop webobjects.

- Using server admin, stop web.

- Now replace the application and update databases.

- Using server admin, start web.

- Using server admin, start webobjects.

- Using server admin, turn on monitor, save.

- Using monitor, start my instance(s).

[Aristedes Maniatis]

Create two instances of the same application, each one pointing to a
separate folder on disk. Then update the application which is not
running.

Post by Webobjects Developer
Installing new webobjects application.
- Using monitor, stop my instance(s) from running.

Sure, but you might like to start the new application first.

Post by Webobjects Developer
- Using server admin, turn off monitor, save.

No.

Post by Webobjects Developer
- Using server admin, stop webobjects.

Don't do that either.

Post by Webobjects Developer
- Using server admin, stop web.

No need.


In short, start your new instance. Stop the old application (by
clicking 'refuse new sessions'). That's it.

Perhaps you could sign your emails so that others know what you call
you.


Ari Maniatis



-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone [phone] fax [phone]
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A

[Owen McKerrow]

Hi THere,

Hmmm I would say that that is complete overkill. You should only need
to stop the app under Monitor, replace the app, update the database
and then start it back up again. My initial guess would be that under
Java Monitor you have your app set to auto restart. So your steps
should be something like this.....

- Using monitor, turn off scheduling for the instance(s).

- Using monitor, turn off Auto Restart for the instance(s).

- Using monitor, stop my instance(s) from running.

- Now replace the application and update databases.

And repeat in reverse to turn them all back on.

Owen McKerrow
WebMaster, emlab
Ph : [phone]
http://emlab.uow.edu.au

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - -

People who prefer typing to pointing then seem to prefer acronyms to
save typing :-)
-Denis Stanton, On people using Command Line Interfaces

Post by Webobjects Developer
If I have a running server, what is the suggested way of updating an
application on the server?
Here is my current technique (below). I run one instance at once and this
technique works consistently for me, but requires me to shut down the web
server.
It seems like if I skip any of the steps, webobjects keeps using some cached
version of the old application. The sequence of steps (below)
works, but it
is tedious and has more downtime than I'd prefer.
Is there an easier way to do this?
Installing new webobjects application.
- Using monitor, stop my instance(s) from running.
- Using server admin, turn off monitor, save.
- Using server admin, stop webobjects.
- Using server admin, stop web.
- Now replace the application and update databases.
- Using server admin, start web.
- Using server admin, start webobjects.
- Using server admin, turn on monitor, save.
- Using monitor, start my instance(s).
_______________________________________________
WebObjects-admin mailing list
http://www.omnigroup.com/mailman/listinfo/webobjects-admin

[Cheong Hee (Datasonic)]

Sometimes I found out that without restarting web server, application
instances somehow will not get the latest components from new application.
On safe site, I always restart the websever and app instance after new
application is applied.

----- Original Message -----
From: "Owen McKerrow" <***@uow.edu.au>
To: "Webobjects Developer" <***@gmail.com>
Cc: <webobjects-***@omnigroup.com>
Sent: Monday, October 15, 2007 3:00 PM
Subject: Re: Installing new application

Post by Owen McKerrow
Hi THere,
Hmmm I would say that that is complete overkill. You should only need to
stop the app under Monitor, replace the app, update the database and then
start it back up again. My initial guess would be that under Java Monitor
you have your app set to auto restart. So your steps should be something
like this.....
- Using monitor, turn off scheduling for the instance(s).
- Using monitor, turn off Auto Restart for the instance(s).
- Using monitor, stop my instance(s) from running.
- Now replace the application and update databases.
And repeat in reverse to turn them all back on.
Owen McKerrow
WebMaster, emlab
Ph : [phone]
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - -
People who prefer typing to pointing then seem to prefer acronyms to save
typing :-)
-Denis Stanton, On people using Command Line Interfaces

Post by Webobjects Developer
If I have a running server, what is the suggested way of updating an
application on the server?
Here is my current technique (below). I run one instance at once and
this
technique works consistently for me, but requires me to shut down the
web
server.
It seems like if I skip any of the steps, webobjects keeps using some
cached
version of the old application. The sequence of steps (below) works, but
it
is tedious and has more downtime than I'd prefer.
Is there an easier way to do this?
Installing new webobjects application.
- Using monitor, stop my instance(s) from running.
- Using server admin, turn off monitor, save.
- Using server admin, stop webobjects.
- Using server admin, stop web.
- Now replace the application and update databases.
- Using server admin, start web.
- Using server admin, start webobjects.
- Using server admin, turn on monitor, save.
- Using monitor, start my instance(s).
_______________________________________________
WebObjects-admin mailing list
http://www.omnigroup.com/mailman/listinfo/webobjects-admin

_______________________________________________
WebObjects-admin mailing list
http://www.omnigroup.com/mailman/listinfo/webobjects-admin