Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 119.1
edited by David Avendasora
on 2010/11/29 20:09
Change comment: There is no comment for this version
To version 123.1
edited by David Avendasora
on 2010/11/29 19:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,20 +3,16 @@
1 -[[image:WonderJavaMonitor.png||border="1"]]
2 -
3 3  {{toc}}{{/toc}}
4 4  
5 5  === Introduction ===
6 6  
7 -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.
5 +WebObject's wotaskd and JavaMonitor deployment tools were open sourced 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 since their release as open source. These improved versions of **wotaskd.woa** and **JavaMonitor.woa** are available as full Wonder applications.
8 8  
9 -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.
7 +[[image:WonderJavaMonitor.png||border="1"]]
10 10  
11 -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.
9 +=== Where to get them ===
12 12  
13 -=== Where To Get Them ===
14 -
15 15  You can either download them pre-built from [[Wonder's Hudson build server>>http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]] or build them from the source code.
16 16  
17 -To build them from the [[Wonder source code>>WONDER:Download Wonder Source, Build, Install and Upgrade]], simply run the following command from the Wonder directory at the root of the Wonder source.
13 +To build them from the [[Wonder source code>>WONDER:Download Wonder Source, Build, Install and Upgrade]], simply run the following Command from the Wonder directory at the root of the Wonder source.
18 18  
19 19  {{code}}
20 20  ant frameworks deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
... ... @@ -32,30 +32,8 @@
32 32  
33 33  {{/info}}
34 34  
35 -=== Major Improvements over Apple's versions ===
31 +=== Statistics ===
36 36  
37 -==== Automatic archive of SiteConfig.xml ====
38 -
39 -On every change you make to an application's configuration, a backup of SiteConfig.xml will be created in, by default, /Library/WebObjects/Configuration.
40 -
41 -==== Simplified/Automated Bouncing ====
42 -
43 -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 :
44 -
45 -* Find the inactive (eg : not started) instance and start it
46 -* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
47 -* Bounce the active instances when the minimum session count is reached
48 -
49 -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.
50 -
51 -{{note}}
52 -
53 -How this will work if your new version uses ERXMigrations to change your schema (e.g., The old instances might raise exceptions because the database schema changed), so try it out on a test server first and then update this page so everyone knows!
54 -
55 -{{/note}}
56 -
57 -==== Statistics ====
58 -
59 59  If you call [[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics]], the answer send you back statistics, in JSON format, about instances, per application. Sample :
60 60  
61 61  {{code}}
... ... @@ -101,7 +101,7 @@
101 101  
102 102  [[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]
103 103  
104 -==== Direct Actions to many tasks ====
78 +=== Direct Actions to many tasks ===
105 105  
106 106  You can do most of the standard tasks you do in Monitor by calling direct actions. They are in a different query handler, ///admin//. They follow the same format and use the same query parameters. Those DA can be useful if you need to restart instances or other tasks within ant or other build/deployment systems.
107 107  
... ... @@ -143,8 +143,22 @@
143 143  ///stop// : stop an application/instance the normal way.
144 144  ///start// : start an application/instance the normal way.
145 145  
146 -==== Remote Control via REST Routes ====
120 +=== Automatic archive of SiteConfig.xml ===
147 147  
122 +On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
123 +
124 +=== Bounce feature ===
125 +
126 +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 :
127 +
128 +* Find the inactive (eg : not started) instance and start it
129 +* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
130 +* Bounce the active instances when the minimum session count is reached
131 +
132 +This feature, from my understanding, allow you to upload new versions of your app, start up the new version and refuse sessions for the instances running on the older version. I don't know how this will work if your new version use migrations to change your schema (eg : old instances might raise exceptions because of database schema changes), so try it out on a test server before and put your results here.
133 +
134 +=== REST routes ===
135 +
148 148  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.
149 149  
150 150  Examples of REST calls :