6. z/TPF Automated Generation of zREST Artifacts from Swagger Document

1. TVPT, Citi, Amex, Delta,
2. Headline: Automated Generation of zREST Artifacts from Swagger Document
3. Lead Contact: mark.whitney@travelport.com
4. Date 2018-04-26
5. Description:
a. Multiple z/TPF Customers, Travelport, Amex, and Delta desire a Tooling implementation that will convert a consumer/producer REST Swagger Open API Document into its producer/consumer complement of z/TPF zREST Loadable Objects.
b. If presented with a Client Swagger Document the tooling would produce the following:
i. z/TPF zREST Producer Swagger Document
ii. Up to 4 Request /Reply Pairs of DFDL Schemas for the GET, POST, PUT, DELETE REST Operations that reflect the Swagger
iii. zREST Service Descriptor File.
iv. Given that zDFDL can only transform a structure to a similar structure and that many legacy z/TPF Data/Message Structures are quite different from today's API Service Interface Objects, there is a need to construct software that copies data from one structure to a dissimilar structure. That is a z/TPF Structure to Structure Mapping (S2SMap) Program
v. Ideally the S2SMap Program would be produced in full or part by Graphical Tooling that would perform the following:
1. The developer would present the Graphical Tool with a dissimilar z/TPF Data/Message Structure such as an Assembler DSECT, C Header, or Java Object
2. Using the tool the developer would graphically link fields/element from within the zREST JSON/XML Structure to those in the developer provided dissimilar structure.
3. The tool would then construct a z/TPF Structure to Structure Mapping (S2SMap) Program either in whole or in part in either in C++ or Java.
4. If the S2SMap Program is incomplete the developer would then be able to complete construction.
c. All of the constructed zDFDL objects, REST Service Descriptor File, S2SPrograms, and Swagger File would be bundled for load in a z/TPF Loadset.