This project provides a Reference Implementation for migrating existing Java EE applications from on-premise to cloud-based deployments, as well as migration to a microservices-based architecture.
Our best practice in moving applications from on-premise to the cloud is to first do the upgrade on premise and pass at least the integration (or functional) tests. Then once that is done to move it to the cloud and handle the connectivity issues. So, I would start this session with the upgraded migration - the one that worked on-prem in WAS V9 ... so you would only see the connectivity issues at this time and would not see all of the other issues that were addressed in the previous section. So, I'd re-run the tool with the on-prem migrated ear/war.
We can see in the report that the issues in the green boxes were already reported during the previous code migration phase in which these were already addressed. The reason for these issues to appear again in the report is because we did not address them per se since we are 'lifting & shifting' our existing old WebSphere Application Server applications running on existing on-premise resources to a newer WebSphere Application Server version and different IBM platform. That is, we want to do that 'lift & shift' the simplest and least intrusive. This means to do the least changes to the code or structure of the applications as well as reuse as most as possible the same Java Technologies and versions of them as long as the new WebSphere Application Server version and IBM platform support them.
Our best practice in moving applications from on-premise to the cloud is to first do the upgrade on premise and pass at least the integration (or functional) tests. Then once that is done to move it to the cloud and handle the connectivity issues. So, I would start this session with the upgraded migration - the one that worked on-prem in WAS V9 ... so you would only see the connectivity issues at this time and would not see all of the other issues that were addressed in the previous section. So, I'd re-run the tool with the on-prem migrated ear/war.