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

Summary

Details

Page properties
Content
... ... @@ -28,17 +28,35 @@
28 28  * *\-Dwonder.patch=54*: tells Wonder to build for WebObjects version 5.4. You need this if you are building against Wonder Trunk. Some branches don't need it, but it doesn't hurt either.
29 29  * *\-Ddeployment.standalone=true*: argument will embed the required Wonder and WebObjects frameworks in built applications. You need this to ensure that the required frameworks are embedded in the built applications.
30 30  
31 -
32 -
33 33  {{/info}}
34 34  
35 35  === Major Improvements over Apple's versions ===
36 36  
35 +==== Automatic archive of SiteConfig.xml ====
36 +
37 +On every change you make to an application's configuration, a backup of SiteConfig.xml will be created in, by default, /Library/WebObjects/Configuration.
38 +
39 +==== Simplified/Automated Bouncing ====
40 +
41 +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 :
42 +
43 +* Find the inactive (eg : not started) instance and start it
44 +* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
45 +* Bounce the active instances when the minimum session count is reached
46 +
47 +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.
48 +
49 +{{warning title="Database Changes"}}
50 +
51 +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\!*
52 +
53 +{{/warning}}
54 +
37 37  ==== Statistics ====
38 38  
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 :
57 +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.
40 40  
41 -{{code}}
59 +{{code title="Statistics Example Results"}}
42 42  
43 43  (
44 44   {
... ... @@ -79,12 +79,10 @@
79 79  
80 80  If JavaMonitor is configured with a password, and I hope you do, pass //pw=monitorpassword// as a argument to the query :
81 81  
82 -[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]
100 +##http:~/~/monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword##
83 83  
84 84  ==== Direct Actions to many tasks ====
85 85  
86 -=== ===
87 -
88 88  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.
89 89  
90 90  //?type=all// : return details about all applications and instances
... ... @@ -125,76 +125,44 @@
125 125  ///stop// : stop an application/instance the normal way.
126 126  ///start// : start an application/instance the normal way.
127 127  
128 -==== Automatic archive of SiteConfig.xml ====
129 -
130 -=== ===
131 -
132 -On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
133 -
134 -==== Simplified/Automated Bouncing ====
135 -
136 -=== ===
137 -
138 -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 :
139 -
140 -* Find the inactive (eg : not started) instance and start it
141 -* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
142 -* Bounce the active instances when the minimum session count is reached
143 -
144 -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.
145 -
146 146  ==== Remote Control via REST Routes ====
147 147  
148 -=== ===
149 -
150 150  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.
151 151  
152 152  Examples of REST calls :
153 153  
154 -Fetching the details of all applications :
150 +{{code title="Adding a New Host"}}
155 155  
156 -{{code}}
152 +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
157 157  
158 -curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
159 -
160 160  {{/code}}
161 161  
162 -Adding a new application :
156 +{{code title="Fetching Details for All Applications"}}
163 163  
164 -{{code}}
158 +curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
165 165  
166 -curl -X POST -d "{id: 'AjaxExample',type: 'MApplication', name: 'AjaxExample',unixOutputPath: '/opt/Local/Library/WebObjects/Logs', unixPath: '/opt/Local/Library/WebObjects/Applications/AjaxExample.woa/AjaxExample'}" http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
167 -
168 168  {{/code}}
169 169  
170 -Adding a new instance :
162 +{{code title="Adding a New Application"}}
171 171  
172 -{{code}}
164 +curl -X POST -d "{id: 'AjaxExample',type: 'MApplication', name: 'AjaxExample',unixOutputPath: '/opt/Local/Library/WebObjects/Logs', unixPath: '/opt/Local/Library/WebObjects/Applications/AjaxExample.woa/AjaxExample'}" http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
173 173  
174 -curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance&host=localhost
175 -
176 176  {{/code}}
177 177  
178 -Delete an application :
168 +{{code title="Delete an Application"}}
179 179  
180 -{{code}}
181 -
182 182  curl -X DELETE http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample.json
183 183  
184 184  {{/code}}
185 185  
186 -Delete an instance :
174 +{{code title="Adding a New Instance"}}
187 187  
188 -{{code}}
176 +curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance&host=localhost
189 189  
190 -curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/deleteInstance?id=1
191 -
192 192  {{/code}}
193 193  
194 -Adding a new host :
180 +{{code title="Delete an Instance :"}}
195 195  
196 -{{code}}
182 +curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/deleteInstance?id=1
197 197  
198 -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
199 -
200 200  {{/code}}