Standalone Config File Subsystems 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 WildFly 10
-
Add WildFly 10 new subsystems, which are included in the default WildFly 10 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.
batch Subsystem
The batch subsystem is not supported by WildFly 10, if found its configuration will be removed from the migrated configuration file, and the console and log(s) will display the following message:
07:18:02,536 INFO [org.wildfly.migration.core.logger] (main) Unsupported subsystem batch 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:
07:18:02,550 INFO [org.wildfly.migration.core.logger] (main) Unsupported extension org.wildfly.extension.batch removed.
batch-jberet Subsystem
The batch-jberet is a WildFly 10 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.
bean-validation Subsystem
The Bean Validation functionality was previously provided by the ee subsystem on WildFly 8, but on WildFly 10 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.
jacorb Subsystem
The jacorb subsystem is deprecated on WildFly 10, and the tool migrates its configuration to the WildFly 10 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.
messaging Subsystem
The messaging subsystem is deprecated on WildFly 10, and the tool migrates its configuration to the WildFly 10 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.
request-controller Subsystem
The request-controller is a WildFly 10 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.
security-manager Subsystem
The security-manager is a WildFly 10 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.
Standalone Config File Security Realms Migration
WildFly 10 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.