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 23.1
edited by David Avendasora
on 2010/11/30 07:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -=== WebObjects Deployment Types ===
1 +=== WebObjects Application Server Types / Deployment Styles ===
2 2  
3 3  There are three ways to deploy your WebObjects Application. They all have different components and configurations, but they all take a .woa bundle.
4 4  
... ... @@ -6,14 +6,16 @@
6 6  
7 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 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.
9 +* **JavaMonitor** - 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 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.
11 +* **wotaskd** - a daemon whose main task is to start up instances of your applications when the application server (host) 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 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.
13 +* **HTTP Adapter** - a native application that forwards requests from the web server to your application's instance(s) and returns responses from the instance(s) back to the Webserver.
14 14  
15 -* **WebServer (Apache, IIS)**
15 +* **Webserver (Apache, IIS)**
16 16  
17 +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, or to have multiple servers filling each roll if needed.
18 +
17 17  ===== Servlet Deployment (Tomcat) =====
18 18  
19 19  * Tomcat
... ... @@ -20,20 +20,18 @@
20 20  * HTTP Adapter or Module
21 21  * WebServer (Apache, IIS)
22 22  
23 -===== AJP Deployment =====
25 +===== Apache Java Protocol (AJP) Deployment =====
24 24  
25 -* WebServer (Apache)
27 +Andrew Lindesay has written an open-source [[AJP>>http://en.wikipedia.org/wiki/Apache_JServ_Protocol]] adaptor for WebObjects 5 which should allow you to deploy your WebObjects application without servlets or the 'wotaskd' infrastructure. Such a deployment is most easily achieved with versions of the Apache HTTP server 2.2 or better as they have built-in support for load-balancing and AJP request-forwarding.
26 26  
27 -A deployment setup consists of 4 parts:
29 +This adaptor is distributed under the [[LEWOStuff>>LEWOStuff-Overview]] open-source framework. It is however stand-alone and has no direct dependency on other libraries or frameworks other than obviously WO 5. For more details on this, see the relevant section of the PDF overview supplied with the LEWOStuff framework.
28 28  
29 -* Your Application
30 -* wotaskd.woa
31 -* JavaMonitor.woa (formally know as WOMonitor)
32 -* A module for your Web server (Apache or IIS)
31 +* AJP Adaptor
32 +* WebServer (Apache)
33 33  
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.
34 +All three of these Application Servers / Deployment Styles can run on any platform that supports Java 1.5 or later. The ones that there is documentation for are:
35 35  
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.
36 +{{children page="Platforms" sort="title"}}{{/children}}
37 37  
38 38  === Deployment Podcast ===
39 39