Chapter 6. Migrating JBoss EAP 6.4 Configurations to JBoss EAP 7.4

The following JBoss EAP 6.4 subsystems are not supported by JBoss EAP 7.4 :

The JBoss Server Migration Tool removes all unsupported subsystem configurations and extensions from migrated server configurations. The tool logs each subsystem and extension to its log file and to the console as it is removed.

To skip removal of the unsupported subsystems, set the subsystems.remove-unsupported-subsystems.skip environment property to true.

You can override the default behavior of the JBoss Server Migration Tool and specify which subsystems and extensions should be included or excluded during the migration using the following environment properties.

A configuration that is migrated from a source server to a target server might reference or depend on a module that is not installed on the target server. The JBoss Server Migration Tool detects this and automatically migrates the referenced modules, plus their dependent modules, from the source server to the target server.

A module referenced by a standalone server configuration is migrated using the following process.

The console logs a message noting the module ID for any module that is migrated. It is possible to exclude the migration of specific modules by specifying the module ID in the modules.excludes environment property. See Configuring the Migration of Modules for more information.

A configuration that is migrated from a source server to a target server might reference or depend on file paths and directories that must also be migrated to the target server. The JBoss Server Migration Tool does not migrate absolute path references. It only migrates files or directories that are configured as relative to the source configuration. The console logs a message noting each path that is migrated.

The JBoss Server Migration Tool automatically migrates the following path references:

To skip the migration of referenced paths, set the paths.migrate-paths-requested-by-configuration.vault.skip environment property to true.

The jacorb subsystem is deprecated in JBoss EAP 7.4 and is replaced by the iiop-openjdk subsystem. By default, the JBoss Server Migration Tool automatically migrates the jacorb subsystem configuration to its replacement iiop-openjdk subsystem configuration and logs the results to its log file and to the console.

To skip the automatic migration to the iiop-openjdk subsystem configuration, set the subsystem.jacorb.migrate.skip environment property value to true.

The web subsystem is deprecated in JBoss EAP 7.4 and is replaced by the undertow subsystem. By default, the JBoss Server Migration Tool automatically migrates the web subsystem configuration to its replacement undertow subsystem configuration and logs the results to its log file and to the console.

To skip automatic migration of the web subsystem, set the subsystem.web.migrate.skip environment property value to true.

The messaging subsystem is deprecated in JBoss EAP 7.4 and is replaced by the messaging-activemq subsystem. The JBoss Server Migration Tool automatically migrates the messaging subsystem configuration to its replacement messaging-activemq subsystem configuration and logs the results to its log file and to the console.

To skip automatic migration of the messaging subsystem, set the subsystem.messaging.migrate.skip environment property value to true.

The JBoss Server Migration Tool updates the infinispan subsystem configuration to better align with the default JBoss EAP 7.4 configurations.

The JBoss Server Migration Tool automatically updates the infinispan subsystem configuration and logs the results to its log file and to the console.

You can customize the update of the infinispan system by setting the following environment properties.

The JBoss Server Migration Tool updates the ee subsystem to configure the Jakarta EE features supported in JBoss EAP 7.4.

The JBoss Server Migration Tool automatically updates the ee subsystem configuration and logs the results to its log file and to the console.

You can customize the update of the ee system by setting the following environment properties.

Configuring Concurrency Utilities in the EE Subsystem

If you choose to configure the Jakarta EE concurrency utilities, then the tool automatically configures the instances that are present in the default JBoss EAP 7.4 configurations and logs the results to its log file and to the console.

