Red Hat APPLICATION STACK 1.4 - RELEASE NOTES Release Note

Advertisement

Quick Links

Red Hat Application
Stack 1.4
Release Notes
for Use with Red Hat Application Stack 1.4

Advertisement

Table of Contents
loading

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

  • Page 1 Red Hat Application Stack 1.4 Release Notes for Use with Red Hat Application Stack 1.4...
  • Page 2 Release Notes Red Hat Application Stack 1.4 Release Notes for Use with Red Hat Application Stack 1.4 Edition 1.0 Copyright © 2006-2008...
  • 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 BEA, 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 platforms.
  • Page 7: 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 8: Install The Jbossas Package

    2. Mount the Red Hat Application Stack V.1.4 DVD. 3. Add the following line to /etc/sysconfig/rhn/sources to use up2date directly on the RPMs on the disk: dir RedHat-Application-Stack-V1 path_to_mounted_DVD/RedHat/RPMS 4. Install JBoss AS: • For the Application Server (which includes an embedded Tomcat), run: up2date jbossas 5.
  • Page 9 Using up2date / DVD Chapter 4, Using JBoss AS Refer also to below. If you are upgrading from version 1.1 of Red Hat Application Stack, please note that the "jbossas- ejb3" package has now been obsoleted and it's contents merged into the main jbossas package. An "up2date jbossas"...
  • Page 11: Installing Red Hat Application Stack

    Chapter 3. Installing Red Hat Application Stack To install Red Hat Application Stack V.1.4: 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 12 Follow the instructions in to mount the DVD and set 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 13 • Start the new PostgreSQL service: /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 •...
  • Page 15: Using Jboss As

    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 AS is configured with its internal servlet engine to listen for HTTP traffic on port 8080. Once the...
  • Page 16: Using Run.sh (Development)

    Chapter 4. Using JBoss AS http://localhost:8080/web-console You can use the Web Console to administer JBoss AS. The entire JBoss AS 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 AS deployment directory, due to file system permissions.
  • Page 17: 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 18: Using The Jbossas-* Commands From Any Directory

    Chapter 4. Using JBoss AS 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 19: Running Multiple Instances Of Jboss As Using Different Sets Of Ports

    Running multiple instances of JBoss AS using different sets of ports /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 so no file conflicts shall exist. For more flexibility in the configuration of the different servers, you may want to create full copies of Section 4.3, “...
  • Page 20: Running Multiple Instances Of Jboss As Binding To Different Local Ip Addresses

    Chapter 4. Using JBoss AS cp /etc/sysconfig/jbossas /etc/sysconfig/jbossas-ports-01. Uncomment and update JBOSSCONF to ports-01 in /etc/sysconfig/jbossas-ports-01. 3. Then add service-name for management by chkconfig, e.g: chkconfig --add jbossas-ports-01 4. To start/stop the service, simply: service service-name start/stop, e.g: service jbossas-ports-01 start 4.5.2.
  • 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.

Table of Contents