This IBM® Redpaper Redbooks® publication introduces the IBM System z® New Application License Charges (zNALC) pricing structure and provides examples of zNALC workload scenarios. It describes the products that can be run on a zNALC logical partition (LPAR), reasons to consider such an implementation, and covers the following topics: Using the IBM WebSphere Application Server Liberty profile to host applications within an IBM CICS® environment and how it interacts with CICS applications and resources Security technologies available to applications that are hosted within a WebSphere Application Server Liberty profile in CICS How to implement modern presentation in CICS with a CICS Liberty Java virtual machine (JVM) server How to share scenarios to develop Liberty JVM applications to gain benefits from IBM CICS Transaction Server for IBM z/OS® Value Unit Edition Considerations when using mobile devices to interact with CICS applications and explains specific CICS technologies for connecting mobile devices by using the z/OS Value Unit Edition How IBM Operational Decision Manager for z/OS runs in the transaction server to provide decision management services for CICS COBOL and PL/I applications Installing the CICS Transaction Server for z/OS (CICS TS) Feature Pack for Modern Batch to enable the IBM WebSphere® batch environment to schedule and manage batch applications in CICS This book also covers what is commonly referred to as plain old Java objects (POJOs). The Java virtual machine (JVM) server is a full-fledged JVM that includes support for Open Service Gateway initiative (OSGi) bundles. It can be used to host open source Java frameworks and does just about anything you want to do with Java on the mainframe. POJO applications can also qualify for deployment using the Value Unit Edition. Read about how to configure and deploy them in this companion Redbooks publication: IBM CICS and the JVM server: Developing and Deploying Java Applications, SG24-8038 Examples of POJOs are terminal-initiated transactions, CICS web support, web services, requests received via IP CICS sockets, and messages coming in via IBM WebSphere MQ messaging software.

This book introduces the IBM System z New Application License Charges (zNALC) pricing structure and provides examples of zNALC workload scenarios. It describes the products that can be run on a zNALC logical partition (LPAR) and reasons to consider such an implementation. It also covers what is commonly referred to as plain old Java objects (POJOs). The Java virtual machine (JVM) server is a full-fledged JVM that includes support for Open Service Gateway initiative (OSGi) bundles. It can be used to host open source Java frameworks and does just about anything you want to do with Java on the mainframe. POJO applications can also qualify for deployment using the Value Unit Edition. --

IBM® CICS® Transaction Server (CICS TS) has been available in various guises for over 40 years, and continues to be one of the most widely used pieces of commercial software. This IBM Redbooks® publication helps application architects discover the value of CICS Transaction Server to their business. This book can help architects understand the value and capabilities of CICS Transaction Server and the CICS tools portfolio. The book also provides detailed guidance on the leading practices for designing and integrating CICS applications within an enterprise, and the patterns and techniques you can use to create CICS systems that provide the qualities of service that your business requires.

This IBM® Redbooks® publication provides information about how you can connect mobile devices to IBM Customer Information Control System (CICS®) Transaction Server (CICS TS), using existing enterprise services already hosted on CICS, or to develop new services supporting new lines of business. This book describes the steps to develop, configure, and deploy a mobile application that connects either directly to CICS TS, or to CICS via IBM Worklight® Server. It also describes the advantages that your organization can realize by using Worklight Server with CICS. In addition, this Redbooks publication provides a broad understanding of the new CICS architecture that enables you to make new and existing mainframe applications available as web services using JavaScript Object Notation (JSON), and provides support for the transformation between JSON and application data. While doing so, we provide information about each resource definition, and its role when CICS handles or makes a request. We also describe how to move your CICS applications, and business, into the mobile space, and how to prepare your CICS environment for the following scenarios: Taking an existing CICS application and exposing it as a JSON web service Creating a new CICS application, based on a JSON schema Using CICS as a JSON client This Redbooks publication provides information about the installation and configuration steps for both Worklight Studio and Worklight Server. Worklight Studio is the Eclipse interface that a developer uses to implement a Worklight native or hybrid mobile application, and can be installed into an Eclipse instance. Worklight Server is where components developed for the server side (written in Worklight Studio), such as adapters and custom server-side authentication logic, run. CICS applications and their associated data constitute some of the most valuable assets owned by an enterprise. Therefore, the protection of these assets is an essential part of any CICS mobile project. This Redbooks publication, after a review of the main mobile security challenges, outlines the options for securing CICS JSON web services, and reviews how products, such as Worklight and IBM DataPower®, can help. It then shows examples of security configurations in CICS and Worklight.

