Deploying Felix as a Windows service

[Stephen Brady <st...@bitlev.com>]

I have been playing around with deploying Felix as a Windows service and
have had mixed success with various wrappers (Java Service Wrapper, YAJSW,
Apache Commons).  These, however, create two processes, the "wrapper" and
the wrapped Felix, and I'd prefer to avoid this messiness.

Can anyone suggest an alternative?

Does anyone recommend NOT deploying Felix as a Windows service?

Re: Deploying Felix as a Windows service

[Guo Du <mr...@duguo.org>]

On Wed, Aug 11, 2010 at 6:50 PM, Stephen Brady <st...@bitlev.com> wrote:
> Can anyone suggest an alternative?
You could launch felix as windows scheduled task to run when windows start.

-Guo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

Re: Deploying Felix as a Windows service

[Christopher Brind <br...@brindy.org.uk>]

On 11 August 2010 18:50, Stephen Brady <st...@bitlev.com> wrote:

> I have been playing around with deploying Felix as a Windows service and
> have had mixed success with various wrappers (Java Service Wrapper, YAJSW,
> Apache Commons).  These, however, create two processes, the "wrapper" and
> the wrapped Felix, and I'd prefer to avoid this messiness.
>
> Can anyone suggest an alternative?
>

A different operating system? Sorry, just kidding, I know that's not always
an option. ;-)


>
> Does anyone recommend NOT deploying Felix as a Windows service?
>

I've had success with both JSW and YAJSW on pretty securely tied down
Windows Server environments so couldn't give a reason NOT to.  The main
gotchas are things like permissions for installing the wrapper, service
interaction with the desktop, etc.

Hope that helps.

Cheers,
Chris