JavaMonitor is a web-based tool used to configure and maintain deployed WebObjects applications. It is capable of handling multiple WebObjects applications, multiple instances of each application, and multiple WebObjects Applications Servers. In most cases you'll have one instance of JavaMonitor controlling all instances of your applications, even if they are spread across multiple Application Servers.
wotaskd (WebObjects task daemon) is the WebObjects Deployment tool that manages the instances on an Application Server. It's used by Monitor to propagate site configuration changes throughout the site's application hosts.
Apple released the original wotaskd and JavaMonitor to the community as open source in WebObjects 5.4. The source was then quickly modified and included in Project Wonder. Substantial improvements in both functionality and look-and-feel have been made over the years. These improved versions of wotaskd.woa and JavaMonitor.woa are available as standard Wonder applications.
You can either download them pre-built from Wonder's Hudson build server or build them from the source code.
To build them from the [Wonder source code], simply run the following command from the Wonder directory at the root of the Wonder source.
What this command does:
- ant: calls Apache Ant. It is assumed that you have this already installed.
- frameworks: tells Ant to build the "frameworks" target. This may not be needed if you already have Wonder built and installed in a location Ant can find automatically.
- deployment.tools: tells Ant to build the "deployment.tools" target. This is the target that builds both wotaskd.woa and JavaMonitor.woa. You absolutely need this one.
- -Dwonder.patch=54: tells Wonder to build for WebObjects version 5.4. You need this if you are building against Wonder Trunk. Some branches don't need it, but it doesn't hurt either.
- -Ddeployment.standalone=true: argument will embed the required Wonder and WebObjects frameworks in built applications. You need this to ensure that the required frameworks are embedded in the built applications.
On every change you make to an application's configuration, a backup of SiteConfig.xml will be created in, by default, /Library/WebObjects/Configuration.
In the "list instances" page, you get a "Bounce" action link. This action only work if you have at least one active instance and one inactive. What it does is :
- Find the inactive (i.e., not started) instance and start it
- Find the active instances (minus the one started in the previous step) and enable "Refuse New Session"
- Bounce the active instances when the minimum session count is reached
This feature, from Pascal's understanding, allows you to upload new versions of your application, start up the new version and refuse sessions for the instances running on the older version.
It is uncertain what will happen if the new version of your application makes changes to your database schema (e.g., uses [ERXMigrations]). The old instances may raise exceptions before they can gracefully shut down because the schema no longer matches what the old application's EOF expects. Try it out on a test server first and then update this page so everyone knows!
If you call
http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics, JavaMonitor will send you back statistics, in JSON format, about instances, per application.
If JavaMonitor is configured with a password, and I hope you do, pass pw=monitorpassword as a argument to the query :
You can do most of the standard management tasks you'd normally do in JavaMonitor's web UI by calling standard WebObjects Direct Actions. Instead of using the
/wa/ request handler though, these management tasks use a new
/admin/ request handler. These Direct Actions can be very useful, especially if you need to restart instances or other do tasks from the command line, from within Ant or other build or deployment systems.
List of available direct actions :
YESif all of the specified are running,
YESif all the specified is running,
OKafter Bouncing (see description above) as specified
OKafter clearing deaths as specified
OKafter turning on scheduling as specified. Call /turnScheduledOff to do the opposite.
OKafter turning on "Refuse new sessions" as specified
OKafter turning off "Refuse new sessions" as specified
OKafter turning on "Auto Recover" as specified
OKafter turning off "Auto Recover" as specified
OKafter force quitting as specified. This could be useful to call from a monitoring system.
OKafter calling "Stop" as specified
OKafter calling "Start" as specified
To get details about all instances of all applications:
To get details about the AjaxExample application:
To get details about instance 1 of the AjaxExample application:
On September 28th 2010, REST routes were added in JavaMonitor. Those routes + the direct actions explained in this document allow you to control almost everything remotely (make sure that your JavaMonitor installation is secure!). As the direct actions, append
?pw=XXXX to the URLs if JavaMonitor is password protected.
Examples of REST calls :