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

Summary

Details

Page properties
Content
... ... @@ -83,6 +83,8 @@
83 83  
84 84  ==== Direct Actions to many tasks ====
85 85  
86 +=== ===
87 +
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  
88 88  //?type=all// : return details about all applications and instances
... ... @@ -125,10 +125,14 @@
125 125  
126 126  ==== Automatic archive of SiteConfig.xml ====
127 127  
130 +=== ===
131 +
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 130  ==== Simplified/Automated Bouncing ====
131 131  
136 +=== ===
137 +
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  
134 134  * Find the inactive (eg : not started) instance and start it
... ... @@ -139,6 +139,8 @@
139 139  
140 140  ==== Remote Control via REST Routes ====
141 141  
148 +=== ===
149 +
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  
144 144  Examples of REST calls :