I used some of last weekend to come up with somewhat
better initialization scripts for RedHat Linux
deployment, and made a more sane building process
(that allow you to build from the source distributed
on the jboss.org website).

The scripts seems to work fine, although I have had
problems shutting the server down properly sometimes.
It seems to occur whenever I have also run other Java-
programs on the server during the session.

You can find these at:
http://www.student.uib.no/~st01294/jboss/rpm/
jboss-2.0-1.spec        Build file for the program packages
jboss-test-2.0-1.spec   Build file for example bean; this
                        can also serve as a template for
                        packing other beans as well.
jboss                   Initialization script to go in
                        /etc/rc.d/init.d

All of these assumes that you are installing in
/usr/local/jboss. If you want tomcat integration, you'll
have to download the jboss_tomcat.tar.gz file and split
it into two components.

If you are going to build RPMs, please denote yourself
as the packager in the .spec files. Currently, I don't
have a website to put RPMs on, but if somebody wants to
hosts them, I can deliver turn-key RPMs.

While I'm at it, I would like to know how to redirect
jBoss to use a .conf file outside of the conf sibling
directory. I sure there is a property for it, but I
haven't found it in the manual yet.

Also, I would like opinions on the directory layout.
The advantage of having relative paths in jboss.conf
is that one can unpack the tarball anywhere and run
from that directory.

On a stock Linux system, I feel one should rather use:

    /etc/jboss             for configuration files
    /home/jboss            for databases
    /usr/local/lib    or
    /usr/local/jboss       for the server itself
    /usr/local/beans       for the beans
    /usr/local/src         for sources
    /usr/local/doc         for documentation
    /var/log/jboss         for logs
    /var/tmp/jboss    or
    /tmp/jboss             for temporaries

Because a lot of installations mount /usr read-only,
and the server will not be able to write anything.
Backups are often taken just from the /home hierarchy,
so that's where you'll want to put the user's data.

I didn't reorganize the files, putting everything into
/usr/local/jboss instead. (and I didn't bother changing
the .conf file).

I am sorry that all file and directory names are in
lowercase, but that's the tradition.

        R.

-- 
No, I'm not an (e)mail-chauvinist.




Reply via email to