NOTE: This book contains information about technologies that have been superseded and it is retained for historical purposes only. IBM CICS Transaction Server (CICS TS) has supported the deployment of Java applications since the 1990's. In CICS TS V1.3 (1999), IBM introduced the 'Pooled JVM' style of JVM infrastructure within CICS TS. This infrastructure was designed to be similar in nature to that which a CICS application developer for a language such as COBOL would be used to. It brought the benefits of the new Java language to CICS TS, without a dramatic change to the way CICS users thought of core concepts such as re-entrancy and isolation. As enterprise usage of Java evolved it began to make more and more use of multi-threaded environments where isolation was not a desired characteristic. Additionally, technologies such as OSGi (Open Service Gateway Initiative) evolved to overcome some of the original disadvantages of applying Java to an enterprise environment. As such, the limitations of the 'Pooled JVM' approach began to outweigh the benefits. In CICS TS V4.1 (2009), IBM introduced the new 'JVM server' infrastructure in CICS TS as a replacement to the 'Pooled JVM' approach. This 'JVM server' infrastructure provides a much more standard Java environment that makes the writing and porting of Java applications for CICS TS much simpler. In CICS TS V5.1 (2012), support for the old 'Pooled JVM' infrastructure was removed. While there is a relatively simple migration path from 'Pooled JVM' to 'JVM server', applications should no longer be written to the 'Pooled JVM' infrastructure. There are a number of more recent IBM Redbooks publications covering the replacement 'JVM server' technology, including: IBM CICS and the JVM server: Developing and Deploying Java Applications, SG24-8038 A Software Architect's guide to New Java Workloads in IBM CICS Transaction Server, SG24-8225

This IBM® Redbooks® publication provides information about the new Java virtual machine (JVM) server technology in IBM CICS® Transaction Server for z/OS® V4.2. We begin by outlining the many advantages of its multi-threaded operation over the pooled JVM function of earlier releases. The Open Services Gateway initiative (OSGi) is described and we highlight the benefits OSGi brings to both development and deployment. Details are then provided about how to configure and use the new JVM server environment. Examples are included of the deployment process, which takes a Java application from the workstation Eclipse integrated development environment (IDE) with the IBM CICS Explorer® software development kit (SDK) plug-in, through the various stages up to execution in a stand-alone CICS region and an IBM CICSPlex® environment. The book continues with a comparison between traditional CICS programming, and CICS programming from Java. As a result, the main functional areas of the Java class library for CICS (JCICS) application programming interface (API) are extensively reviewed. Further chapters are provided to demonstrate interaction with structured data such as copybooks, and how to access relational databases by using Java Database Connectivity (JDBC) and Structured Query Language for Java (SQLJ). Finally, we devote a chapter to the migration of applications from the pooled JVM model to the new JVM server run time.

Mainframe computers play a central role in the daily operations of many of the world's largest corporations. Batch processing is still a fundamental, mission-critical component of the workloads that run on the mainframe. A large portion of the workload on IBM® z/OS® systems is processed in batch mode. This IBM Redbooks® publication is the first volume in a series of four in which we specifically address new technologies introduced by IBM to facilitate the use of hybrid batch applications that combine the best aspects of Java and procedural programming languages such as COBOL. This volume specifically focuses on the latest support in CICS to run batch tasks. The audience for this book includes IT architects and application developers, with a focus on batch processing on the z/OS platform in a CICS environment.