EAP 6 to EAP 7 Migration: Difference between revisions
(Created page with "=External= * =Internal= * EAP7 =Overview= Incompatible subsystems, such as messaging or web can be migrate to their counterparts messaging-activemq or...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
=External= | =External= | ||
* | * https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/html-single/migration_guide/ | ||
=Internal= | =Internal= | ||
* [[ | * [[EAP 7#Subjects|EAP7]] | ||
=Overview= | =Overview= | ||
Latest revision as of 16:10, 15 March 2017
External
Internal
Overview
Incompatible subsystems, such as messaging or web can be migrate to their counterparts messaging-activemq or undertow on a subsystem per subsystem basis, as described below.
Procedure
Get a copy of the EAP 6 configuration file in the same "configuration" directory its EAP 7 counterpart exists. The migration procedure works for both standalone-*.xml or domain.xml. In case of domain mode, we will need to navigate in CLI to the required profile, as shown below.
Name the configuration file suggestively, something like "domain-eap6-to-migrate.xml".
Start the EAP 7 instance in admin mode, in top of the file to be migrated.
cd $JBOSS_HOME/bin ./domain.sh --admin-only --domain-config=domain-eap6-to-migrate.xml
Connect with CLI:
cd $JBOSS_HOME/bin ./jboss-cli.sh -c
Navigate to the subsystem in question. This is done differently in standalone and domain mode.
/profile=full-ha ./subsystem=messaging:describe-migration
Perform the migration:
./subsystem=messaging:migrate
The result should be similar to:
{
"outcome" => "success",
"result" => {"migration-warnings" => []},
"server-groups" => undefined
}
Shut down the server.
The domain-eap6-to-migrate.xml will contain the migrated configuration.