best practices to migrate web sphere WAS applications to a modern version cloud ready

1. WebSphere Migration
Planning, Tools and Help
Davide Veronese
davide.veronese@it.ibm.com
https://davideveronese.wordpress.com/
https://www.linkedin.com/in/davide-veronese-b8b08b28/

2. Agenda
• current environment: WAS versions, JEE version, etc.
• New functionalities introduced by WAS9
• Main differences between WAS7 and WAS9
• WAS7 to WAS 9 migration, attention points
• Available tools and solutions to support the WAS9 migration
• WAS Liberty evolution
• IBM Lab services support
• Q&A, opens discussion
• Evolution to Coud

3. Current stack of techsets regarding different versions of apps
Arch v.1 Arch v.2 Arch v.3

4. Agenda
• Current environment: WAS versions, JEE version, etc.
• New functionalities introduced by WAS9
• Main differences between WAS7 and WAS9
• WAS7 to WAS 9 migration, attention points
• Available tools and solutions to support the WAS9 migration
• WAS Liberty evolution
• How IBM Lab services could support
• Q&A, opens discussion

5. WAS v9 Delivers
Fit for Purpose Servers enabling unmatched combination of Application Server runtime and
development experience, from the highly resilient to the lightweight and nimble

6. WAS v9 Delivers

7. Agenda
• Current environment: WAS versions, JEE version, etc.
• New functionalities introduced by WAS9
• Main differences between WAS7 and WAS9
• WAS7 to WAS 9 migration, attention points
• Available tools and solutions to support the WAS9 migration
• WAS Liberty evolution
• How IBM Lab services could support
• Q&A, opens discussion

8. 8

10. 10

11. Agenda
• Current environment: WAS versions, JEE version, etc.
• New functionalities introduced by WAS9
• Main differences between WAS7 and WAS9
• WAS7 to WAS 9 migration, attention points
• Available tools and solutions to support the WAS9 migration
• WAS Liberty evolution
• How IBM Lab services could support
• Q&A, opens discussion

12. Migration impacts (worst case scenario)

13. JEE specification change analysis (1 of 3)

14. JEE specification change analysis (2 of 3)

15. JEE specification change analysis (3 of 3)

16. Agenda
• Current environment: WAS versions, JEE version, etc.
• New functionalities introduced by WAS9
• Main differences between WAS7 and WAS9
• WAS7 to WAS 9 migration, attention points
• Available tools and solutions to support the WAS9 migration
• WAS Liberty evolution
• How IBM Lab services could support
• Q&A, opens discussion

23. 23

24. 24

25. 25

28. 28

30. 30

40. • Command-line analysis of application binaries
• High level evaluation report
• Detailed analysis for migration to Liberty & Bluemix
I have many apps, what do they need?
• Scans application source to provide:
• A high level evaluation report showing which Java EE technologies your
application uses
• A line-by-line analysis of code changes required
• with detailed information
• with quick fix code changes where possible
• Both run in eclipse against application source
WAS Application Migration Toolkit (WAMT)
https://developer.ibm.com/wasdev/downloads/#asset/tools-WebSphere_Application_Server_Migration_Toolkit
https://developer.ibm.com/wasdev/downloads/#asset/tools-Migration_Toolkit_for_Application_Binaries
• Download from wasdev.net/repo or Eclipse Marketplace

48. I need help with resource config migration
• Eclipse plugin, converts configuration for specific resources to
• server.xml for liberty
• wsadmin jython script for traditional profile
• Input for tWAS profile source is WAS config properties file
• wsadmin -lang jython -c "AdminTask.extractConfigProperties(['-
propertiesFileName my.props'])”
• for application-related resources, not full topology migration
• Written by ISSW World-Wide WebSphere Competitive Migration team
• used (proven) in customer engagements
WebSphere Configuration Migration Toolkit (WCMT)
https://developer.ibm.com/wasdev/downloads/#asset/tools-WebSphere_Configuration_Migration_Tool
http://www.ibm.com/developerworks/websphere/library/techarticles/1404_vines2/1404_vines2.html

49. Agenda
• Current environment: WAS versions, JEE version, etc.
• New functionalities introduced by WAS9
• Main differences between WAS7 and WAS9
• WAS7 to WAS 9 migration, attention points
• Available tools and solutions to support the WAS9 migration
• WAS Liberty evolution
• How IBM Lab services could support
• Q&A, opens discussion

51. Deprecated J2EE
APIs
Full WAS API
Common WAS API
Full Java EE
Java EE
Web
Remaining API Gap
Common WAS API
Full Java EE
Java EE
Web
WAS Liberty 16.0.0.2 WAS traditional
API Gap
JAX-RPC
EJB Entity Beans
JAXR/UDDI
WAS Batch/Compute Grid
WS-BA, WS-RM
JAXM 1.3
ApplicationProfile
AsyncBeans, I18N
Startup Beans, WorkArea
SCA, SDO, XML
J2EE Extensions
Liberty Development -> tWAS
Deployment JAX-WS stacks are different
Runtime class visibility is different
Less EJB/IIOP QOS in Liberty
Client code may be different
v9 Removal v9 Stabilization

53. Agenda
• Current environment: WAS versions, JEE version, etc.
• New functionalities introduced by WAS9
• Main differences between WAS7 and WAS9
• WAS7 to WAS 9 migration, attention points
• Available tools and solutions to support the WAS9 migration
• WAS Liberty evolution
• How IBM Lab services could support
• Q&A, opens discussion

54. IBM DevOps
tools (CI/CD)
IBM
Local
team
Bank premises
Migration factory solutioning for WAS applications in Bank
Bank
DWP
Source code
repository
IBM Migration and Test factory
Actor Role
Bank DWP Development WorkPlace, an existing set of Bank tools for Dev, Build and deploy of WAS applications
Bank Migration
Env
Dedicated Bank environment for WebSphere application migration testing
Bank SMEs Team of Bank Application Architects to support IBM local team to define WAS7èWAS9 application migration policies
IBM Local team Team of IBM GBS Java Application Architects and Specialists to define WAS7èWAS9 application migration policies. The
GBS team could be supported by IBM SWG Specialist. The application migration policies could be proved locally before
being formalized and implemented by the remote IBM GBS team on Bank’s JEE applications
IBM Migration
team
Team composed by IBM GBS Java Application Architects and Specialists to implement the WAS7èWAS9 application
migration policies to the Bank’s JEE applications
IBM Test team Team composed by IBM GBS Test Specialists to implement no regression tests jointly defined by IBM Local team and Bank
SMEs
Bank
SMEs
IBM Migration
team
Migration
env
IBM Test
team
IBM Test
automation tools

55. Agenda
• Current environment: WAS versions, JEE version, etc.
• New functionalities introduced by WAS9
• Main differences between WAS7 and WAS9
• WAS7 to WAS 9 migration, attention points
• Available tools and solutions to support the WAS9 migration
• WAS Liberty evolution
• How IBM Lab services could support
• Evolution to Cloud
• Q&A, opens discussion

56. Evolution to Cloud – the path
Objectives
Move Bank’s applications to WebSphere Liberty as Containers, adopt a LMI (Last Mile Installer) tool
to industrialize the automation, move to Containers on ICP
Traditional XFrame2 App
1 - Modernize (if required)
2 - Libertize
3 - Containerize
Operate
1. Modernize – lift the application code from the
WAS runtime environment, assisted by the
Transformation Advisor as accelerator
2. Libertize – Deploy the application code on the
Java Liberty
3. Containerize – Deploy the application and Liberty
code in a Docker container
4. Operate - Deploy the container package in the
Private Cloud with a LMI tool

57. Thank You