Most legacy mainframe applications provide access through terminal screens whereas others can only be reached through other applications like CRM, ERP or SCM.
SOA best practice goes to decoupling, i.e. separating screen display (UI) and business logic. Application development and testing are easier and quicker as front and back end updates are independently conducted, subject you can browse your legacy application’s code and rules.
Data Mapper provides direct connection to the non-visual, non screen-based mainframe Service-Oriented Applications (SOA) and business logic.
Thanks to a smart mapping of rules written in COBOL, developers bypass the legacy code review to retrieve the required data and combine it in new Java web applications.
Data Mapper is part of our Enterprise Studio development workshop.
It allows the production of stand-alone and standard Java components from the COBOL description in the Commarea CICS (via the CTG) or the MID / MOD IMS (via IMS Connect) corresponding to a serviced application.
With Data Mapper, you can:
🔹 import / adapt COBOL records
🔹develop / adapt services
🔹 test the services via CTG (or IMS Connect)
🔹 generate Beans Services / Records Beans In-Out
Mainframe SOAs are strictly transaction-based, meaning they:
🔹accept input for an atomic process
🔹apply the process to the data
🔹send back the results to the connected application
Emulating this transaction processes, Data Mapper generates:
🔹Data Components that manage data exchange with the SOA
🔹Service Objects: made up of Data Components, they act as transactions in the SOA. You can then deploy these Service Objects as Web Services in the target environment, where they connect to the SOA and perform transactions.