Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 180.1
edited by Marc Guenther
on 2023/08/10 01:45
Change comment: fixed the download link to Jenkins
To version 185.1
edited by David Avendasora
on 2023/11/13 11:56
Change comment: Renamed from xwiki:documentation.Wonder JavaMonitor and wotaskd

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Deployment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marc
1 +XWiki.avendasora
Tags
... ... @@ -1,0 +1,1 @@
1 +favourite|deployment
Content
... ... @@ -16,7 +16,7 @@
16 16  
17 17  You can either download them pre-built from [[Wonder's Jenkins build server>>url:http://jenkins.wocommunity.org/job/Wonder7/lastSuccessfulBuild/||shape="rect"]] or build them from the source code.
18 18  
19 -To build them from the [[Wonder source code>>doc:WEB.Getting the Wonder Source Code]], simply run the following command from the Wonder directory at the root of the Wonder source.
19 +To build them from the [[Wonder source code>>doc:WEB.Home.Getting Started.Getting the Wonder Source Code.WebHome]], simply run the following command from the Wonder directory at the root of the Wonder source.
20 20  
21 21  {{code}}
22 22  ant frameworks deployment.tools -Ddeployment.standalone=true
... ... @@ -206,6 +206,8 @@
206 206  
207 207  If the control offered by the Direct Actions isn't enough, JavaMonitor allows additional control via [[REST>>doc:ERRest Framework]] calls. Between the two methods (Direct Actions, REST) 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 {{code language="none"}}?pw=XXXX{{/code}} to the URLs if your JavaMonitor is password protected.
208 208  
209 +Be careful with these. This allows to do illegal stuff, that the UI wouldn't allow, for example, create two applications with the same name.
210 +
209 209  Examples of REST calls :
210 210  
211 211  {{code title="Adding a New Host" 0="none"}}
... ... @@ -246,7 +246,7 @@
246 246  
247 247  {{code title="Adding a New Instance" 0="none"}}
248 248  
249 -curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance&host=localhost
251 +curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance?host=localhost
250 250  
251 251  {{/code}}
252 252  
... ... @@ -274,6 +274,10 @@
274 274  
275 275  Starting on August 10th 2012, wotaskd also have REST routes. By using them, you can do most of the tasks using REST and you might not even need JavaMonitor. Just like the JavaMonitor REST and Direct Actions, you need to append {{code language="none"}}?pw=XXXX{{/code}} to the URLs if wotaskd is password protected.
276 276  
279 +Unfortunately, all changes you make in {{code language="none"}}wotaskd{{/code}} via this API will not be picked up by an already running {{code language="none"}}JavaMonitor{{/code}}, making all the modification endpoints here mostly useless.
280 +
281 +\\
282 +
277 277  {{code title="Fetching Details for All Applications" 0="none"}}
278 278  
279 279  curl -X GET http://wotaskdhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json
... ... @@ -303,7 +303,7 @@
303 303  
304 304  {{code title="Adding a New Instance" 0="none"}}
305 305  
306 -curl -X GET http://wotaskdhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance&host=localhost
312 +curl -X GET http://wotaskdhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance?host=localhost
307 307  
308 308  {{/code}}
309 309  
... ... @@ -489,4 +489,4 @@
489 489  
490 490  === Troubleshooting ===
491 491  
492 -If JavaMonitor won't start up check the [[troubleshooting deployment>>doc:Troubleshooting Deployment]] section. In particular pay attention to the [[WOTaskd Didn't Start>>doc:Troubleshooting Deployment]] Q&A.
498 +If JavaMonitor won't start up check the [[troubleshooting deployment>>doc:documentation.Home.Deployment.Troubleshooting.Troubleshooting Deployment.WebHome]] section. In particular pay attention to the [[WOTaskd Didn't Start>>doc:documentation.Home.Deployment.Troubleshooting.Troubleshooting Deployment.WebHome]] Q&A.
WonderJavaMonitor.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +32.7 KB
Content
XWiki.XWikiComments[0]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dholt
Comment
... ... @@ -1,0 +1,3 @@
1 +In Misc it says that wotaskd and JavaMonitor are not built fully embedded. Is this still true? I thought with the move to Hudson, that the Applications were fully embedded at this location: [[http:~~/~~/webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/>>url:http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/||rel="nofollow" shape="rect" class="external-link"]]
2 +
3 +Can anyone confirm this so that we remove this information if incorrect?
Date
... ... @@ -1,0 +1,1 @@
1 +2010-11-26 19:47:32.0
XWiki.XWikiComments[1]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.probert
Comment
... ... @@ -1,0 +1,3 @@
1 +The wotaskd/Monitor builds on webobjects.mdimension.com are fully embedded, but if you build them yourself, they are not fully embedded unless you use the "-Ddeployment.standalone=true" argument.
2 +
3 +And I just saw that the Wonder-latest-Applications* archive doesn't exist anymore in Hudson, but wotaskd and JavaMonitor are available as downloads and they are fully embedded.
Date
... ... @@ -1,0 +1,1 @@
1 +2010-11-26 20:40:32.0
XWiki.XWikiComments[2]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.dholt
Comment
... ... @@ -1,0 +1,1 @@
1 +I have updated that section. Thanks Pascal.
Date
... ... @@ -1,0 +1,1 @@
1 +2010-11-26 21:48:35.0
XWiki.XWikiComments[3]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.tedpet
Comment
... ... @@ -1,0 +1,3 @@
1 +On a Centos VM that I just created I tried to build both wotaskd/Monitor. There were errors until I told ant where the frameworks lived.
2 +
3 +ant -Dwo.system.frameworks=/opt/WO/Library/Frameworks frameworks deployment.tools -Ddeployment.standalone=true
Date
... ... @@ -1,0 +1,1 @@
1 +2016-07-01 08:21:16.993