Java Workloads in CICS Transaction Server
This IBM® Redbooks® publication introduces the System z® New Application License Charge (zNALC) pricing structure and examples of zNALC workload scenarios which is the focus of this book. This book describes the products that can be run on a zNALC LPAR and reasons why one would consider such an implementation.
This book provides:
- an introduction to the WebSphere Application Server Liberty Profile, its ability to host applications within a IBM CICS® environment, and how it will interact with CICS applications and resources. In addition, it describes the security technologies that are available to applications that are hosted within a WebSphere Application Server Liberty Profile in CICS.
- describes how to implement the modernization of presentation in CICS with CICS Liberty JVM server and share scenarios to develop CICS Liberty JVM server applications to gain the benefit from IBM CICS Transaction Server for z/OS® Value Unit Edition. Java on System z has received significant and on-going investment from IBM, building the Java Virtual Machine (JVM) from the ground up, developing hardware that can be exploited by the JVM, and building core middleware technology using Java, making Java on the mainframe one of the world’s most optimized Java environments.
- discusses some general considerations when using mobile devices to interact with CICS applications and explains specific CICS technologies for connecting mobile devices using IBM CICS Transaction Server for z/OS Value Unit Edition.
- introduces the concept of decision management and describes how IBM Operational Decision Manager for z/OS can run inside CICS Transaction Server for z/OS to provide decision management for CICS COBOL and PL/I applications.
- discusses the CICS Transaction Server for z/OS (CICS TS) Feature Pack for Modern Batch. This capability can be installed into CICS TS V4.2 or higher and enables the WebSphere® Batch Environment to schedule and manage batch applications in CICS.
In addition to the items described above, do not forget what is commonly referred to as Plain old Java objects (PoJo). The JVM server is a fully fledged JVM that includes support for OSGi bundles, can be used to host Open Source Java frameworks, and do just about anything you want to do with Java on the mainframe. Net new PoJo applications can also qualify for deployment using CICS TS VUE. Read about how to configure and deploy them in the companion IBM® Redbooks® publication, IBM CICS and the JVM server: Developing and Deploying Java Applications, available here: https://www.redbooks.ibm.com/redbooks.nsf/RedpieceAbstracts/sg248038.html?Open
Examples of PoJo objects are terminal initiated transactions, CICS Web Support, Web Services, requests received via IP CICS Sockets and messages coming in via WebSphere MQ Series.
Table of contents
Part 1 – Considering new workloads on the mainframe
Chapter 1: Mainframe workload pricing – overview
Part 2 - Liberty and CICS
Chapter 2: Overview of WebSphere Application Server Liberty Profile in CICS
Chapter 3: Modernization of presentation
Chapter 4: Consolidating applications in CICS Liberty
Part 3 - Mobile
Chapter 5: Overview of connecting mobile devices to CICS
Chapter 6: Mobile devices and CICS Liberty
Chapter 7: Mobile devices and CICS Java
Part 4 - IBM Operational Decision Manager
Chapter 8: Understanding Decision Management in CICS
Chapter 9: Implementing Decision Management in CICS
Part 5 - Modern Batch
Chapter 10: Modern Batch
Chapter 11: Modern Batch Scenario
These pages are Web versions of IBM Redbooks- and Redpapers-in-progress. They are published here for those who need the information now and may contain spelling, layout and grammatical errors.
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. Your feedback is welcomed to improve the usefulness of the material to others.
IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a customer responsibility and depends upon the customer's ability to evaluate and integrate them into the customer's operational environment.