Migrating from GlassFish to Payara Server can be a simple and straightforward process, made even simpler with the help of our ‘GlassFish to Payara Server Migration Guide’.
When commercial support for GlassFish ended in 2014, Payara Server was created as a fully-supported drop-in replacement. Payara Services was born in 2016 to offer support solutions for the application server. By 2017, Payara Services had joined The Eclipse Foundation and the Payara Platform expanded to include Payara Micro and comprehensive commercial support options for development projects, in-production support, and consultancy solutions.
Download the Migration Guide to take a look at the things you will need to consider in your GlassFish to Payara Server migration project; as well as details of Payara Server’s tools and features which will make your life (and your application server management) much easier!
The Migration Guide features the following sections:
- 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.
| Feature |
GlassFish 5.x |
Payara Server Enterprise |
| License |
Open Source |
Open Source |
| Release frequency |
Irregular |
Monthly |
| Releases in 2019 |
1 |
22: 4 community stream, 12 stability stream, 6 feature stream |
| Patch releases |
For versions < 4.0. only |
- Monthly for Payara Enterprise customers
- Quarterly for community
|
| Security fixes |
Infrequent |
- Instant emergency and backported fixes for Payara Enterprise customers
- As soon as possible for community
|
| Production support |
✗ |
✓ |
| Migration & Project Support |
✗ |
✓ |
| Component Upgrades (e.g. Tyrus, Mojarra) |
Irregular |
Quarterly |
| Supported IDEs |
- Eclipse
- Netbeans
- IntelliJ IDEA
|
- Eclipse
- Netbeans
- IntelliJ IDEA
- Visual Studio
|
| Caching tools |
|
JCache, Domain Data Grid, Payara Scales (additional cost) |
| Automatic Clustering |
✗ |
✓via Hazelcast |
| Asadmin command recorder |
✗ |
✓ |
| Slow SQL logging |
✗ |
✓ |
| Healthcheck service |
✗ |
✓ |
| Request tracing |
✗ |
✓ |
| Monitoring logging |
✗ |
✓ |
| Microservices distribution |
✗ |
✓Payara Micro |
| MicroProfile support |
|
Compatible with MicroProfile |
| Docker support |
Community provided |
Official images |
| IBM JDK release |
✗ |
✓Payara Blue |
| HTTP & HTTPS port auto-binding |
✗ |
✓(Payara Micro only) |
| Generate Uber JAR |
✗ |
✓(Payara Micro only) |
| Production-tuned domain template |
✗ |
✓ |
| Upgrade tool |
✓ |
✗ (Coming soon) |
| Jakarta EE Compatible |
✓ |
✓
|
{{cta(‘3382707d-3c20-4768-8acd-0a5b78c43d95’)}}
4 minutes
Curious to learn about payara