Changes for page Wonder JavaMonitor and wotaskd
Last modified by Pascal Robert on 2023/08/10 22:21
From version 138.1
edited by David Holt
on 2010/11/26 21:52
on 2010/11/26 21:52
Change comment:
There is no comment for this version
To version 144.1
edited by Pascal Robert
on 2010/11/25 18:23
on 2010/11/25 18:23
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dholt1 +XWiki.probert - Content
-
... ... @@ -2,11 +2,9 @@ 2 2 3 3 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. 4 4 5 -[[image:LaunchBarScreenSnapz001.png||border="1"]] 6 - 7 7 === Statistics === 8 8 9 -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 : 10 10 11 11 {{code}} 12 12 ... ... @@ -49,7 +49,7 @@ 49 49 50 50 If JavaMonitor is configured with a password, and I hope you do, pass //pw=monitorpassword// as a argument to the query : 51 51 52 - [[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 53 53 54 54 === Direct Actions to many tasks === 55 55 ... ... @@ -61,21 +61,28 @@ 61 61 62 62 For example, if you want to get details about all instances and applications, you call : 63 63 64 - [[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 65 65 66 66 To get details about the //AjaxExample// application : 67 67 68 - [[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 69 69 70 70 And for a specific instance : 71 71 72 - [[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 73 73 74 74 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 : 75 75 76 76 {{code}} 77 77 78 -[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"}] 79 79 80 80 {{/code}} 81 81 ... ... @@ -88,7 +88,7 @@ 88 88 ///clearDeaths// : clear the number of deaths (same action as clicking the "Clear deaths" in JavaMonitor) 89 89 ///turnScheduledOn// : turn scheduling on for an application or instance. Call ///turnScheduledOff// to do the opposite. 90 90 ///turnRefuseNewSessionsOn// : turn "Refuse new sessions" on, call //turnRefuseNewSessionsOff// to do the opposite. 91 -///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! 92 92 ///forceQuit// : force quit an application, might be useful to call it from a monitoring system. 93 93 ///stop// : stop an application/instance the normal way. 94 94 ///start// : start an application/instance the normal way. ... ... @@ -95,7 +95,7 @@ 95 95 96 96 === Automatic archive of SiteConfig.xml === 97 97 98 -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. 99 99 100 100 === Bounce feature === 101 101 ... ... @@ -109,7 +109,7 @@ 109 109 110 110 === REST routes === 111 111 112 -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. 113 113 114 114 Examples of REST calls : 115 115 ... ... @@ -121,7 +121,7 @@ 121 121 122 122 {{/code}} 123 123 124 -Adding a new application : 129 +Adding a new application : 125 125 126 126 {{code}} 127 127 ... ... @@ -163,10 +163,8 @@ 163 163 164 164 === Misc === 165 165 166 - Thecommunity'simprovedversionsof**wotaskd.woa**and**JavaMonitor.woa**arenow availableasfullWonder.Youcandownload them pre-built from the[[HudsonWonderbuildserver>>http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]].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//). 167 167 168 -Alternatively you can build them from Wonder source and embed the frameworks or copy the frameworks into the //appserver// user home (on OS X 10.5, it's in ///var/empty//). 169 - 170 170 If you build everything from Wonder source, you can run : 171 171 172 172 {{code}}