Skip to Content

Changes for page Deployment

Last modified by Gavin Eadie on 2013/07/02 18:57
From version 34.1
edited by Gavin Eadie
on 2013/07/02 18:35
Change comment: There is no comment for this version
To version 38.1
edited by Gavin Eadie
on 2013/07/02 18:57
Change comment: Migrated to Confluence 5.3

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Home
Tags
... ... @@ -1,0 +1,1 @@
1 +deployment
Content
... ... @@ -1,20 +1,20 @@
1 1  === WebObjects Application Server Types / Deployment Styles ===
2 2  
3 -There are three ways to deploy your WebObjects Application. They all have different components and configurations, but they all take your Application as a .woa bundle.
3 +There are two ways to deploy your WebObjects Application, "Standard" and "Servlet". They have different components and configurations, but they all take your Application as a .woa bundle.
4 4  
5 5  ===== Standard Deployment =====
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:
7 +This is how a great majority of WebObjects applications are deployed. This is the type of deployment for which there is the most documentation and support. It requires four distinct pieces of software to be installed to support your application:
8 8  
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.
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. JavaMonitor is actually a WebObjects application in its own right.
10 10  
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.
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. The wotaskd daemon is also a WebObjects application in its own right, but with no browser interface.
12 12  
13 -* **HTTP Adapter** - This is an application that serves as the interface between your web server and your application instances. The HTTP adaptor routes requests from the web server to the appropriate application instance and sends the responses generated back to the web server. The adaptor does this while performing load balancing to distribute an application's users among its active instances. Load balancing helps to spread the user load of your site evenly across your application hosts.
13 +* **HTTP Adapter** - This is an Apache httpd module that serves as the interface between the Apache httpd web server and your application instances. The adaptor routes requests from the web server to the appropriate application instance and sends the responses generated back to the web server. The adaptor does this while performing load balancing to distribute an application's users among its active instances. Load balancing helps to spread the user load of your site evenly across your application hosts.
14 14  ** Apache Adapter: [[doc:mod_WebObjects]]
15 15  ** IIS Adapter:
16 16  
17 -* **Webserver (Apache, IIS)**
17 +* **Webserver (Apache httpd or Window IIS)**
18 18  
19 19  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 role if needed.
20 20  
... ... @@ -21,8 +21,6 @@
21 21  ===== Servlet Deployment (Tomcat) =====
22 22  
23 23  * Tomcat
24 -* HTTP Adapter or Module
25 -* WebServer (Apache, IIS)
26 26  
27 27  ===== Apache Java Protocol (AJP) Deployment (% style="color: rgb(255,0,0);" %)(NO LONGER AVAILABLE)(%%) =====
28 28  
... ... @@ -37,10 +37,10 @@
37 37  
38 38  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:
39 39  
38 +[[doc:Platforms]]
40 40  
40 +{{children sort="title"/}}
41 41  
42 -{{children sort="title" page="Platforms"/}}
43 -
44 44  === Deployment Podcast ===
45 45  
46 46  You can learn more about deployment by listening to the [[Practical Deployment>>url:http://www.wocommunity.org/podcasts/wowodc/east09/WOWODC09E-Deployment.mov||shape="rect"]] session from WOWODC 2009, available from the [[podcast page>>url:http://www.wocommunity.org/webobjects_screencasts.html||shape="rect"]] on wocommunity.org.
Deploying_Applications.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +4.6 MB
Content