If you’re running GlassFish in your production or development environment and are worried about the lack of support, infrequent application server releases, lack of bug fixes and patches – Then you might be considering migration. Payara Server is an open source application server originally derived from GlassFish – supporting reliable and secure deployments of Jakarta EE (Java EE) applications in any environment: on premise, in the cloud or hybrid. To do our part to help advance the Jakarta EE project, Payara Services is a project lead for GlassFish, the Jakarta EE compatible implementation, but we recommend Payara Server Enterprise for your production environments for our included support services, stability, and security. Migrating from GlassFish to Payara Server can be a simple and straightforward process. In this webinar, Payara CEO Steve Millidge will explain all the things you need to consider in order to make a migration as smooth as possible. If you have any questions about the above, this will be a great opportunity to get answers directly from the source.

1. Date:
Time:
Duration:
Move Your
GlassFish Upstream
What You Need to Know About Migration
Steve Millidge - @l33tj4v4
24/08/22
15:00 BST
45Mins

2. GlassFish 5.x is Outdated
GlassFish 5.x Has Bugs
GlassFish 5.x Is Vulnerable

3. We built Payara as a
better GlassFish
We built Payara as
a better runtime for
Jakarta EE

5. Modernizing Jakarta EE
Cloud Containers DevOps
IoT Jakarta EE MicroProfile

6. The GlassFish Journey

7. Issues with running GlassFish 5.x
GlassFish 5.x is OLD and not really updated for 5+ years
GlassFish is NOT built for Cloud
GlassFish has No Microservices Support
GlassFish No Fat/Hollow Jar Functionality
GlassFish does not support the latest JDKs
GlassFish does not receive regular security patches
GlassFish is NOT Supported
Payara presents solutions to these issues…

8. Problem: Lack of Maintenance and Framework Updates
in GlassFish
Solution: Frequent Releases for Payara Community
and Guaranteed Monthly Releases for Payara
Enterprise – Supporting latest Jakarta EE & LTS Java
SE releases

9. Problem: Lack of Support in
GlassFish
Solution: Support Direct From Our Engineers with
Payara Enterprise

10. 10 Year Software Lifecycle

11. Problem: GlassFish is NOT built for the Cloud
Solution: Payara Server Data Grid works out of the box on
public cloud

12. Problem: GlassFish Has No Fat/Hollow JAR
Functionality
Solution: Payara Micro Supports Fat/Hollow JAR - the
runtime is available in a single JAR file which can be
started pointing to your WAR artifact

13. Problem: No Microservices Support In GlassFish
Solution: Payara Micro Launched as microservices
optimised implementation
MicroProfile
Jakarta EE

14. Weaknesses of GlassFish
GlassFish Doesn’t have Automation Recording for Server Configuration
No Internal Monitoring System for Real Time Metrics
GlassFish is Lacking Critical Server Event Alerts and Notifiers
GlassFish is Lacking Some Modern Security Standards
GlassFish does not have supported Docker images
Payara presents solutions to these issues…

15. Problem: GlassFish Doesn’t Offer Automation
Assistance for Server Configuration
Solution: Payara Platform Asadmin
Recorder Offers Automation Assistance

16. Problem: No Internal Monitoring System for
Real Time Metrics in GlassFish
Solution: Payara InSight Allows Real-Time Visualisation and
Alerts for Server and Web App Metrics

17. Problem: GlassFish is Lacking Critical Server
Event Alerts & Notifiers
Solution: Payara Allows Creating and Customising
Notifiers and Alerts

18. Problem: GlassFish is Lacking Some Modern
Security Standards
Solution: Payara Secures your Applications with Built-
in Security Features

19. Solution: Secures your Applications with Built-in
Security Features
Problem: No Supported Docker Images for GlassFish

20. Payara Enterprise vs Payara Community
Community
• Built for the needs of development environments
• Focus on performance over scalability & availability
• Focus on leading edge innovation
• Security issues dealt with at next release
• Community driven
• Manual focus rather than automated
• No guarantee of backwards compatibility or software lifecycle
Enterprise
• Built for the needs of production environments
• Automated with focus on scalability & availability
• Focus on stability with 10-year software lifecycle
• Security alerts and patches for ‘regulatory compliance’ &
quality assurance
• Migration & Project Support, 24x7, or 10x5 support options
• Backwards compatibility

21. GlassFish to Payara Server 5 Migration

22. JDK Migration Considerations
• Payara 5 Enterprise is compatible with both JDK 8, JDK 11 and
JDK 17.
• If your GlassFish domains are currently running on JDK 7 or a
lower version, you will have to update your JDK installation to
JDK 8 as a minimum before starting the migration for Payara
Enterprise.

