2.6. RPM Installation
2.6.1. About JBoss EAP 6 Software Channels
Installing JBoss EAP 6 via RPM requires a subscription to several software channels. Subscription to both the Red Hat Enterprise Linux Server base software channel and a specific JBoss EAP 6 channel is required.
Note
From Red Hat Enterprise Linux 7, the term
channel was replaced with the term repository. In these instructions only the term channel is used.
Up to JBoss EAP 6.3.2 the choice of JBoss EAP channel is determined only by the Red Hat Enterprise Linux version and the hardware architecture. A subscription to this, the current channel provides the latest JBoss EAP release.
From JBoss EAP 6.3.3 you can either subscribe to the current JBoss EAP channel or a minor channel that provides a specific minor release and all applicable patches. This allows you to maintain the same minor version of JBoss EAP 6, while still staying current with high severity and security patches.
Warning
Library version conflicts occur when using RPM packages to install both JBoss Web Server 3 and JBoss EAP 6 on the same machine. To workaround the issue, you can install either JBoss Web Server 3 or JBoss EAP 6 using the RPM installation method, and the other using the ZIP installation method.
2.6.2. JBoss EAP Channel Naming Convention
The naming convention for the current channel is
jbappplatform-6-ARCHITECTURE-server-6-rpm. Installing JBoss EAP 6.4 on an x86_64 architecture and Red Hat Enterprise Linux 6 would require a subscription to the jbappplatform-6-x86_64-server-6-rpm channel.
The naming convention of the minor version channel for Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6 is
jbappplatform-EAP_VERSION-ARCHITECTURE-server-RHEL_VERSION-rpm.
The naming convention of the minor version channel for Red Hat Enterprise Linux 7 is
jb-eap-EAP_VERSION-for-rhel-7-server-rpms for x86_64 architecture and jb-eap-EAP_VERSION-for-rhel-7-for-power-rpms for ppc64 architecture
- EAP_VERSION
- This is the major and minor version of JBoss EAP. An EAP_VERSION value of
6.4would install JBoss EAP 6.4, while a value of6would install JBoss EAP 6. - ARCHITECTURE
- This is either
i386,x86_64orppc. - RHEL_VERSION
- This is either
5for Red Hat Enterprise Linux 5,6for Red Hat Enterprise Linux 6 or7for Red Hat Enterprise Linux 7.
2.6.3. How to Subscribe to the JBoss EAP 6 Current Channel
The subscription command depends on the registration method - Red Hat Subscription Manager or Red Hat Network Classic. Red Hat Subscription Manager is the only method available on Red Hat Enterprise Linux 7.
For Red Hat Subscription Manager:
- Ensure that your Red Hat Enterprise Linux system is registered to your account using Red Hat Subscription Manager. For more information, see the Red Hat Subscription Management documentation.
- Enter the following command to subscribe to the JBoss EAP 6 current repository:
subscription-manager repos --enable=jb-eap-6-for-rhel-7-server-rpms
For Red Hat Network Classic:
- Ensure that your Red Hat Enterprise Linux system is registered to your account using Red Hat Network Classic. For more information, see the this Customer Portal solution: https://access.redhat.com/solutions/11216.
- Enter the following command to subscribe to the JBoss EAP 6 current channel:
rhn-channel --add -c jbappplatform-6-x86_64-server-6-rpmNote
Therhn-channelcommand does not provide an error message if the specified software channel does not exist. Before proceeding, confirm the registration was successful by listing the subscribed channels. To do this, enter the following command:rhn-channel-l
2.6.4. How To Subscribe to the JBoss EAP 6 Minor Channel
The subscription command depends on the registration method - Red Hat Subscription Manager or Red Hat Network Classic. Red Hat Subscription Manager is the only method available on Red Hat Enterprise Linux 7.
For Red Hat Subscription Manager:
- Ensure that your Red Hat Enterprise Linux system is registered to your account using Red Hat Subscription Manager. For more information, see the Red Hat Subscription Management documentation.
- Enter the following command to subscribe to the JBoss EAP 6 minor repository:
subscription-manager repos --enable=jb-eap-6.4-for-rhel-7-server-rpms
For Red Hat Network Classic:
- Ensure that your Red Hat Enterprise Linux system is registered to your account using Red Hat Network Classic. For more information, see the this Customer Portal solution: https://access.redhat.com/solutions/11216.
- Enter the following command to subscribe to the JBoss EAP 6 minor channel:
rhn-channel --add -c jbappplatform-6.4-x86_64-server-6-rpmNote
Therhn-channelcommand does not provide an error message if the specified software channel does not exist. Before proceeding, confirm the registration was successful by listing the subscribed channels. To do this, enter the following command:rhn-channel-l
2.6.5. Support for Changing Subscription Channels
Over the lifespan of a JBoss EAP 6.3.3 (or greater) installation, you may want to change the software subscription from one JBoss EAP channel to another. Changing between channels is supported but with the following conditions.
- Changing from the current channel to a minor channel
- Supported if changing to the latest minor channel.
- Changing from a minor current channel to another minor channel
- Supported if changing to the next minor JBoss EAP version. For example, changing from JBoss EAP 6.3 to JBoss EAP 6.4 is supported, but from JBoss EAP 6.3 to JBoss EAP 6.5 is not supported.
- Changing from a minor channel to the current channel
- Supported if changing from the latest minor channel.
2.6.6. How to Change from the Current Channel to the Minor Channel
Complete this procedure if a Red Hat Enterprise Linux system is subscribed to the
current channel and you want to instead switch to the minor channel. Doing so will ensure that the system will only receive updates to the JBoss EAP 6.4 RPMs and it will not be updated to a later version.
Before changing channel, it is necessary to ensure the JBoss EAP installation has all applicable updates applied.
For Red Hat Classic, enter the following commands to update the host and unsubscribe from the
current channel and instead subscribe to the minor channel.
yum updaterhn-channel --remove -c jbappplatform-6-x86_64-server-6-rpmrhn-channel --add -c jbappplatform-6.4-x86_64-server-6-rpmNote
The
rhn-channel command does not provide an error message if the specified software channel does not exist. Before proceeding, confirm the registration was successful by listing the subscribed channels. To do this, enter the command:
rhn-channel-l
For Red Hat Subscription Manager, enter the following commands to update the host and unsubscribe from the
current channel and instead subscribe to the minor channel.
yum updatesubscription-manager repos --disable=jb-eap-6-for-rhel-7-server-rpms --enable=jb-eap-6.4-for-rhel-7-server-rpms2.6.7. Install JBoss EAP 6 (Graphical RPM Installation)
Prerequisites:
Summary
The Graphical RPM package method of installing JBoss EAP 6 is available for Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This topic covers the steps required to complete the installation.
Procedure 2.9. Install JBoss EAP 6 (Graphical RPM Installation)
Use PackageKit to graphically install JBoss EAP 6 on your target machine.
Launch PackageKit
PackageKit is an open source package management software installed as part of Red Hat Enterprise Linux. On the target machine launch PackageKit by selecting. - Type
jboss-eap6in the search box and then press the button. You will be presented with the JBoss EAP 6 package in the result box. - Select the JBoss EAP 6 package and press the button. See figure below.
Figure 2.2. JBoss EAP 6 PackageKit Install
- Follow the rest of the steps to install JBoss EAP 6 on your target machine.
Result
The installation is complete and JBoss EAP 6 is installed in your target machine.
2.6.8. Install JBoss EAP 6 (Text-based RPM Installation)
Prerequisites:
Summary
The RPM package method of installing JBoss EAP 6 is appropriate for Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, and Red Hat Enterprise Linux 7. This topic covers the steps required to install an instance using the command line.
Procedure 2.10. Install JBoss EAP 6 (Text-based RPM Installation)
Install the RPM packages
Use YUM to install the default JBoss EAP 6 group package by using thegroupinstallcommand.yum groupinstall jboss-eap6Configure initialization options.
The RPM install contains initialization scripts for launching the server. The configuration for the initialization scripts are contained in several additional files. Refer to Section A.4, “RPM Installation Configuration Files for JBoss EAP 6” for details about these files and the options contained within.
Result
The installation is complete. The default EAP_HOME path for the RPM installation is /usr/share/jbossas. Refer to Section A.3, “RPM Package List for JBoss EAP 6” for a complete list of all the packages installed.
2.6.9. Configure RPM Service Properties
This section shows you how to configure the RPM service properties and other startup options for your JBoss EAP installation. Note that it is recommended to back up your configuration files before making modifications.
See Section A.4, “RPM Installation Configuration Files for JBoss EAP 6” for a listing of all available startup configuration options for an RPM installation.
- Specify the server configuration file.
- When starting a standalone server, the
standalone.xmlfile is used by default. When running in a managed domain, thehost.xmlfile is used by default. You can start JBoss EAP with a different configuration file by setting theJBOSS_SERVER_CONFIGproperty in the appropriate RPM configuration file, for example,/etc/sysconfig/jbossas. See Section A.4, “RPM Installation Configuration Files for JBoss EAP 6” for the list of RPM configuration files.JBOSS_SERVER_CONFIG="standalone-full-ha.xml"
- Set JVM options or Java properties.
- You can specify JVM options or Java properties to pass into the JBoss EAP startup script by editing the startup configuration file. This file is
EAP_HOME/bin/standalone.conffor a standalone server orEAP_HOME/bin/domain.conffor a managed domain. The below example configures the heap size and binds the JBoss EAP management interfaces to an IP address.JAVA_OPTS="$JAVA_OPTS -Xms2048m -Xmx2048m" JAVA_OPTS="$JAVA_OPTS -Djboss.bind.address.management=192.168.0.1"
