Wiki source code of Deployment
Version 15.1 by Pascal Robert on 2010/11/20 02:24
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | === Introduction === | ||
2 | |||
3 | This page have child pages for information about specific deployment tasks, check the child page list at the bottom of this page. | ||
4 | |||
5 | === Deployment basics. === | ||
6 | |||
7 | A deployment setup consists of 4 parts: | ||
8 | |||
9 | * Your application | ||
10 | * wotaskd | ||
11 | * JavaMonitor (also know as WOMonitor) | ||
12 | * A module for your Web server (Apache or IIS) | ||
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. | ||
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. | ||
17 | |||
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 | |||
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 | |||
22 | === Differences between Apple's and Wonder's versions of the deployment tools === | ||
23 | |||
24 | 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>>WO:Project Wonder additions to wotaskd and JavaMonitor]] were made on the tools in Project Wonder. We strongly suggest that you use the Wonder version of the tools. |