INFO  [ServerMigrationTask#49] Default ContextService added to EE subsystem configuration.
INFO  [ServerMigrationTask#49] Default ManagedThreadFactory added to EE subsystem configuration.
INFO  [ServerMigrationTask#49] Default ManagedExecutorService added to EE subsystem configuration.
INFO  [ServerMigrationTask#49] Default ManagedScheduledExecutorService added to EE subsystem configuration.

Configuring Default Resources in the EE Subsystem

When defining the Jakarta EE default resources the tool automatically selects those that are present in the default JBoss EAP 7.4 configuration.

INFO  [ServerMigrationTask#50] Java EE Default Datasource configured with Java Naming and Directory Interface and name java:jboss/datasources/ExampleDS.

If no default resource is found, the tool lists all resources that are available in the configuration, and then provides a prompt to select the default resource or to provide the Java Naming and Directory Interface address of the resource that should be set as the default.

The following is an example of the interaction that occurs when migrating a configuration file with an ExampleDS datasource.

INFO  [ServerMigrationTask#22] Default datasource not found.
0. ExampleDS
1. Unconfigured data source, I want to enter the Java Naming and Directory Interface name...
Please select Java EE's Default Datasource: (0): 0
INFO  [ServerMigrationTask#22] Java EE Default Datasource configured with Java Naming and Directory Interface name java:jboss/datasources/ExampleDS.

Save this Java EE Default Datasource Java Naming and Directory Interface name and use it when migrating other config files?
yes/no? y

The JBoss Server Migration Tool makes the following updates to the Jakarta Enterprise Beans subsystem to better align with the default JBoss EAP 7.4 configurations.

The JBoss Server Migration Tool automatically updates the Jakarta Enterprise Beans subsystem configuration and logs the results to its log file and to the console.

Upon successful update of the Jakarta Enterprise Beans subsystem configuration, the JBoss Server Migration Tool logs the results to its log file and to the console.

 INFO  Subsystem ejb3 updated.

You can customize the update of the Jakarta Enterprise Beans subsystem by setting the following environment properties.

The JBoss Server Migration Tool updates the jgroups subsystem to align with the JBoss EAP 7.4 configurations.

Upon successful migration of the jgroups subsystem configuration, the JBoss Server Migration Tool logs the results to its log file and to the console.

 INFO  Subsystem jgroups updated.

To skip the automatic migration of the jgroups subsystem, set the subsystem.jgroups.update.skip environment property to true.

JBoss EAP 7.4 includes an HTTP connector that replaces all legacy remoting protocols and ports using a single port. The JBoss Server Migration Tool automatically updates the remoting subsystem to use the HTTP connector.

To skip the automatic update of the remoting subsystem configuration, set the subsystem.remoting.update.skip environment property to true.

The JBoss Server Migration Tool updates the transactions subsystem with the configuration changes required by the JBoss EAP 7.4 server.

The JBoss Server Migration Tool removes the path and relative-to attributes from the transactions subsystem and replaces them with the equivalent object-store-path and object-store-relative-to attributes.

To skip the automatic update of the transactions subsystem configuration, set the subsystem.transactions.update-xml-object-store-paths.skip environment property to true.

In addition to migrating the web subsystem for JBoss EAP 7.4, the JBoss Server Migration Tool updates its replacement undertow subsystem to add the features it supports.

The JBoss Server Migration Tool automatically updates the undertow subsystem configuration and logs the results to its log file and to the console.

Upon successful migration of the undertow subsystem configuration, the JBoss Server Migration Tool logs the results to its log file and to the console.

 INFO  Subsystem undertow updated.

You can customize the update of the undertow system by setting the following environment properties.

In addition to migrating the messaging subsystem for JBoss EAP 7.4, the JBoss Server Migration Tool updates its replacement messaging-activemq subsystem to add the new features it supports.

The JBoss Server Migration Tool automatically updates the messaging-activemq subsystem configuration and logs the results to its log file and to the console.

To skip the automatic update of the messaging-activemq subsystem, set the subsystem.messaging-activemq.update.skip environment property to true.

The JBoss EAP 7.4 batch-jberet subsystem provides support for the Jakarta Batch 1.0 specification. The JBoss Server Migration Tool automatically adds the default batch-jberet subsystem configuration to the migrated configuration.

To skip the addition of the batch-jberet subsystem configuration, set the subsystem.batch-jberet.add.skip environment property to true.

The JBoss EAP 7.4 core-management subsystem provides management-related resources, which were previously configured in the management core service. Examples of these resources include the ability to view a history of configuration changes made to the server and the ability to monitor for server lifecycle events. The JBoss Server Migration Tool automatically adds the default core-management subsystem configuration to the migrated configuration file.

To skip the addition of the core-management subsystem configuration, set the subsystem.core-management.add.skip environment property to true.

The JBoss Server Migration Tool automatically adds the default discovery subsystem configuration to the migrated configuration file.

To skip the addition of the discovery subsystem configuration, set the subsystem.discovery.add.skip environment property to true.

The JBoss EAP 7.4 ee-security subsystem provides support and compliance for Jakarta Security. The JBoss Server Migration Tool automatically adds the default ee-security subsystem configuration to the migrated configuration file.

To skip the addition of the ee-security subsystem configuration, set the subsystem.ee-security.add.skip environment property to true.

The JBoss EAP 7.4 elytron subsystem provides a single unified security framework that can manage and configure access for both standalone servers and managed domains. It can also be used to configure security access for applications deployed to JBoss EAP servers. The JBoss Server Migration Tool automatically adds the default elytron subsystem configuration to the migrated configuration file.

To skip the addition of the elytron subsystem configuration, set the subsystem.elytron.add.skip environment property to true.

The JBoss EAP 7.4 health subsystem provides support for a server’s health functionality. The JBoss Server Migration Tool automatically adds the default health subsystem configuration to the migrated configuration file.

To skip the addition of the health subsystem configuration, set the subsystem.health.add.skip environment property to true.

After you add the health subsystem to JBoss EAP 7.4, you’ll see the following message in your web console:

INFO  Subsystem health added.

The JBoss EAP 7.4 metrics subsystem provides support for a server’s metric functionality. The JBoss Server Migration Tool automatically adds the default metrics subsystem configuration to the migrated configuration file.

To skip the addition of the metrics subsystem configuration, set the subsystem.metrics.add.skip environment property to true.

After you add the metrics subsystem to JBoss EAP 7.4, you’ll see the following message in your web console:

INFO  Subsystem metrics added.

The JBoss EAP 7.4 request-controller subsystem provides congestion control and graceful shutdown functionality. The JBoss Server Migration Tool automatically adds the default request-controller subsystem configuration to the migrated configuration file.

To skip the addition of the request-controller subsystem configuration, set the subsystem.request-controller.add.skip environment property to true.

The JBoss EAP 7.4 security-manager subsystem provides support for Jakarta Security permissions. The JBoss Server Migration Tool automatically adds the default security-manager subsystem configuration to the migrated configuration file.

To skip the addition of the security-manager subsystem configuration, set the subsystem.security-manager.add.skip environment property to true.

The JBoss EAP 7.4 singleton subsystem provides singleton functionality. The JBoss Server Migration Tool automatically adds the default singleton subsystem configuration to the migrated configuration file.

To skip the addition of the singleton subsystem configuration, set the subsystem.singleton.add.skip environment property to true.

The addition of Undertow in JBoss EAP 7.4 added HTTP Upgrade, which allows for multiple protocols to be multiplexed over a single port. This means a management client can make an initial connection over HTTP, but then send a request to upgrade that connection to another protocol. The JBoss Server Migration Tool automatically updates the configuration to support HTTP Upgrade management.

To skip configuration of HTTP Upgrade management, set the management.setup-http-upgrade.skip environment property to true.

The JBoss EAP 7.4 default configuration uses a private interface on all jgroups socket bindings. The JBoss Server Migration Tool automatically updates the migrated jgroups socket bindings to use same configuration.

To skip the configuration of the private interface, set the interface.private.setup.skip environment property to true.

The JBoss EAP 7.4 default configurations use value expressions for the port attribute of the following socket bindings:

The JBoss Server Migration Tool automatically adds these value expressions to the migrated server configurations.

To skip update of the socket binding port expressions, set the socket-bindings.add-port-expressions.skip environment property to true.

The JBoss EAP 7.4 default configuration uses value expressions in the multicast-address attribute of mod_cluster socket bindings. The JBoss Server Migration Tool automatically adds these value expressions to the migrated configuration files.

To skip the addition of these expressions, set the socket-bindings.multicast-address.add-expressions.skip environment property to true.

Because the JBoss EAP 7.4 security realm configurations are fully compatible with the JBoss EAP 6.4 security realm configurations, they require no update by the JBoss Server Migration Tool. However, if the application-users.properties, application-roles.properties, mgmt-users.properties, and mgmt-groups.properties files are not referenced using an absolute path, the tool copies them to the path expected by the migrated configuration file.

To skip the security realms migration, set the security-realms.migrate-properties.skip environment property to true.

The JBoss EAP 7.4 default configuration includes an SSL server identity for the default ApplicationRealm security realm. The JBoss Server Migration Tool automatically adds this identity to the migrated configuration files.

To skip the addition of this identity, set the security-realm.ApplicationRealm.add-ssl-server-identity.skip environment property to true.

The JBoss Server Migration Tool can migrate the following types of standalone server deployment configurations.

The migration of a deployment consists of installing related file resources on the target server, and possibly updating the migrated configuration.

The JBoss Server Migration Tool is preconfigured to skip deployments by default when running in non-interactive mode. To enable migration of deployments, set the deployments.migrate-deployments.skip environment property to false.

To enable the migration of specific types of deployments, see the following sections.

INFO  [ServerMigrationTask#67] Persistent deployments found: [cmtool-helloworld3.war, cmtool-helloworld4.war, cmtool-helloworld2.war, cmtool-helloworld1.war]

The following JBoss EAP 6.4 subsystems are not supported by JBoss EAP 7.4 :

The JBoss Server Migration Tool removes all unsupported subsystem configurations and extensions from migrated server configurations. The tool logs each subsystem and extension to its log file and to the console as it is removed.

To skip removal of the unsupported subsystems, set the subsystems.remove-unsupported-subsystems.skip environment property to true.

You can override the default behavior of the JBoss Server Migration Tool and specify which subsystems and extensions should be included or excluded during the migration using the following environment properties.

A configuration that is migrated from a source server to a target server might reference or depend on a module that is not installed on the target server. The JBoss Server Migration Tool detects this and automatically migrates the referenced modules, plus their dependent modules, from the source server to the target server.

A module referenced by a managed domain configuration is migrated using the following process.

The console logs a message noting the module ID for any module that is migrated. It is possible to exclude the migration of specific modules by specifying the module ID in the modules.excludes environment property. See Configuring the Migration of Modules for more information.

A configuration that is migrated from a source server to a target server might reference or depend on file paths and directories that must also be migrated to the target server. The JBoss Server Migration Tool does not migrate absolute path references. It only migrates files or directories that are configured as relative to the source configuration. The console logs a message noting each path that is migrated.

The JBoss Server Migration Tool automatically migrates the following path references:

To skip the migration of referenced paths, set the paths.migrate-paths-requested-by-configuration.vault.skip environment property to true.

The jacorb subsystem is deprecated in JBoss EAP 7.4 and is replaced by the iiop-openjdk subsystem. By default, the JBoss Server Migration Tool automatically migrates the jacorb subsystem configuration to its replacement iiop-openjdk subsystem configuration and logs the results to its log file and to the console.

To skip the automatic migration to the iiop-openjdk subsystem configuration, set the subsystem.jacorb.migrate.skip environment property value to true.

The web subsystem is deprecated in JBoss EAP 7.4 and is replaced by the undertow subsystem. By default, the JBoss Server Migration Tool automatically migrates the web subsystem configuration to its replacement undertow subsystem configuration and logs the results to its log file and to the console.

To skip automatic migration of the web subsystem, set the subsystem.web.migrate.skip environment property value to true.

The messaging subsystem is deprecated in JBoss EAP 7.4 and is replaced by the messaging-activemq subsystem. The JBoss Server Migration Tool automatically migrates the messaging subsystem configuration to its replacement messaging-activemq subsystem configuration and logs the results to its log file and to the console.

To skip automatic migration of the messaging subsystem, set the subsystem.messaging.migrate.skip environment property value to true.

The JBoss Server Migration Tool updates the infinispan subsystem configuration to better align with the default JBoss EAP 7.4 configurations.

The JBoss Server Migration Tool automatically updates the infinispan subsystem configuration and logs the results to its log file and to the console.

You can customize the update of the infinispan system by setting the following environment properties.

The JBoss Server Migration Tool updates the ee subsystem to configure the Jakarta EE features supported in JBoss EAP 7.4.

The JBoss Server Migration Tool automatically updates the ee subsystem configuration and logs the results to its log file and to the console.

You can customize the update of the ee system by setting the following environment properties.

Configuring Concurrency Utilities in the EE Subsystem

If you choose to configure the Jakarta EE concurrency utilities, then the tool automatically configures the instances that are present in the default JBoss EAP 7.4 configurations and logs the results to its log file and to the console.

INFO  [ServerMigrationTask#49] Default ContextService added to EE subsystem configuration.
INFO  [ServerMigrationTask#49] Default ManagedThreadFactory added to EE subsystem configuration.
INFO  [ServerMigrationTask#49] Default ManagedExecutorService added to EE subsystem configuration.
INFO  [ServerMigrationTask#49] Default ManagedScheduledExecutorService added to EE subsystem configuration.

Configuring Default Resources in the EE Subsystem

When defining the Jakarta EE default resources the tool automatically selects those that are present in the default JBoss EAP 7.4 configuration.

INFO  [ServerMigrationTask#50] Java EE Default Datasource configured with Java Naming and Directory Interface and name java:jboss/datasources/ExampleDS.

If no default resource is found, the tool lists all resources that are available in the configuration, and then provides a prompt to select the default resource or to provide the Java Naming and Directory Interface address of the resource that should be set as the default.

The following is an example of the interaction that occurs when migrating a configuration file with an ExampleDS datasource.

INFO  [ServerMigrationTask#22] Default datasource not found.
0. ExampleDS
1. Unconfigured data source, I want to enter the Java Naming and Directory Interface name...
Please select Java EE's Default Datasource: (0): 0
INFO  [ServerMigrationTask#22] Java EE Default Datasource configured with Java Naming and Directory Interface name java:jboss/datasources/ExampleDS.

Save this Java EE Default Datasource Java Naming and Directory Interface name and use it when migrating other config files?
yes/no? y

The JBoss Server Migration Tool makes the following updates to the Jakarta Enterprise Beans subsystem to better align with the default JBoss EAP 7.4 configurations.

The JBoss Server Migration Tool automatically updates the Jakarta Enterprise Beans subsystem configuration and logs the results to its log file and to the console.

Upon successful update of the Jakarta Enterprise Beans subsystem configuration, the JBoss Server Migration Tool logs the results to its log file and to the console.

 INFO  Subsystem ejb3 updated.

You can customize the update of the Jakarta Enterprise Beans subsystem by setting the following environment properties.

The JBoss Server Migration Tool updates the jgroups subsystem to align with the JBoss EAP 7.4 configurations.

Upon successful migration of the jgroups subsystem configuration, the JBoss Server Migration Tool logs the results to its log file and to the console.

 INFO  Subsystem jgroups updated.

To skip the automatic migration of the jgroups subsystem, set the subsystem.jgroups.update.skip environment property to true.

JBoss EAP 7.4 includes an HTTP connector that replaces all legacy remoting protocols and ports using a single port. The JBoss Server Migration Tool automatically updates the remoting subsystem to use the HTTP connector.

To skip the automatic update of the remoting subsystem configuration, set the subsystem.remoting.update.skip environment property to true.

The JBoss Server Migration Tool updates the transactions subsystem with the configuration changes required by the JBoss EAP 7.4 server.

The JBoss Server Migration Tool removes the path and relative-to attributes from the transactions subsystem and replaces them with the equivalent object-store-path and object-store-relative-to attributes.

To skip the automatic update of the transactions subsystem configuration, set the subsystem.transactions.update-xml-object-store-paths.skip environment property to true.

In addition to migrating the web subsystem for JBoss EAP 7.4, the JBoss Server Migration Tool updates its replacement undertow subsystem to add the features it supports.

The JBoss Server Migration Tool automatically updates the undertow subsystem configuration and logs the results to its log file and to the console.

Upon successful migration of the undertow subsystem configuration, the JBoss Server Migration Tool logs the results to its log file and to the console.

 INFO  Subsystem undertow updated.

You can customize the update of the undertow system by setting the following environment properties.

In addition to migrating the messaging subsystem for JBoss EAP 7.4, the JBoss Server Migration Tool updates its replacement messaging-activemq subsystem to add the new features it supports.

The JBoss Server Migration Tool automatically updates the messaging-activemq subsystem configuration and logs the results to its log file and to the console.

To skip the automatic update of the messaging-activemq subsystem, set the subsystem.messaging-activemq.update.skip environment property to true.

The JBoss EAP 7.4 batch-jberet subsystem provides support for the Jakarta Batch 1.0 specification. The JBoss Server Migration Tool automatically adds the default batch-jberet subsystem configuration to the migrated configuration.

To skip the addition of the batch-jberet subsystem configuration, set the subsystem.batch-jberet.add.skip environment property to true.

The JBoss EAP 7.4 core-management subsystem provides management-related resources, which were previously configured in the management core service. Examples of these resources include the ability to view a history of configuration changes made to the server and the ability to monitor for server lifecycle events. The JBoss Server Migration Tool automatically adds the default core-management subsystem configuration to the migrated configuration file.

To skip the addition of the core-management subsystem configuration, set the subsystem.core-management.add.skip environment property to true.

The JBoss Server Migration Tool automatically adds the default discovery subsystem configuration to the migrated configuration file.

To skip the addition of the discovery subsystem configuration, set the subsystem.discovery.add.skip environment property to true.

The JBoss EAP 7.4 ee-security subsystem provides support and compliance for Jakarta Security. The JBoss Server Migration Tool automatically adds the default ee-security subsystem configuration to the migrated configuration file.

To skip the addition of the ee-security subsystem configuration, set the subsystem.ee-security.add.skip environment property to true.

The JBoss EAP 7.4 elytron subsystem provides a single unified security framework that can manage and configure access for both standalone servers and managed domains. It can also be used to configure security access for applications deployed to JBoss EAP servers. The JBoss Server Migration Tool automatically adds the default elytron subsystem configuration to the migrated configuration file.

To skip the addition of the elytron subsystem configuration, set the subsystem.elytron.add.skip environment property to true.

The JBoss EAP 7.4 request-controller subsystem provides congestion control and graceful shutdown functionality. The JBoss Server Migration Tool automatically adds the default request-controller subsystem configuration to the migrated configuration file.

To skip the addition of the request-controller subsystem configuration, set the subsystem.request-controller.add.skip environment property to true.

The JBoss EAP 7.4 security-manager subsystem provides support for Jakarta Security permissions. The JBoss Server Migration Tool automatically adds the default security-manager subsystem configuration to the migrated configuration file.

To skip the addition of the security-manager subsystem configuration, set the subsystem.security-manager.add.skip environment property to true.

The JBoss EAP 7.4 singleton subsystem provides singleton functionality. The JBoss Server Migration Tool automatically adds the default singleton subsystem configuration to the migrated configuration file.

To skip the addition of the singleton subsystem configuration, set the subsystem.singleton.add.skip environment property to true.

The JBoss Server Migration Tool automatically updates the unsecure interface configuration to align with the JBoss EAP 7.4 default configuration.

To skip configuration of the unsecure interface, set the interface.unsecure.update.skip environment property to true.

The JBoss EAP 7.4 default configuration uses a private interface on all jgroups socket bindings. The JBoss Server Migration Tool automatically updates the migrated jgroups socket bindings to use same configuration.

To skip the configuration of the private interface, set the interface.private.setup.skip environment property to true.

The JBoss EAP 7.4 default configurations use value expressions for the port attribute of the following socket bindings:

The JBoss Server Migration Tool automatically adds these value expressions to the migrated server configurations.

To skip update of the socket binding port expressions, set the socket-bindings.add-port-expressions.skip environment property to true.

The JBoss EAP 7.4 default configuration uses value expressions in the multicast-address attribute of mod_cluster socket bindings. The JBoss Server Migration Tool automatically adds these value expressions to the migrated configuration files.

To skip the addition of these expressions, set the socket-bindings.multicast-address.add-expressions.skip environment property to true.

JBoss EAP 7.4 includes a default profile specifically tailored for hosts that serve as load balancers. The JBoss Server Migration Tool automatically adds and configures this profile to all migrated managed domain configurations.

To skip the addition of this profile, set the profile.load-balancer.add.skip environment property to true.

The JBoss EAP 7.4 domain controller can potentially include functionality that is not supported by hosts running on older versions of the server. The host-exclude configuration specifies the resources that should be hidden from those older versions.

When migrating a domain controller configuration, the JBoss Server Migration Tool adds to or replaces the source server’s host-exclude configuration with the configuration of the target JBoss EAP 7.4 server.

The JBoss Server Migration Tool automatically updates the host-exclude configuration and logs the results to its log file and to the console.

  INFO  Host-excludes configuration added.

The usage of PermGen attributes in JVM configurations is deprecated in JBoss EAP 7. The JBoss Server Migration Tool automatically removes them from all JVM configurations for all server groups.

To skip removal of the PermGen attributes, set the jvms.remove-permgen-attributes.skip environment property value to true.

The JBoss Server Migration Tool can migrate the following types of managed domain deployment configurations.

The migration of a deployment consists of installing related file resources on the target server, and possibly updating the migrated configuration.

The JBoss Server Migration Tool is preconfigured to skip deployments by default when running in non-interactive mode. To enable migration of deployments, set the deployments.migrate-deployments.skip environment property to false.

To enable the migration of specific types of deployments, see the following sections.

INFO  [ServerMigrationTask#67] Persistent deployments found: [cmtool-helloworld3.war, cmtool-helloworld4.war, cmtool-helloworld2.war, cmtool-helloworld1.war]

A configuration that is migrated from a source server to a target server might reference or depend on a module that is not installed on the target server. The JBoss Server Migration Tool detects this and automatically migrates the referenced modules, plus their dependent modules, from the source server to the target server.

A module referenced by a host server configuration is migrated using the following process.

The console logs a message noting the module ID for any module that is migrated. It is possible to exclude the migration of specific modules by specifying the module ID in the modules.excludes environment property. See Configuring the Migration of Modules for more information.

A configuration that is migrated from a source server to a target server might reference or depend on file paths and directories that must also be migrated to the target server. The JBoss Server Migration Tool does not migrate absolute path references. It only migrates files or directories that are configured as relative to the source configuration. The console logs a message noting each path that is migrated.

The JBoss Server Migration Tool automatically migrates the following path references:

To skip the migration of referenced paths, set the paths.migrate-paths-requested-by-configuration.vault.skip environment property to true.

The JBoss EAP 7.4 core-management subsystem provides management-related resources, which were previously configured in the management core service. Examples of these resources include the ability to view a history of configuration changes made to the server and the ability to monitor for server lifecycle events. The JBoss Server Migration Tool automatically adds the default core-management subsystem configuration to the migrated configuration file.

To skip the addition of the core-management subsystem configuration, set the subsystem.core-management.add.skip environment property to true.

The JBoss EAP 7.4 elytron subsystem provides a single unified security framework that can manage and configure access for both standalone servers and managed domains. It can also be used to configure security access for applications deployed to JBoss EAP servers. The JBoss Server Migration Tool automatically adds the default elytron subsystem configuration to the migrated configuration file.

To skip the addition of the elytron subsystem configuration, set the subsystem.elytron.add.skip environment property to true.

The JBoss EAP 7.4 jmx subsystem provides the ability to manage and monitor systems. The JBoss Server Migration Tool automatically adds this subsystem to the migrated configuration file.

To skip the addition of the jmx subsystem configuration, set the subsystem.jmx.add.skip environment property to true.

The JBoss Server Migration Tool automatically removes the unsecure interface configuration to align with the JBoss EAP 7.4 default configuration.

To skip removal of the unsecure interface, set the interface.unsecure.remove.skip environment property to true.

The addition of Undertow in JBoss EAP 7.4 added HTTP Upgrade, which allows for multiple protocols to be multiplexed over a single port. This means a management client can make an initial connection over HTTP, but then send a request to upgrade that connection to another protocol. The JBoss Server Migration Tool automatically updates the configuration to support HTTP Upgrade management.

To skip configuration of HTTP Upgrade management, set the management.setup-http-upgrade.skip environment property to true.

The usage of PermGen attributes in JVM configurations is deprecated in JBoss EAP 7. The JBoss Server Migration Tool automatically removes them from all JVM configurations for all server groups.

To skip removal of the PermGen attributes, set the jvms.remove-permgen-attributes.skip environment property value to true.

Because the JBoss EAP 7.4 security realm configurations are fully compatible with the JBoss EAP 6.4 security realm configurations, they require no update by the JBoss Server Migration Tool. However, if the application-users.properties, application-roles.properties, mgmt-users.properties, and mgmt-groups.properties files are not referenced using an absolute path, the tool copies them to the path expected by the migrated configuration file.

To skip the security realms migration, set the security-realms.migrate-properties.skip environment property to true.

The JBoss EAP 7.4 default configuration includes an SSL server identity for the default ApplicationRealm security realm. The JBoss Server Migration Tool automatically adds this identity to the migrated configuration files.

To skip the addition of this identity, set the security-realm.ApplicationRealm.add-ssl-server-identity.skip environment property to true.