BW DATA FORMAT_UNSTRUCTURED| WISHTREE TECHNOLOGIES | LEARNING | TIBCO TRAINING |CORPORATE | TRAINING
Getting the Enterprise Ready for Digital Disruption - TIBCO Software · 2018-09-19 · TIBCO BW...
Transcript of Getting the Enterprise Ready for Digital Disruption - TIBCO Software · 2018-09-19 · TIBCO BW...
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
© 2018 Equinix.com
Our global reach is unmatched
5 Continents 24 Countries 52 Metro Areas 200 Data Centers
© 2018 Equinix.com
TIBCO BusinessWorks 6.x UpgradeModular 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
© 2018 Equinix.com7
Key Highlights
§ Productivity
§ Modernization
§ Cloud Native
§ Security
§ BW6/BWCE/TCI Deployment Flexibility - Choose any platform of your choice
§ DevOps with TIBCO
Deployed State
Desired State
TIBCO Upgrade
© 2018 Equinix.com
TIBCO Upgrade- Why BW6.X ?
MODERNIZATION
Benefit from true web scale with ready containers, microservices, and tooling for APIs, Mobile, Cloud, IoT and microservices
Distributed scalability for mission-critical systems and ultra-high performance
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
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
© 2018 Equinix.com 9
Two use cases for Upgrade:
TLSv1.0 to TLSv1.1Vendor 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 TLSv1.1
25 Interfaces Impacted
Disabled RC4 cipherWhy 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
Need for Upgrade
RC4Cipher
© 2018 Equinix.com
§ 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
§ Auto Generates Retrieve WSDL
Incentives for Upgrade{REST}
SOAP
© 2018 Equinix.com
Mandate vs Opportunity
RC4Cipher
{REST/json}
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
Mandate§ TLS upgrade from TLSv1.0 to TLSv1.1
§ RC4 Cipher disability
§ New Initiatives which involve extensive REST/JSON based interfaces
© 2018 Equinix.com
EQIX Integration PlatformKey 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
© 2018 Equinix.com
EQIX- BW 5 Landscape
TIBCO
EMS 7.0 On Premise Apps
TLS 1.0RC4 Cipher SOAP APIs
SOAP APIs
OpportunityQuote Agreement
TLS 1.0
AgreementQuotes
AgreementQuotes
Portals
AccountsContacts
MDM
TIBCO BW 5.X
Legal OMCRM
© 2018 Equinix.com
TIBCO 6.X
EQIX- BW 6 Landscape
EMS 8.3
TLS 1.1Support after RC4 Retirement
OpportunityQuote Agreement
TLS 1.1
AgreementQuotes
AgreementQuotes
Portals
AccountsContacts
Orders
Amazon SQS/JSON – 9 Interfaces
REST/JSON APIs – 24 Interfaces
REST/JSON APIs – 40 Interfaces
On Premise AppsEMS 8.3
Portals
MDM
Legal OMCRM
Fulfillment
© 2018 Equinix.com
16.13MTransactions
Integration Stats (Q2 2018)
90msAverage
244Interfaces
99.6%success
10328 8072 8777 10780 11219
41047289
14712 134189610 7893
10702 10053 7706 7642
1799013656
29993
3008141 2950551
2609294
2595152
3571722
3315542
2754258
34279183802918
4520729
4178483
3609142
4240977
4780687
4139873
5422098
4880646
5835077
1000
11000
21000
31000
41000
51000
61000
71000
81000
91000
3000
1003000
2003000
3003000
4003000
5003000
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-18
Volu
me
FAILED PROCESSED
Transaction trend
6.x
© 2018 Equinix.com
§ 207 Interfaces Migrated § Aggressive 9 month project§ 2 SIT/QA Cycles§ Other Applications Migrated
§ Insight Services§ Customer Finder§ People Finder§ Transaction Monitoring§ Lead Backup
Development Updates
§ 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
Challenges
§ 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 2018 950+ TIBCO Customers (~50%)have moved to BW6/BWCE
Stats
2017 2017Mar Apr May Jun Jul Aug
Development3/22/2017
Integration Testing4/7/2017
Internal SIT5/30/2017
Performance Test6/26/2017
Aug Rel SIT7/8/2017
Aug Rel UAT7/21/2017
Go Live8/14/2017
SFDC Enable TLS 1.28/20/2017
Equinix Timeline
© 2018 Equinix.com
Cloud Readiness
9 complex interfaces with JSON for Cloud Integration in 7 weeks vs 13-14 weeks.
Improved Agility
Re designed 24 interfaces JSON/REST in 4 monthsDeveloped 45 complex Interfaces in 5 months v/s 8 in BW 5
Improved Security
Support for Upgraded Security protocol for 30 + Interfaces
VersatilitySupport for Amazon SQS Plugin/
All Nextgen endpoints
Skill Set Development
Trained a team of 10+ developers on BW6.X
Our Journey After Upgrade - Few Highlights
© 2018 Equinix.com 18
§ 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
Coding/Testing Convenience in BW6 compared to 5{REST/json}
SOAP
© 2018 Equinix.com 19
§ 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
Migration Strategy from BW5.x to BW6.x
© 2018 Equinix.com 20
§ 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
Key Takeaways