Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 125.1
edited by David Avendasora
on 2010/11/29 19:45
Change comment: There is no comment for this version
To version 143.1
edited by Pascal Robert
on 2010/11/25 18:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.probert
Content
... ... @@ -1,36 +3,10 @@
1 -{{toc}}{{/toc}}
2 -
3 3  === Introduction ===
4 4  
5 -WebObject's wotaskd and JavaMonitor deployment tools were open sourced in WebObjects 5.4. The source was then quickly modified and included in Project Wonder. Substantial improvements in both functionality and look-and-feel have been made over the years since their release as open source. These improved versions of **wotaskd.woa** and **JavaMonitor.woa** are available as full Wonder applications.
3 +wotaskd and JavaMonitor were open sourced when WebObjects 5.4 was released in 2007. In 2008 and 2009, the source was modified and included in Project Wonder. This is the list of additions that were added to the Wonder versions of the tools.
6 6  
7 -[[image:WonderJavaMonitor.png||border="1"]]
8 -
9 -=== Where to get them ===
10 -
11 -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.
12 -
13 -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.
14 -
15 -{{code}}
16 -ant frameworks deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
17 -{{/code}}
18 -
19 -{{info title="What this command does:"}}
20 -
21 -* *ant*: calls Apache Ant. It is assumed that you have this already installed.
22 -* *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.
23 -* *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.
24 -* *\-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.
25 -* *\-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.
26 -
27 -
28 -
29 -{{/info}}
30 -
31 31  === Statistics ===
32 32  
33 -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 :
7 +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 :
34 34  
35 35  {{code}}
36 36  
... ... @@ -73,7 +73,7 @@
73 73  
74 74  If JavaMonitor is configured with a password, and I hope you do, pass //pw=monitorpassword// as a argument to the query :
75 75  
76 -[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]
50 +http:~/~/monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword
77 77  
78 78  === Direct Actions to many tasks ===
79 79  
... ... @@ -85,21 +85,28 @@
85 85  
86 86  For example, if you want to get details about all instances and applications, you call :
87 87  
88 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all]]
62 +http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all
89 89  
90 90  To get details about the //AjaxExample// application :
91 91  
92 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample]]
66 +http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample
93 93  
94 94  And for a specific instance :
95 95  
96 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1]]
70 +http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1
97 97  
98 98  The response for the direct actions will either send a JSON array or YES/NO. For example, the query //info// for all instances will return :
99 99  
100 100  {{code}}
101 101  
102 -[Hudson Build Server for Wonder|http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]
76 +[{"name": "AjaxExample", "id": "1", "host": "leopards.macti.lan", "port": "2001", "state": "ALIVE", "deaths": "0", "refusingNewSessions": false, "scheduled": false,
77 + "transactions": "88", "activeSessions": "0", "averageIdlePeriod": "2.078", "avgTransactionTime": "0.197"},
78 +{"name": "AjaxExample", "id": "2", "host": "leopards.macti.lan", "port": "2002", "state": "ALIVE", "deaths": "0", "refusingNewSessions": false, "scheduled": false,
79 +"transactions": "0", "activeSessions": "0", "averageIdlePeriod": "0.0", "avgTransactionTime": "0.0"},
80 +{"name": "AjaxExample2", "id": "1", "host": "leopards.macti.lan", "port": "2003", "state": "ALIVE", "deaths": "0", "refusingNewSessions": false, "scheduled": false,
81 +"transactions": "0", "activeSessions": "0", "averageIdlePeriod": "0.0", "avgTransactionTime": "0.0"},
82 +{"name": "AjaxExample2", "id": "2", "host": "leopards.macti.lan", "port": "2004", "state": "ALIVE", "deaths": "0", "refusingNewSessions": false, "scheduled": false,
83 +"transactions": "1", "activeSessions": "0", "averageIdlePeriod": "325.443", "avgTransactionTime": "0.0"}]
103 103  
104 104  {{/code}}
105 105  
... ... @@ -112,7 +112,7 @@
112 112  ///clearDeaths// : clear the number of deaths (same action as clicking the "Clear deaths" in JavaMonitor)
113 113  ///turnScheduledOn// : turn scheduling on for an application or instance. Call ///turnScheduledOff// to do the opposite.
114 114  ///turnRefuseNewSessionsOn// : turn "Refuse new sessions" on, call //turnRefuseNewSessionsOff// to do the opposite.
115 -///turnAutoRecoverOn// : guess what? It activate "Auto recover" And guess again? ///turnAutoRecoverOff// do the opposite
96 +///turnAutoRecoverOn// : guess what? It activate "Auto recover"! And guess again? ///turnAutoRecoverOff// do the opposite!
116 116  ///forceQuit// : force quit an application, might be useful to call it from a monitoring system.
117 117  ///stop// : stop an application/instance the normal way.
118 118  ///start// : start an application/instance the normal way.
... ... @@ -119,7 +119,7 @@
119 119  
120 120  === Automatic archive of SiteConfig.xml ===
121 121  
122 -On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
103 +On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
123 123  
124 124  === Bounce feature ===
125 125  
... ... @@ -133,7 +133,7 @@
133 133  
134 134  === REST routes ===
135 135  
136 -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.
117 +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.
137 137  
138 138  Examples of REST calls :
139 139  
... ... @@ -145,7 +145,7 @@
145 145  
146 146  {{/code}}
147 147  
148 -Adding a new application :
129 +Adding a new application :
149 149  
150 150  {{code}}
151 151  
... ... @@ -184,3 +184,19 @@
184 184  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
185 185  
186 186  {{/code}}
168 +
169 +=== Misc ===
170 +
171 +wotaskd and JavaMonitor are now full Wonder applications, and needs Ajax.framework, ERExtensions.framework, ERJars.framework, JavaWOExtensions.framework and JavaMonitor.framework to work correctly. If you get wotaskd.woa and JavaMonitor.woa from the //Wonder-latest-Applications-54// archive, those frameworks are NOT embedded inside wotaskd.woa and JavaMonitor.woa, so either build them from source and embed the frameworks or copy the frameworks into the //appserver// user home (on OS X 10.5, it's in ///var/empty//).
172 +
173 +If you build everything from Wonder source, you can run :
174 +
175 +{{code}}
176 +ant deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
177 +{{/code}}
178 +
179 +Please note that you have to build the Wonder before calling //ant deployment.tools//, if you get classpath errors when building the deployment tools, first run:
180 +
181 +{{code}}
182 +ant frameworks
183 +{{/code}}