Cracking the Legacy Integration Dilemma: Five Easy Steps to Get Started

1. Cracking the Legacy Integration Dilemma:Five Easy Steps to Get Started www.openlegacy.com #OpenLegacy 

2. Agenda Rethinking digital transformation Steps to incorporate your on-prem systems Test and deployment strategies Real-life samples - DevOps driven transformation Demo Questions and answers #OpenLegacy

3. Speakers Martin Bakal Product Marketing Director OpenLegacy Zeev Avidan Chief Product Officer OpenLegacy #OpenLegacy

4. #OpenLegacy How do we start our digital transformation?

5. #OpenLegacy With OpenLegacy, you can start off easy and grow at your own pace.

6. DevOps The topics discussed here aren’t just for organizations moving to DevOps. They are exacerbated by DevOps usage: • Quick releases • Testing The general concepts are useful for any methodologies. SOFTWARE PROCESS • Plan • Release • Deploy • Code • Test • Operate • Monitor • Build DevOps is a spectrum. #OpenLegacy

7. Examples of enterprises that jumped right in An insurance company created 100 APIs in 2 months. • Saved total development time of about 1 full year of man-hours A bank deployed 27 new APIs, with more than 70 microservices in 10 weeks. Creating an API in less than an hour - compared to 1-2 months previously. #OpenLegacy

8. #OpenLegacy

9. 1. Get started with limited resources Why are legacy team members normally required? • Analysis   • Data type translation • Building facades Legacy team members are a limited resource. To keep teams small, don’t require them! #OpenLegacy

10. Transformation without legacy team members/systems You gain: • Flexibility • Resource Availability • Fewer approvals needed OpenLegacy achieves this by: • Automatic parsing • Java • Direct connection Result: Teams can move between cloud and hybrid integration projects. #OpenLegacy

11. 2. Start with an MVP Skew tradeoff decisions towards the strategic. Pick a pain point from the organization: • Impactful to stakeholders • Easily definable Automatic parsing simplifies the monolith—the team can pick the content  Simplifies the integration scenario and allows teams to get started GOALNot have IT be a bottleneck USE CASENew deal with large bank Sell to their business customers Software updates completed 2 months before signed agreement SOLUTION Legacy Integration DevOps #OpenLegacy

12. #OpenLegacy Ayalon Platform JENKINS Unit Test Req. Mgmt. Development + Configuration Mgmt. Pipeline CI/CD JIRA IDE/OpenLegacy GIT(source & conf.) BITBUCKET(UI & admin) DOCKER(container) Build QA ICP KUBERNETES Prod Management & Orchestration

13. 3. Build connections to legacy quickly and easily This might look daunting: • Design the API • Build the facade • Streamline communication • Retrofit deployment environment • Build on proprietary processes But automation makes the process simpler: • Exposes potential APIs • Generates connecting code • Direct Connections speed execution #OpenLegacy

14. 4. Automate test generation Testing Process A typical process build: Test Driven Design (TDD) OpenLegacy automates: Unit Testing Deployment Integration Regression #OpenLegacy

15. 5. Simplify deployment “Simplified our architecture to deploy faster and more efficiently.” — Creditcorp Bringing legacy data to the cloud • Microservices ease deployment • OpenLegacy generates Docker with binding, a configured Gateway • Simplified process Microservices make DevOps deployment work Deploy anywhere with microservices architecture “Architects have grown accustomed to thinking that robustness equals complexity. OpenLegacy demonstrates the other way is true.” — Senior Architect #OpenLegacy #OpenLegacy

16. #OpenLegacy Modernize with a Scalable Microservices and API Integration Design the API using Point-and-Click or Open Java code 3 5 Digital services rollout Using DevOps standards 1 Legacy and on-prem systems & applications 2 4 Automatic generation of SDK (standard Java code) One-click deployment of microservices applications

17. DEMO / Create and Run Mainframe API OpenLegacy API Contract OpenLegacy Front End OpenLegacy SDK API Dependencies DEPLOY Swagger Spec / Microservice / API Gateway Entity MetaData 1 Connector Contract OpenLegacy SDK 1 Connection Properties Angular Application Legacy System Orchestration / Transformation Entity MetaData 2 OpenLegacy SDK 2 • Console for: • Analytics • Optimizations • Security Optionally manual Entity MetaData N OpenLegacy SDK N API Structure Generation Structure Generation Metadata Model Generation Contract Generation Automated MS Deploy Automated Front End OL Wizards #OpenLegacy 17

18. Getting steered in the right direction with these offers • Schedule a personalized demo • https://go.openlegacy.com/devopsdemo • Schedule a Proof of Concept (PoC) • https://go.openlegacy.com/devopspoc #OpenLegacy

19. Wrap-up and Q&A Q&A Get started with limited resources Start with an MVP Build connections to legacy quickly and easily Automate test generation Simplify deployment #OpenLegacy

20. Appendix

21. #OpenLegacy OpenLegacy Platform Management Console API Gateway Private Cloud, Public Cloud, or On-Prem System Mobile Cloud EJB Web Security Discovery Analytics Performance High Availability IBM i DevOps CI/CD Mainframe SDK Java Microservice API Automatic Generation of Microservice based APIs Databases JSON REST API Communicate Parse Fetch Automate SOAP Templates