The task named server is the server migration root task.
The task execution merely delegates the server migration to its subtasks:
standalone
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The server subtask named standalone is responsible for migrating the source's standalone server.
The standalone server migration consists of migrating the standalone server's config files, and such work is delegated to its subtask config-files
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The standalone subtask named config-files is responsible for migrating the source's standalone server config files.
The task execution gathers the config files to be migrated, and then for each tof hese files it executes a config-file subtask, which handles its migration.
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The config-files subtask named config-file handles the migration a single standalone server config file. The task name includes a source attribute, used to distinguish multiple instances of the task, and which value is the path of the specific config file to migrate.
The task execution copies the source config file, to the target server standalone configuration directory, and then delegates to subtasks the actual migration of the configuration:
subsystems-xml-config
subsystems-management-resources
security-realms
deployments
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The config-file subtask named subsystems-xml-config processes the subsystems (and extensions) XML configuration, modifying it so the server is able to boot with such configuration.
The task execution may execute multiple instances of subtasks remove-extension and remove-subsystem, delegating to these the removal of unsupported extensions and subsystems.
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The subsystems-xml-config subtask named remove-extension handles the removal of an unsupported extension, from a standalone server config file. The task name includes a module attribute, which value is the unsupported extension's module name.
The task execution's status result is:
Success, if the task successfully removed the unsupported extension
Skipped, if the task was skipped by the environment
Failed, if the task's failed to remove the unsupported extension, due to an error
The subsystems-xml-config subtask named remove-subsystem is responsible for the removal of a single unsupported subsystem, from the standalone server config file in context. The task name includes a namespace attribute, which value is the unsupported subsystem's XML namespace.
The task execution's status result is:
Success, if the task successfully removed the unsupported subsystem
Skipped, if the task was skipped by the environment
Failed, if the task's failed to remove the unsupported subsystem, due to an error
The config-file subtask named subsystems-management-resources is responsible for migrating the subsystems configuration, through management operations. In concrete such migration consists of: adding the default config of new subsystems, migrating the configuration of deprecated legacy subsystems, and do any necessary configuration update of existent and supported subsystems.
The following subtasks are executed to add new subsystems:
add-subsystem(name=batch-jberet)
add-subsystem(name=singleton)
The following subtasks are executed to migrate legacy subsystems:
migrate-subsystem(name=messaging)
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The subsystems-management-resources subtask named add-subsystem, and attribute name of value batch-jberet, is responsible for adding the batch-jberet subsystem.
The task fully delegates its work to subtasks:
add-extension(name=org.wildfly.extension.batch.jberet), which adds the subsystem's extension
add-subsystem-config(name=batch-jberet), which adds the subsystem configuration
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The add-subsystem(name=batch-jberet) subtask named add-extension, and attribute name of value org.wildfly.extension.batch.jberet, is responsible for adding the extension with module name org.wildfly.extension.batch.jberet subsystem to the configuration.
The task execution's status result is:
Success, if the extension was added
Skipped, if the extension was already in configuration
Failed, if the extension was not added due to an error
The add-subsystem(name=batch-jberet) subtask named add-subsystem-config, and attribute name of value batch-jberet, is responsible for adding the batch-jberet subsystem's configuration.
The task execution's status result is:
Success, if the subsystem was added
Skipped, if the subsystem was already in configuration
Failed, if the task failed to add the subsystem due to an error
The subsystems-management-resources subtask named add-subsystem, and attribute name of value request-controller, is responsible for adding the subsystem.
The task fully delegates its work to subtasks:
add-extension(name=org.wildfly.extension.clustering.singleton), which adds the subsystem's extension
add-subsystem-config(name=singleton), which adds the subsystem configuration
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The add-subsystem(name=singleton) subtask named add-extension, and attribute name of value org.wildfly.extension.clustering.singleton, is responsible for adding the extension with module name org.wildfly.extension.clustering.singleton subsystem to the configuration.
The task execution's status result is:
Success, if the extension was added
Skipped, if the extension was already in configuration
Failed, if the extension was not added due to an error
The add-subsystem(name=singleton) subtask named add-subsystem-config, and attribute name of value singleton, is responsible for adding the subsystem's configuration.
The task execution's status result is:
Success, if the subsystem was added
Skipped, if the subsystem was already in configuration
Failed, if the task failed to add the subsystem due to an error
The subsystems-management-resources subtask named migrate-subsystem, and attribute name of value messaging, is responsible for migrating the configuration of the legacy subsystem.
The task execution's status result is:
Success, if the subsystem was migrated
Skipped, if the subsystem was not found in the configuration
Failed, if the task failed to migrate the subsystem due to an error
Please note that if the subsystem migration may succeed with warnings, for instance due to an unsupported feature. In such case the warnings will be provided in the result attribute named migration-warnings.
The config-file subtask named security-realms is responsible for migrating the security realms configuration, through management operations.
The task execution gathers the security realms present in the config file, and executes an instance of the security-realm subtask for each security-realm found, to handle its migration.
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The security-realms subtask named security-realm handles the migration a single security-realm. The task name also includes a name attribute, which value is the specific security-realm name migrated.
The task execution's status result is:
Success, if the task's security-realm migration was successful
Skipped, if the task was skipped by the environment
Failed, if the task's security-realm migration failed due to an error
The config-file subtask named deployments is responsible for migrating the config file's deployments configuration, through management operations.
The task execution gathers the deployments present in the config file, and executes an instance of the remove-deployment subtask for each deployment found, to handle its removal.
The task execution's status result is:
Success, if no subtask failed, and at least one subtask succeed
Skipped, if all subtasks were skipped
Failed, if a subtask failed
The deployments subtask named remove-deployment handles the removal of a single deployment. The task name also includes a name attribute, which value is the specific deployment name.
The task execution's status result is:
Success, if the deployment removal was successful
Skipped, if the task was skipped by the environment
Failed, if the deployment removal failed due to an error