This document guides usage of the Server Migration Tool, when the source server is JBoss EAP 6.4, and the target server is JBoss EAP 7.
---------------------------------------------------------- ---- JBoss Server Migration Tool ----------------------- ---------------------------------------------------------- Retrieving servers... 05:26:35,601 INFO [org.wildfly.migration.core.logger] (main) SOURCE server name: EAP, version: 6.4.0.GA. 05:26:35,631 INFO [org.wildfly.migration.core.logger] (main) TARGET server name: EAP, version: 7.0.0.GA.
This specific server migration consists of:
migration of the standalone server
migration of the host/domain controller
Currently the migration of the host/domain controller is not yet supported.
The standalone server migration is just the migration of each standalone XML config file, and as a starting point, in case the tool is running in interactive mode, the user is asked if all config files should be migrated:
Server migration starting... 05:26:35,648 INFO [org.wildfly.migration.core.logger] (main) Scanning for standalone server configurations... 05:26:35,648 INFO [org.wildfly.migration.core.logger] (main) /Users/emmartins/wildfly/dist/jboss-eap-6.4/standalone/configuration/standalone.xml 05:26:35,649 INFO [org.wildfly.migration.core.logger] (main) /Users/emmartins/wildfly/dist/jboss-eap-6.4/standalone/configuration/standalone-ha.xml 05:26:35,649 INFO [org.wildfly.migration.core.logger] (main) /Users/emmartins/wildfly/dist/jboss-eap-6.4/standalone/configuration/standalone-full.xml 05:26:35,649 INFO [org.wildfly.migration.core.logger] (main) /Users/emmartins/wildfly/dist/jboss-eap-6.4/standalone/configuration/standalone-full-ha.xml Migrate all configurations? yes/no?
To migrate all config files the user should input y or yes, otherwise the user should input n or no, and then the tool will go through each config file, asking the user if migration of such config file should be done:
Migrate configuration /Users/emmartins/wildfly/dist/jboss-eap-6.4/standalone/configuration/standalone.xml ? yes/no?
Please note that if the tool is running in non interactive mode all config files will be migrated.
The standalone config file migration consists of:
Subsystems Migration
Security Realms Migration
Management Interfaces Migration
Socket Bindings Migration
Deployments Migration
This task migrates the subsystems configuration in the source standalone server config file, which consist of:
Remove any unsupported subsystems
Migrate the configuration of deprecated legacy subsystems, into related replacements subsystems
Update the configuration of supported subsystems, to match defaults on EAP 7
Add EAP 7 new subsystems, which are included in the default EAP 7 standalone server config files
The starting of the subsystems migration is indicated by the message:
04:25:23,584 INFO [org.wildfly.migration.core.logger] (main) Migrating subsystems...
The end of the subsystems migration is indicated by the message:
04:25:24,069 INFO [org.wildfly.migration.core.logger] (main) Subsystems migration done.
The batch-jberet is a EAP 7 subsystem that provides support for the Java EE 7 Batch Specification, and it's default configuration is added to the migrated configuration file.
Please note that such subsystem, and related extension, is added without any interaction with the user, the migration console and log(s) will only indicate it was added, an example:
19:57:01,695 INFO [org.wildfly.migration.core.logger] (main) Extension org.wildfly.extension.batch.jberet added. 19:57:01,705 INFO [org.wildfly.migration.core.logger] (main) Subsystem batch-jberet added.
The Bean Validation functionality was previously provided by the ee subsystem on EAP 6, but on EAP 7 such functionality is provided the subsystem bean-validation, and it's default configuration is added to the migrated configuration file.
Please note that such subsystem, and related extension, is added without any interaction with the user, the migration console and log(s) will only indicate it was added, an example:
19:57:01,732 INFO [org.wildfly.migration.core.logger] (main) Extension org.wildfly.extension.bean-validation added. 19:57:01,742 INFO [org.wildfly.migration.core.logger] (main) Subsystem bean-validation added.
The cmp subsystem is not supported by EAP 7, if found its configuration will be removed from the migrated configuration file, and the console and log(s) will display the following message:
17:28:54,865 INFO [org.wildfly.migration.core.logger] (main) Unsupported subsystem cmp removed.
The extension that provides the removed subsystem, if present in the configuration file, will also be removed, and in such case the console and log(s) will display the following message:
17:28:54,898 INFO [org.wildfly.migration.core.logger] (main) Unsupported extension org.jboss.as.cmp removed.
EAP 7 ee Subsystem provides new Java EE 7 functionalities, and it's configuration may be used to:
configure instances of Java EE 7 Concurrency Utilities, such as container managed Executors
define the Java EE 7 default resources, such as the default data source, by specifying the original JNDI addresses
With respect to the Concurrency Utilities instances configuration, the tool configures the exact same instances present in all EAP 7 default configurations, an action which does not requires any interaction with the user. The log will simply indicate the instances were added:
19:56:44,227 INFO [org.wildfly.migration.core.logger] (main) EE Concurrency Utilities added.
With respect to the definition of Java EE 7 default resources, the tool will look for the resources present in default EAP 6 configurations, and use these if present, but if that's not the case then the user input will be required, the tool will show all available resources in the configuration, and ask the user to pick the one which should be set as the default, or provide manually the JNDI address of the original resource. An example of such interaction, in this case to define the default datasource, when migrating a configuration file with two configured datasources, ExampleDS1 and ExampleDS2:
19:56:44,288 INFO [org.wildfly.migration.core.logger] (main) Default datasource not found. 0. ExampleDS1 1. ExampleDS2 2. Unconfigured data source, I want to enter the JNDI name... Please select Java EE's Default Datasource: (0): 0 19:56:56,017 INFO [org.wildfly.migration.core.logger] (main) Datasource ExampleDS1 set as the Java EE Default Datasource. 19:56:56,035 INFO [org.wildfly.migration.core.logger] (main) Java EE Default Bindings configured.
Please note that, if the tool is running in non interactive mode, and the expected EAP 6 default resources are not available, the tool will not configure such specific resource(s) (e.g. default JMS Connection Factory)
The ejb subsystem configuration is updated so EJB remoting uses the new HTTP Connector.
The changes on the subsystem configuration are fully automated, the tool console and log(s) will includes indicate these were done, e.g.:
19:56:56,077 INFO [org.wildfly.migration.core.logger] (main) EJB3 subsystem's remote service configured to use HTTP Remoting connector.
The jacorb subsystem is deprecated on EAP 7, and the tool migrates its configuration to the EAP 7 subsystem that replaces it, named IIOP OpenJDK.
The legacy subsystem migration is done without any interaction with the user, and any issue with the legacy subsystem configuration, e.g. missing functionality, results in a warning shown in the migration console and log(s). A successful migration of the legacy subsystem configuration is indicated by the following message:
19:57:01,065 INFO [org.wildfly.migration.core.logger] (main) Subsystem jacorb migrated.
The jaxr subsystem is not supported by EAP 7, if found its configuration will be removed from the migrated configuration file, and the console and log(s) will display the following message:
17:28:54,859 INFO [org.wildfly.migration.core.logger] (main) Unsupported subsystem jaxr removed.
The extension that provides the removed subsystem, if present in the configuration file, will also be removed, and in such case the console and log(s) will display the following message:
17:28:54,889 INFO [org.wildfly.migration.core.logger] (main) Unsupported extension org.jboss.as.jaxr removed.
The messaging subsystem is deprecated on EAP 7, and the tool migrates its configuration to the EAP 7 subsystem that replaces it, named messaging-activemq.
The legacy subsystem migration is done without any interaction with the user, and any issue with the legacy subsystem configuration, e.g. missing functionality, results in a warning shown in the migration console and log(s). A successful migration of the legacy subsystem configuration is indicated by the following message:
19:57:01,405 INFO [org.wildfly.migration.core.logger] (main) Subsystem messaging migrated.
Please note that the tool goes beyond the legacy subsystem configuration migration, it also adds new functionality provided by the new subsystem, which is present in EAP 7 default standalone config files, more specifically:
adds the default HTTP Connector and Acceptor, enabling the new HTTP based remote messaging clients
04:25:24,059 INFO [org.wildfly.migration.core.logger] (main) HTTP Acceptor named http-acceptor added to Messaging ActiveMQ subsystem configuration. 04:25:24,069 INFO [org.wildfly.migration.core.logger] (main) HTTP Connector named http-connector added to Messaging ActiveMQ subsystem configuration.
The request-controller is a EAP 7 subsystem that provides congestion control and graceful shutdown functionalities, and it's default configuration is added to the migrated configuration file.
Please note that such subsystem, and related extension, is added without any interaction with the user, the migration console and log(s) will only indicate it was added, an example:
19:57:01,767 INFO [org.wildfly.migration.core.logger] (main) Extension org.wildfly.extension.request-controller added. 19:57:01,779 INFO [org.wildfly.migration.core.logger] (main) Subsystem request-controller added.
One of the most relevant features introduced by EAP 7 is the new HTTP connector, a connector that is able to replace all legacy remoting protocols and ports, using a single port. The HTTP Connector is configured by the remoting subsystem, and the tool simply updates the subsystem configuration to turn it on.
The changes on the subsystem configuration are fully automated, the tool console and log(s) will includes indicate these were done, e.g.:
19:56:56,107 INFO [org.wildfly.migration.core.logger] (main) Http connector http-remoting-connector added to Remoting subsystem configuration.
The security-manager is a EAP 7 subsystem that provides the support for Java EE 7 security permissions, and it's default configuration is added to the migrated configuration file.
Please note that such subsystem, and related extension, is added without any interaction with the user, the migration console and log(s) will only indicate it was added, an example:
19:57:01,805 INFO [org.wildfly.migration.core.logger] (main) Extension org.wildfly.extension.security.manager added. 19:57:01,827 INFO [org.wildfly.migration.core.logger] (main) Subsystem security-manager added.
The threads subsystem is not supported by EAP 7, if found its configuration will be removed from the migrated configuration file, and the console and log(s) will display the following message:
17:28:54,873 INFO [org.wildfly.migration.core.logger] (main) Unsupported subsystem threads removed.
The extension that provides the removed subsystem, if present in the configuration file, will also be removed, and in such case the console and log(s) will display the following message:
17:28:54,907 INFO [org.wildfly.migration.core.logger] (main) Unsupported extension org.jboss.as.threads removed.
The web subsystem is deprecated on EAP 7, and the tool migrates its configuration to the EAP 7 subsystem that replaces it, named undertow.
The legacy subsystem migration is done without any interaction with the user, and any issue with the legacy subsystem configuration, e.g. missing functionality, results in a warning shown in the migration console and log(s). A successful migration of the legacy subsystem configuration is indicated by the following message:
19:57:01,112 INFO [org.wildfly.migration.core.logger] (main) Subsystem web migrated.
Please note that the tool goes beyond the legacy subsystem configuration migration, it also adds new functionality provided by the new subsystem, which is present in EAP 7 default standalone config files, more specifically:
adds a buffer cache
changes the http listener config to match defaults in EAP 7
adds support for Java EE 7 Websockets
19:56:56,465 INFO [org.wildfly.migration.core.logger] (main) Undertow's default HTTP listener 'redirect-socket' set to 'https'. 19:56:56,477 INFO [org.wildfly.migration.core.logger] (main) Undertow's default Servlet Container configured to support Websockets.
EAP 7 Security Realms configuration is fully compatible with the EAP 6 Security Realms configuration, which means that no changes are required and done. As for any properties file referenced by such configuration, in case its path is not absolute then the tool will copy such file, to the path expected by the migrated config file.
The migration of Security Realms is fully automated, no user interaction is needed, and details about its execution are shown in the migration console and log(s):
12:20:53,144 INFO [org.wildfly.migration.core.logger] (main) Migrating security realms... 12:20:53,150 INFO [org.wildfly.migration.core.logger] (main) Migrating security realm: ApplicationRealm 12:20:53,153 INFO [org.wildfly.migration.core.logger] (main) Migrating security realm: ManagementRealm 12:20:53,155 INFO [org.wildfly.migration.core.logger] (main) Security realms migration done.
The Management Interfaces migration consists of turning on HTTP Management Interface's support for HTTP Upgrade, functionality required by EAP 7 Management Clients, such as the JBoss CLI, to connect and manage the server, without any configuration changes on the client side.
The migration of Management Interfaces is fully automated, and the following messages, in the migration console and log(s), indicate that such migration was done as expected:
10:43:06,374 INFO [org.wildfly.migration.core.logger] (main) Migrating management interfaces... 10:43:06,383 INFO [org.wildfly.migration.core.logger] (main) Activated HTTP Management Interface's support for HTTP Upgrade. 10:43:06,383 INFO [org.wildfly.migration.core.logger] (main) Management interfaces migration done.
The Socket Bindings migration consists of ensuring that the port used by the socket binding named management-https is 9993, since such port is used by EAP 7 Management Clients, such as the JBoss CLI, to connect and manage the server, without any configuration changes on the client side.
The migration of Socket Bindings is fully automated, and the following messages, in the migration console and log(s), indicate that such migration was done as expected:
10:43:06,383 INFO [org.wildfly.migration.core.logger] (main) Migrating socket bindings... 10:43:06,406 INFO [org.wildfly.migration.core.logger] (main) Socket binding 'management-https' default port set to 9993. 10:43:06,406 INFO [org.wildfly.migration.core.logger] (main) Socket bindings migration done.
The migration tool does not migrates deployments in the source configuration, and removes these from the migrated configuration.