[Novalug] where *should* I put jboss-as?

[Brander Snaxe]

For development and experimentation I tend to create paths such as
/home/user/dev/env/application-dev1/tomcat
or
/home/user/dev/env/application-dev1/jboss

On a production deployment, I use /opt for pre-compiled 3rd party binaries. E.g. /opt/tomcat or /opt/weblogic.

If I compile something myself, it goes to /usr/local, regardless of where I got the source (I wrote it or downloaded a tarball).



________________________________
 From: Peter Larsen <plarsen at famlarsen.homelinux.com>
To: novalug at calypso.tux.org 
Sent: Sunday, February 19, 2012 2:31 PM
Subject: Re: [Novalug] where *should* I put jboss-as?
 
So to the list here - being in the JBoss business this question has
gotten a lot of input that all seems to focus on one out of many
different areas.

Look at tomcat, look at Apache - or just your plain old LibraOffice. Now
look at where the files go - and then come back here and tell me which
ONE location the files go to. You cannot?  Well, that's correct! Those
complex system consists of files with different purposes and hence they
end up scattered around the file system in the areas that everyone in
this thread has highlighted.

JBoss is no different. There are libraries, log files, configuration
files, executables, startup scripts, system configurations etc. and they
all will end up in different areas to fit the standard file structure of
Fedora (I don't know if this is shared with Ubuntu/Debian - sorry for my
ignorance here). The result, once AS7 gets released on F17 is you'll
find pretty much components of AS7 in every suggested path except
for /usr/local and /opt. Personally I've never understood those
structures to begin with (apps are apps, regardless of who releases
them).

For now, what we have done to test and use AS7 is to simply install a
mis-mash of files from a zip file into a single directory under home. By
no means is this acceptable for production or standard Linux - mixing
r/o, static and dynamic/changing files all put in a single structure.
It's not the Linux way and definitely will not be how AS7 is delivered
once in RPMs. But it's a big task to split out the components, decide on
the security model and create enough dynamics so you can manage the
JBoss installation from Linux tools as well as from within AS7 itself. 

Currently the RPMs of early JBoss installations
uses /var/lib, /etc/jbossas, /usr/lib, /var/log/jbossas - and I presume
that it's going to be a similar mix for AS7 maybe with some added
flexibility for choosing modules to include with the installation.

As I wrote earlier to greg - if the goal is to just play around with AS7
just unzip it straight into the HOME directory. It will give plenty of
options for getting to know the beast.

On Wed, 2012-02-15 at 07:09 -0500, greg pryzby wrote:
> I decided to start playing around w/ JBoss AS7. There is no rpm, zip
> or tgz. And it explodes in the current directory.
> 
> Where do people install it?
>    /var/jboss-as7
>    /opt/jboss-as7
>    /usr/local/jboss-as7
> 
> 


-- 
Best Regards
  Peter Larsen

Wise words of the day:
/*
* Buddy system. Hairy. You really aren't expected to understand this
*
*/
    -- From /usr/src/linux/mm/page_alloc.cA

_______________________________________________
Novalug mailing list
Novalug at calypso.tux.org
http://calypso.tux.org/mailman/listinfo/novalug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://calypso.tux.org/pipermail/novalug/attachments/20120220/9e0935c5/attachment.html