Chapter 1. Introduction
1.1. About Red Hat JBoss Enterprise Application Platform 7
Red Hat JBoss Enterprise Application Platform 7 (JBoss EAP) is a middleware platform built on open standards and compliant with the Java Enterprise Edition 7 specification.
JBoss EAP provides two operating modes for server instances.
- Standalone server
- The standalone server operating mode represents running JBoss EAP as a single server instance.
- Managed domain
- The managed domain operating mode allows for the management of multiple JBoss EAP instances from a single control point.
JBoss EAP includes APIs and development frameworks for quickly developing secure and scalable Java EE applications. Many of the APIs and capabilities that are exposed to applications deployed to JBoss EAP servers are organized into subsystems that are configured in the server configuration files. For example, you configure database access information in the
datasources subsystem so that it can be accessed by applications deployed to JBoss EAP standalone servers or managed domains. The introduction of new features and deprecation of other features can require modification of the server configurations from one release of JBoss EAP to another.
For more information about Red Hat JBoss Enterprise Application Platform, see the Product Documentation for JBoss EAP located on the Red Hat Customer Portal.
1.2. About the JBoss Server Migration Tool
Migrating an existing application server configuration from one release to another is a complex task. To plan and execute a successful migration not only requires a complete understanding the current server configuration, but also knowledge of features and changes in the target server configuration. With a manual migration, you generally copy and edit several configuration files, and then make the updates needed to keep the same behavior in the target release. If this is not done correctly, the target server does not work as expected. This is often because some functionality is not supported by the target server.
The JBoss Server Migration Tool is a Java application that automatically migrates JBoss EAP server configurations with minimal or no interaction required. It is the preferred method to update your JBoss EAP server configuration to include the new features and settings in JBoss EAP 7 while keeping your existing configuration. The JBoss Server Migration Tool reads your existing source server configuration files and adds configurations for any new subsystems, updates the existing subsystem configurations with new features, and removes any obsolete subsystem configurations.
The JBoss Server Migration Tool supports the migration of standalone servers and managed domains for the following configurations.
- Migrating to JBoss EAP 7.2
The JBoss Server Migration Tool ships with JBoss EAP 7.2, so there is no separate download or installation required. This tool supports migration to JBoss EAP 7.2 from the previous major release of the product, which is JBoss EAP 6.4, and from the previous minor release of the product, which is JBoss EAP 7.1.
You run the tool by executing the
jboss-server-migrationscript located in the
EAP_HOME/bindirectory. For more information about how to run the tool, see Running the JBoss Server Migration Tool.
It is recommended that you use this version of the JBoss Server Migration Tool to migrate your server configuration to JBoss EAP 7.2 as this version of the tool is supported.Important
Migration to JBoss EAP 7.2 from JBoss EAP 7.0 is provided as Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
See Technology Preview Features Support Scope on the Red Hat Customer Portal for information about the support scope for Technology Preview features.
- Migrating from WildFly to JBoss EAP
If you want to migrate from the WildFly server to JBoss EAP, you must download the latest binary distribution of the JBoss Server Migration Tool from the wildfly-server-migration GitHub repository. This open source, standalone version of the tool supports migration from several versions of the WildFly server to JBoss EAP. For information about how to install and run this version of the tool, see the JBoss Server Migration Tool User Guide.Important
The binary distribution of the JBoss Server Migration Tool is not supported. If you are migrating from a previous release of JBoss EAP, it is recommended that you use this supported version of the tool to migrate your server configuration to JBoss EAP 7.2 instead.
1.3. About the Use of EAP_HOME in this Document
In this document, the variable
EAP_HOME is used to denote the path to the target server installation. Replace this variable with the actual path to your server installation.
EAP_HOME is a replaceable variable, not an environment variable.
JBOSS_HOME is the environment variable used in scripts.
JBoss EAP Installation Path
If you installed JBoss EAP using the ZIP install method, the install directory is the
jboss-eap-7.2directory where you extracted the ZIP archive.
If you installed JBoss EAP using the RPM install method, the install directory is
If you used the installer to install JBoss EAP, the default path for
For Red Hat Enterprise Linux, Solaris, and HP-UX:
For Microsoft Windows:
- For Red Hat Enterprise Linux, Solaris, and HP-UX:
If you used the JBoss Developer Studio installer to install and configure the JBoss EAP server, the default path for
For Red Hat Enterprise Linux:
For Microsoft Windows:
C:\Documents and Settings\USER_NAME\jbdevstudio\runtimes\jboss-eap\
- For Red Hat Enterprise Linux: