1 / 21

T PF to T PF F unction S erver (TTFS)

T PF to T PF F unction S erver (TTFS). SABRE / TPF Software. Agenda. TTFS - OVERVIEW FORWARD OUTBOUND - REQUEST INBOUND - REVERSE TTFS FEATURES SABRE BACKGROUND CURRENT SABRE TESTING ENVIRONMENT PROPOSED SOLUTION – TTFS PROOF OF CONCEPT PROOF OF CONCEPT PLANNING

ifama
Download Presentation

T PF to T PF F unction S erver (TTFS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TPF to TPF Function Server (TTFS) SABRE / TPF Software

  2. Agenda • TTFS - OVERVIEW • FORWARD OUTBOUND - REQUEST • INBOUND - REVERSE • TTFS FEATURES • SABRE BACKGROUND • CURRENT SABRE TESTING ENVIRONMENT • PROPOSED SOLUTION – TTFS PROOF OF CONCEPT • PROOF OF CONCEPT PLANNING • TTFS PROOF OF CONCEPT – CONCLUSIONS • CONTACTS

  3. TPF to TPF Function Server (TTFS)Overview -TPF Software-

  4. TTFS Overview • Simulates or provides virtual connectivity for systems with no real connectivity. • TPF to TPF Function Server • Client Server architecture. • Acts as switch, uses the routing table or intercept table to manage the message traffic – INBOUND or OUTBOUND.

  5. TTFS Overview • Multiple clients connected to Server, can share same connection. (FORWARD OUTBOUND) • Server controls the reverse message traffic and routes it to respective Clients. (REVERSE) • Intercept tables used to define the rules and message route definitions.

  6. Forward Outbound Request Client 1 Server zVM Repository • Configuration tables from repository copied to client and server • Transaction initiated • Check Intercept table for condition • If condition is satisfied send the request to Server • Server processes the request • Response is sent to Client & transaction completes • Response to user • Multiple Clients can communicate with similar mode External System

  7. Inbound Reverse Administrator TPF Server zVM VPARS Client 1 Repository Condition Table • Configuration tables updated • Administrator can UPD config table dynamically • Reverse traffic received • Check Rules table for condition. • If satisfied send to destination Client. • Send request to CLNT • Receive response from CLNT • Reply to external system. External System

  8. Capability to exchange multiple types of ECB data between Client and Server. Configuration Tables used to manage message routing. Management tools for administration of Intercepts in Client/Server. Usage tools to display Message Statistics, Timeouts and Average Response Time etc.. Data logging for administration and debugging purpose. TTFS Features

  9. Background -SABRE-

  10. A Communications Gateway Switch provides TPF connectivity to Sabre’s external trading partners Our TPF testing environments currently face the following limitations : Forward Connectivity - A maximum of 8 TPF Test processors (CPUID’s A-H) can connect with the Sabre Communications Gateway to send traffic (forward transactions) to external trading partners. Reverse Connectivity: Unsolicited message traffic coming from external trading partners into the Sabre Communications Gateway is limited to a single end point (TPF Test System) Background

  11. CurrentSabre Testing Environment UNSOLICITED MSSGS AKA REVERSE HOST TRAFFIC NORMAL TRAFFIC EXCHANGE AKA FORWARD TRAFFIC Communications Gateway External Trading Partners X X 9th VPARS not allowed PKGE CERTC CERTD TSTA zTPF-F zTPF-H TSTB CERTIFICATION INTEGRATION zTPF zTPF-G

  12. Proposed Solution - TTFS External Trading Partners UNSOLICITED MSSGS AKA REVERSE HOST TRAFFIC NORMAL TRAFFIC EXCHANGE AKA FORWARD TRAFFIC Communications Gateway X 9th VPARS not allowed X TTFS SERV zTPF-G TTFS SERV PKGE CERTC CERTD zTPF-F zTPF-H TTFS CLNT TTFS CLNT TTFS CLNT TTFS CLNT TEST VPARS WITH NO CONNECTIVITY

  13. Proof-of-Concept -SABRE-

  14. Parties Involved HP – Middleware SME TPF Software – Product Sabre – TSMO List of Intercepts Program / Macro to intercept Data to send the other side Conditions to trap the intercept RPPCC Sabre Unique Communications API Extensively used across applications for external access POC Planning

  15. Proof of Concept Sabre/HP/TSI conducted a proof-of-concept to evaluate whether TTFS could resolve current connectivity limitations Two different scenarios were utilized: Scenario 1- Isolated Test Bed - To avoid any disruption to our test environments and customers, an isolated test bed consisting of three internal VPARS was initially used to demonstrate the TTFS capabilities. Scenario 2- PKGE VPARS as the TTFS Server – PKGE which is one of the 8 test systems with actual connectivity to the Communications Gateway was used as the TTFS/Server to further demonstrate whether TTFS could process outbound / inbound messages from / to an external system. Both scenarios included: Forward Messaging (SYNC & ASYNC) Reverse Messages (SYNC)

  16. POC – Forward/Reverse Connectivity Simulation Client VPARS with No connectivity Test Host of External Partners T T F S User Terminal TTFS Server (PKGE) T T F S ACPMXA43 Client VPARS with No connectivity User Terminal ACPMXA44 Communications Gateway ACPMXA42

  17. Forward Connectivity Simulation Main Goal - to demonstrate that: TTFS running on the client VPARS (ACPMXA43 with no connectivity) intercepts the input message coming from the user and sends it to TTFS The TTFS server (ACPMXA44) accepts the request message coming from the TTFS client (ACPMXA43) and sends it to the Communications Gateway The Communications Gateway receives the input request message, sends the request to the external trading partner, receives the response message from the trading partner and routes the response message back to the TTFS server (ACPMXA44) The TTFS Server (ACPMAX44) receives the response message from the Communications Gateway which in turn sends the response message to the TTFS Client completing the request. TTFS Client (No connectivity) TTFS Server - PKGE User Terminal T T F S T T F S Test Host of External Partners Communications Gateway ACPMXA44 ACPMXA43

  18. Reverse Host Connectivity Simulation Main Goal - to demonstrate that; TTFS running on the server (ACPMXA44) would intercept the reverse input message coming from the Communications Gateway and forwards it to TTFS running on the client VPARS (ACPMXA43) that has no connectivity TTFS running on the client VPARS (ACPMXA43) receives the message and delivers it to the application for processing and then intercepts the response and sends it back to the TTFS server (ACPMXA44) TTFS running on the server (ACPMXA44) accepts the response message from the client (ACPMXA43) and sends it to the Communications Gateway which responds to the external requestor TTFS Client (No connectivity) TTFS Server - PKGE User Terminal (Remote Partner) T T F S T T F S Test Host of External Partners Communications Gateway ACPMXA44 ACPMXA43

  19. Overall, the TTFS POC objectives were met Forward Connectivity Simulation Demonstrated Synchronous and Asynchronous transactions Including Schedule Displays Availability Interline Electronic Ticketing (IET) Requests Through Check-in Pricing were successfully executed. Reverse Connectivity Simulation Demonstrated Synchronous and Asynchronous transactions Originating from an external client that were successfully executed on the client VPARS as if it had a direct connection to the Communications Gateway Tool features were demonstrated and results considered successful TTFS Proof of Concept - Conclusions

  20. Over time, TTFS can become an intelligent switch to be used in resolving other TPF Test System connectivity issues SABRE approved TTFS product for TPF 4.1 and zTPF TPF Software to continue installation of the TTFS product in SABRE environment TTFS Proof of Concept - Conclusions

  21. Contact Information ThiruThirupuvanam TPF Software Inc. information@tpfsoftware.com (1) 919-676-5501 http://tpfsoftware.com Steve Hackler Sabre Holdings • Steve.Hackler@sabre.com • (1) 682-605-1716 http://sabre.com

More Related