AEM 6.5 and Java 17

Summary

This session delves into Adobe Experience Manager (AEM) 6.5's future compatibility with Java 17. Key speakers, Ashok Kumar and Sagar Miglani, highlight the benefits of Java 17, including improved performance, security, and developer productivity. They discuss the new 'AEM 6.5 2025 Edition' quickstart, detailing updates such as modernized open-source libraries, improved security profiles, and support for Jakarta Servlet APIs. The presentation also covers the options for upgrading to Java 17 and the beta program launch in December 2024, with insights into the transition process, backward compatibility, and long-term support for users. Additionally, they address questions on Java versions and platform compatibility.

Takeaways

• 😀 Adobe is upgrading Adobe Experience Manager (AEM) 6.5 to support Java 17 to enhance performance, security, and developer productivity.
• 😀 The main motivation for moving to Java 17 is the longevity of the support cycle and improved features like modernized code practices and reduced memory footprint.
• 😀 The Java 17 upgrade will bring improvements to the open-source stack used by AEM, including Apache Sling, Felix, and Oak.
• 😀 Java 17 introduces better garbage collection, security patches, and language enhancements, such as text blocks and records.
• 😀 AEM 6.5 users will be able to use new Java 17 features, enhancing developer productivity and code readability.
• 😀 A new quick start, code-named AEM 6.5 2025 Edition, will be released to implement the Java 17 upgrade and include the latest open-source stack.
• 😀 The AEM 6.5 2025 Edition will support Jakarta Servlet APIs and improve compatibility with modern servlet containers like Apache Tomcat and IBM WebSphere.
• 😀 AEM 6.5 2025 Edition will streamline security updates by using the latest versions of core libraries and removing outdated dependencies like Common Collections 3 and the old Guava library.
• 😀 The upgrade process for AEM 6.5 to Java 17 will involve two main options: an in-place upgrade or a side-grade for more complex migrations.
• 😀 AEM users can participate in a beta program for the Java 17 upgrade, with general availability expected by the end of 2024.
• 😀 Future AEM updates will include both the current 6.5 Service Packs and the new 6.5 2025 Edition, with the possibility of a shift towards the new edition depending on adoption rates.

Q & A

Why is Java 17 being introduced in AEM 6.5?

Java 17 is being introduced in AEM 6.5 to provide better long-term support, enhanced developer efficiency, improved performance, and faster security patches. It offers modernized language features such as text blocks, records, and improved garbage collection, which makes the code more readable and reduces memory usage.

How does Java 17 benefit AEM users?

Java 17 benefits AEM users by providing a more modern codebase, enhanced security patches, and better performance through improved JVM memory footprint and garbage collection. Additionally, it enables developers to use new language features, improving development efficiency and reducing technical debt.

What is the core motivation behind upgrading to Java 17 for AEM?

The core motivation is the longevity of Java 17's support cycle, which ensures that the platform will be maintained for a longer period. Java 17 also supports more modern coding practices, improving developer productivity, and it provides better security updates compared to previous Java versions.

What changes will occur in AEM 6.5 with the Java 17 upgrade?

AEM 6.5 with Java 17 will leverage the latest versions of Apache Sling, Felix, and Oak. These upgrades bring performance improvements, security enhancements, and support for newer libraries, such as Jakarta Servlet APIs. There are also deprecations of outdated libraries, such as Common Collections 3, and removal of old versions of the Guava library.

What is the role of the new AEM 6.5 2025 Edition quick start?

The AEM 6.5 2025 Edition quick start introduces compatibility with Java 17, and it includes upgraded open-source core components, like Sling and Felix. It enables users to benefit from the latest security fixes, performance improvements, and simplifies future updates for AEM customers, while ensuring minimal disruption during the transition.

Why is there no Java 17 upgrade via Service Pack for AEM 6.5?

Java 17 cannot be delivered via a Service Pack because of compatibility issues between Java 8 and Java 17. The changes are significant enough that they require a new quick start rather than just a backward-compatible Service Pack. Additionally, the upgrade involves a complete overhaul of core open-source components, making it too complex for a Service Pack update.

What does the AEM 6.5 2025 Edition offer in terms of security improvements?

The AEM 6.5 2025 Edition improves security by deprecating outdated libraries like Common Collections 3 and removing old versions of the Guava library, providing customers more flexibility. It also includes upgraded JVM, core libraries, and third-party dependencies, offering a better overall security profile.

How will Jakarta Servlet API compatibility impact AEM 6.5 2025 Edition?

The AEM 6.5 2025 Edition brings compatibility with Jakarta Servlet APIs, allowing the Apache Felix J2EE container to support modern servlet containers. This ensures that War packaging is compatible with external servlet containers like Tomcat or WebSphere, and legacy servlet APIs will continue to work with Sling Servlets without disruption.

What are the two main upgrade options for AEM 6.5 2025 Edition?

The two main upgrade options are in-place upgrade and side-grade. The in-place upgrade involves directly replacing the AEM 6.5 jar with the new AEM 6.5 2025 jar, while the side-grade option is used for more complex migrations, such as repository migration, typically involving a change in servlet container or repository structure.

When will Java 17 support be available in AEM 6.5, and what are the beta testing plans?

Java 17 support for AEM 6.5 is expected to be available with the AEM 6.5 2025 Edition quick start, with a beta program opening towards the end of December 2024. Customers interested in upgrading to Java 17 can subscribe to the beta program to get early access and contribute feedback before the general availability of the release.