23. How to Replace Features of Oracle
GlassFish
Coherence Active
Cache
Oracle Coherence =
replaced by Hazelcast
(another in-memory data
grid) out-of-the-box.
Monitoring Scripting Client
Replaced by embedded JMX Server
with support for AMX MBeans that
can be used to monitor JVM and
Server statistics in real-time;
MicroProfile Metrics Support; Health
Check service to monitor the status
of basic environment resources; and
Customisable Monitoring Console.
Oracle Access Management
Integration
Payara Server itself contains
a simple Single Sign On
solution that can be easily
configured using standard
JAAS mechanisms.
Payara Supports modern
standards like JWT, OAuth2
and OpenID Connect.

24. Features to Consider During or
After Migrating
Slow SQL Logging
A crucial production feature
which allows you to easily
detect when a query to the
database exceeds a specific
time.
Payara Health Check
Service
A powerful tool that makes it
easier for the Operation
Teams to run Payara Server
in production by periodically
checking Host CPU Usage.
Request Tracing Service
Helps you to identify
performance issues and
their causes to successfully
solve them.

25. Features to Consider During or
After Migrating
Working With Third Party
Libraries
Payara Server now includes
an isolated classloader for
both EAR and WAR
deployments, so that 3rd
party libraries packaged with
the application are preferred
over those from the server.
Cloud Deployment
Improvements
Better clustering integration
with cloud environments and
friendly configuration options
that cover most common use
cases in cloud environments:
TCPIP, DNS, Multicast,
Kubernetes.
Default Role/Group
Mapping
Payara Server introduces an
additional setting for
deployment descriptors to
explicitly enable or disable
the default role mapping.

26. Payara Accelerator can help!
Designed to accelerate your Payara
Platform deployment, migration, or
business growth through infrastructure
improvements.

27. • Exclusive services for Payara Enterprise customers
• Customized solutions provided on-site or remote
Common services:
• Migration
• Application server upgrades
• Health checks
• Configuration reviews
• Monitoring
• Performance tuning
• Troubleshooting
Payara Accelerator
Add-On Consultancy Services

28. Why Do Companies Migrate
from GlassFish to the Payara Platform?
We’ve been working with Payara Server for over a year in full production and the server
and support have been really good. Support is very professional and helpful. After looking
at GlassFish 4, we considered migrating to other Java EE servers, until we found Payara
Server. Migration from GlassFish 3 to Payara Server was quicker than anticipated. All of
our GlassFish knowledge is still usable but now we have a new and more stable server
that is regularly updated and patched. Also, new added features in Payara Server are
helpful and improve stability and usability. We would recommend Payara Server to
anyone who is still on GlassFish, or looking for a new Java EE application server.
- Eugen Bozic, MIPS d.o.o.

29. Why Do Companies Migrate
from GlassFish to the Payara Platform?
Overall the migration from GlassFish 3 to Payara Platform was a straightforward
process. There was no need for major code rewrites. Setar invested in the Migration
& Project Support for help during the migration process and Payara’s engineering
team was clearly knowledgeable when answering the support tickets.
I’m enjoying the fact that all my knowledge about GlassFish can now be applied to
the usage of Payara Platform. There is no need to put time aside to learn about a
different technology, our team can start working with Payara Platform hands-on
straight away.
-Enrick Lopez, Lead Developer at SETAR NV

30. More Case Studies To Explore
We'll share these links in the chat
Appriss Migrates from GlassFish
to Payara Server to Deliver Critical
Web Applications
Luxury German Vehicle
Manufacturer Migrates from
GlassFish to Payara Server
Leading Telecoms Company
Swisscom Moves to Payara Server
from GlassFish

31. Summary
GlassFish 4.x and 5.x are OLD you need to migrate
Migrating from GlassFish to Payara Server should
be an easy and painless process.
Majority of the work will be making use of new
features.
"Try-before-you-buy" and see how easy it is to swap
over simply by using Payara Server to start up your
existing domain.

32. Questions?

33. We'll share the
link in the chat...​
Already using
Payara?
GET A $20 AMAZON VOUCHER
REVIEW US ON G2

34. We are always looking for the best
Talent so if you are interested in
becoming a Payaran, send your CV
to careers@payara.fish
Learn more:
https://payara.fish/careers
We’re Hiring

35. Join our Global Meetup Group to find out more about our
future events and get involved with our community
Learn more:
https://www.meetup.com/payara-global-meetup/
Payara Global Meetup

36. Download the open source software:
payara.fish/downloads
Get Started:
payara.fish/get-started