Skip to Content

Deployment

Version 14.1 by Pascal Robert on 2010/11/20 02:31

Introduction

This page have child pages for information about specific deployment tasks, check the child page list at the bottom of this page.

Deployment basics.

A deployment setup consists of 4 parts:

  • Your application
  • wotaskd
  • JavaMonitor (also know as WOMonitor)
  • A module for your Web server (Apache or IIS)

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.

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.

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.

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.

Deployment podcast

You can learn more about deployment by listening to the Practical Deployment session from WOWODC 2009, available from the podcast page on wocommunity.org.

Differences between Apple's and Wonder's versions of the deployment tools

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 were made on the tools in Project Wonder. We strongly suggest that you use the Wonder version of the tools.