Changes for page Wonder JavaMonitor and wotaskd
Last modified by Pascal Robert on 2023/08/10 22:21
From version 134.1
edited by David Avendasora
on 2010/11/29 17:57
on 2010/11/29 17:57
Change comment:
There is no comment for this version
To version 149.1
edited by simon
on 2010/12/01 07:55
on 2010/12/01 07:55
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - ProjectWonder additionsto wotaskdand JavaMonitor1 +Wonder JavaMonitor and wotaskd - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. avendasora1 +XWiki.simon - Content
-
... ... @@ -1,33 +1,70 @@ 1 +[[image:WonderJavaMonitor.png||border="1"]] 2 + 1 1 {{toc}}{{/toc}} 2 2 3 3 === Introduction === 4 4 5 - wotaskd andJavaMonitor were opensourcedwhen WebObjects5.4 was releasedin2007. In2008and2009,the sourcewasmodifiedand includedin ProjectWonder.This isthelist of additions that were addedto theWonderions of the tools.7 +JavaMonitor is a web-based tool used to configure and maintain deployed WebObjects applications. It is capable of handling multiple WebObjects applications, multiple instances of each application, and multiple WebObjects Applications Servers. In most cases you'll have one instance of JavaMonitor controlling all instances of your applications, even if they are spread across multiple Application Servers. 6 6 7 - [[image:WonderJavaMonitor.png||border="1"]]9 +wotaskd (WebObjects task daemon) is the WebObjects Deployment tool that manages the instances on an Application Server. It's used by Monitor to propagate site configuration changes throughout the site's application hosts. 8 8 9 - ===Misc===11 +Apple released the original wotaskd and JavaMonitor to the community as open source 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. These improved versions of **wotaskd.woa** and **JavaMonitor.woa** are available as standard Wonder applications. 10 10 11 - Thecommunity's improved versions of **wotaskd.woa** and **JavaMonitor.woa** are now available as fullWonder applications. You can download them pre-builtfromthe[[Hudson Wonder build server>>http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]].13 +=== Where To Get Them === 12 12 13 - If youbuildeverythingfrom Wonder source, youn: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. 14 14 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 + 15 15 {{code}} 16 -ant deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true 20 +ant frameworks deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true 17 17 {{/code}} 18 18 19 - The //Ddeployment.standalone=true// argument will embed the requiredframeworksin wotaskd and JavaMonitor. Please note thatyou haveto build the Wonder frameworksbeforecalling //ant deployment.tools//, if you get classpath errors whenbuildingthedeployment tools, first run:23 +{{info title="What this command does:"}} 20 20 21 -{{code}} 22 -ant frameworks 23 -{{/code}} 25 +* *ant*: calls Apache Ant. It is assumed that you have this already installed. 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 +* *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. 29 +* *\-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. 24 24 25 - === Statistics ===31 +{{/info}} 26 26 27 - Ifyoucall [[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics]],theanswerend you back statistics, in JSON format, about instances,per application. Sample :33 +=== Bug Fixes to Apple's Versions === 28 28 29 - {{code}}35 +==== JavaMonitor ==== 30 30 37 +* Fixes an issue with the Application Delete page 38 +* Selection in Application Detail page is now Ajax and is maintained 39 + 40 +=== Improvements to Apple's versions === 41 + 42 +==== Automatic archive of SiteConfig.xml ==== 43 + 44 +On every change you make to an application's configuration, a backup of SiteConfig.xml will be created in, by default, /Library/WebObjects/Configuration. 45 + 46 +==== Simplified/Automated Bouncing ==== 47 + 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 : 49 + 50 +* Find the inactive (i.e., not started) instance and start it 51 +* Find the active instances (minus the one started in the previous step) and enable "Refuse New Session" 52 +* Bounce the active instances when the minimum session count is reached 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. 55 + 56 +{{warning title="Database Changes"}} 57 + 58 +It is uncertain what will happen if the new version of your application makes changes to your database schema (e.g., uses [ERXMigrations|WO:Project WONDER-Frameworks-ERXMigration]). The old instances may raise exceptions before they can gracefully shut down because the schema no longer matches what the old application's EOF expects. *Try it out on a test server first and then update this page so everyone knows\!* 59 + 60 +{{/warning}} 61 + 62 +==== Statistics ==== 63 + 64 +If you call ##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics]]##, JavaMonitor will send you back statistics, in JSON format, about instances, per application. 65 + 66 +{{code title="Statistics Example Results"}} 67 + 31 31 ( 32 32 { 33 33 "configuredInstances" = "2"; ... ... @@ -67,114 +67,136 @@ 67 67 68 68 If JavaMonitor is configured with a password, and I hope you do, pass //pw=monitorpassword// as a argument to the query : 69 69 70 -[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]] 107 +##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]## 71 71 72 -=== Direct Actions tomanytasks ===109 +==== Direct Actions for Management Tasks ==== 73 73 74 -You can do most of the standard tasks you do in Monitor by calling direct actions.Theyarein adifferentqueryhandler,///admin//. They followtheameformat andusethesamequeryparameters. Those DA can be useful if you need to restart instances or other tasks withinant or other build/deployment systems.111 +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. 75 75 76 -//?type=all// : return details about all applications and instances 77 -//?type=app&name=AppName// : return details about all instances of a specific application 78 -//?type=ins&name=AppName-InstanceNo// : return details about one specific instance 113 +List of available direct actions : 79 79 80 -For example, if you want to get details about all instances and applications, you call : 115 +* {{{*}info{*}}} : Returns details (number of deaths, state, etc.), in JavaScript Object Notation (JSON) as specified 116 +##info?##{{{}{*}type=all{*}}} 117 +##info?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 118 +##info?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 81 81 82 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all]] 120 +* {{{*}running{*}}} : Returns {{{*}YES{*}}} if **all** of the specified are running, ##NO## if not 121 +##running?##{{{}{*}type=all{*}}} 122 +##running?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 123 +##running?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 83 83 84 -To get details about the //AjaxExample// application : 125 +* {{{*}stopped{*}}} : Returns {{{*}YES{*}}} if **all** the specified is running, {{{*}NO{*}}} if not. 126 +##stopped?##{{{}{*}type=all{*}}} 127 +##stopped?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 128 +##stopped?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 85 85 86 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample]] 130 +* {{{*}bounce{*}}} : Returns {{{*}OK{*}}} after Bouncing (see description above) as specified 131 +##bounce?##{{{}{*}type=all{*}}} 132 +##bounce?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 87 87 88 -And for a specific instance : 134 +* {{{*}clearDeaths{*}}} : Returns {{{*}OK{*}}} after clearing deaths as specified 135 +##clearDeaths?##{{{}{*}type=all{*}}} 136 +##clearDeaths?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 89 89 90 -[[http://hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1]] 138 +* {{{*}turnScheduledOn{*}}} : Returns {{{*}OK{*}}} after turning on scheduling as specified. Call ///turnScheduledOff// to do the opposite. 139 +##turnScheduledOn?##{{{}{*}type=all{*}}} 140 +##turnScheduledOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 141 +##turnScheduledOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 91 91 92 -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 : 143 +* {{{*}turnRefuseNewSessionsOn{*}}} : Returns {{{*}OK{*}}} after turning on "Refuse new sessions" as specified 144 +##turnRefuseNewSessionsOn?##{{{}{*}type=all{*}}} 145 +##turnRefuseNewSessionsOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 146 +##turnRefuseNewSessionsOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 93 93 94 -{{code}} 148 +* {{{*}turnRefuseNewSessionsOff{*}}} : Returns {{{*}OK{*}}} after turning off "Refuse new sessions" as specified 149 +##turnRefuseNewSessionsOn?##{{{}{*}type=all{*}}} 150 +##turnRefuseNewSessionsOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 151 +##turnRefuseNewSessionsOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 95 95 96 -[Hudson Build Server for Wonder|http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/] 153 +* {{{*}turnAutoRecoverOn{*}}} : Returns {{{*}OK{*}}} after turning on "Auto Recover" as specified 154 +##turnAutoRecoverOn?##{{{}{*}type=all{*}}} 155 +##turnAutoRecoverOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 156 +##turnAutoRecoverOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 97 97 98 -{{/code}} 158 +* {{{*}turnAutoRecoverOff{*}}} : Returns {{{*}OK{*}}} after turning off "Auto Recover" as specified 159 +##turnAutoRecoverOn?##{{{}{*}type=all{*}}} 160 +##turnAutoRecoverOn?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 161 +##turnAutoRecoverOn?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 99 99 100 -List of available direct actions : 163 +* {{{*}forceQuit{*}}} : Returns {{{*}OK{*}}} after force quitting as specified. This could be useful to call from a monitoring system. 164 +##forceQuit?##{{{}{*}type=all{*}}} 165 +##forceQuit?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 166 +##forceQuit?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 101 101 102 -///info// : return details (number of deaths, state, etc.; see above), in JSON, about an instance. 103 -///running// : return YES if the instance is running, NO if not. 104 -///stopped// : return NO if the instance is running, YES if not. 105 -///bounce//: more on it later. 106 -///clearDeaths// : clear the number of deaths (same action as clicking the "Clear deaths" in JavaMonitor) 107 -///turnScheduledOn// : turn scheduling on for an application or instance. Call ///turnScheduledOff// to do the opposite. 108 -///turnRefuseNewSessionsOn// : turn "Refuse new sessions" on, call //turnRefuseNewSessionsOff// to do the opposite. 109 -///turnAutoRecoverOn// : guess what? It activate "Auto recover" And guess again? ///turnAutoRecoverOff// do the opposite 110 -///forceQuit// : force quit an application, might be useful to call it from a monitoring system. 111 -///stop// : stop an application/instance the normal way. 112 -///start// : start an application/instance the normal way. 168 +* {{{*}stop{*}}} : Returns {{{*}OK{*}}} after calling "Stop" as specified 169 +##stop?##{{{}{*}type=all{*}}} 170 +##stop?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 171 +##stop?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 113 113 114 -=== Automatic archive of SiteConfig.xml === 173 +* {{{*}start{*}}} : Returns {{{*}OK{*}}} after calling "Start" as specified 174 +##start?##{{{}{*}type=all{*}}} 175 +##start?##{{{}{*}type=app&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}} 176 +##start?##{{{}{*}type=ins&name=*{}}}{{color value="maroon"}}{{{}{*}AppName{*}{}}}{{/color}}{{{}*\-*{}}}{{color value="maroon"}}{{{}{*}InstanceNumber{*}{}}}{{/color}} 115 115 116 -On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration. 178 +To get details about all instances of all applications: 179 +##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=all]]## 117 117 118 -=== Bounce feature === 181 +To get details about the **AjaxExample** application: 182 +##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample]]## 119 119 120 -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 : 184 +To get details about instance **1** of the **AjaxExample** application: 185 +##[[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1]]## 121 121 122 -* Find the inactive (eg : not started) instance and start it 123 -* Find the active instances (minus the one started the step below) and enable "Refuse New Session" 124 -* Bounce the active instances when the minimum session count is reached 187 +==== Remote Control via REST Routes ==== 125 125 126 - Thisfeature,frommyunderstanding, allow youtoupload newversionsof your app,startup thenewversionandrefusesessionsfortheinstances runningontheolderversion.Idon'tknowhowthiswillworkifyournew versionusemigrations to changeyourschema(eg :oldinstances might raise exceptionsbecauseof databaseschemachanges),sotryitutonatest serverbeforeand putyourresultshere.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. 127 127 128 - ===RESTroutes===191 +Examples of REST calls : 129 129 130 - On September 28th 2010, REST routes were addedin JavaMonitor. Those routes + the directactions explainedin thisdocument allow you to control almost everythingremotely (makesurethat your JavaMonitor installation is secure). As the direct actions, append //?pw=XXXX//tothe URLsif JavaMonitor is password protected.193 +{{code title="Adding a New Host"}} 131 131 132 - Examples ofRESTcalls :195 +curl -X POST -d "{id: 'otherserver.com',type: 'MHost', osType: 'MACOSX',address: '192.168.20.5', name: 'otherserver.com'}" http://monitorhost:port/apps/WebObjects/JavaMonitor.woa/ra/mHosts.json 133 133 134 - Fetching thedetails of all applications :197 +{{/code}} 135 135 136 -{{code}} 199 +{{code title="Fetching Details for All Applications"}} 137 137 138 -curl -X GET http:// 127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json201 +curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json 139 139 140 140 {{/code}} 141 141 142 -Adding a newapplication:205 +{{code title="Adding a New Application"}} 143 143 144 -{ {code}}207 +curl -X POST -d "{id: 'AjaxExample',type: 'MApplication', name: 'AjaxExample',unixOutputPath: '/opt/Local/Library/WebObjects/Logs', unixPath: '/opt/Local/Library/WebObjects/Applications/AjaxExample.woa/AjaxExample'}" http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json 145 145 146 -curl -X POST -d "{id: 'AjaxExample',type: 'MApplication', name: 'AjaxExample',unixOutputPath: '/opt/Local/Library/WebObjects/Logs', unixPath: '/opt/Local/Library/WebObjects/Applications/AjaxExample.woa/AjaxExample'}" http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications.json 147 - 148 148 {{/code}} 149 149 150 - Addingaewinstance :211 +{{code title="Delete an Application"}} 151 151 152 - {{code}}213 +curl -X DELETE http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample.json 153 153 154 -curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance&host=localhost 155 - 156 156 {{/code}} 157 157 158 - Delete an application:217 +{{code title="Adding a New Instance"}} 159 159 160 - {{code}}219 +curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/addInstance&host=localhost 161 161 162 -curl -X DELETE http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample.json 163 - 164 164 {{/code}} 165 165 166 -Delete an instance:223 +{{code title="Delete an Instance"}} 167 167 168 - {{code}}225 +curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/deleteInstance?id=1 169 169 170 -curl -X GET http://127.0.0.1:56789/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/deleteInstance?id=1 171 - 172 172 {{/code}} 173 173 174 - Addinganewhost:229 +{{code title="Configuring the Site"}} 175 175 176 - {{code}}231 +curl -X PUT -d "{woAdaptor:'www.mydomain.com'}" http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mSiteConfig.json 177 177 178 -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 179 - 180 180 {{/code}} 234 + 235 +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. 236 + 237 +=== Troubleshooting === 238 + 239 +If JavaMonitor did not start on your fresh install of WebObjects, check out the [[WOTaskd Didn't Start>>WO:Troubleshooting Deployment]] question in the troubleshooting section.