GlassFish to Payara Server 4 Migration Guide
GlassFish to Payara Server 4 Migration Guide
If you’re running GlassFish in your production or development environment and are worried about the lack of support from Oracle, infrequent application server releases, lack of bug fixes and patches – Payara Server is an ideal solution for you!
Payara Server Enterprise is an open source application server derived from GlassFish, supporting reliable and secure deployments of Jakarta EE (Java EE) applications in any environment: on premise, in the cloud or hybrid.
Migrating from GlassFish to Payara Server 4 can be a simple and straightforward process, made even simpler with the help of our ‘GlassFish to Payara Server 4 Migration Guide’.
In this detailed, step-by-step guide, you’ll learn:
- Why choose Payara Server?
- Migrating from GlassFish 3.x
- Migrating from GlassFish 4.x
- Working with 3rd-party libraries
- How to deal with Oracle Commercial Features
- Post-migration considerations
How is Payara Server Enterprise better than GlassFish?
Optimized for mission critical production systems in any environment, Payara Server (see the data sheet) is compatible with the services you’re already using, container-friendly, and fully supported with a 10-year software lifecycle. Used as a drop in replacement for GlassFish Server Open Source Edition, Payara Server gives you a peace of mind of monthly releases containing bug fixes and patches to ensure the security and stability of your production environment.
Looking for Migration Guide to Payara Server 5?
Click Here!
The Migration & Project Support that I’ve received from the Payara Engineers has been exceptional thus far. They helped me pinpoint an issue that we’ve been having and also referenced me to the GitHub page where another user had a similar issue. Furthermore, they have back-tested the issue that we’d experienced and figured out what the latest version is that we can upgrade to, where our existing code-base would still work. In the meantime, while the Support Team was busy investigating the issue, we migrated from GlassFish to Payara Server on one of our production servers. Thus far, the transition has been seamless and exciting.
Mark Bekker, HelloGroup
Payara Server vs GlassFish
Feature | GlassFish 5.x | Payara Server Enterprise 5 |
---|---|---|
License | Open Source | Open Source |
Release Frequency | Irregular | Monthly |
Releases in 2020 | 3 | 12 |
Security Fixes | Infrequent |
|
Production Support | No | Yes |
Migration & Project Support | No | Yes |
Component Upgrades (e.g. Tyrus, Mojarra) | Irregular | As needed |
Supported IDEs |
|
|
Caching Tools | No | JCache, Domain Data Grid, Payara Scales (additional cost) |
Automatic Clustering | No | Yes (via Hazelcast) |
Asadmin Command Recorder | No | Yes |
Slow SQL Logging | No | Yes |
Health Check Service | No | Yes |
Request Tracing | No | Yes |
Monitoring Logging | No | Yes |
Custom Notifiers | No | Yes |
Microservices Distribution | No | Yes (Payara Micro) |
MicroProfile Support | No | Yes |
Docker Support | Community provided | Official images |
HTTP & HTTPS Port Auto-binding | No | Yes (Payara Micro only) |
Generate Uber JAR | No | Yes (Payara Micro only) |
Production-tuned Domain Template | No | Yes |
Upgrade Tool | No | Yes (Watch demo.) |
Jakarta EE Compatible | Yes | Yes |
Runs on JDK 11 | Yes | Yes |
Embedded Data Grid | No | Yes (Domain Data Grid) |