启用 winstall 安装 SAP Machine
https://winstall.app/apps/SAP.SapMachine.21.JDK
winget install -e --id SAP.SapMachine.21.JDK
SAP 开源了 https://github.com/SAP/SapMachine
This project contains a downstream version of the OpenJDK project. It is used to build and maintain a SAP supported version of OpenJDK for SAP customers and partners who wish to use OpenJDK to run their applications.
We want to stress that this is clearly a "friendly fork". SAP is committed to ensuring the continued success of the Java platform.
More details about theSAP’s Engagement in the OpenJDK project,installation instructions,frequently asked questions,the maintenance and support statement, and more are available in the documentation.
该项目包含OpenJDK项目的下游版本，旨在为希望使用OpenJDK运行应用程序的SAP客户及合作伙伴构建和维护SAP支持的OpenJDK版本。
我们特别强调这属于"友好分支"。SAP致力于确保Java平台的持续成功。
关于SAP参与OpenJDK项目的详情、安装指南、常见问题解答、维护支持声明等内容，请参阅文档部分。
https://www.sap.com/about/company/innovation/open-source.html
Our commitments:
Consistent contributions
Championing open standards
Open-first approach
Nurturing open source ecosystems
Feedback-driven approach
How we engage:
Respectful engagement
Sustained support
Clear and fair licensing
Empowering our employees:
Encouraging open source participation
Continuous learning
Acknowledgment of excellence
InnerSource
JDK 21 Upgrade Learnings from SAP Commerce Version 2205
https://community.sap.com/t5/crm-and-cx-blog-posts-by-sap/sap-cc-jdk-21-upgrade/ba-p/14282138
We have successfully completed a JDK 21 upgrade from SAP Commerce version 2205 (previously on JDK 17). Sharing our learnings and resolutions encountered during the upgrade which may be helpful for similar implementations.
1. Automation Support Using OpenRewrite
SAP has provided customized OpenRewrite recipes to automate static code migrations. These greatly reduce manual effort.
👉Refer to SAP Note #3618495 (OpenRewrite automation guide) for detailed execution steps.
Outcome: Automates majority of standard class and package-level updates.
2. Manual Fixes Post-OpenRewrite Execution
Some library-level changes require manual fixes such as: - Assertion - Common.lang - RFCConstantsjakarta.jms
Action: Update imports and usage based on the upgraded libraries.
3. Server Startup & Initialization Issues
Several issues were observed during server startup and platform initialization. Details and solutions below.
Issue A — Spring Security Context Initialization Failure
Error:
Context initialization failed - Error creating bean with name 'org.springframework.security.filterChains'
NoSuchBeanDefinitionException: No bean named 'mvcHandlerMappingIntrospector' available.
Root Cause: Spring Security 6.x requires a shared ApplicationContext with Spring MVC when using MvcRequestMatcher.
Resolution:Update web.xml to ensure MVC config loads into the main context instead of DispatcherServlet.
➡Added MVC configuration into global context
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>
WEB-INF/config/customextension-web-app-config.xml
WEB-INF/config/customextension-spring-mvc-config.xml
</param-value>
</context-param>
➡Cleared separate servlet context
<param-name>contextConfigLocation</param-name>
<param-value></param-value>
Outcome:Application started successfully.
Issue B — Invalid URL Pattern Mapping in Spring MVC
Error:
PatternParseException: No more pattern data allowed after {*...} or ** pattern element
Root Cause:Legacy wildcards like /**/something, /**, {*path} are not supported under PathPatternParser.
Solution:Switch back to AntPathMatcher in spring-mvc-config.xml.
<bean id="pathMatcher" class="org.springframework.util.AntPathMatcher" />
<mvc:annotation-driven>
<mvc:path-matching path-matcher="pathMatcher"/>
</mvc:annotation-driven>
Outcome:Legacy mappings restored, storefront initialized.
Issue C — Spring Security 6 Intercept-URL Failure
Error:
IllegalArgumentException: expressionString cannot be empty
Root Cause:Spring Security 6 does not allow intercept-url without an access expression.
Fix:Add default authorization
<security:intercept-url pattern="/**" access="permitAll()" />
Outcome:Security filter chain initialized successfully.
Issue D — AuditReportServices Impex Failure During UpdateSystem
Error:Deprecated password encoder triggered failure.
PBKDF2WithHmacSHA1SaltedPasswordEncoder is deprecated
Fix:Temporarily allow legacy password encoding
legacy.password.encoding.enabled=true
🔄Revert setting post-update if needed for backward compatibility.
Issue E — Ambiguous Mapping for “/” After Upgrade
Error:
IllegalStateException: Ambiguous handler methods mapped for '/'
Root Cause:Two controllers mapped to /.
Solution:Update default controller fallback
@RequestMapping(value = "/**", method = RequestMethod.GET)
Issue F — Spring 6 JSP BindTag Error
Error:Missing command model attribute.
Neither BindingResult nor plain target object for bean name 'command'
Resolution:Add required model attributes
@ModelAttribute("command")
public LoginForm commandLoginForm() { return new LoginForm(); }
Issue G — Security JSP authorize Tag Failure
Error:Missing ExpressionHandler
No visible WebSecurityExpressionHandler instance could be found
Fix:
<bean id="webSecurityExpressionHandler"
class="org.springframework.security.web.access.expression.DefaultWebSecurityExpressionHandler"/>
Issue H — No Mapping for GET Warnings
Solution: Add explicit URL mappings where needed.
@RequestMapping("/search/")
@GetMapping("/quote-requests/")
Conclusion
JDK 21 + Spring 6 migration introduces strict compatibility constraints requiring updates in: - Spring MVC URL mapping - Spring Security configuration rules - Application context structure - JSP model binding - Password encoding framework
The above resolutions enabled successful storefront startup and full system initialization.
