Skip to Content

Changes for page Deployment

Last modified by Gavin Eadie on 2013/07/02 18:57
From version 21.1
edited by David Avendasora
on 2010/11/30 07:35
Change comment: There is no comment for this version
To version 22.1
edited by David Avendasora
on 2010/11/30 02:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,29 +1,9 @@
1 -=== WebObjects Deployment Types ===
1 +=== Introduction ===
2 2  
3 -There are three ways to deploy your WebObjects Application. They all have different components and configurations, but they all take a .woa bundle.
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 -===== Standard Deployment =====
5 +=== Deployment Basics ===
6 6  
7 -This is the way 95%+ of all WebObjects applications are deployed. This is the type of deployment for which there is the most documentation for, and the most support for. It consists of 3 Major pieces:
8 -
9 -* **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.
10 -
11 -* **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.
12 -
13 -* **HTTP Adapter** is a native application that forwards requests from a web server to application instances and returns responses from instances back to the server.
14 -
15 -* **WebServer (Apache, IIS)**
16 -
17 -===== Servlet Deployment (Tomcat) =====
18 -
19 -* Tomcat
20 -* HTTP Adapter or Module
21 -* WebServer (Apache, IIS)
22 -
23 -===== AJP Deployment =====
24 -
25 -* WebServer (Apache)
26 -
27 27  A deployment setup consists of 4 parts:
28 28  
29 29  * Your Application
... ... @@ -31,6 +31,10 @@
31 31  * JavaMonitor.woa (formally know as WOMonitor)
32 32  * A module for your Web server (Apache or IIS)
33 33  
14 +wotaskd.woa 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 +
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 +
34 34  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.
35 35  
36 36  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.