Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 70.1
edited by Pascal Robert
on 2009/08/09 19:34
Change comment: There is no comment for this version
To version 71.1
edited by Pascal Robert
on 2009/08/08 20:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -100,18 +100,4 @@
100 100  
101 101  === Automatic archive of SiteConfig.xml ===
102 102  
103 -On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
104 -
105 -=== Bounce feature ===
106 -
107 -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 :
108 -
109 -* Find the inactive (eg : not started) instance and start it
110 -* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
111 -* Bounce the active instances when the minimum session count is reached
112 -
113 -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.
114 -
115 -=== Misc ===
116 -
117 -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//).
103 +On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.