Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

WebObjects Application Server Types / Deployment Styles

There are three two ways to deploy your WebObjects Application, "Standard" and "Servlet". They all have different components and configurations, but they all take your Application as a .woa bundle.

Standard Deployment

This is the way 95%+ of all how a great majority of 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 piecesrequires four distinct pieces of software to be installed to support your application:

  • 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.
  • 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.
  • HTTP Adapter - This is an application Apache httpd module that serves as the interface between your the Apache httpd 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.
  • Webserver (Apache , httpd or Window IIS)

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.

Servlet Deployment (Tomcat)
  • Tomcat
  • HTTP Adapter or Module
  • WebServer (Apache, IIS)
Apache Java Protocol (AJP) Deployment (NO LONGER AVAILABLE)