Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 115.1
edited by David Avendasora
on 2010/11/29 20:01
Change comment: There is no comment for this version
To version 131.1
edited by Pascal Robert
on 2010/11/28 08:33
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,41 +3,29 @@
1 -[[image:WonderJavaMonitor.png||border="1"]]
2 -
3 3  {{toc}}{{/toc}}
4 4  
5 5  === Introduction ===
6 6  
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.
5 +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.
8 8  
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.
7 +[[image:LaunchBarScreenSnapz001.png||border="1"]]
10 10  
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.
9 +=== Misc ===
12 12  
13 -=== Where To Get Them ===
11 +The community's improved versions of **wotaskd.woa** and **JavaMonitor.woa** are now available as full Wonder applications. You can download them pre-built from the [[Hudson Wonder build server>>http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]].
14 14  
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.
13 +If you build everything from Wonder source, you can run :
16 16  
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 -
19 19  {{code}}
20 -ant frameworks deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
16 +ant deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
21 21  {{/code}}
22 22  
23 -{{info title="What this command does:"}}
19 +The //-Ddeployment.standalone=true// argument will embed the required frameworks in wotaskd and JavaMonitor. Please note that you have to build the Wonder frameworks before calling //ant deployment.tools//, if you get classpath errors when building the deployment tools, first run:
24 24  
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.
21 +{{code}}
22 +ant frameworks
23 +{{/code}}
30 30  
25 +=== Statistics ===
31 31  
32 -
33 -{{/info}}
34 -
35 -=== Major Improvements over Apple's versions ===
36 -
37 -==== Statistics ====
38 -
39 39  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 :
40 40  
41 41  {{code}}
... ... @@ -81,10 +81,8 @@
81 81  
82 82  [[http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/wa/statistics?pw=monitorpassword]]
83 83  
84 -==== Direct Actions to many tasks ====
72 +=== Direct Actions to many tasks ===
85 85  
86 -=== ===
87 -
88 88  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.
89 89  
90 90  //?type=all// : return details about all applications and instances
... ... @@ -125,16 +125,12 @@
125 125  ///stop// : stop an application/instance the normal way.
126 126  ///start// : start an application/instance the normal way.
127 127  
128 -==== Automatic archive of SiteConfig.xml ====
114 +=== Automatic archive of SiteConfig.xml ===
129 129  
130 -=== ===
131 -
132 132  On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
133 133  
134 -==== Simplified/Automated Bouncing ====
118 +=== Bounce feature ===
135 135  
136 -=== ===
137 -
138 138  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 :
139 139  
140 140  * Find the inactive (eg : not started) instance and start it
... ... @@ -143,10 +143,8 @@
143 143  
144 144  This feature, from my understanding, allow you to upload new versions of your app, start up the new version and refuse sessions for the instances running on the older version. I don't know how this will work if your new version use migrations to change your schema (eg : old instances might raise exceptions because of database schema changes), so try it out on a test server before and put your results here.
145 145  
146 -==== Remote Control via REST Routes ====
128 +=== REST routes ===
147 147  
148 -=== ===
149 -
150 150  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.
151 151  
152 152  Examples of REST calls :