JBoss EAP migration
JBoss EAP migration to Tomcat or Spring Boot.
Most of the work is configuration. Read your standalone.xml first and the plan follows from it.
The short answer
A JBoss EAP migration moves applications to Tomcat or Spring Boot and removes the EAP subscription. Most of the work is configuration: standalone.xml or domain.xml, JBoss modules, CLI scripts and CDI wiring. Ace8 maps these, tests behavior, then migrates in phases with AI-assisted code changes that engineers verify.
Start here
Reading standalone.xml: configuration mapping
On JBoss EAP, the server file describes subsystems: data sources, messaging, security domains, logging and more. Each subsystem becomes either application properties, a library or a separate service. This is how we read it.
| EAP configuration | Becomes | Note |
|---|---|---|
| datasources subsystem | spring.datasource properties or a Tomcat resource | Pool sizes and validation queries carry over |
| messaging (Artemis) subsystem | A standalone broker and Spring messaging, or an embedded Artemis | Decide whether the broker stays inside the app |
| security domains | Spring Security or container authentication | Role mapping and login modules |
| logging subsystem | Logging configuration in the application | Categories and levels |
| undertow subsystem | Embedded server settings | Context paths, HTTP limits, TLS |
| JBoss modules | Ordinary dependencies in the build | Module-level classpath tricks need unpicking |
| CLI scripts (jboss-cli) | Pipeline steps and configuration in code | Read them: they record the server's history |
| CDI beans and EJBs | Spring beans or kept as CDI where it fits | Scope and transaction handling |
Choosing
EAP, WildFly or Tomcat
WildFly is the community project that EAP is built from. It removes the subscription but keeps the full application server model and the same operational burden. Tomcat or Spring Boot removes more.
| EAP | WildFly | Tomcat | Spring Boot | |
|---|---|---|---|---|
| Subscription | Yes | No | No | No |
| Full Jakarta EE server | Yes | Yes | No | No |
| Code change from EAP | None | Small, but version-dependent | Moderate | Largest up front |
| Supported by the vendor | Red Hat | Community | Community, plus AceMQ support | Community, plus AceMQ support |
Motive
Why teams leave JBoss EAP
- The subscription is an annual cost for software the team may use lightly.
- Version upgrades of the server force code changes anyway.
- Containers favor a smaller runtime.
- A move to Spring Boot is often the next step after a Java upgrade.
Cost
Subscription cost model
We build the comparison from your subscription terms and core count against the cost of the target. The formula and sources are shown. A worked model will be published on this page, and we do not quote a saving before we have your numbers.
Plan
Phased cutover
- 1
Inventory subsystems
List what each application actually uses.
- 2
Write tests
Characterization tests for transactions, security and messaging.
- 3
Move code and config
Tools do the repetitive edits. Engineers sign each change.
- 4
Run side by side
Traffic moves in steps, one application at a time.
- 5
Cancel the subscription
After the last application has moved and the rollback window is over.
Risk
Risks and rollback
Rollback means routing traffic back to the EAP instance, which stays up until the new one has carried load.
- Classpath behavior that depended on module ordering.
- Transaction behavior that the container supplied silently.
- Security domain differences that surface under real logins.
- Subscription renewal dates that constrain the schedule.
After go-live
After go-live
AceMQ supports Tomcat, Java and Spring around the clock. See supported after migration.
After go-live
Keep it running after cutover.
WildFly is the community project that EAP is based on. EAP adds a subscription with vendor support. WildFly removes the cost but keeps the application server model.
Yes, if your applications do not depend on EJBs, JMS or other full-server features, or if those can be replaced. The configuration mapping shows which.
We build the model from your subscription and core count and show the formula. We do not quote a saving before we have your numbers.
We read them, document what they do, and replace them with configuration in code and pipeline steps.
Often, yes. Current Spring needs Java 17 or later. The assessment sets the order.
Know the cost before anything moves.
A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.
Book a Fixed-Price AssessmentGet in touch
Talk to a modernization engineer
Tell us what you run today. An engineer, not a sales script, replies within one business day.