Skip to Content

Changes for page Deployment

Last modified by Gavin Eadie on 2013/07/02 18:57
From version 11.1
edited by David Avendasora
on 2010/11/30 01:43
Change comment: There is no comment for this version
To version 12.1
edited by David Avendasora
on 2010/11/30 01:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
2 2  
3 3  This page have child pages for information about specific deployment tasks, check the child page list at the bottom of this page.
4 4  
5 -=== Deployment Basics ===
5 +=== Deployment basics. ===
6 6  
7 7  A deployment setup consists of 4 parts:
8 8  
... ... @@ -11,15 +11,15 @@
11 11  * JavaMonitor (also know as WOMonitor)
12 12  * A module for your Web server (Apache or IIS)
13 13  
14 -wotaskd is a daemon and is also a WebObjects application. Its main task is to start up instances of your applications when the application server is restarted. wotaskd also receives lifebeats from your application instances, if wotaskd stops receiving lifebeats after a certain amount of time, it will assume that your application is dead.
14 +wotaskd is a daemon, who is also a WebObjects application, that its main task is to start up instances when hosts are restarted. wotaskd also accepts lifebeats from your application instances, if wotaskd stops receiving lifebeats after a certain amount of time, it will assume that your application is dead.
15 15  
16 -JavaMonitor is simply a Web front-end to manage your wotaskd configuration. You can use one copy of JavaMonitor to manage multiple wotaskd daemons running on different application servers.
16 +JavaMonitor is simply a Web front-end to manage your wotaskd configuration. You can use one copy of JavaMonitor to manage multiple wotaskd daemons running on different nodes.
17 17  
18 18  The job of the module for your Web server is to talk to wotaskd to find the list of available applications and act as a request proxy between the browser on the client-side and your application.
19 19  
20 -Usually, people run wotaskd, JavaMonitor, their applications and the Web server on the same server, but it's also possible to run each part on different servers if needed.
20 +Usually, people run wotaskd, JavaMonitor, their applications and the Web server on the same server, but it's also possible to run each part on different servers if needed.
21 21  
22 -=== Deployment Podcast ===
22 +==== Deployment podcast ====
23 23  
24 24  You can learn more about deployment by listening to the [[Practical Deployment>>http://www.wocommunity.org/podcasts/wowodc/east09/WOWODC09E-Deployment.mov]] session from WOWODC 2009, available from the [[podcast page>>http://www.wocommunity.org/webobjects_screencasts.html]] on wocommunity.org.
25 25