A Software Architect S Guide To New Java Workloads In Ibm Cics Transaction Server
Download A Software Architect S Guide To New Java Workloads In Ibm Cics Transaction Server PDF/ePub or read online books in Mobi eBooks. Click Download or Read Online button to get A Software Architect S Guide To New Java Workloads In Ibm Cics Transaction Server book now. This website allows unlimited access to, at the time of writing, more than 1.5 million titles, including hundreds of thousands of titles in various foreign languages.
A Software Architect's Guide to New Java Workloads in IBM CICS Transaction Server
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. --
A Software Architect's Guide to New Java Workloads in IBM CICS Transaction Server
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.
ARCHIVED: Pooled JVM in CICS Transaction Server V3
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