On 23 November 2011 09:28, Peter Ondruška <peter.ondruska_at_gmail.com> wrote:
> Do you asadmin deploy --enabled=false?
>
Very cool.
I see the admin console also has this option.
A bit confusing as it phrases it as 'Enabled Allows users to access the
application.'
If I have timers / startup beans / MDB's, I also don't want those to run.
i.e. DR should not be active if Main is active.
regards
Richard
>
> "Allows users to access the application. If set to false, users will
> not be able to access the
> application. This option enables the application on the specified
> target instance or cluster.
> If you deploy to the target domain, this option is ignored, since
> deploying to the domain
> doesn't deploy to a specific instance or cluster. The default is true."
>
> On Wed, Nov 23, 2011 at 8:14 AM, <forums_at_java.net> wrote:
> > We are using GF 3.1.1 for both our production and disaster recovery (DR)
> > environments. The applications being deployed onto the DR environment
> cannot
> > run, not even for a second. My question is, is there a way that GF can
> > 'almost' deploy and app and immediately have it in a disabled state? I
> > realise that apps. can be disabled or undeployed AFTER being completely
> > deployed, but is what l am asking possible?
> >
> > Thank you.
> >
> >
> > --
> >
> > [Message sent by forum member 'jnegem']
> >
> > View Post: http://forums.java.net/node/867119
> >
> >
> >
>
>
>
> --
> Peter
>