First & Best Step towards Modernization - IBM WAS & IBM TXSeries with CICS TG
KasturiMohan 270001WRDK Visits (3853)
For long, clients have been using TXSeries with WebSphere application server in an architectural pattern that has allowed them to build modern front end with Java EE and continue using COBOL apps for core transaction processing. This deployment pattern within itself was an evolution towards modernization of existing core transaction processing applications, where in clients took to such patterns to build modern front ends using WebSphere Application Server and invoke core applications in the backend through JCA with CICS Transaction Gateway.
Over the last few years, more and more new applications have been written in Java and deployed on Java EE application servers. As more business logic is written in Java, extending the business logic to re-use existing and time tested applications will create higher business value for clients at a much faster turn around than something like re-writing the whole application in Java in one shot.
TXSeries for Multiplatforms v9.1 and CICS Transaction Gateway v9.2 enable sharing of transactional context across Java EE programs deployed on Liberty and COBOL programs deployed on TXSeries. Unit of work is common across Java and COBOL thus allowing clients to extend business value that has been existing for a long time. See the below picture for a view.
TXSeries v9.1 provides bi-directional integration with Java EE servers like WebSphere Liberty over 2 – phase commit. Transactions can start in Java and span over COBOL code and come back to commit or rollback in Java, while the same is true from the COBOL side as well. The constructs are retained based on the skill needs. For instance, Java developer will call a COBOL program as if he is just calling another Java EE Liberty application, whereas a COBOL developer too continues to use constructs that are familiar. This reduces the need for rewrite of applications.
Net is, TXSeries v9.1 is best suited for your application modernization initiatives
Read this blog for Implementation details : http