3051_ModernizeWebSphereAtUSAA.pdf

《3051_ModernizeWebSphereAtUSAA.pdf》由會員分享，可在線閱讀，更多相關《3051_ModernizeWebSphereAtUSAA.pdf（12頁珍藏版）》請在三個皮匠報告上搜索。

1、1USAA Classification:PublicIBM IBM TechXchangeTechXchange 2024 2024 Las VegasLas VegasAndre Andre WiradarmaWiradarmaTechnical Architect PrincipalModernizing WebSphereModernizing WebSphere-based based applications at USAAapplications at USAAOctober 20242USAA Classification:PublicOUR MISSIONOUR MISSIO

2、Nis to empower our members to achieve financial security through highly is to empower our members to achieve financial security through highly competitive products,exceptional service and trusted advice.We seek to be competitive products,exceptional service and trusted advice.We seek to be the#1 cho

3、ice for the military community and their families.the#1 choice for the military community and their families.Service.Loyalty.Honesty.Integrity.We takeWe takeWe strive forWe strive forWe fosterWe fosterownership.ownership.excellence.excellence.belonging.belonging.ExceptionalExceptionalWinningWinningF

4、inancialFinancialCommunityCommunityServiceServiceTeamTeamStrengthStrengthImpactImpactfor members.for members.for employees.for employees.for the for the for external for external association.association.stakeholders.stakeholders.OPERATING WITHIN RISK APPETITEOPERATING WITHIN RISK APPETITEOUR CORE VA

5、LUESOUR CORE VALUESOUR BEHAVIORSOUR BEHAVIORSOUR PERFORMANCE OUR PERFORMANCE STANDARDSSTANDARDS3USAA Classification:PublicBackgroundConsiderationsDisposition ApproachReplatform RequirementsReplatform Technical ApproachAgenda4USAA Classification:PublicEnterprise-wide effort to migrate applications of

6、f WebSphere Application ServerA mix of rewrite,replatform and retire dispositionMoving from a traditional weekly release train model to a release-when-ready Continuous Integration/Continuous Delivery modelBackground5USAA Classification:PublicConsideration-A Rapidly Changing Landscape6USAA Classifica

7、tion:PublicConsideration-Layers of Technical DebtvmmiddlewareJava 8tWAS 8.5.5wwwruntime-provided apisusaa app-inf apisenterprise apisapplicationapplication Mixed workload in a single JVM WebApp,reliance on persistent routing,HttpSession Service endpoint using optional Java EE technologies(JAX-RPC)Us

8、ing outdated technologies(EJB,JCA,etc.)Reliance on USAA proprietary apis with baked-in assumptions:monolithic weekly deployment model traditional operational topology shared,unversioned filesystem structure implicit contract Reliance on IBM proprietary APIs LTPA WorkArea WorkManager Outdated impleme

9、ntation of Java EE interfaces/abstract classes Limited lifespan of traditional WebSphere runtime Limited lifespan of JDK 8 Tight coupling with supporting middleware with limited lifespan(e.g.MQ)Limited lifespan of underlying OS7USAA Classification:PublicTarget Statemiddlewarecontainer/vmcontainerlan

10、guageserviceruntime apisapp-inf apiscontainerlanguageenterprise apisSPAcontainerlanguageserviceruntime apisapp-inf apis Single workload per container Single Page Application interaction with backend services Separation of services based on their bounded context Minimal reliance on USAA proprietary A

11、PIs Choice of runtime and programming languages Loose coupling with enterprise capability via service invocation Loose coupling with supporting middleware(e.g.MQ,Kafka,etc.)Release-when-ready via Continuous Integration/Continuous Deployment8USAA Classification:PublicDisposition ApproachEARs&JARsEARE

12、AREARIs it still actively used?Is it going to be retired in 1-2 years?Is it going to be replaced in 1-2 years?What are the modernization challenges?Cost&complexityLeast preferredMost preferredTooling,Process and Platform InvestmentApplication Modernization OptionsRebuild/RewriteRearchitectRevise/Rep

13、latformModernize Application Infrastructure ComponentsModernize Enterprise ComponentsModernize LOB Components9USAA Classification:PublicDisposition ApproachRevise:Modernize the underlying middleware(s)and operational environment with minimal changes to the application.Example:Redeploy JAX-RS applica

14、tions to a containerized Open Liberty runtime,reconfigure MDBs to interact with remote Queue Manager instead of a local one,etc.Rearchitect:In addition to component revisions,some changes to the application architecture are introduced,while keeping the bulk of the application codebase and design int

15、act.Example:Replace Java Connector Architecture interaction with z/OS Connect REST API to invoke CICS/IMS transactions,replace JMS-based communication with Kafka,etc.Rebuild:Rewrite the application,providing the same business capabilities with some differences in user experience.Dependent services o

16、r upstream consumers might need to be modified or replaced.Example:Rewrite Web Application as a Single Page Application,etc.10USAA Classification:Public10Allow minimal changes to allow application migration at-scaleProvide flexibility for developers to choose when to upgrade specifications that thei

17、r application depends onProvide timely support for emerging specificationsLightweight,designed and optimized for cloud native Smooth migration strategy for javax.*to jakarta.*(Jakarta EE 9 and above)Minimize day-2 chores for application ownersReplatformReplatform Disposition Disposition-Requirements

18、Requirements11USAA Classification:Public11Open Liberty using Java 11/17Adoption of standard DevSecOps tooling and CI/CD pipelineAdoption of Jakarta EE 9(adopt jakarta.*namespace)Migrate SOAP services from JAX-RPC to JAX-WS Replace JMS/MQ with Kafka interaction wherever possibleLeverage MQ Uniform Cl

19、uster when needed(point-to-point)Remove EJB usage wherever possibleRemoval of most USAA specific application infrastructure library dependenciesRemoval of Java Connector Architecture interaction with Z,replaced with z/OS Connect interactionReplatformReplatform Disposition Disposition Technical Approach HighlightsTechnical Approach Highlights