Related Manuals for Red Hat APPLICATION STACK 2.4 - RELEASE NOTES
Summary of Contents for Red Hat APPLICATION STACK 2.4 - RELEASE NOTES
- Page 1 Red Hat Application Stack 2.4 Release Notes for Use with Red Hat Application Stack 2.4...
- Page 2 Release Notes Red Hat Application Stack 2.4 Release Notes for Use with Red Hat Application Stack 2.4 Edition 1.0 Copyright © 2009 Red Hat...
-
Page 3: Table Of Contents
1. Introduction 1.1. Overview of This Release ..................... 1 1.2. Installation Prerequisites ....................1 1.3. Package-specific Notes ....................1 2. Configuring the Java Environment 2.1. Install a supported SDK ....................3 2.1.1. Installing a IBM or Sun SDK ................3 2.2. -
Page 5: Introduction
Chapter 1. Introduction 1.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. -
Page 7: Configuring The Java Environment
Chapter 2. Configuring the Java Environment JBoss Application Server relies on an installed JVM, such as those by Sun, or IBM Both JVMs are available from the Red Hat Enterprise Linux 5 Supplementary channels. THIS RELEASE HAS BEEN CERTIFIED WITH THE SUN JVM. Currently Red Hat Application Stack is certified with the Sun JVM version 1.5.0 update 15 or later. -
Page 8: Install The Jbossas Package
Chapter 2. Configuring the Java Environment Make sure you do the same for javac and java_sdk_1.5.0. We recommend that all point to the same manufacturer and version. 2.2. Install the jbossas package 2.2.1. Using yum / RHN 1. Update your Red Hat Enterprise Linux 5 installation and install the JVM as described above. 2. -
Page 9: Installing Red Hat Application Stack
Chapter 3. Installing Red Hat Application Stack To install Red Hat Application Stack V.2.4: 1. If you have an existing database and are installing Red Hat Application Stack for the first time, back up your data and shut down the database: •... - Page 10 Chapter 3. Installing Red Hat Application Stack • Run as root: yum groupinstall stacks Note You may need to install the following packages to satisfy dependencies before executing the above command, if they are not already installed: • apr-devel • apr-util-devel •...
- Page 11 /sbin/service postgresql start • Restore your data from back-up psql -U username < /tmp/pg.backup • Start the http daemon: /sbin/service httpd start • For MySQL: • Start MySQL: /sbin/service mysqld start • Update MySQL: mysql_upgrade • Restore your data: mysql -p < /tmp/mysqldumpfile.sql 5.
-
Page 13: Using Jboss Application Server
Where $JBOSS_HOME is the install directory (/var/lib/jbossas) and $CONFIG is the server configuration you are using. http://kbase.redhat.com/faq/FAQ_107_9963.shtm Please see for more information JBoss Application Server is configured with its internal servlet engine to listen for HTTP traffic on port 8080. -
Page 14: Using Run.sh (Development)
Chapter 4. Using JBoss Application Server http://localhost:8080/web-console You can use the Web Console to administer JBoss Application Server. The entire JBoss Application Server suite runs under a new jboss system user. It may be necessary to use the 'su -s /bin/bash jboss' system command to deposit .ear / .war / .jar files under the JBoss Application Server deployment directory, due to file system permissions. -
Page 15: Creating Copies Of Jboss_Home
Creating copies of JBOSS_HOME JAVA_HOME can be set system-wide in /etc/profile. But beware, some users may not want to have JAVA_HOME set to this same SDK. Also, some may prefer to use the alternatives-selected one instead. These users may be affected by this global setting of JAVA_HOME. -
Page 16: Using The Jbossas-* Commands From Any Directory
Chapter 4. Using JBoss Application Server Note Please note that automated updating of copies created using methods above is not supported. If you create custom copies, you will manually have to port files / changes from a new update to that copy. 4.4. -
Page 17: Running Multiple Instances Of Jboss Application Server Using Different Sets Of Ports
Running multiple instances of JBoss Application Server using different sets of ports Note The original init script log files are created under /var/log/jbossas in directories that correspond to the configuration used (like 'default') with the usual server.log name. For instance: /var/log/jbossas/default/server.log In general, each log file is created by the SysV script as /var/log/service-name/$JBOSSCONF/server.log... -
Page 18: Running Multiple Instances Of Jboss Application Server Binding To Different Local Ip Addresses
Chapter 4. Using JBoss Application Server ln -s /etc/init.d/jbossas /etc/init.d/jbossas-ports-01 2. Create a new config file for service-name, /etc/sysconfig/service-name. The contents of this file should be similar to /etc/sysconfig/jbossas, except with instance specific values uncommented and updated, e.g: cp /etc/sysconfig/jbossas /etc/sysconfig/jbossas-ports-01. Uncomment and update JBOSSCONF to ports-01 in /etc/sysconfig/jbossas-ports-01. -
Page 19: More Information
More Information 4.6. More Information More general documentation for JBoss Application Server is available under /usr/share/doc/ jbossas-4.2.0 or /usr/share/doc/jbossas-4.3.0 depending on your installation. -
Page 21: Export Control
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.