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

Summary

Details

Page properties
Content
... ... @@ -34,26 +34,6 @@
34 34  
35 35  === Major Improvements over Apple's versions ===
36 36  
37 -==== Automatic archive of SiteConfig.xml ====
38 -
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 -
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}}
52 -
53 -How this will work if your new version uses ERXMigrations to change your schema (e.g., The old instances might raise exceptions because the database schema changed), so try it out on a test server first and then update this page so everyone knows!
54 -
55 -{{/note}}
56 -
57 57  ==== Statistics ====
58 58  
59 59  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 :
... ... @@ -143,6 +143,20 @@
143 143  ///stop// : stop an application/instance the normal way.
144 144  ///start// : start an application/instance the normal way.
145 145  
126 +==== Automatic archive of SiteConfig.xml ====
127 +
128 +On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
129 +
130 +==== Simplified/Automated Bouncing ====
131 +
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 +
134 +* Find the inactive (eg : not started) instance and start it
135 +* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
136 +* Bounce the active instances when the minimum session count is reached
137 +
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 +
146 146  ==== Remote Control via REST Routes ====
147 147  
148 148  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.