Skip to Content

Changes for page Deployment

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

Summary

Details

Page properties
Content
... ... @@ -11,13 +11,13 @@
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, 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.
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.
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 nodes.
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.
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 22  ==== Deployment podcast ====
23 23  
... ... @@ -25,4 +25,4 @@
25 25  
26 26  === Differences between Apple's and Wonder's versions of the deployment tools ===
27 27  
28 -wotaskd and JavaMonitor were released as open source when WebObjects 5.4 was released in 2007. A copy of the source was added to Project Wonder, and [[improvements and bug fixes>>Wonder wotaskd and JavaMonitor]] were made on the tools in Project Wonder. We strongly suggest that you use the Wonder version of the tools.
28 +wotaskd and JavaMonitor were released as open source when WebObjects 5.4 was released in 2007. A copy of the source was added to Project Wonder, and [[improvements and bug fixes>>Wonder JavaMonitor and wotaskd]] were made on the tools in Project Wonder. We strongly suggest that you use the Wonder version of the tools.