4.4. Install JBoss Enterprise Application Platform 6 using the Red Hat Network (RPM installation)

Summary

The RPM package method of installing JBoss Enterprise Application Platform 6 is appropriate for Red Hat Enterprise Linux 6. The recommended installation method is to use the Red Hat Network (RHN) to manage your server subscriptions and channels.

Important

The jbossas-hornetq-native package is included for high availability in JBoss Enterprise Application Platform 6 but it is not activated by default.
Prerequisites

To install JBoss Enterprise Application Platform 6 using the Red Hat Network, the host server must meet the following requirements:

  • The server must be registered on the Red Hat Network.
  • The server must be subscribed to the Red Hat Enterprise Linux Server (v.6) base software channel.
  • The server must be subscribed to the JBoss Application Platform (v 6) for 6Server x86_64 sub-channel. The sub-channel is in the Additional Services Channels for Red Hat Enterprise Linux 6 for x86_64 group.
  • A Java 6 JDK must be installed. If you wish to use a Java 7 JDK, you need to install both versions. To configure which JDK your system uses as the default, run the following command, with superuser privileges: 
    [root@host /root]# alternatives --config java
    A plus sign (+) is displayed beside the current default. Follow the on-screen instructions to make any changes, or press the Enter key to keep the current selection.
A system configured for RHN installation of JBoss Enterprise Application Platform 6

Figure 4.1. A system configured for RHN installation of JBoss Enterprise Application Platform 6

Procedure 4.3. Task

Access and install the RPM package by using the YUM install via the Red Hat Network.

  1. Install the RPM package by using YUM and the Red Hat Network

    Use YUM to install the default JBoss Enterprise Application Platform 6 group package by using the groupinstall command. 
    [user@host ~]$ yum groupinstall jboss-eap6

  2. Configure init options.

    The RPM install contains init scripts for launching the server. The configuration for the init scripts are contained in serveral additional files. Refer to Section 4.5, “RPM Installation Configuration Files” for details about these files and the options contained within.
Result

The installation is complete. Refer to Section A.1, “RPM Package List and Dependencies” for a complete list of all the packages installed.