# Migrating from JBoss EAP 6.4 to JBoss EAP 7.0

version 1.1.0.Alpha-SNAPSHOT, 2018-03-12T07:45:04Z

## 1. Overview

This document describes how to use the JBoss Server Migration Tool to migrate from JBoss EAP 6.4 to JBoss EAP 7.0.

    ----------------------------------------------------------
    ----  JBoss Server Migration Tool  -----------------------
    ----------------------------------------------------------

    Retrieving servers...
    INFO SOURCE server name: EAP, version: 6.4.0.GA.
    INFO TARGET server name: JBoss EAP, version: 7.0.0.GA.

    Server migration starting...

The server migration from JBoss EAP 6.4 to JBoss EAP 7.0 includes:

- Modules Migration

- Standalone Server Migration

- Managed Domain Migration

## 2. Modules Migration

The JBoss Server Migration Tool is capable of migrating any module installed in the source server, as long as the module is not already installed on the target server.

The migration of source server’s module can be done explicitly, i.e. by user demand, or implicitly, because a migrated module or server configuration depends on it.

You can specify which modules should be migrated or not, by using the `modules.includes` and `modules.excludes` environment properties:

- A module whose ID is referenced by the `modules.excludes` environment property is never migrated.

- A module whose ID is referenced by the `modules.includes` environment property is always migrated, unless it referenced by the `modules.excludes` environment property.

Important | The syntax for a module ID is name:slot; The slot is optional, and if it is not specified, defaults to main.

As an example, to migrate modules `com.example.moduleA` and `com.example.moduleB`, and do not migrate module `com.example.moduleC`:

- You can configure the properties in the tool’s `config/environment.properties` file:

      modules.includes=com.example.moduleA,com.example.moduleB
      modules.excludes=com.example.moduleC

- You can include the above properties in your own custom properties file, and then pass the file on the command line using the `--environment` argument.

- You can pass the information on the command line using a system property. The environment property names must be prefixed with `jboss.server.migration.`:

      -Djboss.server.migration.modules.includes="com.example.moduleA,com.example.moduleB" -Djboss.server.migration.modules.excludes="com.example.moduleC"

Warning | The JBoss Server Migration Tool does not verify that the source server’s module is compatible with the target server, and the migration of an incompatible module may cause the target server to malfunction, or not work at all.

## 3. Standalone Server Migration

### 3.1. Standalone Configuration Processing Overview

When tasked to migrate standalone server configurations, the JBoss Server Migration Tool migrates the configuration files and related content from the source server to the target server. This migration task is optional.

If you run the migration tool in `interactive` mode, which is the default, you are are prompted to confirm its execution.

    Migrate the source's standalone server?
    yes/no?

- If you reply with yes or y, the standalone server migration proceeds.

- If you reply with no or n, the standalone server migration is skipped.

