Application Server v.7 & 8 on April 30th is fast approaching 26 - - PowerPoint PPT Presentation
End of Support for IBM WebSphere Application Server v.7 & 8 on April 30th is fast approaching 26 th of April 2018 Host: Lisa Hedlund Agenda Why migrate Whats new with WAS V.9 including Liberty Application migration tools
End of Support for IBM WebSphere Application Server v.7 & 8 on April 30th is fast approaching
26th of April 2018 Host: Lisa Hedlund
Agenda
management solution from Tech Data
Talos Overview
Easily configure, deploy, manage & migrate middleware Philip Leaper Domain Architect, Tech Data philip.leaper@techdata.com
The current state of the middleware market
The worldwide application integration and middleware (AIM) software market continues to grow faster than the overall infrastructure software market Growth in mobile, big data, analytics, in-memory computing, cloud and Internet of Things initiatives is associated with digital business and requires application and integration professionals to invest in new AIM technologies “Established approaches to application infrastructure are too rigid, closed and cumbersome to support many digital business requirements,” said Fabrizio Biscotti, research vice president at Gartner.
Worldwide Middleware market: $27 billion in 2017, +7% on 2016. Gartner, Inc . https://www.smechannels.com/gartner-predicts-middleware-software-market-to-reach-27b-in-2017/ Orchestration
New Software Tooling & the Cloud
“By 2020 50% of the CIO’s that have not transformed their capabilities will be displaced from the digital leadership team.”
Gartner
http://www.gartner.com/binaries/content/assets/events/keywords/infrastructure-operations-management/iome5/gartner-predicts-for-it-infrastructure-and-operations.pdf http://www.idc.com/getdoc.jsp?containerId=US42079317"Over the next five years, new custom application development will continue to be built on a cloud architecture, and we'll also see an acceleration in the use of containers to migrate existing bespoke applications to the cloud. Migration will inhibit growth," according to Maureen Fleming, vice president of IDC's Business Process Management and Middleware research
IDC
Hybrid Clouds
The move to DevOps
Some of the stats behind DevOps on the surface seem incredible:
Regardless of the numbers, the movement to seamless tool chains and continuous development seems inevitable.
Stats from Puppet State of DevOpS 2017 Describe how Talos forms part of a DevOps toolchain that substantially reduces the complexity of configuring, managing & migrating middleware
I need a single method for multiple middleware platforms We have identified need to save money I want to be able to move into (or out of) cloud environments and avoid vendor lock in I have released code into a different environment and it doesn’t work I want to migrate to the cloud I’ve already purchased
why do I need this too? I’m dependant
guru, what if he leaves?! My configuration management is out of control I need to do everything faster I have too many highly skilled people focussed on this How do I migrate to micro- services running on Docker containers?
Common Customer Challenges
I want a quicker implementation cycle for applications
Customer Challenges CommonTheme
Talos is for
Middleware users who want to:
Talos is
A migration and configuration tool which has pre-built interfaces to popular middleware, container and cloud platforms
Talos differs
In contrast to configuration and orchestration tools such as Puppet and Ansible, Talos provides a comprehensive toolkit that normalises the administration of multiple middleware platforms
(i.e. one method for all)
Enables:
How Talos fits with modern DevOps Tooling
So why do you need Talos?
Agile Dev Continuous Integration Continuous Delivery Continuous test
Version Control Build Server Artefact Repository Application Deployment Environment Deployment Configuration Management Automated TestingDevelopers
integration
platform integration
migrating to microservices
migrating to microservices
Automatically migrate from monolithic legacy middleware run-times to microservices run-times on containers
Automatic template translation from traditional middleware to microservices run-times Build middleware based containers leveraging a wizard Map Talos templates to both traditional middleware and microservice based containers thereby leveraging a common deployment approach across both estates
platforms supported
What if my middleware is not currently supported?
If the Middleware platform is unsupported, then we can offer toolkit development – typically an 8 week build cycle (4 Week Beta / 4 Week Production)
I need a single method for multiple middleware platforms We have identified need to save money I want to be able to move into (or out of) cloud environments and avoid vendor lock in I have released code into a different environment and it doesn’t work I want to migrate to the cloud I’ve already purchased
why do I need this too? I’m dependant
guru, what if he leaves?! My configuration management is out of control I need to do everything faster I have too many highly skilled people focussed on this How do I migrate to micro- services running on Docker containers?
Common Customer Challenges
I want a quicker implementation cycle for applications
Prevents cloud “Lock-In” Negates the requirement for producing and maintaining scripts Supports migrations – retaining customer’s investment in current Middleware Middleware can scale without having to scale resources Reduce Risk of losing key people, through capturing Tribal Knowledge Eliminate scripting Move to a DevOps methodology quicker Enables ease of migration to the cloud with Cloud Provider plugins Reduces release and deploy cycles Works with and enhances other DevOps tools you’ve already got Brings consistency to multiple teams (Dev/Ops/geographic) Eradicates the inconsistencies between environments Removes human error Provides a standard normalised platform for multiple Middleware Vendors Enforcing consistent global changes securely while ensuring compliance; data protection and security Manage performance and quality of your outsourced IT / infrastructure provider
Benefits
Case Study #1 International Bank
An international organisation that provides offshore banking services to their personal, business, commercial, corporate and financial intermediary customers were facing a predicament in the way they deployed and managed the applications in their IBM WebSphere Application Server environment. After implementing Talos the bank is now able to build environments for IBM WebSphere, read existing IBM WebSphere Cell configurations and deploy applications in existing or new IBM WebSphere Cells from test to production environments Once implemented we compared the time it used to take for build and deploy applications prior to, and post, the installation of Talos.
What used to take 40 man hours of build and deploy now takes just two and a half hours, a time saving of 93.75%.
Case Study #2 Financial Clearing House
A financial organisation was looking to upgrade from WebSphere Application Server 7.0 to WebSphere Application Server 8.5.5. There were 30 WebSphere cells across Development, QA, Staging and Production environments The organisation was keen to use Talos for the ability to migrate and promote configurations, apply and rollback fix-packs, plus it would be set up to compare environment configurations. The customer originally estimated that to do the migration manually using internal consulting services, it would take four months.
The project was delivered in four weeks. Leveraging Talos allowed for a 75% reduction in delivery time and 60% savings on the costs as well as providing a solution for
after the initial migration.
Summary
Talos and other DevOps tools – where it fits Orchestration Engines, Cloud & Container integration Middleware platforms Cost, Quality, Speed Case studies – actual benefits proven
Talos is a key part of any DevOps toolchain that substantially reduces the complexity of configuring, managing & migrating middleware
WAS Version Migration Demo
Contact: lisa.hedlund@techdata.com