Chapter 1. Introduction 1. Overview of This Release Red Hat Application Stack is a set of software components that have been tested and certified to work together in an integrated fashion. Red Hat Application Stack is designed for dynamic web applications for both the LAMP and Java (TM) platforms. 2.
Chapter 2. Configuring the Java Environment JBoss Application Server relies on an installed JVM, such as those by Sun, or BEA. Both JVMs are available from the Red Hat Enterprise Linux 5 Supplementary channels. THIS RELEASE HAS BEEN CERTIFIED WITH THE SUN AND BEA JVMS.
Chapter 2. Configuring the Ja... As root, issue the following command: /usr/sbin/alternatives --config java and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted. Make sure you do the same for We recommend that all point to javac java_sdk_1.5.0.
Page 11
Using / DVD 4. Install JBoss Application Server: • For the Application Server (which includes an embedded Tomcat), run: yum install jbossas 5. After the installation is complete, remove the file you added in in Step 3 /etc/yum.repos.d/ (or set enabled=0 in that file). Failure to do this will result in exiting with an error whenever it is run again without mounting the Red Hat Application Stack V.2.0 DVD.
Chapter 3. Installing Red Hat Application Stack To install Red Hat Application Stack V.2.0: 1. If you have an existing database, back up your data and shut down the database: If you are using PostgreSQL: • Back-up your database. For example, run: su - rm -rf /tmp/pg.backup su - postgres...
Page 14
Chapter 3. Installing Red Hat... b. Run as root: yum update c. Run as root: yum groupinstall stacks • Option 2. To install from RPMs on Disk: Follow the instructions in Section 2.2, “ Using / DVD ” to mount the DVD and set up the local RHN channel (steps 1-3).
Page 15
When using the directive, you can specify multiple groups at the groupinstall same time (even if they share packages). Analogous to , you can use the directive to groupinstall "groupremove" remove all the packages in a group. The groupremove directive will only remove packages in the group;...
Page 16
Chapter 3. Installing Red Hat... • Update MySQL: mysql_upgrade • Restore your data: mysql -p < /tmp/mysqldumpfile.sql 5. Start the remaining daemons: • Start the http daemon: /sbin/service httpd start The installation is now complete.
Chapter 4. Using JBoss Application Server 1. Using the Linux service (production) JBoss Application Server can be started, stopped, and configured to start automatically at boot time either from the command line or using a graphical tool. You can start and stop the service using the command as root on a console jbossas...
Page 18
Chapter 4. Using JBoss Applic... Please see http://kbase.redhat.com/faq/FAQ_107_9963.shtm for more information JBoss Application Server is configured with its internal servlet engine to listen for HTTP traffic on port 8080. Once the jbossas service has been started, you can verify that it is running by...
Using run.sh (development) Note Please note that automated updating of configurations created using method above is not supported. If you create custom configurations, you will manually have to port files / changes from a new update to that configuration. 2. Using run.sh (development) For development, you can activate the JBoss Application Server with the familiar run.sh command as usual.
Chapter 4. Using JBoss Applic... 'production', 'minimal' and 'all', you must create a new directory for your configuration as follows (note the switches given to the command): JBOSS_BASE=/var/lib/jbossas cd $JBOSS_HOME cp -pL -R server/default server/myownconfig You can then change the configuration and request it to be used by specifying it in the flag to , as usual.
Running multiple instances of JBoss export JAVA_HOME=/usr/lib/jvm/java where the value you give for is the location of your installed Java VM. JAVA_HOME 5. Running multiple instances of JBoss Application Server Note Please note that automated updating of instances created using methods below is not supported.
Chapter 4. Using JBoss Applic... so no file conflicts shall exist. For more flexibility in the configuration of the different servers, you may want to create full copies of . This is described in Creating copies of JBOSS_HOME above -- make JBOSS_HOME sure you use the command's...
Application Server e.g: ln -s /etc/init.d/jbossas /etc/init.d/jbossas-ports-01 2. Create a new config file for . The contents of service-name /etc/sysconfig/service-name this file should be similar to , except with instance specific values /etc/sysconfig/jbossas uncommented and updated, e.g: . Uncomment and cp /etc/sysconfig/jbossas /etc/sysconfig/jbossas-ports-01 update JBOSSCONF...
Chapter 4. Using JBoss Applic... 6. More Information More general documentation for JBoss Application Server is available under /usr/share/doc/jbossas-4.2.0...
Chapter 5. Export Control As required by U.S. law, you represent and warrant that you: a. Understand that certain parts of the software are subject to export controls under the U.S. Commerce Departments Export Administration Regulations (EAR) b. Are not located in a prohibited destination country under the EAR or U.S. sanctions regulations (currently Cuba, Iran, Iraq, Libya, North Korea, Sudan, and Syria) c.
Need help?
Do you have a question about the APPLICATION STACK 2.0 - RELEASE NOTES and is the answer not in the manual?
Questions and answers