The general (there are variations) approach used by people for small
deployments (a few manageable instances) are:
1) Deploy new embedded Application and embedded WebServer Resources bundles
with unique versioned bundle names (IIRC you can set this in build.app.name in
project properties in Eclipse and build.xml uses it)
myapp-r123.woa (current running version may be myapp-r122.woa)
2) Pre-app-rollout SQL Migration
Changes that provide needed changes for new version and keeps schema
still compatible with old version
3) In WOMonitor, update app config and click "Update for New Instances Only"
button
4) Begin adding new instances
5) Turn off Auto Recover and turn on Refuse New Sessions
6) When old version instances have all died, run your optional post rollout SQL
migration script that brings schema to exactly the way you want it for new app
version. (remove columns no longer needed, etc.)
Hope this helps,
Kieran
On May 4, 2011, at 6:14 PM, Daniel Mejia wrote:
> Thank you very much,
>
> I'm going to try this solution tonight.
>
> regards,
>
> Daniel.
>
> On 04/05/2011, at 15:25, Pascal Robert wrote:
>
>>
>> Le 2011-05-04 à 16:17, Jesse Tayler a écrit :
>>
>>> oh!
>>>
>>> is that what bounce does?
>>>
>>> well then!
>>>
>>> so,
>>>
>>> 1 press bounce
>>>
>>> 2 deploy new files
>>
>> 2 is press bounce, 1 is deploy new files
>>
>>> 3 wait for new instances to come up
>>
>> The bounce action will start any inactive instances. So you have one running
>> instance and one idle, and when you "bounce" the already running instance go
>> under "refuse new sessions" mode (so current users can finish their work)
>> and the idle instance kicks off with the new code.
>>
>>> so, new instances have the new files and existing instance sessions
>>> reliably run on old files?
>>
>> Yes, the new instances have to start from another bundle. So say "old"
>> instances runs on /opt/MyApp.woa.20110101 and the "new" instances runs on
>> /opt/MyApp.woa.20110504
>>
>>>
>>>
>>> On May 4, 2011, at 4:08 PM, Pascal Robert wrote:
>>>
>>>>
>>>> Le 2011-05-04 à 16:00, Daniel Mejia a écrit :
>>>>
>>>>> Hi,
>>>>>
>>>>> I have a question regarding the deploy. Is it possible to redeploy an
>>>>> application when the application is running, or I need to shutdown every
>>>>> instance, deploy the application and restart every instance?
>>>>
>>>> You will have classpath issues when doing that. It's better to use the
>>>> "Bounce" feature of Monitor, which put the "old" app in "refuse new
>>>> sessions" mode and start new instances with the new code.
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
>>>> Help/Unsubscribe/Update your Subscription:
>>>> http://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com
>>>>
>>>> This email sent to jtay...@oeinc.com
>>>>
>>>
>>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/kelleherk%40gmail.com
>
> This email sent to kelleh...@gmail.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
