HATS applications support most of the versions of IBM WebSphere Application Server Liberty (WAS Liberty) starting from liberty 16 to liberty 19.
Each of these server versions in turn support different versions of server features, which are configurable based on the needs of the deploying application.
HATS web service support can be used to create Service-Oriented Architecture (SOA) assets, that provide a standard programming interface to business logic and transactions that are controlled within Mainframe applications. These core business tasks can be reused as standard Web services that are an integral part of a business process integration plan.
As a developer using IBM Host Access Transformation Services (HATS), you can add macros into the HATS application which helps performing repetitive tasks faster and more efficiently. Macros are also the basis for creating RESTful services in HATS.
IBM Host Access Transformation Services (HATS) allows you to reuse and transform your user experience, by extending terminal applications to the web, mobile, portal, rich client, or as standard SOAP or RESTful web services without touching the existing application.
What is Swagger
Swagger is an open specification for defining REST APIs.
A Swagger document is the REST API equivalent of a WSDL document for a SOAP-based web service. The Swagger document specifies the list of resources that are available in the REST API and the operations that can be called on those resources. The Swagger document also specifies the list of parameters to an operation, including the name and type of the parameters, whether the parameters are required or optional, and information about acceptable values for those parameters. Additionally, the Swagger document can include JSON Schema that describes the structure of the request body that is sent to an operation in a REST API, and the JSON schema describes the structure of any response bodies that are returned from an operation.
Legacy applications contain the time-tested business knowledge, distilled over a long period of time. How best to evolve or reuse these legacy IT Assets, under changing business, economic and IT environments, is a challenge that every mainframe enterprise has to address. Many have tried solving the aging legacy applications by rewriting it in new technology, most have failed to eliminate the legacy. Not because of the technical feasibility of such rewrite, but due to the time, effort and risk associated with these approaches.