Last modified by Pascal Robert on 2023/08/10 22:21

From version 136.1
edited by David Avendasora
on 2010/11/29 19:35
Change comment: There is no comment for this version
To version 149.1
edited by simon
on 2010/12/01 07:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Project Wonder additions to wotaskd and JavaMonitor
1 +Wonder JavaMonitor and wotaskd
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.simon
Content
... ... @@ -1,16 +1,20 @@
1 +[[image:WonderJavaMonitor.png||border="1"]]
2 +
1 1  {{toc}}{{/toc}}
2 2  
3 3  === Introduction ===
4 4  
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.
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.
6 6  
7 -[[image:WonderJavaMonitor.png||border="1"]]
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.
8 8  
9 -=== Where to get them ===
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.
10 10  
13 +=== Where To Get Them ===
14 +
11 11  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.
12 12  
13 -To build them from the source, simply run the following Command from the Wonder directory at the root of the Wonder source code directory:
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.
14 14  
15 15  {{code}}
16 16  ant frameworks deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
... ... @@ -18,21 +18,49 @@
18 18  
19 19  {{info title="What this command does:"}}
20 20  
21 -* *ant*: calls Ant
22 -* *frameworks*: tells Ant to build the "frameworks" target
23 -* *deployment.tools* tells Ant to build the "deployment.tools" target
24 -* *\-Ddeployment.standalone=true*: argument will embed the required Wonder and WebObjects frameworks in the wotaskd.woa
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.
25 25  
31 +{{/info}}
26 26  
33 +=== Bug Fixes to Apple's Versions ===
27 27  
28 -{{/info}}
35 +==== JavaMonitor ====
29 29  
30 -=== Statistics ===
37 +* Fixes an issue with the Application Delete page
38 +* Selection in Application Detail page is now Ajax and is maintained
31 31  
32 -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 +=== Improvements to Apple's versions ===
33 33  
34 -{{code}}
42 +==== Automatic archive of SiteConfig.xml ====
35 35  
44 +On every change you make to an application's configuration, a backup of SiteConfig.xml will be created in, by default, /Library/WebObjects/Configuration.
45 +
46 +==== Simplified/Automated Bouncing ====
47 +
48 +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 :
49 +
50 +* Find the inactive (i.e., not started) instance and start it
51 +* Find the active instances (minus the one started in the previous step) and enable "Refuse New Session"
52 +* Bounce the active instances when the minimum session count is reached
53 +
54 +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.
55 +
56 +{{warning title="Database Changes"}}
57 +
58 +It is uncertain what will happen if the new version of your application makes changes to your database schema (e.g., uses [ERXMigrations|WO:Project WONDER-Frameworks-ERXMigration]). 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\!*
59 +
60 +{{/warning}}
61 +
62 +==== Statistics ====
63 +
64 +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.
65 +
66 +{{code title="Statistics Example Results"}}
67 +
36 36  (
37 37   {
38 38   "configuredInstances" = "2";
... ... @@ -72,114 +72,136 @@
72 72  
73 73  If JavaMonitor is configured with a password, and I hope you do, pass //pw=monitorpassword// as a argument to the query :
74 74  
75 -[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]
107 +##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]##
76 76  
77 -=== Direct Actions to many tasks ===
109 +==== Direct Actions for Management Tasks ====
78 78  
79 -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.
111 +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.
80 80  
81 -//?type=all// : return details about all applications and instances
82 -//?type=app&name=AppName// : return details about all instances of a specific application
83 -//?type=ins&name=AppName-InstanceNo// : return details about one specific instance
113 +List of available direct actions :
84 84  
85 -For example, if you want to get details about all instances and applications, you call :
115 +* {{{*}info{*}}} : Returns details (number of deaths, state, etc.), in JavaScript Object Notation (JSON) as specified
116 +##info?##{{{}{*}type=all{*}}}
117 +##info?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
118 +##info?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
86 86  
87 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all]]
120 +* {{{*}running{*}}} : Returns {{{*}YES{*}}} if **all** of the specified are running, ##NO## if not
121 +##running?##{{{}{*}type=all{*}}}
122 +##running?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
123 +##running?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
88 88  
89 -To get details about the //AjaxExample// application :
125 +* {{{*}stopped{*}}} : Returns {{{*}YES{*}}} if **all** the specified is running, {{{*}NO{*}}} if not.
126 +##stopped?##{{{}{*}type=all{*}}}
127 +##stopped?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
128 +##stopped?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
90 90  
91 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample]]
130 +* {{{*}bounce{*}}} : Returns {{{*}OK{*}}} after Bouncing (see description above) as specified
131 +##bounce?##{{{}{*}type=all{*}}}
132 +##bounce?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
92 92  
93 -And for a specific instance :
134 +* {{{*}clearDeaths{*}}} : Returns {{{*}OK{*}}} after clearing deaths as specified
135 +##clearDeaths?##{{{}{*}type=all{*}}}
136 +##clearDeaths?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
94 94  
95 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1]]
138 +* {{{*}turnScheduledOn{*}}} : Returns {{{*}OK{*}}} after turning on scheduling as specified. Call ///turnScheduledOff// to do the opposite.
139 +##turnScheduledOn?##{{{}{*}type=all{*}}}
140 +##turnScheduledOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
141 +##turnScheduledOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
96 96  
97 -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 :
143 +* {{{*}turnRefuseNewSessionsOn{*}}} : Returns {{{*}OK{*}}} after turning on "Refuse new sessions" as specified
144 +##turnRefuseNewSessionsOn?##{{{}{*}type=all{*}}}
145 +##turnRefuseNewSessionsOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
146 +##turnRefuseNewSessionsOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
98 98  
99 -{{code}}
148 +* {{{*}turnRefuseNewSessionsOff{*}}} : Returns {{{*}OK{*}}} after turning off "Refuse new sessions" as specified
149 +##turnRefuseNewSessionsOn?##{{{}{*}type=all{*}}}
150 +##turnRefuseNewSessionsOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
151 +##turnRefuseNewSessionsOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
100 100  
101 -[Hudson Build Server for Wonder|http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]
153 +* {{{*}turnAutoRecoverOn{*}}} : Returns {{{*}OK{*}}} after turning on "Auto Recover" as specified
154 +##turnAutoRecoverOn?##{{{}{*}type=all{*}}}
155 +##turnAutoRecoverOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
156 +##turnAutoRecoverOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
102 102  
103 -{{/code}}
158 +* {{{*}turnAutoRecoverOff{*}}} : Returns {{{*}OK{*}}} after turning off "Auto Recover" as specified
159 +##turnAutoRecoverOn?##{{{}{*}type=all{*}}}
160 +##turnAutoRecoverOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
161 +##turnAutoRecoverOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
104 104  
105 -List of available direct actions :
163 +* {{{*}forceQuit{*}}} : Returns {{{*}OK{*}}} after force quitting as specified. This could be useful to call from a monitoring system.
164 +##forceQuit?##{{{}{*}type=all{*}}}
165 +##forceQuit?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
166 +##forceQuit?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
106 106  
107 -///info// : return details (number of deaths, state, etc.; see above), in JSON, about an instance.
108 -///running// : return YES if the instance is running, NO if not.
109 -///stopped// : return NO if the instance is running, YES if not.
110 -///bounce//: more on it later.
111 -///clearDeaths// : clear the number of deaths (same action as clicking the "Clear deaths" in JavaMonitor)
112 -///turnScheduledOn// : turn scheduling on for an application or instance. Call ///turnScheduledOff// to do the opposite.
113 -///turnRefuseNewSessionsOn// : turn "Refuse new sessions" on, call //turnRefuseNewSessionsOff// to do the opposite.
114 -///turnAutoRecoverOn// : guess what? It activate "Auto recover" And guess again? ///turnAutoRecoverOff// do the opposite
115 -///forceQuit// : force quit an application, might be useful to call it from a monitoring system.
116 -///stop// : stop an application/instance the normal way.
117 -///start// : start an application/instance the normal way.
168 +* {{{*}stop{*}}} : Returns {{{*}OK{*}}} after calling "Stop" as specified
169 +##stop?##{{{}{*}type=all{*}}}
170 +##stop?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
171 +##stop?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
118 118  
119 -=== Automatic archive of SiteConfig.xml ===
173 +* {{{*}start{*}}} : Returns {{{*}OK{*}}} after calling "Start" as specified
174 +##start?##{{{}{*}type=all{*}}}
175 +##start?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}
176 +##start?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}}
120 120  
121 -On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
178 +To get details about all instances of all applications:
179 +##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all]]##
122 122  
123 -=== Bounce feature ===
181 +To get details about the **AjaxExample** application:
182 +##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample]]##
124 124  
125 -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 :
184 +To get details about instance **1** of the **AjaxExample** application:
185 +##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1]]##
126 126  
127 -* Find the inactive (eg : not started) instance and start it
128 -* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
129 -* Bounce the active instances when the minimum session count is reached
187 +==== Remote Control via REST Routes ====
130 130  
131 -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.
189 +If the control offered by the Direct Actions isn't enough, JavaMonitor allows additional control via [[REST>>WONDER:ERRest Framework]] calls. Between the two methods (Direct Actions, REST) you have almost full remote-control of JavaMonitor. Just make sure that your JavaMonitor installation is secure Just like with Direct Actions, you need to append ##?pw=XXXX## to the URLs if your JavaMonitor is password protected.
132 132  
133 -=== REST routes ===
191 +Examples of REST calls :
134 134  
135 -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.
193 +{{code title="Adding a New Host"}}
136 136  
137 -Examples of REST calls :
195 +curl -X POST -d "{id: 'otherserver.com',type: 'MHost', osType: 'MACOSX',address: '192.168.20.5', name: 'otherserver.com'}" http://monitorhost:port/apps/WebObjects/JavaMonitor.woa/ra/mHosts.json
138 138  
139 -Fetching the details of all applications :
197 +{{/code}}
140 140  
141 -{{code}}
199 +{{code title="Fetching Details for All Applications"}}
142 142  
143 -curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
201 +curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
144 144  
145 145  {{/code}}
146 146  
147 -Adding a new application :
205 +{{code title="Adding a New Application"}}
148 148  
149 -{{code}}
207 +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://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
150 150  
151 -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
152 -
153 153  {{/code}}
154 154  
155 -Adding a new instance :
211 +{{code title="Delete an Application"}}
156 156  
157 -{{code}}
213 +curl -X DELETE http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample.json
158 158  
159 -curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance&host=localhost
160 -
161 161  {{/code}}
162 162  
163 -Delete an application :
217 +{{code title="Adding a New Instance"}}
164 164  
165 -{{code}}
219 +curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance&host=localhost
166 166  
167 -curl -X DELETE http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample.json
168 -
169 169  {{/code}}
170 170  
171 -Delete an instance :
223 +{{code title="Delete an Instance"}}
172 172  
173 -{{code}}
225 +curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/deleteInstance?id=1
174 174  
175 -curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/deleteInstance?id=1
176 -
177 177  {{/code}}
178 178  
179 -Adding a new host :
229 +{{code title="Configuring the Site"}}
180 180  
181 -{{code}}
231 +curl -X PUT -d "{woAdaptor:'www.mydomain.com'}" http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mSiteConfig.json
182 182  
183 -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
184 -
185 185  {{/code}}
234 +
235 +Note that before configuring the site you must first add a host. If you attempt to configure the site prior to adding a host you will get an InvalidStateException.
236 +
237 +=== Troubleshooting ===
238 +
239 +If JavaMonitor did not start on your fresh install of WebObjects, check out the [[WOTaskd Didn't Start>>WO:Troubleshooting Deployment]] question in the troubleshooting section.