Getting the Enterprise Ready for Digital Disruption Presented By: George Thadathil

Transcription

1 Getting the Enterprise Ready for Digital Disruption Presented By: George Thadathil Sep 5, 2018

2 Equinix connects the world's leading businesses to their customers, employees and partners inside the world's most connected data centers in 50+ markets across five continents

3 Platform Equinix: A Robust Interconnection Platform 3

4 Our global reach is unmatched 5 Continents 24 Countries 52 Metro Areas 200 Data Centers

5 The Equinix Journey - Moving from BW5 to BW6

6 TIBCO BusinessWorks 6.x Upgrade Modular to Microservices Migration Accelerated productivity with Business Studio Build REST API as First-Class citizens Out of the box CI/CD Open Ecosystem - broad range of connectivity with enterprise services and SaaS & Plugins API Frist Design Cloud Ready Enterprise Integrations

7 TIBCO Upgrade BW6/BWCE/TCI Deployment Flexibility - Choose any platform of your choice Deployed State Key Highlights Productivity Modernization Desired State Cloud Native DevOps with TIBCO Security 7

8 TIBCO Upgrade- Why BW6.X? Productivity Build once, run and deploy anywhere, with DevOps tooling and modular application deployment to shrink release cycles from weeks to days Zero-coding process designer for quick implementation, testing, and maintenance MODERNIZATION Benefit from true web scale with ready containers, microservices, and tooling for APIs, Mobile, Cloud, IoT and microservices Distributed scalability for missioncritical systems and ultra-high performance Cloud Native Multi-cloud support to run on AWS, Azure, Google, Pivotal, and others, and web native development tooling with REST support Security Support for new security protocols like TLSv1.1 and strong ciper

9 Need for Upgrade Two use cases for Upgrade: TLSv1.0 to TLSv1.1 Vendor upgraded their Transport Layer Security(TLS) from TLSv1.0 to TLSv1.1 TIBCO BW 5.10 doesn t support TLSv1.1. Hence there is a need to upgrade to TIBCO BW 5.13 or BW 6 to support TLSv Interfaces Impacted RC4 Cipher Disabled RC4 cipher Why RC4 is being disabled? The RC4 stream cipher is known to have major vulnerabilities, and most ISVs have started phasing out support for it. Applications running on older versions of Java (version 1.6 or lower) that communicate with the SaaS service will encounter SSL/TLS handshake failures TIBCO BW 5.10 doesn t support Java 8 hence the need to upgrade to TIBCO BW 5.13 or BW 6 5 Interfaces Impacted 9

10 Incentives for Upgrade {REST} Inbuild JSON and REST palettes available A major M&A project needing 40+ new interfaces with REST protocol and JSON messaging format With BW6 the LOE for building Rest APIs has come down substantially Can easily create XML schemas using JSON payload for JSON XML transformations. Swagger documentation is auto-generated, and provided for any REST endpoint build and deployed using BW6. TIBCO API Exchange can be leveraged to make this REST service available as Open API via the Swagger-generated document Invoking and Hosting Web Services is easier SOAP Auto Generates Retrieve WSDL

11 Mandate vs Opportunity Mandate TLS upgrade from TLSv1.0 to TLSv1.1 RC4 Cipher {REST/json} RC4 Cipher disability New Initiatives which involve extensive REST/JSON based interfaces Opportunity Cloud Ready - Deploy the applications in cloud without changes to BW 6 code Can create Java projects using Studio for BW 6 where a combination for Tibco and Java is involved CI/CD is possible as we can easily integrate with Maven/Jenkins Integration with standard platforms like GIT OSGi standard is followed for Java, which is common across Tibco products

12 EQIX Integration Platform Key Highlights Highly Decoupled SOA architecture to easily Integrate new Systems ~ 250 Integration interfaces deployed ~ 20 SaaS and On-Premise applications integrated Integrated ~ 85 business processes primarily covering the Q2C and P2P Business processes 800+ PTE Transformations On Path to Cloud Ready Hybrid Architecture

13 EQIX- BW 5 Landscape CRM Legal OM Portals Opportunity Quote Agreement Agreement Quotes Agreement Quotes TLS 1.0 TLS 1.0 RC4 Cipher SOAP APIs SOAP APIs TIBCO BW 5.X MDM Accounts Contacts EMS 7.0 On Premise Apps

