Sie sind auf Seite 1von 4

JBOSS 6.1.

#JBOSS Community recommends using latest Jboss packages with latest JDK(java) kit #Download move all the jboss and java binaries into /usr/local/src cd /usr/local/src wget wget #for x64 machine use the below link #JBOSS user creation with home directory /home/jboss and group jboss using the following commands. groupadd -g 501 jboss useradd -c "jboss user" -d /home/jboss -g 501 -m -u 501 jboss #Installing JAVA cd /usr/local/src cp -rvf jdk-7u2-linux-i586.tar.gz /usr/local/ cd /usr/local/ tar -xzvf jdk-7u2-linux-i586.tar.gz rm -rf jdk-7u2-linux-i586.tar.gz #Installing JAVA for x64 machines cd /usr/local/src cp -rvf jdk-7u2-linux-x64.tar.gz /usr/local/ cd /usr/local/ tar -xzvf jdk-7u2-linux-x64.tar.gz rm -rf jdk-7u2-linux-x64.tar.gz #Adding JAVA_HOME and java binary path to /etc/profile #Add the below lines to /etc/profile above export keyword and change the export argument as below vim /etc/profile JAVA_HOME=/usr/local/jdk1.7.0_02 PATH=$PATH:/usr/local/jdk1.7.0_02/bin export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC JAVA_HOME

#Exporting or Sourcing the etc profile into the same shell . /etc/profile source /etc/profile #Check the JAVA version that was installed. java -version #here is the output java version "1.7.0_01" Java(TM) SE Runtime Environment (build 1.7.0_01-b08) Java HotSpot(TM) Client VM (build 21.1-b02, mixed mode) #Installing JBoss cd /usr/local/src cp -rvf /usr/local/ cd /usr/local/ unzip rm -rf #The jboss folder is /usr/local/jboss-6.1.0.Final #Create Symbolic link jboss to jboss-6.1.0.Final ln -s jboss-6.1.0.Final jboss #Change ownership of both symbolic link and jboss directory chown -R jboss:jboss jboss chown -R jboss:jboss jboss-6.1.0.Final #Export JBOSS_HOME env variable su - jboss #Add the below line to jboss user's profile vim ~/.bash_profile JBOSS_HOME=/usr/local/jboss

#change the export argument from export PATH #to export PATH JBOSS_HOME #jboss user profile is as below after changing PATH=$PATH:$HOME/bin JBOSS_HOME=/usr/local/jboss export PATH JBOSS_HOME #Source/Export the jboss user profile source ~/.bash_profile . ~/.bash_profile #Check all the variables for JAVA AND JBOSS, Below commands prints the value of variable if set correctly else prints the variable not set correctly. echo ${JAVA_HOME:-JAVA_HOME is not set} echo ${JBOSS_HOME:-JBOSS_HOME is not set} echo $PATH|grep -i jdk &>/dev/null; echo $?|sed -e 's/1/jdk\ path\ is\ not\ set/g' -e 's/0/jdk\ path\ is\ set\ correctly/g' #Finetuning/slimming down JBoss during Installation Phase. #Remove HornetQ Messg module in JBoss(It is recommended not to use Messaging service as builtin jboss module, becoz , if JBoss service is down, Messaging will also be down, subsequently leading to shutdown of Mule, It is good to run HornetQ as a standalone process on a different server) cd /usr/local/jboss #Remove HornetQ, mail,uuid related libraries,conf files and folders find ./ -name 'hornetq*' -exec rm -rvf {} \; find ./ -name 'mail*' -exec rm -rvf {} \; find ./ -name 'uuid*' -exec rm -rvf {} \;

#Create our own Custom Jboss profile named twinspires cd /usr/local/jboss/server cp -prvf default/ twinspires #Finetuning Twinspires JBoss Profile cd /usr/local/jboss/server/twinspires/deploy rm -rvf schedule-manager-service.xml scheduler-service.xml quartz-ra.rar xnio-provider.jar jmsra.rar cd /usr/local/jboss/server/twinspires/deployers rm -rvf bsh.deployer jbossws-jaxrpc.deployer xnio.deployer jboss-jpa-mcint.jar weld.deployer cd /usr/local/jboss/server/twinspires/conf/props/ rm -rvf messaging-* #Change/Equialize the min and max memory setting of jboss cd /usr/local/jboss/bin #512 MB for jboss sed -i 's/\-Xms128m\ \-Xmx512m/\-Xms512m\ \-Xmx512m/g' run.conf #1024 MB for jboss sed -i 's/\-Xms128m\ \-Xmx512m/\-Xms1024m\ \-Xmx1024m/g' run.conf #2048 MB for jboss sed -i 's/\-Xms128m\ \-Xmx512m/\-Xms2048m\ \-Xmx2048m/g' run.conf #3076 MB for jboss sed -i 's/\-Xms128m\ \-Xmx512m/\-Xms3076m\ \-Xmx3076m/g' run.conf #Starting JBoss Service with twinspires profile. cd /usr/local/jboss/bin ./run.conf -b -c twinspires &