Java™ Application Development on Linux - Dator

462Chapter 20Open Source Web <strong>Application</strong> Serversrestart)$0 stop$0 start;;*)echo "usage: $0 (start|stop|restart|help)"esac# define where JBoss is - this is the directory# containing directories log, bin, conf, etc.JBOSS_HOME=${JBOSS_HOME:-"/usr/local/jboss"}# make sure Java is on your pathJAVAPTH=${JAVAPTH:-"/usr/java/jdk/bin"}Finally, we don’t need to run the “all” configuration, we only need thedefault configuration at the moment, so we change the argument to the run.shinvocation:# define the script to use to start JBossJBOSSSH=${JBOSSSH:-"$JBOSS_HOME/bin/run.sh -c default"}JBoss ConfigurationsWhen you unpacked JBoss, it contained three predefined server configurationslocated in jboss/server. The three configurations are namedall (which runs every single service JBoss supports, including RMI/IIOPand clustering features), default (which runs only the set needed to runservlets, JSP, and EJBs), and minimal (which runs just JNDI, the logger,and a URL deployment service; no Web container, no JMS, no EJBs).In effect, the selected configuration is the server. You can, ofcourse, customize any configuration, and you may create additionalconfigurations.Now, this script allows you to run JBoss as any user. It defaults to userjboss if none is specified. You have to decide what to do here. Without specifyinga user, it will run as root. That is a major security risk. On an out-of-theboxRedHat or Fedora system, there is no user called jboss. We will have tocreate one. There are a lot of security concerns to creating a special “nonlogin”user. The most important involve changing the user entries in /etc/passwd