Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Related Manuals for Red Hat APPLICATION STACK 1.1 - RELEASE NOTES
Summary of Contents for Red Hat APPLICATION STACK 1.1 - RELEASE NOTES
- Page 1 Red Hat Application Stack V.1.1 Release Notes ISBN: N/A Publication date:...
- Page 2 Red Hat Application Stack V.1...
- Page 3 Red Hat Application Stack V.1.1 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 32-bit Sun SDK ..............3 1.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. The BEA JVM is available from the Red Hat Enterprise Linux (AS/ES) Extras channel. The Sun SDK must be downloaded directly from Sun (instructions below). - Page 10 Chapter 2. Configuring the Ja... for Linux. Note If you don't want/need to use the SysV service scripts you can also install the "self-extracting file" for Linux instead. 2. Install java-1.4.2-sun-compat or java-1.5.0-sun-compat (optional) This step is only necessary if you want to use the SysV service scripts, which we recommend for production servers.
-
Page 11: Installing A Bea Or Ibm Sdk
Installing a BEA or IBM SDK system allows different versions of Java, from different sources to alternatives co-exist on your system. You should make sure the Sun one is selected so that the service script uses the one you want. As root, issue the following command: /usr/sbin/alternatives --config java and make sure the Sun one is selected (marked with a '+'), or select it by entering its number... -
Page 12: Install The Package
Chapter 2. Configuring the Ja... available from these channels. Make sure you also install the subpackages. -devel There is no BEA JRockit JVM for the x86_64 architecture at this time, but the BEA i386 JVM will work on x86_64 and it is available from the x86_64 channel as well. 2. -
Page 13: Using Up2Date / Dvd
/etc/sysconfig/rhn/sources up2date 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. After the installation is complete, remove the line you added to in Step 3. -
Page 15: Installing Red Hat Application Stack
Chapter 3. Installing Red Hat Application Stack To install Red Hat Application Stack V.1.1: 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 16 Section 2.2, “ Using / DVD ” to mount the DVD and set up2date up the local RHN channel (steps 1-3). Then as root run: up2date --exclude=jbossas-ejb3 --installall RedHat-Application-Stack-V1 Note If you wish to use the package (needs a working Java 1.5 jbossas-ejb3...
- Page 17 After the installation is complete, be sure to follow step 5 from Section 2.2, “ Using up2date / DVD ” to prevent unnecessary warnings. Note You may need to install the following packages to satisfy dependencies before executing the above command, if they are not already installed: •...
- Page 18 Chapter 3. Installing Red Hat... • For MySQL: • Update MySQL: mysql_update • Start MySQL: /sbin/service mysqld start • Restore your data: mysql -p < /tmp/mysqldumpfile.sql • Start the http daemon: /sbin/service httpd start The installation is now complete.
-
Page 19: 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 20 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 21: 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 22: Using The Jbossas-* Commands From Any Directory
Chapter 4. Using JBoss AS To create additional JBoss AS configurations besides the provided 'default', '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 23: Running Multiple Instances Of Jboss As
Running multiple instances of JBoss AS export JBOSS_HOME=/var/lib/jbossas 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 24: Running Multiple Instances Of Jboss As Using Different Sets Of Ports
Chapter 4. Using JBoss AS 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... -
Page 25: Running Multiple Instances Of Jboss As Binding To Different Local Ip Addresses
Running multiple instances of JBoss AS 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: . -
Page 26: More Information
Chapter 4. Using JBoss AS 6. More Information More general documentation for JBoss AS is available under /usr/share/doc/jbossas-4.0.5... -
Page 27: Known Issues
These will eventually be fixed in future releases or updates. The following bugs, identified by number, have been filed in Bugzilla. The Bugzilla's URL is http://bugzilla.redhat.com/ List of bug numbers: Generic: 200992, 206026, 220605, 220606, 220607,220608, 220611, 220613, 220616, 223081, 223085 With a Sun 1.4.2 SDK (32-bit): 200992, 203668... -
Page 29: Export Control
Chapter 6. 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 1.1 - RELEASE NOTES and is the answer not in the manual?
Questions and answers