Title: Prepare for Migration Describe the issue: There should be a clear statement what a major/minor and micro migration means. In general (EAP6 onwards) - a micro migration will not have issues as the configuration files and data should be simple picked up from the newer version. - a minor migration should be compatible for the stored content and data but remove temporary directories - a major migration need to be described as there can be many differences see https://access.redhat.com/solutions/1311784 for details For a major migration there is often no way to copy the configuration, especially for EAP4/EAP5 => EAP6. (Maybe EAP6->EAP7 will be different) A Minor migration from i.e. EAP 6.2 => 6.3 can be done by copy the folders of domain or standalone. But there are some pitfalls. The domain or standalone might include managed deployments which are stored in .../data/content. This folder need to be copied. Otherwise the start will fail as the content is missed. The transaction directory (data/tx-object-store) should be deleted, open transactions should be handled before the migration starts. The persistent timers data/timer-service-data need to be checked whether it is compatible, the different timers will have a file below with the deployment- and bean name, so it can be simple checked before the migration which timers are still in use.
We should also include a statement that the configuration can be copied in case of a minor migration, but after starting the new server the configuration files might be updated and it is not possible to use it with an older version see https://access.redhat.com/solutions/1295743 Next is how to do a rolling domain upgrade, see https://access.redhat.com/solutions/392423 for detailed information
Verified with Revision 6.4.0-37.