If you choose to proceed, the tool starts by migrating the source standalone server’s content. Because both the source and target servers use a similar cyphered content repository to store data that is referenced by standalone server configurations, such as deployments and deployment overlays, migration of this data merely consists of finding and copying the content from the source server to the target server.

    INFO  [ServerMigrationTask#5] Migrating standalone content found: [22/caa450a9ba3b84eaf5a15b6da418b92ce6c98e/content, 23/b62a37ba8a4830622bfcdb960280577cc6796e/content, 40/8bcb8a4480739d370ebf70fbcabb33c1508c50/content, 88/96c992d1b9866945a5015b72f8d254d3d5c132/content, ea/69fbffdf08b320c09ad1acc7d31deba5a7787b/content, fc/8ec517e0b169fb27b61ff90f04de5dd8ca8d52/content]
    INFO  [ServerMigrationTask#6] Resource with path /jboss-eap-6.4/standalone/data/content/22/caa450a9ba3b84eaf5a15b6da418b92ce6c98e/content migrated.
    INFO  [ServerMigrationTask#7] Resource with path /jboss-eap-6.4/standalone/data/content/23/b62a37ba8a4830622bfcdb960280577cc6796e/content migrated.
    INFO  [ServerMigrationTask#8] Resource with path /jboss-eap-6.4/standalone/data/content/40/8bcb8a4480739d370ebf70fbcabb33c1508c50/content migrated.
    INFO  [ServerMigrationTask#9] Resource with path /jboss-eap-6.4/standalone/data/content/88/96c992d1b9866945a5015b72f8d254d3d5c132/content migrated.
    INFO  [ServerMigrationTask#10] Resource with path /jboss-eap-6.4/standalone/data/content/ea/69fbffdf08b320c09ad1acc7d31deba5a7787b/content migrated.
    INFO  [ServerMigrationTask#11] Resource with path /jboss-eap-6.4/standalone/data/content/fc/8ec517e0b169fb27b61ff90f04de5dd8ca8d52/content migrated.

Next, the tool scans the source server for standalone server configurations files and prints the results in the console.

    INFO  [ServerMigrationTask#3] Retrieving source's standalone configurations...
    INFO  [ServerMigrationTask#3] /jboss-eap-6.4/standalone/configuration/standalone-full-ha.xml
    INFO  [ServerMigrationTask#3] /jboss-eap-6.4/standalone/configuration/standalone-full.xml
    INFO  [ServerMigrationTask#3] /jboss-eap-6.4/standalone/configuration/standalone-ha.xml
    INFO  [ServerMigrationTask#3] /jboss-eap-6.4/standalone/configuration/standalone-osgi.xml
    INFO  [ServerMigrationTask#3] /jboss-eap-6.4/standalone/configuration/standalone.xml

If you run the migration tool in `non-interactive` mode, the JBoss Server Migration Tool migrates all listed configuration files.

If you run the migration tool in `interactive` mode, which is the default, you are presented with the following prompt.

    Migrate all configurations?
    yes/no?

- If you reply yes, all listed configuration files are migrated.

- If you reply no, you receive a prompt asking to confirm the migration, for each listed configuration file:

      Migrate configuration /jboss-eap-6.4/standalone/configuration/standalone.xml ?
      yes/no? y

### 3.2. Customizing the Migration of the Standalone Configuration

The standalone server migration can be customized by configuring the following environment properties:

Property Name | Property Description
--- | ---
`standalone.skip` | If set to `true`, the tool skips the entire standalone server migration.
`server.source.standalone.serverDir` | Defines an alternative path for the source standalone server directory, which defaults to the source standalone server’s base directory.
`server.source.standalone.configDir` | Defines an alternative path for the source standalone server configuration directory, which defaults to the source standalone server’s `configuration` directory.
`server.source.standalone.configFiles` | Specifies the file names of the source standalone server configurations to be migrated.
`server.target.standalone.serverDir` | Defines an alternative path for the target standalone server directory, which defaults to the target standalone server’s base directory.
`server.target.standalone.configDir` | Defines an alternative path for the target standalone server configuration directory, which defaults to the target’s standalone server’s `configuration` directory.

The environment configuration can be customized in one of the following ways:

- You can configure the properties in the tool’s `config/environment.properties` file:

      standalone.skip=false
      server.source.standalone.serverDir=standalone
      server.source.standalone.configDir=configuration
      server.source.standalone.configFiles=standalone.xml,standalone-full.xml
      server.target.standalone.serverDir=standalone
      server.target.standalone.configDir=configuration

- You can include the above properties in your own custom properties file, and then pass the file on the command line using the `--environment` argument.

- You can pass the information on the command line using a system property. The environment property names must be prefixed with `jboss.server.migration.`, for example:

      -Djboss.server.migration.server.source.standalone.serverDir="standalone"

### 3.3. Standalone Configuration File Migration

When migrating the standalone server configuration, the JBoss Server Migration Tool first copies the source configuration files to the target server. It then updates the configuration to not only work correctly in the target server, but also to take advantage of the target server’s new functionality.

#### 3.3.1. Remove Unsupported Subsystems

All subsystems, and related extensions, which are not supported by JBoss EAP 7.0, are automatically removed from a migrated configuration.

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

Subsystem Name | Configuration Namespace | Extension Module
--- | --- | ---
cmp | urn:jboss:domain:cmp:* | org.jboss.as.cmp
configadmin | urn:jboss:domain:configadmin:* | org.jboss.as.configadmin
jaxr | urn:jboss:domain:jaxr:* | org.jboss.as.jaxr
osgi | urn:jboss:domain:osgi:* | org.jboss.as.osgi
threads | urn:jboss:domain:threads:* | org.jboss.as.threads

Note | A subsystem installed in JBoss EAP 6.4 by the user, is also considered as unsupported by JBoss EAP 7.0.

The console logs the configuration namespaces, and extension modules, of unsupported subsystems removed from the server configuration being migrated:

    INFO  [ServerMigrationTask#5] Unsupported extensions removed: [org.jboss.as.jaxr, org.jboss.as.threads, org.jboss.as.cmp]
    INFO  [ServerMigrationTask#5] Unsupported subsystems removed: [urn:jboss:domain:jaxr:1.1, urn:jboss:domain:cmp:1.1, urn:jboss:domain:threads:1.1]

#### 3.3.2. Migrate Referenced Modules

A migrated configuration may reference and depend on a module that is not installed on the target server. The tool automatically migrates the referenced modules, and their dependent modules as well.

A module is migrated when it is referenced by:

- A `security-realm` configuration, as plug-in(s) module

- A `datasource` subsystem configuration, as datasource driver(s) module

- An `ee` subsystem configuration, as a global module

- A `naming` subsystem configuration, as an Object Factory module

- A `messaging` subsystem configuration, as JMS Bridge module

- A `vault` configuration

The console logs a message noting the module ID for any module that is migrated, for example:

    INFO  [ServerMigrationTask#18] Module cmtool.security-realms:main migrated.
    INFO  [ServerMigrationTask#19] Module cmtool.datasources:main migrated.
    INFO  [ServerMigrationTask#20] Module cmtool.ee1:main migrated.
    INFO  [ServerMigrationTask#21] Module cmtool.ee2:main migrated.
    INFO  [ServerMigrationTask#22] Module cmtool.naming:main migrated.

Tip | It is possible to exclude the migration of specific modules by specifying the id(s) in the environment property named `modules.excludes`.

#### 3.3.3. Migrate Referenced Paths

A migrated configuration may reference paths, i.e. files and directories, which may need to be migrated to the target server.

A referenced path is migrated only if it’s not an absolute path, and such migration consists in copying the resource to such path, but relative to the migrated configuration, in the target server.

The tools automatically migrates the following paths references:

- `Vault` keystore and encrypted file’s directory.

The console logs a message noting each path migration, for example:

    INFO  [ServerMigrationTask#25] Resource with path /jboss-eap-6.4/vault/vault.keystore migrated.

If you prefer, you can configure the environment properties to customize the migration of referenced paths.

Property Name | Property Description
--- | ---
`paths.migrate-paths-requested-by-configuration.vault.skip` | If set to `true`, the tool skips the migration of `Vault` referenced paths.

#### 3.3.4. Migrate jacorb Subsystem

The jacorb subsystem is deprecated in JBoss EAP 7.0 and is replaced by the iiop-openjdk subsystem.

By default, the JBoss Server Migration Tool automatically migrates any legacy subsystem configuration found. If you prefer this migration task is not executed, you can set the `subsystem.jacorb.migrate.skip` environment property value to `true`.

The legacy subsystem migration is done without requiring any interaction from the user.

The outcome of the legacy jacorb subsystem migration is printed in the console, as an example:

    INFO  [ServerMigrationTask#331] Migrating subsystem jacorb configurations...
    INFO  [ServerMigrationTask#335] Subsystem config /subsystem=jacorb migrated.
    INFO  [ServerMigrationTask#336] Extension org.jboss.as.jacorb removed.
    INFO  [ServerMigrationTask#331] Subsystem jacorb configurations migrated.

Any issues encountered during the migration are written to the log files and displayed in the migration console.

#### 3.3.5. Migrate web Subsystem

The web subsystem is deprecated in JBoss EAP 7.0 and is replaced by the undertow subsystem.

By default, the JBoss Server Migration Tool automatically migrates any legacy subsystem configuration found. If you prefer this migration task is not executed, you can set the `subsystem.web.migrate.skip` environment property value to `true`.

The legacy subsystem migration is done without requiring any interaction from the user.

The outcome of the legacy web subsystem migration is printed in the console, as an example:

    INFO  [ServerMigrationTask#331] Migrating subsystem web configurations...
    INFO  [ServerMigrationTask#335] Subsystem config /subsystem=web migrated.
    INFO  [ServerMigrationTask#336] Extension org.jboss.as.web removed.
    INFO  [ServerMigrationTask#331] Subsystem web configurations migrated.

Any issues encountered during the migration are written to the log files and displayed in the migration console.

#### 3.3.6. Migrate messaging Subsystem

The messaging subsystem is deprecated in JBoss EAP 7.0 and is replaced by the messaging-activemq subsystem.

By default, the JBoss Server Migration Tool automatically migrates any legacy subsystem configuration found. If you prefer this migration task is not executed, you can set the `subsystem.messaging.migrate.skip` environment property value to `true`.

The legacy subsystem migration is done without requiring any interaction from the user.

The outcome of the legacy messaging subsystem migration is printed in the console, as an example:

    INFO  [ServerMigrationTask#331] Migrating subsystem messaging configurations...
    INFO  [ServerMigrationTask#335] Subsystem config /subsystem=messaging migrated.
    INFO  [ServerMigrationTask#336] Extension org.jboss.as.messaging removed.
    INFO  [ServerMigrationTask#331] Subsystem messaging configurations migrated.

Any issues encountered during the migration are written to the log files and displayed in the migration console.

#### 3.3.7. Update the infinispan Subsystem

The JBoss Server Migration Tool makes the following updates to the infinispan subsystem configuration to better match the JBoss EAP 7.0 default configurations.

- Adds the `ejb` cache, which is present in the JBoss EAP 7.0 default configuration.

- Adds the `server` cache, which is present in the JBoss EAP 7.0 default configuration.

- Fixes the module name in the `hibernate` cache configuration.

By default, the tool automatically updates any infinispan subsystem configuration to include these changes. If you prefer, you can configure the environment properties to customize the process of updating the infinispan subsystem configuration.

Property Name | Property Description
--- | ---
`subsystem.infinispan.update.skip` | If set to `true`, the tool skips the update of the infinispan subsystem.
`subsystem.infinispan.update.add-infinispan-ejb-cache.skip` | If set to `true`, the tool does not add the `ejb` cache.
`subsystem.infinispan.update.add-infinispan-server-cache.skip` | If set to `true`, the tool does not add the `server` cache.
`subsystem.infinispan.update.fix-hibernate-cache-module-name.skip` | If set to `true`, the tool does not fix the module name in the `hibernate` cache configuration.

Upon successful migration of a infinispan subsystem configuration, you should see messages in the console such as:

    INFO  [ServerMigrationTask#44] Server cache added to Infinispan subsystem configuration.
    INFO  [ServerMigrationTask#45] Ejb cache added to Infinispan subsystem configuration.
    INFO  [ServerMigrationTask#46] Infinispan subsystem's cache hibernate 'module' attribute updated to org.hibernate.infinispan.

#### 3.3.8. Update the ee Subsystem

The ee Subsystem in JBoss EAP 7.0 provides support for new Java EE 7 features.

- You can configure instances of Java EE 7 concurrency utilities, such as container-managed `Executors`.

- You can define the Java EE 7 default resources, such as the default data source, by specifying the original JNDI addresses.

By default, the tool updates the ee subsystem configuration to include the new features. If you prefer, you can configure the environment properties to customize the process of updating the ee subsystem configuration.

Property Name | Property Description
--- | ---
`subsystem.ee.update.skip` | If set to `true`, the tool skips the update of the ee subsystem.
`subsystem.ee.update.setup-ee-concurrency-utilities.skip` | If set to `true`, the tool does not add the default instances of concurrency utilities
`subsystem.ee.update.setup-javaee7-default-bindings.skip` | If set to `true`, the tool does not set up Java EE 7 default resources.
`subsystem.ee.update.setup-javaee7-default-bindings.defaultDataSourceName` | Specifies the name of the default data source to look for in the source configuration.
`subsystem.ee.update.setup-javaee7-default-bindings.defaultDataSourceJndiName` | Specifies the JNDI name for the default data source.
`subsystem.ee.update.setup-javaee7-default-bindings.defaultJmsConnectionFactoryName` | Specifies the name of the JMS connection factory.
`subsystem.ee.update.setup-javaee7-default-bindings.defaultJmsConnectionFactoryJndiName` | Specifies the JNDI name for the default JMS connection factory.

Warning | JNDI names that are specified are assumed to be valid. JNDI names are not validated by the tool.

For concurrency utilities instances, the tool automatically configures the exact same instances that are present in all JBoss EAP 7.0 default configurations and does not require any user interaction. The log simply indicates the instances were added:

    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.

When defining Java EE 7 default resources, by default the tool looks for the resources present in default JBoss EAP 6.4 configurations and select these if present.

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

In the case where the tool does not find such resources, then user input is required. The tool lists all available resources in the configuration, and then asks the user to select the one that should be set as the default, or to manually provide the JNDI address of the original resource. The following is an example of the interaction that occurs when migrating a configuration file with two configured data sources, `ExampleDS1` and `ExampleDS2` and defining the default data source:

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

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

Note | If you run the migration tool in `non-interactive` mode and the expected JBoss EAP 6.4 default resources are not available, for example the default JMS connection factory, the tool will not configure those resources.

#### 3.3.9. Update the ejb3 Subsystem

The JBoss Server Migration Tool makes the following updates to the ejb3 subsystem configuration to better match the JBoss EAP 7.0 default configurations.

- The remote service configuration is updated to reference the new HTTP connector.

- The `default-sfsb-passivation-disabled-cache` attribute is configured to use the `efault-sfsb-cache`.

- Legacy passivation store and cache configurations are replaced with the JBoss EAP 7.0 defaults.

By default, the tool updates any ejb3 subsystem configuration to include these changes. If you prefer, you can configure the environment properties to customize the process of updating the ejb3 subsystem configuration.

Property Name | Property Description
--- | ---
`subsystem.ejb3.update.skip` | If set to `true`, the tool skips the update of the ejb3 subsystem.
`subsystem.ejb3.update.activate-ejb3-remoting-http-connector.skip` | If set to `true`, the tool does not update the `EJB Remoting` configuration.
`subsystem.ejb3.update.add-infinispan-passivation-store-and-distributable-cache.skip` | If set to `true`, the tool does not replace the `passivation store` and `cache` configurations.
`subsystem.ejb3.update.setup-default-sfsb-passivation-disabled-cache.skip` | If set to `true`, the tool does not update the `default-sfsb-passivation-disabled-cache` configuration.

Upon successful migration of the ejb3 subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#52] EJB3 subsystem's remote service configured to use HTTP Remoting connector.
    INFO  [ServerMigrationTask#53] EJB3 subsystem's 'default-sfsb-passivation-disabled-cache' attribute set to simple.
    INFO  [ServerMigrationTask#54] Legacy file passivation store removed from EJB3 subsystem configuration.
    INFO  [ServerMigrationTask#54] Infinispan passivation store added to EJB3 subsystem configuration.
    INFO  [ServerMigrationTask#54] Legacy 'passivating' cache removed from EJB3 subsystem configuration.
    INFO  [ServerMigrationTask#54] Distributable cache added to EJB3 subsystem configuration.

#### 3.3.10. Update the remoting Subsystem

One of the most relevant features introduced by JBoss EAP 7.0 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 in the remoting subsystem and the tool simply updates the subsystem configuration to activate it.

By default, the tool automatically updates the remoting subsystem. If you prefer, you can set the `subsystem.remoting.update.skip` environment property to `true` to skip automatic update of the remoting subsystem configuration.

Upon successful migration of the remoting subsystem configuration, you should see the following message in the console:

    INFO  [ServerMigrationTask#33] Http connector http-remoting-connector added to Remoting subsystem configuration.

#### 3.3.11. Update the undertow Subsystem

In addition to migrating the web subsystem to JBoss EAP 7.0, the JBoss Server Migration Tool adds the following functionality provided by the new undertow subsystem, which is configured in the JBoss EAP 7.0 default server configurations.

- Sets the default `HTTP Listener` redirect socket.

- Adds support for Java EE 7 `Websockets`.

- Sets the default `Server` response header.

- Sets the default `X-Powered-By` response header.

By default, the tool automatically updates any undertow subsystem configuration to include these changes. If you prefer, you can configure the environment properties to customize the process of updating the undertow subsystem configuration.

Property Name | Property Description
--- | ---
`subsystem.undertow.update.skip` | If set to `true`, the tool skips the update of the undertow subsystem.
`subsystem.undertow.update.set-default-http-listener-redirect-socket.skip` | If set to `true`, the tool does not set the default `HTTP Listener` redirect socket.
`subsystem.undertow.update.add-undertow-websockets.skip` | If set to `true`, the tool does not add support for WebSockets.
`subsystem.undertow.update.add-response-header.server-header.skip` | If set to `true`, the tool does not set the default `Server` response header.
`subsystem.undertow.update.add-response-header.x-powered-by-header.skip` | If set to `true`, the tool does not set the default `X-Powered-By` response header.

Upon successful migration of a undertow subsystem configuration, you should see messages in the console such as:

    INFO  [ServerMigrationTask#33] Undertow's default HTTP listener 'http' redirect-socket set as 'https'.
    INFO  [ServerMigrationTask#34] Undertow's default Servlet Container configured to support Websockets.
    INFO  [ServerMigrationTask#35] Response header 'server-header' set as 'Server: JBoss-EAP/7' in Undertow's config /subsystem=undertow
    INFO  [ServerMigrationTask#36] Response header 'x-powered-by-header' set as 'X-Powered-By: Undertow/1' in Undertow's config /subsystem=undertow

#### 3.3.12. Update the messaging-activemq Subsystem

In addition to migrating the messaging subsystem to JBoss EAP 7.0, the JBoss Server Migration Tool also adds the following new functionality provided by the messaging-activemq subsystems, which is configured in the JBoss EAP 7.0 default standalone configuration files.

- Adds the default HTTP connector and acceptor, enabling the new HTTP-based remote messaging clients.

By default, the tool automatically updates any messaging-activemq subsystem configuration. If you prefer, you can set the `subsystem.messaging-activemq.update.skip` environment property to `true` to skip automatic update of messaging-activemq subsystem configurations.

Upon successful migration of a messaging-activemq subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#123] HTTP Acceptor named http-acceptor added to Messaging ActiveMQ subsystem configuration.
    INFO  [ServerMigrationTask#123] HTTP Connector named http-connector added to Messaging ActiveMQ subsystem configuration.

#### 3.3.13. Add the batch-jberet Subsystem

The JBoss EAP 7.0 batch-jberet subsystem provides support for JSR 352: Batch Applications for the Java Platform.

Its default configuration is automatically added to the migrated configuration file, unless the environment property named `subsystem.batch-jberet.add.skip` is set to `true`.

The subsystem and related extension are added without any interaction required by the user. Upon successful addition of the batch-jberet subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#49] Adding subsystem batch-jberet configuration(s)...
    INFO  [ServerMigrationTask#50] Extension org.wildfly.extension.batch.jberet added.
    INFO  [ServerMigrationTask#51] Subsystem config /subsystem=batch-jberet added.

#### 3.3.14. Add the request-controller Subsystem

The JBoss EAP 7.0 request-controller subsystem provides congestion control and graceful shutdown functionality.

Its default configuration is automatically added to the migrated configuration file, unless the environment property named `subsystem.request-controller.add.skip` is set to `true`.

The subsystem and related extension are added without any interaction required by the user. Upon successful addition of the request-controller subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#49] Adding subsystem request-controller configuration(s)...
    INFO  [ServerMigrationTask#50] Extension org.wildfly.extension.request-controller added.
    INFO  [ServerMigrationTask#51] Subsystem config /subsystem=request-controller added.

#### 3.3.15. Add the security-manager Subsystem

The JBoss EAP 7.0 security-manager subsystem provides the support for Java EE 7 security permissions.

Its default configuration is automatically added to the migrated configuration file, unless the environment property named `subsystem.security-manager.add.skip` is set to `true`.

The subsystem and related extension are added without any interaction required by the user. Upon successful addition of the security-manager subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#49] Adding subsystem security-manager configuration(s)...
    INFO  [ServerMigrationTask#50] Extension org.wildfly.extension.security.manager added.
    INFO  [ServerMigrationTask#51] Subsystem config /subsystem=security-manager added.

#### 3.3.16. Add the singleton Subsystem

As its name indicates, the JBoss EAP 7.0 singleton subsystem provides the singleton functionality.

Its default configuration is automatically added to the migrated configuration file, unless the environment property named `subsystem.singleton.add.skip` is set to `true`.

The subsystem and related extension are added without any interaction required by the user. Upon successful addition of the singleton subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#49] Adding subsystem singleton configuration(s)...
    INFO  [ServerMigrationTask#50] Extension org.wildfly.extension.clustering.singleton added.
    INFO  [ServerMigrationTask#51] Subsystem config /subsystem=singleton added.

#### 3.3.17. Setup HTTP Upgrade Management

JBoss EAP 7.0 management clients use the new HTTP Upgrade mechanism, and the JBoss Migration Tool makes all of configuration changes needed for clients to work properly with the migrated configuration.

The configuration changes are fully automated, and upon successful completion of the configuration, you should see the following messages in the console:

    [ServerMigrationTask#75] HTTP upgrade management setup starting...
    [ServerMigrationTask#76] Management interface 'http-interface' http upgrade enabled.
    [ServerMigrationTask#77] Socket binding 'management-https' port set to ${jboss.management.https.port:9993}.
    [ServerMigrationTask#75] HTTP upgrade management setup completed.

If you prefer to skip the configuration of HTTP Upgrade management, set the environment property named `management.setup-http-upgrade.skip` to `true`.

#### 3.3.18. Set Up Private Interface

The JBoss EAP 7.0 default configuration uses a new `private` interface on all `jgroups` socket bindings. The JBoss Server Migration Tool automatically adds the new interface to migrated configurations with `jgroups` socket bindings, and updates these to use it.

Upon successful configuration of the private interface, you should see the following messages in the console:

    INFO  [ServerMigrationTask#160] Interface private added.
    INFO  [ServerMigrationTask#161] Socket binding /socket-binding-group=standard-sockets/socket-binding=jgroups-mping interface set to private
    INFO  [ServerMigrationTask#161] Socket binding /socket-binding-group=standard-sockets/socket-binding=jgroups-tcp interface set to private
    INFO  [ServerMigrationTask#161] Socket binding /socket-binding-group=standard-sockets/socket-binding=jgroups-tcp-fd interface set to private
    INFO  [ServerMigrationTask#161] Socket binding /socket-binding-group=standard-sockets/socket-binding=jgroups-udp interface set to private
    INFO  [ServerMigrationTask#161] Socket binding /socket-binding-group=standard-sockets/socket-binding=jgroups-udp-fd interface set to private

If you prefer to skip the configuration of the private interface, set the environment property named `interface.private.setup.skip` to `true`.

#### 3.3.19. Add Socket Binding Port Expressions

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

- `ajp`

- `http`

- `https`

The tool automatically adds the value expressions to the migrated JBoss EAP 6.4 configurations.

The following message(s) in the console indicates this configuration update:

    INFO  [ServerMigrationTask#465] Adding socket binding's port expressions...
    INFO  [ServerMigrationTask#466] Socket binding /socket-binding-group=standard-sockets/socket-binding=ajp port value expression set as ${jboss.ajp.port:8009}.
    INFO  [ServerMigrationTask#467] Socket binding /socket-binding-group=standard-sockets/socket-binding=http port value expression set as ${jboss.http.port:8080}.
    INFO  [ServerMigrationTask#468] Socket binding /socket-binding-group=standard-sockets/socket-binding=https port value expression set as ${jboss.https.port:8443}.
    INFO  [ServerMigrationTask#465] Socket binding's port expressions added.

Note | The Migration Environment may be configured to skip this conifguration update, by setting environment property named `socket-bindings.add-port-expressions.skip` as `true`.

#### 3.3.20. Migrate Compatible Security Realms

Because the JBoss EAP 7.0 security realms configuration is fully compatible with the JBoss EAP 6.4 security realms configuration, they require no update by the JBoss Server Migration Tool. However, if the properties files are not referenced using an absolute path, the tool copies them to the path expected by the migrated configuration file.

This process is fully automated and requires no interaction by the user. To skip the security realms migration, set the `security-realms.migrate-properties.skip` environment property to `true`.

Upon successful migration of the security realms configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#140]  Migrating security realms...
    INFO  [ServerMigrationTask#141]  Resource with path /jboss-eap-6.4/standalone/configuration/mgmt-users.properties migrated.
    INFO  [ServerMigrationTask#141]  Resource with path /jboss-eap-6.4/standalone/configuration/mgmt-groups.properties migrated.
    INFO  [ServerMigrationTask#141]  Security realm /core-service=management/security-realm=ManagementRealm migrated.
    INFO  [ServerMigrationTask#142]  Resource with path /jboss-eap-6.4/standalone/configuration/application-users.properties migrated.
    INFO  [ServerMigrationTask#142]  Resource with path /jboss-eap-6.4/standalone/configuration/application-roles.properties migrated.
    INFO  [ServerMigrationTask#142]  Security realm /core-service=management/security-realm=ApplicationRealm migrated.

#### 3.3.21. Migrate Deployments

The JBoss Server Migration Tool, when migrating a configuration, may also migrate:

- Deployments it references, also known as persistent deployments.

- Deployments found in directories monitored by its deployment scanners.

- Deployment Overlays it references.

Warning | The migration of a deployment or deployment overlay merely consists of installing related file resources on the target server, and possibly updating the migrated configuration. The tool will not assert if these resources are compatible with the target server, which means that a migrated deployment might not work as expected, or might not work at all. Red Hat recommends that you use Red Hat Application Migration Toolkit to analyze a deployment with respect to compatibility among different JBoss servers.

Note | If you run the migration tool in `non-interactive` mode, by default the JBoss Server Migration Tool will not migrate any deployments and overlays. To migrate deployments the environment property `deployments.migrate-deployments.skip` should be set as `false`.

##### Migrate Persistent Deployments

When migrating a configuration, the tool searches for references to deployments persisted in the source server, and prints the names of the deployments found in the console, e.g.:

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

If you run the migration tool in `interactive` mode, you then see the following prompt:

    This tool is not able to assert if persistent deployments found are compatible with the target server, skip persistent deployments migration?
    yes/no?

- If you reply yes, or y, the all deployment references are removed from the migrated configuration, i.e. the deployments will not be migration.

- If you reply no, or n, you receive an additional prompt asking if all deployments should be the migrated:

      Migrate all persistent deployments found?
      yes/no?

  - If you reply yes, or y, all deployments are migrated.

  - If you reply no, or n, you receive a prompt asking to confirm the migration for each referenced deployment:

        Migrate persistent deployment 'cmtool-helloworld3.war'?
        yes/no?

    - If you reply yes, or y, the deployment is migrated.

    - If you reply no, or n, the deployment reference is removed from the migrated configuration, i.e. the deployment is not migrated.

          INFO  [ServerMigrationTask#68] Removed persistent deployment from configuration /deployment=cmtool-helloworld3.war

If you run the migration tool in `non-interactive` mode, the JBoss Server Migration Tool will migrate or not migrate `all` persistent deployments, depending on the environment configuration. Persistent deployments are migrated only if none of the following environment properties is set as `true`:

- deployments.migrate-deployments.skip

- deployments.migrate-persistent-deployments.skip

##### Migrate Deployment Scanner Deployments

Deployment scanners monitor a directory for new files and manage their deployment automatically or through special deployment marker files, and the migration tool, when migrating the server configuration, first searches for any configured deployment scanners, and then for each scanner found, searches its monitored directories for deployments marked as `deployed`.

A list with the names of deployments found are printed to the console, for instance:

    INFO  [ServerMigrationTask#68] Found deployment scanner 'default' watching directory '/jboss-eap-6.4/standalone/deployments', searching for deployments in it...
    INFO  [ServerMigrationTask#68] Scanner's deployments found: [cmtool-helloworld5.war, cmtool-helloworld6.war]

If you run the migration tool in `interactive` mode, you then see the following prompt:

    This tool is not able to assert if the scanner's deployments found are compatible with the target server, skip scanner's deployments migration?
    yes/no?

- If you reply yes, or y, all deployments are not migrated.

- If you reply no, or n, you receive an additional prompt asking if all deployments should be the migrated:

      Migrate all scanner's deployments found?
      yes/no?

  - If you reply yes, or y, all deployments are migrated.

        INFO  [ServerMigrationTask#69] Resource with path /jboss-eap-6.4/standalone/deployments/cmtool-helloworld5.war migrated.
        INFO  [ServerMigrationTask#70] Resource with path /jboss-eap-6.4/standalone/deployments/cmtool-helloworld6.war migrated.

  - If you reply no, or n, you receive a prompt asking to confirm the migration for each deployment:

        Migrate scanner's deployment 'cmtool-helloworld5.war'?
        yes/no?

    - If you reply no, or n, the deployment is not migrated.

    - If you reply yes, or y, the deployment is migrated.

      INFO  [ServerMigrationTask#69] Resource with path /{server-source-baseDir}/standalone/deployments/cmtool-helloworld5.war migrated.

If you run the migration tool in `non-interactive` mode, the JBoss Server Migration Tool will migrate or not migrate `all` deployments found, depending on the environment configuration. Persistent deployments are migrated only if none of the following environment properties is set as `true`:

- deployments.migrate-deployments.skip

- deployments.migrate-deployment-scanner-deployments.skip

##### Migrate Deployment Overlays

The migration of deployment overlays is a fully automated process. The migration tool searches for deployment overlays referenced in the standalone server configuration. It then migrates those that are linked to deployments that were migrated.

The migration tool prints a message to the console for each deployment overlay that is migrated or removed.

    INFO  [ServerMigrationTask#79] Deployment overlays found: [overlay4, overlay1, overlay2, overlay3]
    INFO  [ServerMigrationTask#79] Migrating deployment overlay 'overlay4', it's linked to deployment cmtool-helloworld2.war
    INFO  [ServerMigrationTask#80] Removed deployment overlay from configuration /deployment-overlay=overlay1
    INFO  [ServerMigrationTask#81] Removed deployment overlay from configuration /deployment-overlay=overlay2
    INFO  [ServerMigrationTask#79] Migrating deployment overlay 'overlay3', it's linked to deployment cmtool-helloworld2.war

## 4. Managed Domain Migration

### 4.1. Managed Domain Processing Overview

When tasked to migrate managed domains, the JBoss Server Migration Tool migrates the domain and host configuration files and their related domain content from the source server to the target server. This migration task is optional.

If you run the migration tool in `interactive` mode, which is the default, you are prompted to confirm its execution.

    Migrate the source's managed domain?
    yes/no?

- If you reply with yes or y, the domain migration proceeds.

- If you reply with no or n, the domain migration is skipped.

If you choose to proceed, the tool begins migrating the domain content of the source server. A cyphered repository used to store data, such as deployments and deployment overlays, that are referenced by the source server’s domain and host configurations. Because the source and target servers use a similar content repository, the migration of this data merely consists of finding and copying the content between the servers. The migration tool prints the results in the console.

    INFO  [ServerMigrationTask#397]  Migrating domain content found: [22/caa450a9ba3b84eaf5a15b6da418b92ce6c98e/content, 23/b62a37ba8a4830622bfcdb960280577cc6796e/content, 40/8bcb8a4480739d370ebf70fbcabb33c1508c50/content, 88/96c992d1b9866945a5015b72f8d254d3d5c132/content, ea/69fbffdf08b320c09ad1acc7d31deba5a7787b/content, fc/8ec517e0b169fb27b61ff90f04de5dd8ca8d52/content]
    INFO  [ServerMigrationTask#398]  Resource with path /jboss-eap-6.4/domain/data/content/22/caa450a9ba3b84eaf5a15b6da418b92ce6c98e/content migrated.
    INFO  [ServerMigrationTask#399]  Resource with path /jboss-eap-6.4/domain/data/content/23/b62a37ba8a4830622bfcdb960280577cc6796e/content migrated.
    INFO  [ServerMigrationTask#400]  Resource with path /jboss-eap-6.4/domain/data/content/40/8bcb8a4480739d370ebf70fbcabb33c1508c50/content migrated.
    INFO  [ServerMigrationTask#401]  Resource with path /jboss-eap-6.4/domain/data/content/88/96c992d1b9866945a5015b72f8d254d3d5c132/content migrated.
    INFO  [ServerMigrationTask#402]  Resource with path /jboss-eap-6.4/domain/data/content/ea/69fbffdf08b320c09ad1acc7d31deba5a7787b/content migrated.
    INFO  [ServerMigrationTask#403]  Resource with path /jboss-eap-6.4/domain/data/content/fc/8ec517e0b169fb27b61ff90f04de5dd8ca8d52/content migrated.

Next, the migration tool scans the source server for domain configuration files and prints the results in the console.

    INFO  [ServerMigrationTask#312]  Retrieving source's domain configurations...
    INFO  [ServerMigrationTask#312]  /jboss-eap-6.4/domain/configuration/domain.xml

If you run the migration tool `non-interactive` mode, the JBoss Server Migration Tool migrates all listed domain configuration files.

If you run the migration tool in `interactive` mode, which is the default, you are presented with the following prompt.

    Migrate all configurations?
    yes/no?

- If you reply with yes, all listed configuration files are migrated.

- If you reply with no, you are prompted to confirm the migration for each listed configuration file:

      Migrate configuration /jboss-eap-6.4/domain/configuration/domain.xml ?
      yes/no? y

Next, the migration tool scans the source server for host configurations files and prints the results in the console.

    INFO  [ServerMigrationTask#457] Retrieving source's host configurations...
    INFO  [ServerMigrationTask#457] /jboss-eap-6.4/domain/configuration/host-master.xml
    INFO  [ServerMigrationTask#457] /jboss-eap-6.4/domain/configuration/host-slave.xml
    INFO  [ServerMigrationTask#457] /jboss-eap-6.4/domain/configuration/host.xml

If you run the migration tool in `non-interactive` mode, the JBoss Server Migration Tool migrates all listed host configuration files.

If you run the migration tool in `interactive` mode, which is the default, you are presented with the following prompt.

    Migrate all configurations?
    yes/no?

- If you reply with yes, all listed configuration files are migrated.

- If you reply with no, you are prompted to confirm the migration for each listed configuration file:

      Migrate configuration /jboss-eap-6.4/domain/configuration/host.xml ?
      yes/no? y

### 4.2. Customizing the Migration of the Managed Domain Configuration

Managed domain migration can be customized by configuring the following environment properties:

Property Name | Property Description
--- | ---
`domain.skip` | If set to `true`, the tool skips the entire domain migration.
`server.source.domain.domainDir` | Defines an alternative path for the source domain server directory, which defaults to the source domain server’s base directory.
`server.source.domain.configDir` | Defines an alternative path for the source domain server `configuration/` directory, which defaults to the source server’s domain `configuration/` directory.
`server.source.domain.domainConfigFiles` | Specifies a comma delimited list of the file names of the source server domain configurations that are to be migrated.
`server.source.domain.hostConfigFiles` | Specifies a comma delimited list of the file names of the source server host configurations that are to be migrated.
`server.target.domain.domainDir` | Defines an alternative path for the target domain server directory, which defaults to the target domain server’s base directory.
`server.target.domain.configDir` | Defines an alternative path for the target domain server `configuration/` directory, which defaults to the target server’s domain `configuration/` directory.

The environment configuration may be done in one of the following ways:

- You can configure the tool’s `config/environment.properties` properties file:

    domain.skip=false
    server.source.domain.domainDir=domain
    server.source.domain.configDir=configuration
    server.source.domain.domainConfigFiles=domain.xml
    server.source.domain.hostConfigFiles=host-master.xml, host.xml
    server.target.domain.domainDir=domain
    server.target.domain.configDir=configuration

- You can configure the properties in your own custom properties file and pass the file on the command line using the `--environment` argument.

- You can pass the information on the command line using system properties. In this case, all environment property names should be prefixed with `jboss.server.migration.`.

### 4.3. Domain Configuration File Migration

When migrating the domain configuration, the JBoss Server Migration Tool first copies the source configuration files to the target server. It then updates the configuration to not only work correctly in the target server, but also to take advantage of the target server’s new functionality.

#### 4.3.1. Remove Unsupported Subsystems

All subsystems, and related extensions, which are not supported by JBoss EAP 7.0, are automatically removed from a migrated configuration.

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

Subsystem Name | Configuration Namespace | Extension Module
--- | --- | ---
cmp | urn:jboss:domain:cmp:* | org.jboss.as.cmp
configadmin | urn:jboss:domain:configadmin:* | org.jboss.as.configadmin
jaxr | urn:jboss:domain:jaxr:* | org.jboss.as.jaxr
osgi | urn:jboss:domain:osgi:* | org.jboss.as.osgi
threads | urn:jboss:domain:threads:* | org.jboss.as.threads

Note | A subsystem installed in JBoss EAP 6.4 by the user, is also considered as unsupported by JBoss EAP 7.0.

The console logs the configuration namespaces, and extension modules, of unsupported subsystems removed from the server configuration being migrated:

    INFO  [ServerMigrationTask#5] Unsupported extensions removed: [org.jboss.as.jaxr, org.jboss.as.threads, org.jboss.as.cmp]
    INFO  [ServerMigrationTask#5] Unsupported subsystems removed: [urn:jboss:domain:jaxr:1.1, urn:jboss:domain:cmp:1.1, urn:jboss:domain:threads:1.1]

#### 4.3.2. Migrate Referenced Modules

A migrated configuration may reference and depend on a module that is not installed on the target server. The tool automatically migrates the referenced modules, and their dependent modules as well.

A module is migrated when it is referenced by:

- A `security-realm` configuration, as plug-in(s) module

- A `datasource` subsystem configuration, as datasource driver(s) module

- An `ee` subsystem configuration, as a global module

- A `naming` subsystem configuration, as an Object Factory module

- A `messaging` subsystem configuration, as JMS Bridge module

- A `vault` configuration

The console logs a message noting the module ID for any module that is migrated, for example:

    INFO  [ServerMigrationTask#18] Module cmtool.security-realms:main migrated.
    INFO  [ServerMigrationTask#19] Module cmtool.datasources:main migrated.
    INFO  [ServerMigrationTask#20] Module cmtool.ee1:main migrated.
    INFO  [ServerMigrationTask#21] Module cmtool.ee2:main migrated.
    INFO  [ServerMigrationTask#22] Module cmtool.naming:main migrated.

Tip | It is possible to exclude the migration of specific modules by specifying the id(s) in the environment property named `modules.excludes`.

#### 4.3.3. Migrate Referenced Paths

A migrated configuration may reference paths, i.e. files and directories, which may need to be migrated to the target server.

A referenced path is migrated only if it’s not an absolute path, and such migration consists in copying the resource to such path, but relative to the migrated configuration, in the target server.

The tools automatically migrates the following paths references:

- `Vault` keystore and encrypted file’s directory.

The console logs a message noting each path migration, for example:

    INFO  [ServerMigrationTask#25] Resource with path /jboss-eap-6.4/vault/vault.keystore migrated.

If you prefer, you can configure the environment properties to customize the migration of referenced paths.

Property Name | Property Description
--- | ---
`paths.migrate-paths-requested-by-configuration.vault.skip` | If set to `true`, the tool skips the migration of `Vault` referenced paths.

#### 4.3.4. Migrate jacorb Subsystem

The jacorb subsystem is deprecated in JBoss EAP 7.0 and is replaced by the iiop-openjdk subsystem.

By default, the JBoss Server Migration Tool automatically migrates any legacy subsystem configuration found. If you prefer this migration task is not executed, you can set the `subsystem.jacorb.migrate.skip` environment property value to `true`.

The legacy subsystem migration is done without requiring any interaction from the user.

The outcome of the legacy jacorb subsystem migration is printed in the console, as an example:

    INFO  [ServerMigrationTask#331] Migrating subsystem jacorb configurations...
    INFO  [ServerMigrationTask#335] Subsystem config /profile=default/subsystem=jacorb migrated.
    INFO  [ServerMigrationTask#336] Extension org.jboss.as.jacorb removed.
    INFO  [ServerMigrationTask#331] Subsystem jacorb configurations migrated.

Any issues encountered during the migration are written to the log files and displayed in the migration console.

#### 4.3.5. Migrate web Subsystem

The web subsystem is deprecated in JBoss EAP 7.0 and is replaced by the undertow subsystem.

By default, the JBoss Server Migration Tool automatically migrates any legacy subsystem configuration found. If you prefer this migration task is not executed, you can set the `subsystem.web.migrate.skip` environment property value to `true`.

The legacy subsystem migration is done without requiring any interaction from the user.

The outcome of the legacy web subsystem migration is printed in the console, as an example:

    INFO  [ServerMigrationTask#331] Migrating subsystem web configurations...
    INFO  [ServerMigrationTask#335] Subsystem config /profile=default/subsystem=web migrated.
    INFO  [ServerMigrationTask#336] Extension org.jboss.as.web removed.
    INFO  [ServerMigrationTask#331] Subsystem web configurations migrated.

Any issues encountered during the migration are written to the log files and displayed in the migration console.

#### 4.3.6. Migrate messaging Subsystem

The messaging subsystem is deprecated in JBoss EAP 7.0 and is replaced by the messaging-activemq subsystem.

By default, the JBoss Server Migration Tool automatically migrates any legacy subsystem configuration found. If you prefer this migration task is not executed, you can set the `subsystem.messaging.migrate.skip` environment property value to `true`.

The legacy subsystem migration is done without requiring any interaction from the user.

The outcome of the legacy messaging subsystem migration is printed in the console, as an example:

    INFO  [ServerMigrationTask#331] Migrating subsystem messaging configurations...
    INFO  [ServerMigrationTask#335] Subsystem config /profile=default/subsystem=messaging migrated.
    INFO  [ServerMigrationTask#336] Extension org.jboss.as.messaging removed.
    INFO  [ServerMigrationTask#331] Subsystem messaging configurations migrated.

Any issues encountered during the migration are written to the log files and displayed in the migration console.

#### 4.3.7. Update the infinispan Subsystem

The JBoss Server Migration Tool makes the following updates to the infinispan subsystem configuration to better match the JBoss EAP 7.0 default configurations.

- Adds the `ejb` cache, which is present in the JBoss EAP 7.0 default configuration.

- Adds the `server` cache, which is present in the JBoss EAP 7.0 default configuration.

- Fixes the module name in the `hibernate` cache configuration.

By default, the tool automatically updates any infinispan subsystem configuration to include these changes. If you prefer, you can configure the environment properties to customize the process of updating the infinispan subsystem configuration.

Property Name | Property Description
--- | ---
`subsystem.infinispan.update.skip` | If set to `true`, the tool skips the update of the infinispan subsystem.
`subsystem.infinispan.update.add-infinispan-ejb-cache.skip` | If set to `true`, the tool does not add the `ejb` cache.
`subsystem.infinispan.update.add-infinispan-server-cache.skip` | If set to `true`, the tool does not add the `server` cache.
`subsystem.infinispan.update.fix-hibernate-cache-module-name.skip` | If set to `true`, the tool does not fix the module name in the `hibernate` cache configuration.

Upon successful migration of a infinispan subsystem configuration, you should see messages in the console such as:

    INFO  [ServerMigrationTask#44] Server cache added to Infinispan subsystem configuration.
    INFO  [ServerMigrationTask#45] Ejb cache added to Infinispan subsystem configuration.
    INFO  [ServerMigrationTask#46] Infinispan subsystem's cache hibernate 'module' attribute updated to org.hibernate.infinispan.

#### 4.3.8. Update the ee Subsystem

The ee Subsystem in JBoss EAP 7.0 provides support for new Java EE 7 features.

- You can configure instances of Java EE 7 concurrency utilities, such as container-managed `Executors`.

- You can define the Java EE 7 default resources, such as the default data source, by specifying the original JNDI addresses.

By default, the tool updates the ee subsystem configuration to include the new features. If you prefer, you can configure the environment properties to customize the process of updating the ee subsystem configuration.

Property Name | Property Description
--- | ---
`subsystem.ee.update.skip` | If set to `true`, the tool skips the update of the ee subsystem.
`subsystem.ee.update.setup-ee-concurrency-utilities.skip` | If set to `true`, the tool does not add the default instances of concurrency utilities
`subsystem.ee.update.setup-javaee7-default-bindings.skip` | If set to `true`, the tool does not set up Java EE 7 default resources.
`subsystem.ee.update.setup-javaee7-default-bindings.defaultDataSourceName` | Specifies the name of the default data source to look for in the source configuration.
`subsystem.ee.update.setup-javaee7-default-bindings.defaultDataSourceJndiName` | Specifies the JNDI name for the default data source.
`subsystem.ee.update.setup-javaee7-default-bindings.defaultJmsConnectionFactoryName` | Specifies the name of the JMS connection factory.
`subsystem.ee.update.setup-javaee7-default-bindings.defaultJmsConnectionFactoryJndiName` | Specifies the JNDI name for the default JMS connection factory.

Warning | JNDI names that are specified are assumed to be valid. JNDI names are not validated by the tool.

For concurrency utilities instances, the tool automatically configures the exact same instances that are present in all JBoss EAP 7.0 default configurations and does not require any user interaction. The log simply indicates the instances were added:

    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.

When defining Java EE 7 default resources, by default the tool looks for the resources present in default JBoss EAP 6.4 configurations and select these if present.

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

In the case where the tool does not find such resources, then user input is required. The tool lists all available resources in the configuration, and then asks the user to select the one that should be set as the default, or to manually provide the JNDI address of the original resource. The following is an example of the interaction that occurs when migrating a configuration file with two configured data sources, `ExampleDS1` and `ExampleDS2` and defining the default data source:

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

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

Note | If you run the migration tool in `non-interactive` mode and the expected JBoss EAP 6.4 default resources are not available, for example the default JMS connection factory, the tool will not configure those resources.

#### 4.3.9. Update the ejb3 Subsystem

The JBoss Server Migration Tool makes the following updates to the ejb3 subsystem configuration to better match the JBoss EAP 7.0 default configurations.

- The remote service configuration is updated to reference the new HTTP connector.

- The `default-sfsb-passivation-disabled-cache` attribute is configured to use the `efault-sfsb-cache`.

- Legacy passivation store and cache configurations are replaced with the JBoss EAP 7.0 defaults.

By default, the tool updates any ejb3 subsystem configuration to include these changes. If you prefer, you can configure the environment properties to customize the process of updating the ejb3 subsystem configuration.

Property Name | Property Description
--- | ---
`subsystem.ejb3.update.skip` | If set to `true`, the tool skips the update of the ejb3 subsystem.
`subsystem.ejb3.update.activate-ejb3-remoting-http-connector.skip` | If set to `true`, the tool does not update the `EJB Remoting` configuration.
`subsystem.ejb3.update.add-infinispan-passivation-store-and-distributable-cache.skip` | If set to `true`, the tool does not replace the `passivation store` and `cache` configurations.
`subsystem.ejb3.update.setup-default-sfsb-passivation-disabled-cache.skip` | If set to `true`, the tool does not update the `default-sfsb-passivation-disabled-cache` configuration.

Upon successful migration of the ejb3 subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#52] EJB3 subsystem's remote service configured to use HTTP Remoting connector.
    INFO  [ServerMigrationTask#53] EJB3 subsystem's 'default-sfsb-passivation-disabled-cache' attribute set to simple.
    INFO  [ServerMigrationTask#54] Legacy file passivation store removed from EJB3 subsystem configuration.
    INFO  [ServerMigrationTask#54] Infinispan passivation store added to EJB3 subsystem configuration.
    INFO  [ServerMigrationTask#54] Legacy 'passivating' cache removed from EJB3 subsystem configuration.
    INFO  [ServerMigrationTask#54] Distributable cache added to EJB3 subsystem configuration.

#### 4.3.10. Update the remoting Subsystem

One of the most relevant features introduced by JBoss EAP 7.0 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 in the remoting subsystem and the tool simply updates the subsystem configuration to activate it.

By default, the tool automatically updates the remoting subsystem. If you prefer, you can set the `subsystem.remoting.update.skip` environment property to `true` to skip automatic update of the remoting subsystem configuration.

Upon successful migration of the remoting subsystem configuration, you should see the following message in the console:

    INFO  [ServerMigrationTask#33] Http connector http-remoting-connector added to Remoting subsystem configuration.

#### 4.3.11. Update the undertow Subsystem

In addition to migrating the web subsystem to JBoss EAP 7.0, the JBoss Server Migration Tool adds the following functionality provided by the new undertow subsystem, which is configured in the JBoss EAP 7.0 default server configurations.

- Sets the default `HTTP Listener` redirect socket.

- Adds support for Java EE 7 `Websockets`.

- Sets the default `Server` response header.

- Sets the default `X-Powered-By` response header.

By default, the tool automatically updates any undertow subsystem configuration to include these changes. If you prefer, you can configure the environment properties to customize the process of updating the undertow subsystem configuration.

Property Name | Property Description
--- | ---
`subsystem.undertow.update.skip` | If set to `true`, the tool skips the update of the undertow subsystem.
`subsystem.undertow.update.set-default-http-listener-redirect-socket.skip` | If set to `true`, the tool does not set the default `HTTP Listener` redirect socket.
`subsystem.undertow.update.add-undertow-websockets.skip` | If set to `true`, the tool does not add support for WebSockets.
`subsystem.undertow.update.add-response-header.server-header.skip` | If set to `true`, the tool does not set the default `Server` response header.
`subsystem.undertow.update.add-response-header.x-powered-by-header.skip` | If set to `true`, the tool does not set the default `X-Powered-By` response header.

Upon successful migration of a undertow subsystem configuration, you should see messages in the console such as:

    INFO  [ServerMigrationTask#33] Undertow's default HTTP listener 'http' redirect-socket set as 'https'.
    INFO  [ServerMigrationTask#34] Undertow's default Servlet Container configured to support Websockets.
    INFO  [ServerMigrationTask#35] Response header 'server-header' set as 'Server: JBoss-EAP/7' in Undertow's config /subsystem=undertow
    INFO  [ServerMigrationTask#36] Response header 'x-powered-by-header' set as 'X-Powered-By: Undertow/1' in Undertow's config /subsystem=undertow

#### 4.3.12. Update the messaging-activemq Subsystem

In addition to migrating the messaging subsystem to JBoss EAP 7.0, the JBoss Server Migration Tool also adds the following new functionality provided by the messaging-activemq subsystems, which is configured in the JBoss EAP 7.0 default standalone configuration files.

- Adds the default HTTP connector and acceptor, enabling the new HTTP-based remote messaging clients.

By default, the tool automatically updates any messaging-activemq subsystem configuration. If you prefer, you can set the `subsystem.messaging-activemq.update.skip` environment property to `true` to skip automatic update of messaging-activemq subsystem configurations.

Upon successful migration of a messaging-activemq subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#123] HTTP Acceptor named http-acceptor added to Messaging ActiveMQ subsystem configuration.
    INFO  [ServerMigrationTask#123] HTTP Connector named http-connector added to Messaging ActiveMQ subsystem configuration.

#### 4.3.13. Add the batch-jberet Subsystem

The JBoss EAP 7.0 batch-jberet subsystem provides support for JSR 352: Batch Applications for the Java Platform.

Its default configuration is automatically added to the migrated configuration file, unless the environment property named `subsystem.batch-jberet.add.skip` is set to `true`.

The subsystem and related extension are added without any interaction required by the user. Upon successful addition of the batch-jberet subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#49] Adding subsystem batch-jberet configuration(s)...
    INFO  [ServerMigrationTask#50] Extension org.wildfly.extension.batch.jberet added.
    INFO  [ServerMigrationTask#51] Subsystem config /profile=default/subsystem=batch-jberet added.
    INFO  [ServerMigrationTask#51] Subsystem config /profile=full/subsystem=batch-jberet added.

#### 4.3.14. Add the request-controller Subsystem

The JBoss EAP 7.0 request-controller subsystem provides congestion control and graceful shutdown functionality.

Its default configuration is automatically added to the migrated configuration file, unless the environment property named `subsystem.request-controller.add.skip` is set to `true`.

The subsystem and related extension are added without any interaction required by the user. Upon successful addition of the request-controller subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#49] Adding subsystem request-controller configuration(s)...
    INFO  [ServerMigrationTask#50] Extension org.wildfly.extension.request-controller added.
    INFO  [ServerMigrationTask#51] Subsystem config /profile=default/subsystem=request-controller added.
    INFO  [ServerMigrationTask#51] Subsystem config /profile=full/subsystem=request-controller added.

#### 4.3.15. Add the security-manager Subsystem

The JBoss EAP 7.0 security-manager subsystem provides the support for Java EE 7 security permissions.

Its default configuration is automatically added to the migrated configuration file, unless the environment property named `subsystem.security-manager.add.skip` is set to `true`.

The subsystem and related extension are added without any interaction required by the user. Upon successful addition of the security-manager subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#49] Adding subsystem security-manager configuration(s)...
    INFO  [ServerMigrationTask#50] Extension org.wildfly.extension.security.manager added.
    INFO  [ServerMigrationTask#51] Subsystem config /profile=default/subsystem=security-manager added.
    INFO  [ServerMigrationTask#51] Subsystem config /profile=full/subsystem=security-manager added.

#### 4.3.16. Add the singleton Subsystem

As its name indicates, the JBoss EAP 7.0 singleton subsystem provides the singleton functionality.

Its default configuration is automatically added to the migrated configuration file, unless the environment property named `subsystem.singleton.add.skip` is set to `true`.

The subsystem and related extension are added without any interaction required by the user. Upon successful addition of the singleton subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#49] Adding subsystem singleton configuration(s)...
    INFO  [ServerMigrationTask#50] Extension org.wildfly.extension.clustering.singleton added.
    INFO  [ServerMigrationTask#51] Subsystem config /profile=default/subsystem=singleton added.
    INFO  [ServerMigrationTask#51] Subsystem config /profile=full/subsystem=singleton added.

#### 4.3.17. Update the Domain Configuration’s Unsecure Interface

The tool updates the `unsecure` interface configuration to match JBoss EAP 7.0 default configurations.

By default, the tool automatically updates the `unsecure` interface configuration. If you prefer, you can set the `interface.unsecure.update.skip` environment property to `true` to skip the automatic update of the `unsecure` interface.

Upon successful update of the `unsecure` interface configuration, you should see the following messages in the console:

    INFO [ServerMigrationTask#432] Interface unsecure inet address value set as ${jboss.bind.address.unsecure:127.0.0.1}.

#### 4.3.18. Set Up Private Interface

The JBoss EAP 7.0 default configuration uses a new `private` interface on all `jgroups` socket bindings. The JBoss Server Migration Tool automatically adds the new interface to migrated configurations with `jgroups` socket bindings, and updates these to use it.

Upon successful configuration of the private interface, you should see the following messages in the console:

    INFO  [ServerMigrationTask#637] Interface private added.
    INFO  [ServerMigrationTask#640] Socket binding /socket-binding-group=full-ha-sockets/socket-binding=jgroups-mping interface set to private
    INFO  [ServerMigrationTask#640] Socket binding /socket-binding-group=full-ha-sockets/socket-binding=jgroups-tcp interface set to private
    INFO  [ServerMigrationTask#640] Socket binding /socket-binding-group=full-ha-sockets/socket-binding=jgroups-tcp-fd interface set to private
    INFO  [ServerMigrationTask#640] Socket binding /socket-binding-group=full-ha-sockets/socket-binding=jgroups-udp interface set to private
    INFO  [ServerMigrationTask#640] Socket binding /socket-binding-group=full-ha-sockets/socket-binding=jgroups-udp-fd interface set to private
    INFO  [ServerMigrationTask#641] Socket binding /socket-binding-group=ha-sockets/socket-binding=jgroups-mping interface set to private
    INFO  [ServerMigrationTask#641] Socket binding /socket-binding-group=ha-sockets/socket-binding=jgroups-tcp interface set to private
    INFO  [ServerMigrationTask#641] Socket binding /socket-binding-group=ha-sockets/socket-binding=jgroups-tcp-fd interface set to private
    INFO  [ServerMigrationTask#641] Socket binding /socket-binding-group=ha-sockets/socket-binding=jgroups-udp interface set to private
    INFO  [ServerMigrationTask#641] Socket binding /socket-binding-group=ha-sockets/socket-binding=jgroups-udp-fd interface set to private

If you prefer to skip the configuration of the private interface, set the environment property named `interface.private.setup.skip` to `true`.

#### 4.3.19. Add Socket Binding Port Expressions

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

- `ajp`

- `http`

- `https`

The tool automatically adds the value expressions to the migrated JBoss EAP 6.4 configurations.

The following message(s) in the console indicates this configuration update:

    INFO  [ServerMigrationTask#642] Adding socket binding's port expressions...
    INFO  [ServerMigrationTask#643] Socket binding /socket-binding-group=full-sockets/socket-binding=ajp port value expression set as ${jboss.ajp.port:8009}.
    INFO  [ServerMigrationTask#644] Socket binding /socket-binding-group=ha-sockets/socket-binding=ajp port value expression set as ${jboss.ajp.port:8009}.
    INFO  [ServerMigrationTask#645] Socket binding /socket-binding-group=standard-sockets/socket-binding=ajp port value expression set as ${jboss.ajp.port:8009}.
    INFO  [ServerMigrationTask#646] Socket binding /socket-binding-group=full-ha-sockets/socket-binding=ajp port value expression set as ${jboss.ajp.port:8009}.
    INFO  [ServerMigrationTask#647] Socket binding /socket-binding-group=ha-sockets/socket-binding=http port value expression set as ${jboss.http.port:8080}.
    INFO  [ServerMigrationTask#648] Socket binding /socket-binding-group=full-ha-sockets/socket-binding=http port value expression set as ${jboss.http.port:8080}.
    INFO  [ServerMigrationTask#649] Socket binding /socket-binding-group=full-sockets/socket-binding=http port value expression set as ${jboss.http.port:8080}.
    INFO  [ServerMigrationTask#650] Socket binding /socket-binding-group=standard-sockets/socket-binding=http port value expression set as ${jboss.http.port:8080}.
    INFO  [ServerMigrationTask#651] Socket binding /socket-binding-group=ha-sockets/socket-binding=https port value expression set as ${jboss.https.port:8443}.
    INFO  [ServerMigrationTask#652] Socket binding /socket-binding-group=full-ha-sockets/socket-binding=https port value expression set as ${jboss.https.port:8443}.
    INFO  [ServerMigrationTask#653] Socket binding /socket-binding-group=full-sockets/socket-binding=https port value expression set as ${jboss.https.port:8443}.
    INFO  [ServerMigrationTask#654] Socket binding /socket-binding-group=standard-sockets/socket-binding=https port value expression set as ${jboss.https.port:8443}.
    INFO  [ServerMigrationTask#642] Socket binding's port expressions added.

Note | The Migration Environment may be configured to skip this conifguration update, by setting environment property named `socket-bindings.add-port-expressions.skip` as `true`.

#### 4.3.20. Remove Permgen Attributes From JVM Configurations

The usage of `Permgen` attributes in JVM configurations is deprecated in JBoss EAP 7.0 and the JBoss Migration Tool removes these from all JVM configurations.

Upon successful removal of the `Permgen` attributes, you should see the following messages in the console:

    INFO  [ServerMigrationTask#677] Permgen attributes removed from JVM /server-group=main-server-group/jvm=default
    INFO  [ServerMigrationTask#678] Permgen attributes removed from JVM /server-group=other-server-group/jvm=default

If you prefer, you can set the `jvms.remove-permgen-attributes.skip` environment property value to `true` to skip the automatic removal.

#### 4.3.21. Migrate Deployments

The JBoss Server Migration Tool, when migrating a configuration, may also migrate:

- Deployments it references, also known as persistent deployments.

- Deployment Overlays it references.

Warning | The migration of a deployment or deployment overlay merely consists of installing related file resources on the target server, and possibly updating the migrated configuration. The tool will not assert if these resources are compatible with the target server, which means that a migrated deployment might not work as expected, or might not work at all. Red Hat recommends that you use Red Hat Application Migration Toolkit to analyze a deployment with respect to compatibility among different JBoss servers.

Note | If you run the migration tool in `non-interactive` mode, by default the JBoss Server Migration Tool will not migrate any deployments and overlays. To migrate deployments the environment property `deployments.migrate-deployments.skip` should be set as `false`.

##### Migrate Persistent Deployments

When migrating a configuration, the tool searches for references to deployments persisted in the source server, and prints the names of the deployments found in the console, e.g.:

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

If you run the migration tool in `interactive` mode, you then see the following prompt:

    This tool is not able to assert if persistent deployments found are compatible with the target server, skip persistent deployments migration?
    yes/no?

- If you reply yes, or y, the all deployment references are removed from the migrated configuration, i.e. the deployments will not be migration.

- If you reply no, or n, you receive an additional prompt asking if all deployments should be the migrated:

      Migrate all persistent deployments found?
      yes/no?

  - If you reply yes, or y, all deployments are migrated.

  - If you reply no, or n, you receive a prompt asking to confirm the migration for each referenced deployment:

        Migrate persistent deployment 'cmtool-helloworld3.war'?
        yes/no?

    - If you reply yes, or y, the deployment is migrated.

    - If you reply no, or n, the deployment reference is removed from the migrated configuration, i.e. the deployment is not migrated.

          INFO  [ServerMigrationTask#68] Removed persistent deployment from configuration /deployment=cmtool-helloworld3.war

If you run the migration tool in `non-interactive` mode, the JBoss Server Migration Tool will migrate or not migrate `all` persistent deployments, depending on the environment configuration. Persistent deployments are migrated only if none of the following environment properties is set as `true`:

- deployments.migrate-deployments.skip

- deployments.migrate-persistent-deployments.skip

##### Migrate Deployment Overlays

The migration of deployment overlays is a fully automated process. The migration tool searches for deployment overlays referenced in the standalone server configuration. It then migrates those that are linked to deployments that were migrated.

The migration tool prints a message to the console for each deployment overlay that is migrated or removed.

    INFO  [ServerMigrationTask#79] Deployment overlays found: [overlay4, overlay1, overlay2, overlay3]
    INFO  [ServerMigrationTask#79] Migrating deployment overlay 'overlay4', it's linked to deployment cmtool-helloworld2.war
    INFO  [ServerMigrationTask#80] Removed deployment overlay from configuration /deployment-overlay=overlay1
    INFO  [ServerMigrationTask#81] Removed deployment overlay from configuration /deployment-overlay=overlay2
    INFO  [ServerMigrationTask#79] Migrating deployment overlay 'overlay3', it's linked to deployment cmtool-helloworld2.war

### 4.4. Host Configuration File Migration

When migrating the host configuration, the JBoss Server Migration Tool first copies the source configuration files to the target server. It then updates the configuration to not only work correctly in the target server, but also to take advantage of the target server’s new functionality.

#### 4.4.1. Migrate Referenced Modules

A migrated configuration may reference and depend on a module that is not installed on the target server. The tool automatically migrates the referenced modules, and their dependent modules as well.

A module is migrated when it is referenced by:

- A `security-realm` configuration, as plug-in(s) module

The console logs a message noting the module ID for any module that is migrated, for example:

    INFO  [ServerMigrationTask#18] Module cmtool.security-realms:main migrated.

Tip | It is possible to exclude the migration of specific modules by specifying the id(s) in the environment property named `modules.excludes`.

#### 4.4.2. Migrate Referenced Paths

A migrated configuration may reference paths, i.e. files and directories, which may need to be migrated to the target server.

A referenced path is migrated only if it’s not an absolute path, and such migration consists in copying the resource to such path, but relative to the migrated configuration, in the target server.

The tools automatically migrates the following paths references:

- `Vault` keystore and encrypted file’s directory.

The console logs a message noting each path migration, for example:

    INFO  [ServerMigrationTask#25] Resource with path /jboss-eap-6.4/vault/vault.keystore migrated.

If you prefer, you can configure the environment properties to customize the migration of referenced paths.

Property Name | Property Description
--- | ---
`paths.migrate-paths-requested-by-configuration.vault.skip` | If set to `true`, the tool skips the migration of `Vault` referenced paths.

#### 4.4.3. Add the jmx Subsystem

The JBoss EAP 7.0 jmx subsystem provides the ability to manage and monitor systems.

Its default configuration is automatically added to the migrated configuration file, unless the environment property named `subsystem.jmx.add.skip` is set to `true`.

The subsystem and related extension are added without any interaction required by the user. Upon successful addition of the jmx subsystem configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#49] Adding subsystem jmx configuration(s)...
    INFO  [ServerMigrationTask#50] Extension org.jboss.as.jmx added.
    INFO  [ServerMigrationTask#51] Subsystem config /host=master/subsystem=jmx added.

#### 4.4.4. Remove the Unsecure Interface

The tool removes the `unsecure` interface configuration from migrated configurations, to match the JBoss EAP 7.0 default configurations. However, you can configure the tool to skip the removal of the `unsecure` interface by setting the `interface.unsecure.remove.skip` environment property value to `true`.

Upon successful removal of the `unsecure` interface configuration, you should see the following message in the console:

    INFO [ServerMigrationTask#480] Interface unsecure removed.

#### 4.4.5. Setup HTTP Upgrade Management

JBoss EAP 7.0 management clients use the new HTTP Upgrade mechanism, and the JBoss Migration Tool makes all of configuration changes needed for clients to work properly with the migrated configuration.

The configuration changes are fully automated, and upon successful completion of the configuration, you should see the following messages in the console:

    INFO  [ServerMigrationTask#896] HTTP upgrade management setup starting...
    INFO  [ServerMigrationTask#897] Management interface 'http-interface' http upgrade enabled.
    INFO  [ServerMigrationTask#896] HTTP upgrade management setup completed.

If you prefer to skip the configuration of HTTP Upgrade management, set the environment property named `management.setup-http-upgrade.skip` to `true`.

#### 4.4.6. Remove Permgen Attributes From JVM Configurations

The usage of `Permgen` attributes in JVM configurations is deprecated in JBoss EAP 7.0 and the JBoss Migration Tool removes these from all JVM configurations.

Upon successful removal of the `Permgen` attributes, you should see the following messages in the console:

    INFO  [ServerMigrationTask#900] Permgen attributes removed from JVM /host=master/jvm=default