In general, transaction propagation is supported by Liberty and you don't need to modify EJBs that run on traditional WebSphere to make them run on Liberty. However, as the original poster says, if you use remote transaction propagation (in which one EJB calls another EJB in a different app server or JVM), the app won't run directly on Liberty.

However, there are workarounds, as @gas says. It might be that you can modify the EJBs so that they run in the same JVM. Sometimes EJBs are configured to use remote interfaces when the calls are actually local; so that's something else that can be easily changed to avoid making remote calls.

If none of that helps, though, you can wrap the EJB in a web service before deploying it to Liberty and then use the web service client to call the EJB web service. But it's worth checking that your app does actually need to be using the EJB's remote interfaces in the first place.

More info about how to check and then how to wrap the EJB in a web service here: https://community.ibm.com/community/user/blogs/laura-cowen1/2025/09/12/transaction-propagation-on-liberty