Last modified by Pascal Robert on 2023/08/10 22:21

From version 83.1
edited by David Avendasora
on 2010/11/29 23:00
Change comment: There is no comment for this version
To version 85.1
edited by David Avendasora
on 2010/11/29 22:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -169,7 +169,7 @@
169 169  ##start?**type=ins&name={{color value="maroon"}}AppName{{/color}}-{{color value="maroon"}}InstanceNumber{{/color}}**##
170 170  
171 171  To get details about all instances of all applications:
172 -##http:~/~/monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all##
172 +##http:~/~/monitorhost:port9/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all##
173 173  
174 174  To get details about the **AjaxExample** application:
175 175  ##http:~/~/monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample##
... ... @@ -179,7 +179,7 @@
179 179  
180 180  ==== Remote Control via REST Routes ====
181 181  
182 -If the control offered by the Direct Actions isn't enough, there are also REST routes in JavaMonitor. Between the two methods (Direct Actions, JSON) you have almost full remote-control of JavaMonitor. Just make sure that your JavaMonitor installation is secure Just like with Direct Actions, you need to append ##?pw=XXXX## to the URLs if your JavaMonitor is password protected.
182 +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.
183 183  
184 184  Examples of REST calls :
185 185