Changes for page Wonder JavaMonitor and wotaskd
Last modified by Pascal Robert on 2023/08/10 22:21
From version 117.1
edited by David Avendasora
on 2010/11/29 20:02
on 2010/11/29 20:02
Change comment:
There is no comment for this version
To version 114.1
edited by David Avendasora
on 2010/11/29 19:56
on 2010/11/29 19:56
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -32,10 +32,8 @@ 32 32 33 33 {{/info}} 34 34 35 -=== Major Improvementsover Apple's versions ===35 +=== Statistics === 36 36 37 -==== Statistics ==== 38 - 39 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 40 41 41 {{code}} ... ... @@ -81,7 +81,7 @@ 81 81 82 82 [[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]] 83 83 84 -=== =Direct Actions to many tasks ====82 +=== Direct Actions to many tasks === 85 85 86 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 87 ... ... @@ -123,11 +123,11 @@ 123 123 ///stop// : stop an application/instance the normal way. 124 124 ///start// : start an application/instance the normal way. 125 125 126 -=== =Automatic archive of SiteConfig.xml ====124 +=== Automatic archive of SiteConfig.xml === 127 127 128 128 On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration. 129 129 130 -=== =Simplified/AutomatedBouncing====128 +=== Bounce feature === 131 131 132 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 133 ... ... @@ -137,7 +137,7 @@ 137 137 138 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 139 140 -=== =Remote Control via RESTRoutes ====138 +=== REST routes === 141 141 142 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 143