2.9. Installing Native Components and Utilities

Native Components are optional components which have been compiled to be optimized for a specific operating system and architecture. In some cases, using the native components may provide performance improvements. Native Components include native support for HornetQ (AIO), and the Tomcat Native Library. For more information, see Section 2.10.2, “Configure JBoss EAP 6 as a Service in Red Hat Enterprise Linux (Zip, Installer)” and the Jsvc section of the Administration and Configuration Guide.
Native Utilities are optional utilities specific to each supported operating system and architecture. These include scripts and utilities for installing JBoss EAP 6 as a service in your operating system, and generating SSL encryption keys and certificates.
In addition to Native Components and Native Utilities, Webserver Connector Natives are used for load balancing and clustering. See the Administration and Configuration Guide to configure Webserver Connector Natives.
Report a bug

2.9.1. Install Native Components and Native Utilities (Zip, Installer)

Prerequisites

  • Install JBoss EAP 6 using the Zip installation, Graphical Installer, or Text-based Installer:
  • Access to the Management CLI or the Management Console for the JBoss EAP 6 server. Refer to Launch the Management CLI or Log in to the Management Console in the Administration and Configuration Guide.
  • For Native Components in Red Hat Enterprise Linux 6 and 7 environments:
    • Ensure that the Apache Portability Runtime (APR) and OpenSSL libraries are installed and updated to the latest version available in the official repositories. Outdated OpenSSL libraries can cause issues as more recent JBoss EAP Native Components require features not available in older versions of OpenSSL. To ensure they are updated, open a terminal and enter the following command: 
      sudo yum update apr apr-util openssl
    • If you intend to use the Tomcat Native Library which is part of the JBoss EAP Native Components, the operating system package tomcatjss must be removed before installation.
  • For Native Components in a HP-UX environment, OpenSSL must be installed.

Procedure 2.14. Download and Install Native Components

  1. Download the Native Components package for your operating system and architecture from the Red Hat Customer Portal. You can download the packages from the same location specified in Section 2.3.1, “Download JBoss EAP 6 (Zip Installation)”.
  2. Extract the downloaded Native Components zip archive over your JBoss EAP 6 installation.
    You can verify a successful extraction by checking if there is a new folder for your operating system and architecture in EAP_HOME/modules/system/layers/base/org/jboss/as/web/main/lib/.
  3. Using the Management CLI, activate the native components for the web subsystem with the following command: 
    /subsystem=web:write-attribute(name=native,value=true)
  4. Restart the JBoss EAP 6 server to apply the changes.

Procedure 2.15. Download and Install Native Utilities

  1. Download the Native Utilities package for your operating system and architecture from the Red Hat Customer Portal. You can download the packages from the same location specified in Section 2.3.1, “Download JBoss EAP 6 (Zip Installation)”.
  2. Extract the downloaded Native Components zip archive over your JBoss EAP 6 installation.
    You can verify a successful extraction by checking if there is native directory in EAP_HOME/modules/system/layers/base/.
  3. Refer to procedures in the JBoss EAP documentation suite and on the Red Hat Customer Portal to configure specific native utilities features.
Report a bug

2.9.2. Install Native Components and Native Utilities (RPM Installation)

You can use the RPM installation method to install native components, utilities and all the corresponding dependencies only if you have installed EAP using RPM installation method. The RPM package method of installing natives is appropriate for Red Hat Enterprise Linux 5, 6 and 7. This topic covers the steps required to install the native components and utilities using the command line.

Prerequisites

Procedure 2.16. Install Native Components and Native Utilities

  1. Install native components and utilities

    To install native components and utilities in Red Hat Enterprise Linux 5, 6 and 7 (with their dependencies) run the following command using your administration account, replacing package_name with name of the native component which you need to install: 
    yum install package_name
    You can install these native components: mod_cluster-native, mod_jk, mod_rt, mod_snmp, apache-commons-daemon-jsvc-eap6, httpd, httpd-devel, jbossas-hornetq-native, jbossas-jbossweb-native.

    Important

    The native components jbossas-hornetq-native and jbossas-jbossweb-native are installed by default when you run the yum groupinstall jboss-eap6 command to install JBoss EAP 6 group package. If you have used Section 2.6.7, “Install JBoss EAP 6 (Graphical RPM Installation)” or Section 2.6.8, “Install JBoss EAP 6 (Text-based RPM Installation)” for JBoss EAP 6 installation you need not install jbossas-hornetq-native and jbossas-jbossweb-native.

    Note

    It is important to give the correct package name in order to install a specific native component. Package names are case sensitive. In Red Hat Enterprise Linux 7 the name of the httpd package is httpd22. Therefore the package httpd must be replaced with httpd22 when you run yum install package_name command for installing Apache HTTP server in Red Hat Enterprise Linux 7.

  2. Restart the server

    Restart the JBoss EAP 6 server to apply the changes
Report a bug