A Red Hat / JBoss enterprise customer recently migrated from JBoss AS 7 to JBoss EAP 6. After they completed the migration process in production, they sent us their notes with permission to share them.
The result, “lot of high-fives were made”.
- REST (JSON)
- There are three physical servers.
- There are two virtual machines per physical server.
- There is a host controller and a managed server per virtual machine.
- The host controllers a managed as a single domain.
- Installed and configured JBoss EAP 6 on each virtual machine using the port offset so that both JBoss AS 7 and JBoss EAP 6 can be started on the same virtual machine.
- Changed the JGroups multicast address so that the JBoss EAP 6 cluster does not overlap with the JBoss AS 7 cluster.
- Configured the JBoss EAP 6 host controllers in the same manner as the JBoss AS 7 host controllers: controller name, server group, server name.
- Configured the JBoss EAP 6 host controllers with a different password than the JBoss AS 7 host controllers.
- Deployed the same application build that was deployed to the JBoss AS 7 domain to the JBoss EAP 6 domain.
- Started the JBoss EAP 6 domain.
- Tested the application build.
- Stopped the JBoss EAP 6 domain.
- Updated the JBoss EAP 6 domain / host configuration to use the default ports (no port offset).
- Stopped the JBoss AS 7 domain controller.
Note: The JBoss AS 7 host controllers were not stopped because they were configured with a different password than the JBoss EAP 6 host controllers.
- Started the JBoss EAP 6 domain controller.
- For each JBoss AS 7 host controller, stopped the JBoss AS 7 host controller and started the JBoss EAP 6 host controller.
Total Migration Time: 22 Minutes
Total Outage Time: 0 Minutes