Tomcat
The usual landing spot for WebLogic, WebSphere and JBoss exits.
After go-live
Supported by AceMQ after go-live.
Modernization is not finished at cutover. The people who run the new stack should know it before it launches.
The short answer
After Ace8 modernizes your applications, AceMQ supports the new stack 24/7. AceMQ provides support for Tomcat, Java, Spring, RabbitMQ and Kafka. The run plan is written before cutover, so operations teams know who to call, what is monitored and how to roll back on day one.
Coverage
What AceMQ supports
Ace8 is the modernization practice of AceMQ. The same engineering team does the migration and supports the result, so nobody has to explain the system to a new vendor on day one.
Java
Current runtimes after a Java upgrade.
Spring
Spring Boot 3 and Spring Framework 6 applications.
RabbitMQ
The messaging layer after an IBM MQ replacement.
Kafka
Event streaming alongside or instead of other brokers.
Principle 8
The run plan we hand over
Principle 8 of the method is to plan the run before the cutover. The run plan covers:
- Who to call, and in what order.
- What is monitored, and what each alert means.
- How to roll back, step by step.
- Where the configuration lives and how it changes.
- Known risks and the first things to check when something is wrong.
Before cutover
Handover checklist
- 1
Support contacts confirmed
Named contacts on both sides, with escalation paths.
- 2
Monitoring in place
Dashboards and alerts live before traffic moves.
- 3
Rollback rehearsed
The rollback has been run, not just written.
- 4
Runbooks reviewed
Operations has read them and asked questions.
- 5
Baseline recorded
Performance, licence cost and CVE counts from before the change, for comparison.
Support model
How the support model works
AceMQ support runs 24/7. The detailed support levels and response commitments are set out in your agreement with AceMQ. We do not quote response times here, because they depend on the level you choose.
AceMQ also supports the Tomcat, Java, Spring, RabbitMQ and Kafka stacks the AceMQ engineering team delivered in the American National project.
Escalation
How escalation works
The run plan names the first contact and the escalation path. Because AceMQ engineers took part in the migration, an escalation reaches people who already know your system.
Afterward
Staying current after go-live
A modern stack still ages. AceMQ support covers the platforms in scope, and Ace8 can return for the next upgrade, such as a further Java release. If you need to stay on older versions of open-source components for longer, OSSeva provides extended support.
AceMQ does, 24/7. AceMQ supports Tomcat, Java, Spring, RabbitMQ and Kafka.
Support is a separate agreement with AceMQ. The run plan is part of the modernization work and is written before cutover.
You can keep them. The run plan and handover checklist work with any support team.
They depend on the support level. They are set out in the AceMQ agreement.
Ace8 is the modernization practice of AceMQ. The same engineering team delivers the work and supports the result.
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.