In our last session, we covered modernizing your operations from WebSphere traditional on-premise to containers. Join us in this session as we cover the next step in your modernization journey, moving from WebSphere traditional base containers to Liberty. This will include how to collect data from WebSphere traditional running in a container, how to make the necessary configuration and code changes, and deploying to Liberty.
Learn how to modernize your operations by moving from WebSphere traditional base containers to Liberty. Including:
- How to collect data from WebSphere traditional running in a container
- How to make the necessary configuration and code changes
- And deploying to Liberty
Liam Westby - WebSphere Migration Tools Development
Liam is a software developer with IBM in Rochester, Minnesota, working on WebSphere application modernization tools and education. He has worked on Java and WebSphere migration tools for 9 years, with a focus on tooling that automates modernizing configuration and deployment of servers and applications, everywhere from mainframes to microservices.
Cindy High - WebSphere Migration Tools Architect
Cindy has worked over 20 years with WebSphere Application Server, Liberty, Java EE and now Jakarta EE as a developer, technical lead, and architect. She is the WebSphere Application Server migration tools architect at IBM and currently works on app mod tools that help with operational and runtime modernization as well as Java SE and EE upgrades.
Alex Motley - WebSphere Migration Tools Development Lead
Alex is a software engineer at IBM leading the WebSphere Application Server migration tools team. His team develops several migration tools to help with a variety of modernization scenarios including WebSphere traditional to Liberty, Java SE and EE versions, and on-premise to cloud. He has almost a decade of experience working with Java EE and Java application server technology. Alex enjoys hiking and skiing and lives in Rochester, MN.