Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 3. Upgrading to the Red Hat JBoss Core Services Apache HTTP Server 2.4.57
The steps to upgrade to the latest Red Hat JBoss Core Services (JBCS) release differ depending on whether you previously installed JBCS from RPM packages or from an archive file.
Upgrading JBCS when installed from RPM packages
If you installed an earlier release of the JBCS Apache HTTP Server from RPM packages on RHEL 7 or RHEL 8 by using the yum groupinstall
command, you can upgrade to the latest release. You can use the yum groupupdate
command to upgrade to the 2.4.57 release on RHEL 7 or RHEL 8.
JBCS does not provide an RPM distribution of the Apache HTTP Server on RHEL 9.
Upgrading JBCS when installed from an archive file
If you installed an earlier release of the JBCS Apache HTTP Server from an archive file, you must perform the following steps to upgrade to the Apache HTTP Server 2.4.57:
- Install the Apache HTTP Server 2.4.57.
- Set up the Apache HTTP Server 2.4.57.
- Remove the earlier version of Apache HTTP Server.
The following procedure describes the recommended steps for upgrading a JBCS Apache HTTP Server 2.4.51 release that you installed from archive files to the latest 2.4.57 release.
Prerequisites
- If you are using Red Hat Enterprise Linux, you have root user access.
- If you are using Windows Server, you have administrative access.
- The Red Hat JBoss Core Services Apache HTTP Server 2.4.51 or earlier was previously installed in your system from an archive file.
Procedure
- Shut down any running instances of Red Hat JBoss Core Services Apache HTTP Server 2.4.51.
- Back up the Red Hat JBoss Core Services Apache HTTP Server 2.4.51 installation and configuration files.
- Install the Red Hat JBoss Core Services Apache HTTP Server 2.4.57 using the .zip installation method for the current system (see Additional Resources below).
Migrate your configuration from the Red Hat JBoss Core Services Apache HTTP Server version 2.4.51 to version 2.4.57.
NoteThe Apache HTTP Server configuration files might have changed since the Apache HTTP Server 2.4.51 release. Consider updating the 2.4.57 version configuration files rather than overwrite them with the configuration files from a different version, such as the Apache HTTP Server 2.4.51.
- Remove the Red Hat JBoss Core Services Apache HTTP Server 2.4.51 root directory.