Browse Prior Art Database

Binding of interface meta-data to the implementation

IP.com Disclosure Number: IPCOM000019953D
Original Publication Date: 2003-Oct-14
Included in the Prior Art Database: 2003-Oct-14
Document File: 2 page(s) / 40K

Publishing Venue

IBM

Abstract

The system disclosed uses a single runtime artefact to contain an existing implementation of a business service with an existing interface along with meta-data that can be used to adapt the interface for use over a different protocol.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Binding of interface meta-data to the implementation

Disclosed is a system comprising application development tools and application server runtime support that simplifies the reuse of existing business logic implementations in configurations that require their existing interface to be adapted to use over a different protocol.

    CICS* customers have billions of dollars of investment in business logic implemented in their application programs. CICS Transaction Server* is providing a feature enabling access to these assets via SOAP (Simple Object Access Protocol). Websphere* Studio Enterprise Developer provides tools to help generate the necessary interface mapping artefacts as part of application development. The tools enable the SOAP form of the request to be mapped to the existing CICS Commarea interface. The current form of solution is to generate an XML description of the interface structure from the COBOL source code and additional program objects that convert the XML to/from the COBOL form of the interface. The XML description
(.XSD) can be incorporated into WSDL describing the CICS service that can be used to generate the client-side artefacts in industry standard ways. The converter programs are compiled and deployed into the CICS server to be used at runtime by the SOAP for CICS processing pipeline.

    This approach is best suited to the case where the interface to the CICS asset is very stable and the interface generation procedure is a one-time task. There is currently no good solution that ties changes to the CICS asset to re-generating the mapping process via the tools. Also, the existing approach generates two addition program objects for every interface that is published - these must be managed in the same way as the original business logic program itself.

    The solution presented here to the two problems identified above is to enable data describing the interface to be generated as part of the build process for the original application program (so integrating with existing change management processes) and t...