Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 114.1
edited by David Avendasora
on 2010/11/29 19:56
Change comment: There is no comment for this version
To version 106.1
edited by David Avendasora
on 2010/11/29 20:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -32,12 +32,34 @@
32 32  
33 33  {{/info}}
34 34  
35 -=== Statistics ===
35 +=== Major Improvements over Apple's versions ===
36 36  
37 -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 :
37 +==== Automatic archive of SiteConfig.xml ====
38 38  
39 -{{code}}
39 +On every change you make to an application's configuration, a backup of SiteConfig.xml will be created in, by default, /Library/WebObjects/Configuration.
40 40  
41 +==== Simplified/Automated Bouncing ====
42 +
43 +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 :
44 +
45 +* Find the inactive (eg : not started) instance and start it
46 +* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
47 +* Bounce the active instances when the minimum session count is reached
48 +
49 +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.
50 +
51 +{{note title="Database Changes"}}
52 +
53 +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\!*
54 +
55 +{{/note}}
56 +
57 +==== Statistics ====
58 +
59 +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.
60 +
61 +{{code title="Statistics Example Results"}}
62 +
41 41  (
42 42   {
43 43   "configuredInstances" = "2";
... ... @@ -79,7 +79,7 @@
79 79  
80 80  [[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]
81 81  
82 -=== Direct Actions to many tasks ===
104 +==== Direct Actions to many tasks ====
83 83  
84 84  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.
85 85  
... ... @@ -121,22 +121,8 @@
121 121  ///stop// : stop an application/instance the normal way.
122 122  ///start// : start an application/instance the normal way.
123 123  
124 -=== Automatic archive of SiteConfig.xml ===
146 +==== Remote Control via REST Routes ====
125 125  
126 -On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
127 -
128 -=== Bounce feature ===
129 -
130 -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 :
131 -
132 -* Find the inactive (eg : not started) instance and start it
133 -* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
134 -* Bounce the active instances when the minimum session count is reached
135 -
136 -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.
137 -
138 -=== REST routes ===
139 -
140 140  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.
141 141  
142 142  Examples of REST calls :