Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 171.1
edited by Pascal Robert
on 2012/04/30 20:45
Change comment: There is no comment for this version
To version 161.1
edited by simon
on 2010/12/01 07:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.probert
1 +XWiki.simon
Content
... ... @@ -12,12 +12,12 @@
12 12  
13 13  === Where To Get Them ===
14 14  
15 -You can either download them pre-built from [[Wonder's Jenkins build server>>http://jenkins.wocommunity.org/job/Wonder/lastSuccessfulBuild/]] or build them from the source code.
15 +You can either download them pre-built from [[Wonder's Hudson build server>>http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]] or build them from the source code.
16 16  
17 -To build them from the [[Wonder source code>>Getting the Wonder Source Code]], simply run the following command from the Wonder directory at the root of the Wonder source.
17 +To build them from the [[Wonder source code>>WONDER:Download Wonder Source, Build, Install and Upgrade]], simply run the following command from the Wonder directory at the root of the Wonder source.
18 18  
19 19  {{code}}
20 -ant frameworks deployment.tools -Ddeployment.standalone=true
20 +ant frameworks deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
21 21  {{/code}}
22 22  
23 23  {{info title="What this command does:"}}
... ... @@ -25,6 +25,7 @@
25 25  * *ant*: calls Apache Ant. It is assumed that you have this already installed.
26 26  * *frameworks*: tells Ant to build the "frameworks" target. This may not be needed if you already have Wonder built and installed in a location Ant can find automatically.
27 27  * *deployment.tools*: tells Ant to build the "deployment.tools" target. This is the target that builds both wotaskd.woa and JavaMonitor.woa. You absolutely need this one.
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.
28 28  * *\-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.
29 29  
30 30  {{/info}}
... ... @@ -44,14 +44,13 @@
44 44  
45 45  ==== Simplified/Automated Bouncing ====
46 46  
47 -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 instance (only one inactive instance takes part in the bounce). What it does is :
48 +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 :
48 48  
49 -* Find one inactive (i.e., not started) instance and start it
50 +* Find the inactive (i.e., not started) instance and start it
50 50  * Find the active instances (minus the one started in the previous step) and enable "Refuse New Session"
51 -* Stop the active instances that are refusing new sessions when the minimum session count is reached
52 -* Restart all but one of the instances that were just stopped and turn on "Auto-Recover"
52 +* Bounce the active instances when the minimum session count is reached
53 53  
54 -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.  This is designed to work so that you always have just **one** inactive instance that is only used while the bounce is performed.  While waiting for the existing sessions to end you will have only one instance of your app accepting new sessions; you need to determine if this is acceptable for your app or not.
54 +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.
55 55  
56 56  {{warning title="Database Changes"}}
57 57  
... ... @@ -102,18 +102,10 @@
102 102  
103 103  {{/code}}
104 104  
105 -{{info}}
105 +If JavaMonitor is configured with a password, and I hope you do, pass //pw=monitorpassword// as a argument to the query :
106 106  
107 -If JavaMonitor is configured with a password, and I hope you do, pass _pw=monitorpassword_ as a argument to the query :
107 +##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]##
108 108  
109 -{code}
110 -http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword
111 -
112 -wget http://monitorhost:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/stop?type=app&name=InstanceName&pw=yourPassword
113 -{code}
114 -
115 -{{/info}}
116 -
117 117  ==== Direct Actions for Management Tasks ====
118 118  
119 119  You can do most of the standard management tasks you'd normally do in JavaMonitor's web UI by calling standard WebObjects Direct Actions. Instead of using the ##/wa/## request handler though, these management tasks use a new ##/admin/## request handler. These Direct Actions can be very useful, especially if you need to restart instances or other do tasks from the command line, from within Ant or other build or deployment systems.
... ... @@ -194,7 +194,7 @@
194 194  
195 195  ==== Remote Control via REST Routes ====
196 196  
197 -If the control offered by the Direct Actions isn't enough, JavaMonitor allows additional control via [[REST>>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 ##?pw=XXXX## to the URLs if your JavaMonitor is password protected.
189 +If the control offered by the Direct Actions isn't enough, JavaMonitor allows additional control via [[REST>>WONDER: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 ##?pw=XXXX## to the URLs if your JavaMonitor is password protected.
198 198  
199 199  Examples of REST calls :
200 200  
... ... @@ -228,20 +228,14 @@
228 228  
229 229  {{/code}}
230 230  
231 -{{code title="Delete an Instance"}}
223 +{{code title="Delete an Instance :"}}
232 232  
233 233  curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/deleteInstance?id=1
234 234  
235 235  {{/code}}
236 236  
237 -{{code title="Configuring the Site"}}
229 +{{code title="Adding a New Instance"}}
238 238  
239 239  curl -X PUT -d "{woAdaptor:'www.mydomain.com'}" http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mSiteConfig.json
240 240  
241 241  {{/code}}
242 -
243 -Note that before configuring the site you must first add a host. If you attempt to configure the site prior to adding a host you will get an InvalidStateException.
244 -
245 -=== Troubleshooting ===
246 -
247 -If JavaMonitor won't start up check the [[troubleshooting deployment>>Troubleshooting Deployment]] section. In particular pay attention to the [[WOTaskd Didn't Start>>Troubleshooting Deployment]] Q&A.