Skip to Content
Version 117.1 by David Avendasora on 2010/11/29 20:02
Show last authors
1 [[image:WonderJavaMonitor.png||border="1"]]
2
3 {{toc}}{{/toc}}
4
5 === Introduction ===
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.
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.
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.
12
13 === Where To Get Them ===
14
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
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.
18
19 {{code}}
20 ant frameworks deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
21 {{/code}}
22
23 {{info title="What this command does:"}}
24
25 * *ant*: calls Apache Ant. It is assumed that you have this already installed.
26 * *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.
27 * *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.
28 * *\-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.
29 * *\-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.
30
31
32
33 {{/info}}
34
35 === Major Improvements over Apple's versions ===
36
37 ==== Statistics ====
38
39 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 :
40
41 {{code}}
42
43 (
44 {
45 "configuredInstances" = "2";
46 "maxSessions" = "0";
47 "maxAvgIdleTime" = "2.078";
48 "avgTransactions" = "44.0000";
49 "sumSessions" = "0";
50 "avgAvgTransactionTime" = "0.0985000";
51 "refusingInstances" = "0";
52 "avgSessions" = "0.0000";
53 "maxTransactions" = "88";
54 "applicationName" = "AjaxExample";
55 "avgAvgIdleTime" = "1.0390000";
56 "maxAvgTransactionTime" = "0.197";
57 "runningInstances" = "2";
58 "sumTransactions" = "88";
59 },
60 {
61 "configuredInstances" = "2";
62 "maxSessions" = "0";
63 "maxAvgIdleTime" = "325.443";
64 "avgTransactions" = "0.5000";
65 "sumSessions" = "0";
66 "avgAvgTransactionTime" = "0.00000";
67 "refusingInstances" = "0";
68 "avgSessions" = "0.0000";
69 "maxTransactions" = "1";
70 "applicationName" = "AjaxExample2";
71 "avgAvgIdleTime" = "162.7215000";
72 "maxAvgTransactionTime" = "0.0";
73 "runningInstances" = "2";
74 "sumTransactions" = "1";
75 }
76 )
77
78 {{/code}}
79
80 If JavaMonitor is configured with a password, and I hope you do, pass //pw=monitorpassword// as a argument to the query :
81
82 [[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]
83
84 ==== Direct Actions to many tasks ====
85
86 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.
87
88 //?type=all// : return details about all applications and instances
89 //?type=app&name=AppName// : return details about all instances of a specific application
90 //?type=ins&name=AppName-InstanceNo// : return details about one specific instance
91
92 For example, if you want to get details about all instances and applications, you call :
93
94 [[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all]]
95
96 To get details about the //AjaxExample// application :
97
98 [[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample]]
99
100 And for a specific instance :
101
102 [[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1]]
103
104 The response for the direct actions will either send a JSON array or YES/NO. For example, the query //info// for all instances will return :
105
106 {{code}}
107
108 [Hudson Build Server for Wonder|http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]
109
110 {{/code}}
111
112 List of available direct actions :
113
114 ///info// : return details (number of deaths, state, etc.; see above), in JSON, about an instance.
115 ///running// : return YES if the instance is running, NO if not.
116 ///stopped// : return NO if the instance is running, YES if not.
117 ///bounce//: more on it later.
118 ///clearDeaths// : clear the number of deaths (same action as clicking the "Clear deaths" in JavaMonitor)
119 ///turnScheduledOn// : turn scheduling on for an application or instance. Call ///turnScheduledOff// to do the opposite.
120 ///turnRefuseNewSessionsOn// : turn "Refuse new sessions" on, call //turnRefuseNewSessionsOff// to do the opposite.
121 ///turnAutoRecoverOn// : guess what? It activate "Auto recover" And guess again? ///turnAutoRecoverOff// do the opposite
122 ///forceQuit// : force quit an application, might be useful to call it from a monitoring system.
123 ///stop// : stop an application/instance the normal way.
124 ///start// : start an application/instance the normal way.
125
126 ==== Automatic archive of SiteConfig.xml ====
127
128 On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
129
130 ==== Simplified/Automated Bouncing ====
131
132 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 :
133
134 * Find the inactive (eg : not started) instance and start it
135 * Find the active instances (minus the one started the step below) and enable "Refuse New Session"
136 * Bounce the active instances when the minimum session count is reached
137
138 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.
139
140 ==== Remote Control via REST Routes ====
141
142 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.
143
144 Examples of REST calls :
145
146 Fetching the details of all applications :
147
148 {{code}}
149
150 curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
151
152 {{/code}}
153
154 Adding a new application :
155
156 {{code}}
157
158 curl -X POST -d "{id: 'AjaxExample',type: 'MApplication', name: 'AjaxExample',unixOutputPath: '/opt/Local/Library/WebObjects/Logs', unixPath: '/opt/Local/Library/WebObjects/Applications/AjaxExample.woa/AjaxExample'}" http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
159
160 {{/code}}
161
162 Adding a new instance :
163
164 {{code}}
165
166 curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance&host=localhost
167
168 {{/code}}
169
170 Delete an application :
171
172 {{code}}
173
174 curl -X DELETE http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample.json
175
176 {{/code}}
177
178 Delete an instance :
179
180 {{code}}
181
182 curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/deleteInstance?id=1
183
184 {{/code}}
185
186 Adding a new host :
187
188 {{code}}
189
190 curl -X POST -d "{id: 'otherserver.com',type: 'MHost', osType: 'MACOSX',address: '192.168.20.5', name: 'otherserver.com'}" http://127.0.0.1:56789/apps/WebObjects/JavaMonitor.woa/ra/mHosts.json
191
192 {{/code}}