Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 134.1
edited by David Avendasora
on 2010/11/29 17:57
Change comment: There is no comment for this version
To version 143.1
edited by Pascal Robert
on 2010/11/25 18:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.probert
Content
... ... @@ -1,30 +3,10 @@
1 -{{toc}}{{/toc}}
2 -
3 3  === Introduction ===
4 4  
5 5  wotaskd and JavaMonitor were open sourced when WebObjects 5.4 was released in 2007. In 2008 and 2009, the source was modified and included in Project Wonder. This is the list of additions that were added to the Wonder versions of the tools.
6 6  
7 -[[image:WonderJavaMonitor.png||border="1"]]
8 -
9 -=== Misc ===
10 -
11 -The community's improved versions of **wotaskd.woa** and **JavaMonitor.woa** are now available as full Wonder applications. You can download them pre-built from the [[Hudson Wonder build server>>http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]].
12 -
13 -If you build everything from Wonder source, you can run :
14 -
15 -{{code}}
16 -ant deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
17 -{{/code}}
18 -
19 -The //Ddeployment.standalone=true// argument will embed the required frameworks in wotaskd and JavaMonitor. Please note that you have to build the Wonder frameworks before calling //ant deployment.tools//, if you get classpath errors when building the deployment tools, first run:
20 -
21 -{{code}}
22 -ant frameworks
23 -{{/code}}
24 -
25 25  === Statistics ===
26 26  
27 -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 :
7 +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 :
28 28  
29 29  {{code}}
30 30  
... ... @@ -67,7 +67,7 @@
67 67  
68 68  If JavaMonitor is configured with a password, and I hope you do, pass //pw=monitorpassword// as a argument to the query :
69 69  
70 -[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]
50 +http:~/~/monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword
71 71  
72 72  === Direct Actions to many tasks ===
73 73  
... ... @@ -79,21 +79,28 @@
79 79  
80 80  For example, if you want to get details about all instances and applications, you call :
81 81  
82 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all]]
62 +http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all
83 83  
84 84  To get details about the //AjaxExample// application :
85 85  
86 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample]]
66 +http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample
87 87  
88 88  And for a specific instance :
89 89  
90 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1]]
70 +http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1
91 91  
92 92  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 :
93 93  
94 94  {{code}}
95 95  
96 -[Hudson Build Server for Wonder|http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]
76 +[{"name": "AjaxExample", "id": "1", "host": "leopards.macti.lan", "port": "2001", "state": "ALIVE", "deaths": "0", "refusingNewSessions": false, "scheduled": false,
77 + "transactions": "88", "activeSessions": "0", "averageIdlePeriod": "2.078", "avgTransactionTime": "0.197"},
78 +{"name": "AjaxExample", "id": "2", "host": "leopards.macti.lan", "port": "2002", "state": "ALIVE", "deaths": "0", "refusingNewSessions": false, "scheduled": false,
79 +"transactions": "0", "activeSessions": "0", "averageIdlePeriod": "0.0", "avgTransactionTime": "0.0"},
80 +{"name": "AjaxExample2", "id": "1", "host": "leopards.macti.lan", "port": "2003", "state": "ALIVE", "deaths": "0", "refusingNewSessions": false, "scheduled": false,
81 +"transactions": "0", "activeSessions": "0", "averageIdlePeriod": "0.0", "avgTransactionTime": "0.0"},
82 +{"name": "AjaxExample2", "id": "2", "host": "leopards.macti.lan", "port": "2004", "state": "ALIVE", "deaths": "0", "refusingNewSessions": false, "scheduled": false,
83 +"transactions": "1", "activeSessions": "0", "averageIdlePeriod": "325.443", "avgTransactionTime": "0.0"}]
97 97  
98 98  {{/code}}
99 99  
... ... @@ -106,7 +106,7 @@
106 106  ///clearDeaths// : clear the number of deaths (same action as clicking the "Clear deaths" in JavaMonitor)
107 107  ///turnScheduledOn// : turn scheduling on for an application or instance. Call ///turnScheduledOff// to do the opposite.
108 108  ///turnRefuseNewSessionsOn// : turn "Refuse new sessions" on, call //turnRefuseNewSessionsOff// to do the opposite.
109 -///turnAutoRecoverOn// : guess what? It activate "Auto recover" And guess again? ///turnAutoRecoverOff// do the opposite
96 +///turnAutoRecoverOn// : guess what? It activate "Auto recover"! And guess again? ///turnAutoRecoverOff// do the opposite!
110 110  ///forceQuit// : force quit an application, might be useful to call it from a monitoring system.
111 111  ///stop// : stop an application/instance the normal way.
112 112  ///start// : start an application/instance the normal way.
... ... @@ -113,7 +113,7 @@
113 113  
114 114  === Automatic archive of SiteConfig.xml ===
115 115  
116 -On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
103 +On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
117 117  
118 118  === Bounce feature ===
119 119  
... ... @@ -127,7 +127,7 @@
127 127  
128 128  === REST routes ===
129 129  
130 -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.
117 +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.
131 131  
132 132  Examples of REST calls :
133 133  
... ... @@ -139,7 +139,7 @@
139 139  
140 140  {{/code}}
141 141  
142 -Adding a new application :
129 +Adding a new application :
143 143  
144 144  {{code}}
145 145  
... ... @@ -178,3 +178,19 @@
178 178  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
179 179  
180 180  {{/code}}
168 +
169 +=== Misc ===
170 +
171 +wotaskd and JavaMonitor are now full Wonder applications, and needs Ajax.framework, ERExtensions.framework, ERJars.framework, JavaWOExtensions.framework and JavaMonitor.framework to work correctly. If you get wotaskd.woa and JavaMonitor.woa from the //Wonder-latest-Applications-54// archive, those frameworks are NOT embedded inside wotaskd.woa and JavaMonitor.woa, so either build them from source and embed the frameworks or copy the frameworks into the //appserver// user home (on OS X 10.5, it's in ///var/empty//).
172 +
173 +If you build everything from Wonder source, you can run :
174 +
175 +{{code}}
176 +ant deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
177 +{{/code}}
178 +
179 +Please note that you have to build the Wonder before calling //ant deployment.tools//, if you get classpath errors when building the deployment tools, first run:
180 +
181 +{{code}}
182 +ant frameworks
183 +{{/code}}