Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 1. Introduction to the JBoss Server Migration Tool
1.1. About Red Hat JBoss Enterprise Application Platform
Red Hat JBoss Enterprise Application Platform (JBoss EAP) is a middleware platform built on open standards that is compatible with the Jakarta Enterprise Edition 10 specification.
The 8.0 release of JBoss EAP is a Jakarta EE Jakarta Enterprise Edition compatible implementation for Web Profile, Core Profile, and Full Platform specifications. The 8.0 release is also a certified implementation of the Jakarta EE Jakarta Enterprise Edition Web Profile, Core Profile, and the Full Platform specifications.
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 Jakarta 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 Use of EAP_PREVIOUS_HOME, EAP_NEW_HOME and MIGRATION_TOOL_HOME in this document
In this document, the variable EAP_PREVIOUS_HOME is used to denote the path to the source server installation. Replace this variable with the actual path to your source server installation. In addition, the variable EAP_NEW_HOME is used to denote the path to the target server installation. Replace this variable with the actual path to your target server installation. Also, the variable MIGRATION_TOOL_HOME states the directory where the migration tool is installed.
1.2.1. JBoss EAP Installation Path
-
If you installed JBoss EAP using the
.zipfile install method, the install directory is thejboss-eap-8.0directory where you extracted the.zipfile. -
If you installed JBoss EAP using the RPM install method, the install directory is
/opt/rh/eap8/root/usr/share/wildfly/. If you used the installer to install JBoss EAP, the default path for
EAP_NEW_HOMEis${user.home}/EAP-8.0.0:-
For Red Hat Enterprise Linux, Solaris, and HP-UX:
/home/USER_NAME/EAP-8.0.0/ -
For Microsoft Windows:
C:\Users\USER_NAME\EAP-8.0.0\
-
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
EAP_NEW_HOMEis${user.home}/jbdevstudio/runtimes/jboss-eap:-
For Red Hat Enterprise Linux:
/home/USER_NAME/jbdevstudio/runtimes/jboss-eap/ -
For Microsoft Windows:
C:\Users\USER_NAME\jbdevstudio\runtimes\jboss-eaporC:\Documents and Settings\USER_NAME\jbdevstudio\runtimes\jboss-eap\
-
For Red Hat Enterprise Linux:
