Business-ready architecture. Work with an open source leader.
Try Payara Enterprise
Luxury German Vehicle Manufacturer Migrates from GlassFish to Payara Server
Download BMW Case Study PDF
Migrating from WildFly to Payara Server 5 can be a simple and straightforward process because both servers rely on the Java EE specifications. We make it even easier with the help of our migration resources and migration guides:
Contact Us about Payara Enterprise
Before your team can start the migration process, you (and the decision makers at your organization) may need to learn more about the Payara Platform. In our ‘Why Migrate to the Payara Platform’ Guide, we’ll provide information about:
Along with providing full support for our application server and more frequent component updates – migrating to Payara Server gives you access to additional features and capabilities:
We Can Help You MigrateWhy Enterprise?
Migrating applications from WildFly to Payara Server can be a simple and straightforward process because both servers rely on the Jakarta EE (Java EE) specifications. However, there are differences in many areas because many Java EE APIs in WildFly and Payara Server are implemented by different components. Moreover, the configuration of certain aspects like external resources, high-availability and deployment is not covered by any specification and is, in fact, very different in both servers.
This guide will explain the differences between clustering in WildFly and Payara Server, how to plan migration of an existing WildFly cluster to Payara Server, and will also show you how to migrate an example cluster step-by-step.