Chapter 1. Introduction to JBoss Core Services Apache HTTP Server installation

Red Hat JBoss Core Services is a set of supplementary software for Red Hat JBoss middleware products. Red Hat JBoss Core Services provides supplementary software, such as the Apache HTTP Server, that is common to multiple JBoss middleware products. This supplementary software is packaged under Red Hat JBoss Core Services to allow for faster distribution of updates, and for a more consistent update experience.

For a full list of components that are supported by Red Hat JBoss Core Services, see the Core Services Apache HTTP Server Component Details web page.

Note

Before you attempt to access the Core Services Apache HTTP Server Component Details web page, you must ensure that you have an active Red Hat subscription, and you are logged in to the Red Hat Customer Portal.

1.1. JBoss Core Services Apache HTTP Server

The Red Hat JBoss Core Services Apache HTTP Server is used in multiple Red Hat JBoss middleware products. The Apache HTTP Server processes requests that web clients send over the Hypertext Transfer Protocol (HTTP).

In older JBoss product releases, the Apache HTTP Server was distributed with each JBoss product separately. Starting from the following product versions, each JBoss middleware product uses the JBoss Core Services distribution of the Apache HTTP Server:

  • Red Hat JBoss Enterprise Application Platform (JBoss EAP) 7.0 and later versions
  • Red Hat JBoss Web Server 3.1 and later versions
Important

Both JBoss Core Services and Red Hat Enterprise Linux provide separate distributions of the Apache HTTP Server.

Consider the following differences between the Apache HTTP Server distributions that are available with JBoss Core Services (JBCS) and Red Hat Enterprise Linux (RHEL):

  • You can install the JBCS Apache HTTP Server from an archive file or RPM package. You can only install the RHEL Apache HTTP Server from an RPM package.
  • The JBCS Apache HTTP Server provides the mod_security module, the mod_proxy_uwsgi module, and the loadbalancing modules mod_jk and mod_cluster.
  • The JBCS Apache HTTP Server does not provide or support the mod_php module. The RHEL Apache HTTP Server supports the mod_php module.

1.2. Supported operating systems for the JBoss Core Services Apache HTTP Server

The JBoss Core Services Apache HTTP Server supports different versions of the Red Hat Enterprise Linux and Microsoft Windows operating systems.

Additional resources

1.3. Installation methods for the JBoss Core Services Apache HTTP Server

You can install the JBoss Core Services Apache HTTP Server on supported Red Hat Enterprise Linux and Microsoft Windows systems by using archive installation files that are available for each platform. You can also install the JBoss Core Services Apache HTTP Server on supported Red Hat Enterprise Linux systems by using RPM packages.

1.4. Upgrading to the JBoss Core Services Apache HTTP Server 2.4.37

If you have previously installed an earlier version of the JBoss Core Services Apache HTTP Server from an archive file, you can upgrade to the JBoss Core Services Apache HTTP Server 2.4.37 release.

The upgrade process includes the following steps:

  1. Installing the Apache HTTP Server 2.4.37.
  2. Setting up the Apache HTTP Server 2.4.37.
  3. Removing an earlier version of Apache HTTP Server.

Prerequisites

  • You have administrative access on Windows Server.
  • You are using a system where the JBoss Core Services Apache HTTP Server 2.4.29 or earlier was installed from a .zip archive.

Procedure

  1. Shut down any running instances of the Apache HTTP Server 2.4.29.
  2. Back up the Apache HTTP Server 2.4.29 installation and configuration files.
  3. Install the Apache HTTP Server 2.4.37 by using the .zip installation method for the current system. For more information see Additional Resources at the end of this section.

  4. Migrate your configuration from the Apache HTTP Server version 2.4.29 to version 2.4.37.

    Note

    The JBoss Core Services configuration files might have changed since the Apache HTTP Server 2.4.29 release. Update the 2.4.37 version configuration files rather than overwrite them with the configuration files from a different version, such as the Apache HTTP Server 2.4.29.

  5. Remove the Apache HTTP Server 2.4.29 root directory.

Additional resources

1.5. Key differences between Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux 8

This section provides an overview of some of the key changes introduced in Red Hat Enterprise Linux 8.

Removed security functionality
All-numeric user and group names are deprecated in Red Hat Enterprise Linux 7 and their support is completely removed in Red Hat Enterprise Linux 8.
Memory management
In Red Hat Enterprise Linux 7, the existing memory bus has capacity for 48/46 bit of virtual/physical memory addressing, and the Linux kernel implements 4 levels of page tables to manage these virtual addresses to physical addresses. With the extended address range, the memory management in Red Hat Enterprise Linux 8 supports the implementation of 5-level page tables, to allow handling of the expanded address range. In Red Hat Enterprise Linux 8, support for 5-level page tables is disabled by default, even if the system supports this feature.
XFS supports
Red Hat Enterprise Linux 7 can mount XFS file systems with shared copy-on-write data extents only in the read-only mode. In Red Hat Enterprise Linux 8, the XFS file system supports shared copy-on-write data extent functionality. This feature enables two or more files to share a common set of data blocks.
NFS configuration
In Red Hat Enterprise Linux 7, the NFS configuration is located in the /etc/sysconfig/nfs file. In Red Hat Enterprise Linux 8, the NFS configuration is located in the /etc/nfs.conf file.
Note

For more information about the differences between Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux 8, see Considerations in adopting RHEL 8.

1.6. Additional resources (or Next steps)