I'm trying to understand exactly what you're referring to when you say "running as a service" on a Linux machine. Can I assume you're just talking about a server that start's up and shut's down at system bootup and shutdown?
If that's the case, then what you're really looking for is the jetty "init" script. On Linux, the init scripts are what are responsible for starting up and shutting down a "service" when the system boots and shutsdown. You can also call these init scripts while the system is running to start, stop, and restart "services" on the fly while the system is running - just like the windows service manager lets you do. Doing a quick google search for "jetty init script", it looks like jetty itself is packaged in some linux distros, including Fedora, as mentioned here: https://bugzilla.redhat.com/show_bug.cgi?id=393071 Assuming you simply want an easy way to start and stop your jetty server using an "init" script, you could do 1 of 2 things: 1) Install this jetty RPM and hijack the init script for your own purposes - updating the paths that it uses to point to your jetty ready-to-run instance. 2) Copy over the OpenBD configs from the ready-to-run instance to the default install of the jetty RPM. Lastly, if those options are too much of a PITN, you could use the installer script that Vivio wrote for OpenBD on CentOS. It's located here: http://openbd.viviotech.net/ Click on the "installer" directory, and download the openbd-1.0.1_rhel_pl0.sh file. This installer will install Tomcat with OpenBD, instead of Jetty - but it's fast, stable, and comes with an init script, the latest version of OpenBD, and the latest version of the OpenBD Admin. HTH Warm regards, Jordan Michaels Vivio Technologies http://www.viviotech.net/ Open BlueDragon Steering Committee Adobe Solution Provider Dakota Burns wrote: > I like the simplicity of Jetty, and modifying the jetty.xml where > apropriate. A while back I read where Alan Williamson said Jetty was > stable, high performing, and he preferred it to Tomcat. Are their any > downfalls to running Jetty versus Tomcat? It seems to me that Jetty is > a lightweight java server, and ... if it does the job -- why not > consider as an option for running "as service" with OpenBD in addition > to the manual "Ready2Run" package, which is great, by the way? I've > searched Google and this OpenBD group, and running Jetty as a service on > Linux seems to be problematic -- and not very well documented, but -- I > may have hit the wrong results when searching. Are either of you > running Jetty as a service with OpenBD on CentOS or other Linux distro? > If yes, can you reply with a pointer to a tutorial or steps? > > Thanks, > Dakota > > > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
