120 likes | 305 Views
zTPFGI Tools & Customer Innovations. Oct. 23, 2012 TPFUG, Denver, CO. 1. Contents. SABRE – TTFS Pilot TTFS Overview SABRE – Forward Traffic I mplementation SABRE – Reverse Traffic I mplementation WELLS FARGO – Development zAUTOMATION Overview WELLS FARGO & zAUTOMATION
E N D
zTPFGI Tools& Customer Innovations Oct. 23, 2012 TPFUG, Denver, CO 1
Contents • SABRE – TTFS Pilot • TTFS Overview • SABRE – Forward Traffic Implementation • SABRE – Reverse Traffic Implementation • WELLS FARGO – Development • zAUTOMATION Overview • WELLS FARGO & zAUTOMATION • SABRE - zTPFGI Installation • Questions ? 2
SABRE - TTFS Pilot TEST SYSTEM INFRASTRUCTURE • DEVELOPER OPTION 1 • Perform LIMITED testing in UNIT TEST SYSTEM • Move code to CUST DEV ENV • Effect – Bugs in integration test system effects user project testing and also other project team testing • Result – Multiple project team time and effort lost • DEVELOPER OPTION 2 • Request to switch the link to UNIT test system temporarily • Effect – Other project teams testing in CUST DEV ENV are on hold • Result – Multiple project team time and effort lost • DEVELOPER OPTION 1 • Perform LIMITED testing in DEVELOPER ENV • Move code to RELEASE ENV • Effect – Bugs in RELEASE ENV effects user project testing and also other project team testing • Result – Multiple project team time and effort lost • DEVELOPER OPTION 2 • Request to switch the link to DEVELOPER ENV temporarily • Effect – Other project teams testing in RELEASE ENV are on hold • Result – Multiple project team time and effort lost User DEVELOPER ENV(4) User DEVELOPER ENV(4) TTFS TEST SYSTEM INFRASTRUCTURE DEVELOPMENT LIMITATIONS DEVELOPMENT LIMITATIONS User RELEASE ENV1 User EXT SYS1 TTFS SOLUTION TTFS RELEASE ENV1 EXT SYS1 TTFS SOLUTION User EXT SYS2 RELEASE ENV2 User TTFS EXT SYS2 RELEASE ENV2
Development teams need not compete for external connectivity. • Configuration files to Route ALL or specific traffic based on rules. • No new hardware required. • TIME, EFFORT and Hardware resources saved • SABRE SW team currently using TTFS tool – • To connect UNIT test system to AIR TRAN test system • To connect UNIT test system to AMADEUS system Productivity TTFS Overview • TPF to TPF Function Server • Client Server architecture. • Provides virtual connectivity for systems with no real connectivity. • Acts as switch, uses the routing table or intercept table to manage the message traffic – INBOUND or OUTBOUND. • TPF 4.1 system can communicate to zTPF or vice versa • Development teams need not compete for external connectivity. • Configuration files to Route ALL or specific traffic based on rules. • No new hardware required. • TIME, EFFORT and HARDWARE resources saved • SABRE TTFS – Pilot usage • To connect DEV ENV and REL ENV to Code Share partner test system • To connect DEV ENV and REL ENV to external GDS system What did we achieve at SABRE? • TPF to TPF Function Server • Client Server architecture. • Provides virtual connectivity for systems with no real connectivity. • Acts as switch, uses the routing table or intercept table to manage the message traffic – INBOUND or OUTBOUND. • TPF 4.1 system can communicate to zTPF or vice versa HOW Does TTFS work? TTFS Overview
SABR SYS1 SABR SYS3 SABR SYS2 zVM Repository SABRE SW – Forward Traffic Implementation • TTFS product is activated with latest CONFIG files from VM repository in SABR SYS1, SABR SYS2 and SABR SYS3 systems • ROUTE ALL messages from SYS2 to Code Share Partner via SYS1 • ROUTE ALL messages from SYS3 to Ext GDS via SYS1 • Multiple Clients can communicate simultaneously Code Share Partner Ext GDS
SABR SYS1 SABR SYS3 SABR SYS2 zVM Repository SABRE SW – Reverse Traffic Implementation • TTFS product is activated with latest CONFIG files from VM repository in SABR SYS1, SABR SYS2 and SABR SYS3 systems • SYS1 receives all the reverse traffic messages • If message from CS route it to SABRE SYS2 • If message from GD route it to SABRE SYS3 • Multiple Clients can communicate simultaneously Code Share Partner Ext GDS
SABRE SW – Reverse Traffic Implementation Going forward, SABRE plans to expand the solution to their Broad Community Test Environments
Wells Fargo Development HOW DO WE? Manage 10 VPARS with 20 Programmers Provide clean VPARS every time to the user zAUTOMATION Achieve Resource Optimization Automate running IPL script
zAUTOMATION Overview Automation Tool to bring up VPARS Uses CONFIG files Does resource optimization Can integrate with zTPFGI/zRTF Automation Tool to bring up VPARS VM Based Product Brings up VPARS from scratch Manages SHARED or POOL VPARS Maintains STANDBY VPARS Uses CONFIG files Brings up VPARS from scratch VM Based Product zAUTOMATION Can Integrate with ZTPFGI/ZRTF Manages SHARED or POOL VPARS Does resource optimization Maintains STANDBY VPARS
Wells Fargo & zAUTOMATION zAUTOMATION Usage • 10 VPARS configured as POOL VPARS • 5 VPARS configured as STANDBY VPARS • Integrated with zTPFGI and zRTF • Advantages • Complete process of Managing VPARS is AUTOMATED • Easy to make changes to CONIFG files • Saves system resource time and effort • Developer always gets a clean system faster for testing using zTPFGI or zRTF • 10 VPARS configured as POOL VPARS • 5 VPARS configured as STANDBY VPARS • Integrated with zTPFGI and zRTF • Advantages • Complete process of Managing VPARS is AUTOMATED • Easy to make changes to CONIFG files • Saves system resource time and effort • Developer always gets a clean system faster for testing using zTPFGI or zRTF • test
SABRE – ZTPFGI Installation • TPF System performance and zTPFGI • zTPFGI CP changes • Multi I-STREAM support • Debugging same transaction using zTPFGI along with Other debugging tools • CTL and OPR dumps • PC exceptions • All issues resolved and running stable with 300+ users. ZTPFGI & SABRE • TPF System performance and ZTPFGI • ZTPFGI CP changes • Multi I-STREAM issues • Users using ZTPFGI along with Other debugging tools • CTL and OPR dumps • PC exceptions • All issues resolved and running stable with 300+ users. • Product installed – Sep 2011 • Production PSS system converted to Z on JUNE 2012 • Products used by SABRE – ZTPFGI & TTFS • ZTPFGI adoption graph • SABRE driven wishlist • Sharing Selective LOADSETS among USERS • Loading loadsets across loosely coupled systems • Support TAXI type Terminal display • Log more performance DATA • Display HEAP NAME • Improvements on ASYNC changes • Export TREX data to other format • Export macro trace viewer to excel format. • Retrofitt TTFS to 4.1 system • Many more wishlist in queue • Sharing Selective LOADSETS among USERS • Loading loadsets across loosely coupled systems • Support TAXI type Terminal display • Log more performance DATA • Display HEAP NAME • Improvements on ASYNC changes • Export TREX data to other format • Export macro trace viewer to excel format. • Retrofit TTFS to 4.1 system • Product installed – Sep 2011 • Production PSS system converted to Z on MAY 2012 • Products used by SABRE – ZTPFGI & TTFS • ZTPFGI adoption graph ZTPFGI & SABRE ZTPFGI RECOMMENDATIONS ZTPFGI RECOMMENDATIONS INSTALLATION CHALLENGES INSTALLATION CHALLENGES