Red Hat APPLICATION STACK 1.2 - RELEASE NOTES Release Note

Advertisement

Quick Links

Red Hat Application Stack V.1.2 Release
Notes
1.2
ISBN: N/A
Publication date:

Advertisement

Table of Contents
loading

Summary of Contents for Red Hat APPLICATION STACK 1.2 - RELEASE NOTES

  • Page 1 Red Hat Application Stack V.1.2 Release Notes ISBN: N/A Publication date:...
  • Page 2 Red Hat Application Stack V.1...
  • Page 3 Red Hat Application Stack V.1.2 Release Notes Copyright © 2006-2007 Red Hat, Inc.
  • Page 4 Red Hat Application Stack V.1...
  • Page 5: Table Of Contents

    1. Introduction ......................1 1. Overview of This Release ................1 2. Installation Prerequisites ................. 1 3. Package-specific Notes .................. 1 2. Configuring the Java Environment ................3 1. Install a supported SDK .................. 3 1.1. Installing a BEA, IBM or Sun SDK ............3 2.
  • Page 7: Introduction

    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 platforms. 2.
  • Page 9: Configuring The Java Environment

    Chapter 2. Configuring the Java Environment JBoss AS relies on an installed JVM, such as those by Sun, or BEA. Both JVMs are available from the Red Hat Enterprise Linux (AS/ES) Extras channel. THIS RELEASE HAS BEEN CERTIFIED WITH THE SUN AND BEA JVMS.
  • Page 10: Install The Package

    JVM as described above. up2date 2. Mount the Red Hat Application Stack V.1.2 DVD. 3. Add the following line to to use directly on the /etc/sysconfig/rhn/sources up2date RPMs on the disk: dir RedHat-Application-Stack-V1 path_to_mounted_DVD/RedHat/RPMS...
  • Page 11 Using / DVD up2date 4. Install JBoss AS: • For the Application Server (which includes an embedded Tomcat), run: up2date jbossas 5. After the installation is complete, remove the line you added to in Step 3. Failure to do this will result in producing /etc/sysconfig/rhn/sources up2date...
  • Page 13: Installing Red Hat Application Stack

    Chapter 3. Installing Red Hat Application Stack To install Red Hat Application Stack V.1.2: 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 / DVD ” to mount the DVD and set up2date up the local RHN channel (steps 1-3). Then as root run: up2date --installall RedHat-Application-Stack-V1 Note If you are upgrading from Stacks V.1.1, and have installed the jbossas-ejb3 package, before running the above command, you need to first remove...
  • Page 15 • apr-devel • apr-util-devel • libc-client • • pcre-devel 4. Restore your database: • For PostgreSQL: • Move (or remove) the database directory: mv /var/lib/pgsql/data /var/lib/pgsql/data.backup • Start the new PostgreSQL service: /sbin/service postgresql start • Restore your data from back-up psql -U username <...
  • Page 16 Chapter 3. Installing Red Hat... • Restore your data: mysql -p < /tmp/mysqldumpfile.sql • Start the http daemon: /sbin/service httpd start The installation is now complete.
  • Page 17: Using Jboss As

    Chapter 4. Using JBoss AS 1. Using the Linux service (production) JBoss AS 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 AS Please see http://kbase.redhat.com/faq/FAQ_107_9963.shtm for more information JBoss AS 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 pointing your web...
  • Page 19: Using Run.sh (Development)

    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 AS server with the familiar command as run.sh...
  • Page 20: Using The Jbossas-* Commands From Any Directory

    Chapter 4. Using JBoss AS '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.
  • Page 21: Running Multiple Instances Of Jboss As

    Running multiple instances of JBoss AS 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 AS Note Please note that automated updating of instances created using methods below is not supported.
  • Page 22: Running Multiple Instances Of Jboss As Using Different Sets Of Ports

    Chapter 4. Using JBoss AS 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 switch to preserve the user and group ownership.
  • Page 23: Running Multiple Instances Of Jboss As Binding To Different Local Ip Addresses

    Running multiple instances of JBoss AS uncommented and updated, e.g: . Uncomment and cp /etc/sysconfig/jbossas /etc/sysconfig/jbossas-ports-01 update JBOSSCONF ports-01 /etc/sysconfig/jbossas-ports-01 3. Then add for management by , e.g: service-name chkconfig chkconfig --add jbossas-ports-01 4. To start/stop the service, simply: , e.g: service service-name start/stop service jbossas-ports-01 start 5.2.
  • Page 25: 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.

Table of Contents