5 Replies Latest reply on Mar 1, 2012 2:01 AM by wdfink

    Need to separate JBoss installation files and  config files

      Hi,

      I installeed

      JBoss in /opt/jboss5

      JDK    in /opt/jdk1.6.0_25-64bit

       

      want to config a profile and start JBoss  instance from /app/projects/MyApp/bin/run.sh

      i want to keep all config files under /app/projects/MyApp/config

      deploy from /app/projects/MyApp/deploy

      log files should go  to /app/projects/MyApp/log

       

      when i specify JBOSS_HOME in run.conf  it is taking configs from  /opt/jboss5/servers/default .

       

      Is it possible this type of config in JBoss .

       

      I really don't want to  start any thing from /opt/

       

      _N

        • 1. Re: Need to separate JBoss installation files and  config files

          ** when i specify JBOSS_HOME in /app/projects/MyApp/bin/run.conf  as /opt/jboss5 its reading configs from /opt/jboss5/servers/default

          • 2. Re: Need to separate JBoss installation files and  config files
            wdfink

            As I understand you want change mostly anything. Why you don't copy the JBoss instance in you projects directory and strip it.

             

            What you can do is to change the config that you have an additional deploy and lib directory.

            • 3. Re: Need to separate JBoss installation files and  config files

              I have more than 25 Weblogic servers are running for different applcaitions  with different domains ..

              some are in 

              /app/frontoffice/amtrade

              /app/frontoffice/fxapp

              /app/securities/energy*

              /app/equities/{equity domains}

               

              all applciations are deistributed based on their catagory .

              all applciations just for example /app/secirities/energyus/domain/mydomain/startWeblogic.sh  refers WebLogic installed in /opt/WebLogic11g

              In setCommonEnv.sh we are refering BEA_HOME to /opt/WeBlogic11g

               

              the reason behing this is if i want to apply a critical pathch , or upgrade from WLS 10.3.5. to 10.3.6 , i don't need to go the all 25 instances .Just change in one place /opt/weblogic11g

               

              I don't want to copy same JBOSS binary files 25 times .

               

              My requirements are in all above 25 folders , i need start stop scripts and that domain specific config files , And also  i don't want  all 25 server logs going to /opt/jboss5/servers/default/log directory .

               

              _Naren

              • 4. Re: Need to separate JBoss installation files and  config files

                Hi any suggessions ??

                We are migrating away from Weblogic to  JBoss .

                We have big solaris server with multiple instances of weblogic running ..

                What is the common practice to run multiple JBoss from different directories in the same server .

                Need some best practices to deploy this topology ...

                 

                _Naren

                • 5. Re: Need to separate JBoss installation files and  config files
                  wdfink

                  Mostly (what I've seen) is that the JBoss installation is duplicated and stripped for each server.

                  This is because of independency if the servers are updated by different versions.

                  Also it might dangerous to change common libraries if the server is up and running, so you have to shutdown all server nodes for update.

                   

                  What can be done is to create a server directory for each and symlink

                  - bin

                  - conf if the configuration is exact the same include JVM otherwise take a copy

                  - server/xxx/lib (if no differences)

                  - common

                   

                  server/XXX/data must be different!

                   

                  With AS7 the new domain mode is what you want, there you can start multiple server instances from one location and configure only the differences for each.