14 EQIX- BW 6 Landscape CRM Opportunity Quote Legal Agreement OM Agreement Quotes Portals Agreement Quotes TLS 1.1 Amazon SQS/JSON 9 Interfaces TLS 1.1 TIBCO 6.X Support after RC4 Retirement REST/JSON APIs 24 Interfaces MDM Accounts Contacts EMS 8.3 Fulfillment Orders REST/JSON APIs 40 Interfaces On Premise Apps

15 Integration Stats (Q2 2018) 16.13M Transactions 90ms Average 244 Interfaces 99.6% success Transaction trend Volume x Jan-17 Feb-17 Mar-17 Apr-17 May-17 Jun-17 Jul-17 Aug-17 Sep-17 Oct-17 Nov-17 Dec-17 Jan-18 Feb-18 Mar-18 Apr-18 May-18 Jun FAILED PROCESSED

16 Equinix Timeline Development 3/22/2017 Aug Rel SIT 7/8/2017 Go Live 8/14/2017 Integration Testing 4/7/2017 Internal SIT 5/30/2017 Performance Test 6/26/2017 Aug Rel UAT 7/21/2017 SFDC Enable TLS 1.2 8/20/ Mar Apr May Jun Jul Aug 2017 Development Updates 207 Interfaces Migrated Aggressive 9 month project 2 SIT/QA Cycles Other Applications Migrated Insight Services Customer Finder People Finder Transaction Monitoring Lead Backup Challenges New platform has significant improvements and changes Lot of learning and troubleshooting Cross-functional impacts identified across systems during migration due to the WSDL namespace conflicts (Minor) New developments for ongoing releases alongside Upgrade Additional hardware sizing Stats Roughly 3% of TIBCO Customers had migrated to BW6 and another 18% were In Progress Total 125 Support Tickets raised by EQIX Team size was 10 developers As of TIBCO Customers (~50%)have moved to BW6/BWCE

17 Our Journey After Upgrade - Few Highlights Improved Agility Versatility Re designed 24 interfaces JSON/REST in 4 months Developed 45 complex Interfaces in 5 months v/s 8 in BW 5 Support for Amazon SQS Plugin/ All Nextgen endpoints Cloud Readiness Improved Security Skill Set Development 9 complex interfaces with JSON for Cloud Integration in 7 weeks vs weeks. Support for Upgraded Security protocol for 30 + Interfaces Trained a team of 10+ developers on BW6.X

18 Coding/Testing Convenience in BW6 compared to 5 {REST/json} SOAP Easy development of JSON based interfaces Pre defined folders for Shared Resources, Schemas, Processes, WSDLs which helps to arrange the code Multi Modelling operations All operations of a service can be implemented in one single process. Each operation can be shown or minimized. SOAP and REST services can also be implemented within one single process implementation Easy for unit testing pointing to different environments using profiles (BW 5 needs manual change of GVs to point to a certain environment and test. It is much easier in BW 6 to create profiles for every environment and test by selecting a profile) Ability to deploy the application directly from studio to TEA Remote debugging feature available for runtime debugging IDE is built on eclipse, allowing inbuilt eclipse based features to be leveraged 18

19 Migration Strategy from BW5.x to BW6.x Migration utility is available for migrating projects from BW5 to BW6(60-70% of the code after migration can be used) Need to do retrofit for issues such as: Installed supported plugin versions Unsupported palettes and activities New implementations for SOAP and REST services using Invoke activity* Recreate custom Xpath functions Create shared modules for shared libraries* Redo mappings as needed Onstartup activities have to be recreated using activator process* Inline schemas are externalized Opportunity to redesign inefficient or complex code in BW6 *Most issues have been addressed as of now in version BW6.5 19

20 Key Takeaways Build a value proposition of BW6.x upgrade Mandated vs Opportunistic BW5.X is very different than BW6.x: There is a huge learning curve even for BW5 experts Arrange for training courses Self learning is possible with help from Product Support and should be explored Significant architecture differences between BW5.x and BW6.x - Take PSG help to validate the configurations BW6.x deployments require larger memory, CPU and storage Review with PSG for PROD sizing Speed vs Size. Our transaction volumes are less but sizes are bigger (sometime100 MB payloads) so design considerations need to be accordingly 20

21 Interconnection-Oriented Architecture