Thanks Jordan.  Yes -- am using ems.mydomain.com as the "host name".  Am
going to print your PDF and give it another shot after lunch.
Best Regards,
Dakota

On Fri, Mar 6, 2009 at 11:55 AM, Jordan Michaels <[email protected]>wrote:

>
>  > Per functionality from your script, did I need to fuss with JkWorker and
>  > worker.properties stuff as referenced from url above?
>
> Not for a simple install, no. Unless you're getting fancy with your
> tomcat setup (clustering?), you shouldn't have to mess with that at all.
> The idea of the installer was to provide as similar experience to the
> commercial versions of CFML servers as possible. That way it's less of a
> learning curve. You can, of course, create your own if you want to, but
> it's not required to get a server up and running.
>
> The only thing you're required to do to get a specific URL functional is
> modify the server.xml file with your site name and root directory.
>
>  >       <Host name="site1"  appBase="webapps"
>  >             unpackWARs="true" autoDeploy="true"
>  >             xmlValidation="false" xmlNamespaceAware="false">
>  >         <Context path="" docBase="/opt/openbd/tomcat/webapps/ROOT/" />
>  >       </Host>
>
> I'm assuming you're replacing "site1" with "yourdomain.com"?
>
> I would also recommend *against* setting up a site in the root context.
> The idea is to place your site files wherever you would "normally" place
> them. /home/user/public_html/ is a common spot to put site files... for
> example. Try to leave the ROOT context alone unless you're sure you want
> to change something there.
>
> There's a PDF document in the installer directory I referred you to
> earlier that covers setting up sites in a bit more detail. I wrote it
> before we had the wiki - and I really need to get the content moved to
> the wiki. I will try to get to that soon...
>
> Hope this helps!
>
> Warm regards,
> Jordan Michaels
> Vivio Technologies
> http://www.viviotech.net/
> Open BlueDragon Steering Committee
> Adobe Solution Provider
>
>
> Dakota Burns wrote:
> > Hi Jordan -
> >
> > I installed your script on a 64-bit test server running CentOS 5.2, and
> > Apache 2.2.  After the install succeeded, I stepped through
> > apache/tomcat connect details starting with "worker.properties" toward
> > the end of this guide: http://tinyurl.com/cou62e , updated my server.xml
> > file with a test domain from my hosts file pointing to
> > "/opt/openbd/tomcat/webapps/ROOT/" -- but no go.  When trying to
> > connect, it times out, whereas trying to connect to a name reference not
> > in the server.xml file pulls up the default apache web site (other stuff
> > -- not cfml).
> >
> > Per functionality from your script, did I need to fuss with JkWorker and
> > worker.properties stuff as referenced from url above?
> >
> > Here's my host reference:
> >
> >       <Host name="site1"  appBase="webapps"
> >             unpackWARs="true" autoDeploy="true"
> >             xmlValidation="false" xmlNamespaceAware="false">
> >         <Context path="" docBase="/opt/openbd/tomcat/webapps/ROOT/" />
> >       </Host>
> >
> >
> > Thanks,
> > Dakota
> >
> >
> > On Thu, Mar 5, 2009 at 11:36 AM, Jordan Michaels <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >
> >     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 <http://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 !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to