Essentials for Java on z Systems

Size: px

Start display at page:

Download "Essentials for Java on z Systems"

Philippa Moore
5 years ago
Views:

1 Essentials for Java on z Systems The why, the how and the what of Liberty in CICS on zos Tobias Leicher CICS Specialist and zchampion for Modernization tobias.leicher@de.ibm.com

2 2

How to run Java on zos? What is this Liberty Server?

3 What will we discuss in this Session Why to run Java on zos at all if you already have Assembler, COBOL and PL/I? How to run Java on zos? What is this Liberty Server? What are typical usage scenarios? Are we missing something? 3

4 4

5 When will/have this happened?! 5

6 This is not going to come true, but look at what the mainframe did become! 6

7 Big Picture: Where to go with the Mainframe Development Today (sample scenario) Modernisation Possible Target Szenario How to implement? Efficient programming model New functions Standard interfaces New functions realised with Java Reduced maintenance costs Stepwise integration Cobol-Modules How to use services of other systems? Java-Modules Java Modul Target Architecture? Cobol-Modules Hard to maintance/change? DB2 DB2 System z Java Modul App Server System z 7 External Systems

8 Java is just another Language which is running on the Mainframe 8

IBM z13 Taking Java Performance to the Next Level Continued aggressive investment in Java on Z Significant new hardware features

0 GHz 8-Core Processor Chip 480MB L4 cache : Optimized for data serving Simultaneous Multi-Threading (SMT) 2x hardware threads/core

and string operations Cryptographic Function (CPACF) Improved performance of crypto co-processors New Instructions Packed Decimal

9 IBM z13 Taking Java Performance to the Next Level Continued aggressive investment in Java on Z Significant new hardware features tailored and co-designed with Java New 5.0 GHz 8-Core Processor Chip 480MB L4 cache : Optimized for data serving Simultaneous Multi-Threading (SMT) 2x hardware threads/core for improved throughput Available on ziips and IFLs Single Instruction Multiple Data (SIMD) Vector processing unit Accelerates loops and string operations Cryptographic Function (CPACF) Improved performance of crypto co-processors New Instructions Packed Decimal ódecimal Floating Point Load Immediate on Condition Load Logical and Zero Rightmost Byte Up to 50% improvement in throughput for generic applications Up to 2X improvement in throughput per core for security enabled applications 9

Java Road Map Language Updates Java 5.0 New Language features: Autoboxing Enumerated types Generics Metadata 5.0 Java 6.0 Performance Improvements Client WebServices Support EE 5 6.0 Java 7.

10 Java Road Map Language Updates Java 5.0 New Language features: Autoboxing Enumerated types Generics Metadata 5.0 Java 6.0 Performance Improvements Client WebServices Support EE Java 7.0 Support for dynamic languages Improve ease of use for SWING New IO APIs (NIO2) Java persistence API JMX 2.x and WS connection for JMX agents Language Changes EE 6.x 7.0 Java 8.0 Language improvements Closures for simplified fork/join IBM Java 8 (J9 R28) Improvements in Performance RAS Monitoring z13 Exploitation SIMD SMT Crypto acceleration SE8 >= 20 platforms WAS 6.0 IBM Java Runtimes IBM Java 5.0 (J9 R23) Improved performance Generational Garbage Collector Shared classes support New J9 Virtual Machine New Testarossa JIT technology First Failure Data Capture Full Speed Debug Hot Code Replace Common runtime technology ME, SE, EE SE platforms WAS 6.1 SE platforms WAS 7.0 IBM Java 6.0 (J9 R24) Improvements in Performance Serviceability tooling Class Sharing XML parser improvements z10 Exploitation DFP exploitation for BigDecimal Large Pages New ISA features SE601/ 7.x >= 20 platforms WAS 8.5 IBM Java 6.0.1/Java 7 (J9 R26) Improvements in Performance GC Technology z196 Exploitation OOO Pipeline 70+ New Instructions JZOS/Security Enhancements SE601/ 7.x >= 20 platforms IBM Java 7.1 (J9 R27) Improvements in Performance RAS Monitoring zec12 Exploitation zedc for zip acceleration SMC-R integration Transactional Execution Runtime instrumentation Hints/traps Data Access Accelerator IBM Java 7 (J9 R26 SR3) Improvements in Performance zec12 Exploitation Transactional Execution Flash 1Meg pageable LPs 2G large pages Hints/traps

11 A Glimps into the past Ressettable JVM CICS EJB & CORBA HPJ compiled bytecode 11 Java 1.4 Continuous JVM and class cache CICS TS V CICS TS V Reusable mode JVM Pool Java5 & shared class cache Java Channels/Containers CICS TS V new era Java bit JVM server Explorer SDK for Java OSGi bundles JVM server hosting Java 6 & AOT CICS TS V3.2 CICS TS V CICS TS V Liberty Web container Java 7 JDBC Performance EJB and JVM Pool removal CICS TS V CICS TS V CICS TS V CICS TS V

12 What's Liberty? 12

13 13

14 14

15 15

16 16

17 17

18 A LIGHTWEIGHT COMPOSABLE FAST 'Profile' of WebSphere Application Server 18

19 If this is twas......this is Liberty (WAS)...so is this...or even this! 19

20 What do we want to achieve with Java on System z and in CICS 1. Provide new APIs for Java applications deployed into CICS Enable porting of JEE applications to CICS from other application servers 2. Update CICS to provide same features and functions as WebSphere Liberty Profile Priority to API based functions Support QoS features and integrate with CICS as required Keep up to date with Liberty service stream 3. Continue to provide a robust JVM hosting environment for other components and services ODM, SAML PHP, Modern Batch, Mobile 20

21 What s in the CICS TS Liberty JVM server? Subset of the WAS for z/os Liberty profile Independently enabled extensions that exploit CICS facilities Liberty behaves exactly the same on all platforms out of the box Only configure the functions you use CICS TS V5.1 CICS TS V5.2 Web/servlet/RESTful technology JEE integration with CICS security Java transactions and CICS UOW integration Local and remote JDBC Java web services (JAXWS) z/os Connect integration (APAR PI25503) CICS TS V5.3 JEE6/7 Web profile JMS (WAS embedded messaging only) MongoDB JCA resource adapters, (and local ECI JCA support) LDAP security registry (and SAF integration) HTTP session persistence (also in V5.2) JMX monitoring (also in V5.2) Dynamic cache service JEE7 Full Profile in Standard mode

Liberty in CICS JVMProfile Explorer SDK Web

22 Liberty in CICS JVMProfile Explorer SDK Web App Export Wizard Deploy CICS Bundle EBA CICS install JVM server Liberty Web App EBA OSGi bundle Web.xml <security_constraint> DB2 VSAM Web Client HttpRequest HttpResponse URIMAP Tran ID COBOL security server.xml 22

23 Let s cross our fingers for a working Live Demo of how to start a Liberty in less then 5 Minutes 23

24 Benefits for CICS Provides off the shelf Web-server capabilities (JSPs and Servlets) Potential to re-use even more WebSphere technology in CICS. JSP and Web servlets have direct, local, access to CICS data and resources. Servlets can take advantage of existing CICS OSGi applications to provide a Dynamic Web front end. 24

25 Liberty is running! (check the logs). Server defaultserver created. Launching defaultserver (wlp /websphere-kernel_1.0.0) on IBM J9 VM, version pmz6470sr _01 (SR1) (en_us) [AUDIT ] CWWKE0001I: The server defaultserver has been launched. [AUDIT ] CWWKG0028A: Processing included configuration resource: file:/u/ivanh/iyk3zih1/liberty1/wlp/usr/servers/defaultserver/installedapps.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: file:/u/ivanh/iyk3zih1/liberty1/wlp/usr/servers/defaultserver/cicssecurity.xml [AUDIT ] CWWKZ0058I: Monitoring dropins for applications. [AUDIT ] CWWKF0011I: The server defaultserver is ready to run a smarter planet. 25

26 Typically - JCA ECI in WebSphere Liberty Profile <featuremanager>... <feature>jca-1.6</feature> </featuremanager> Web app WAS Liberty Profile JNDI <resourceadapter autostart="true" id="eciresourceadapter location="/usr/lpp/cicstg/deployable/cicseci.rar" /> <connectionfactory id="ecitest" jndiname="eis/eci"> <properties.eciresourceadapter /> </connectionfactory> Lookup CF Create Connection Create Interaction Create record Interaction.execute(record) ECI Resource Adapter CTG COMMAREA CICS Program 26

27 'Ported' - JCA ECI in CICS Liberty JVM server CICS region Liberty JVM server JNDI <featuremanager>... <feature>jca-1.6</feature> <feature>cicsts:jcalocaleci-1.0</feature> server.xml </featuremanager> <connectionfactory id= ecilocal" jndiname="eis/eci"> <properties.com.ibm.cics.wlp.jca.local.eci /> </connectionfactory> Web app Lookup CF Create Connection Create Interaction Create record Interaction.execute(record) Local ECI Resource Adapter COMMAREA COBOL Program JCA local ECI feature Channel / Container API is possible as well! 27

28 Test your Applications locally with the remote Development Feature <featuremanager>... <feature>usr:jcaremoteeci-1.0</feature> </featuremanager> WAS Liberty Profile local Developer JNDI Web app <connectionfactory id="defaultcicsconnectionfactory" jndiname="eis/eci"> <properties.com.ibm.cics.wlp.jca.remote.eci servername="tcp://hostname:port"/> </connectionfactory> Lookup CF Create Connection Create Interaction Create record Interaction.execute(record) Remote Development Feature COMMAREA CICS Program 28

29 Link to Liberty zos Developer Eclipse/ Build Engine zfs BundleJEEA_1.0.0 META-INF/cics.xml test.osgibundle TestJEE_1.0.0.ear CICS BUNDEFA [COBOL/PLI] EC LINK(ProgA) JVMServer - WLP BundleJEEA_1.0.0 TestJEE_1.0.0 How to enter a JEE App? 29

30 Link into Liberty Invoking a Java EE application from a CICS program Enable any CICS program to EXEC CICS LINK to a Java EE application in CICS Liberty o Liberty programs also supported as initial program for a transaction o START and START CHANNEL can be used Use cases: o Reuse existing Java code from a Liberty application o Write new Java business logic o Progressively replace COBOL with new Java implementation Current scope and limitations o Support link to POJO in a WAR or EAR Emphasis on targeting business logic not presentation logic Liberty application invoked on the same CICS task and within same UOW No support for invoking EJBs or OSGi applications Liberty application invoked with DPL subset and SYNCONRETURN ignored Using JTA with CICS integration turned on is not supported 30

31 How will a Developer experience this annotation to a Java method Recommend this method is in a CICS-specific wrapper class Requires CICS-supplied annotation processor to build o Provided in CICS Explorer and CICS build toolkit o Standalone annotation processor available for other dev and build environments Annotation processor validates contents and location of annotation o Annotation processing must be turned on per-project Generates code required by CICS to invoke the application 31 public class CustomerLinkTarget public void getcustomer() { Channel currentchannel = Task.getTask().getCurrentChannel(); Container datacontainer = currentchannel.getcontainer("data"); // do work here Container resultcontainer = currentchannel.createcontainer("result"); byte[] results = null; resultcontainer.put(results)); } }

32 This will also bring autoinstall for necessary Program Definitions When an application is installed in Liberty, CICS looks for code generated annotations Dynamically creates a PROGRAM for each annotated method o If a PROGRAM already exists, no PROGRAM is created. If the existing PROGRAM isn't suitable, a message will be issued Dynamically created programs are deleted when the application is removed Programs can be manually defined if desired, using the following syntax for the service name attribute: o wlp:classname[#methodname] Example: o wlp:com.ibm.cics.server.example.example#linkmethod Method name is optional and may be truncated to fit in maximum length of 255 characters 32

33 How to code the LINK in COBOL? EXEC CICS LINK(program) exactly as normal Current channel passed to Java application INPUTMSG and COMMAREA not supported New RESP2 values: o PGMIDERR 26 - A LINK has been attempted to an application in a Liberty JVM server, but the request has failed and target application was not invoked A LINK has been attempted to an application in a Liberty JVM server, but the request timed out and target application was not invoked. o INVREQ 53 - A LINK has been attempted to an application in a Liberty JVM server, but the LINK listener process was not available The COMMAREA option is specified, but it is invalid when linking to an application in a Liberty JVM server The INPUTMSG option is specified, but it is invalid when linking to an application in a Liberty JVM server. 33

34 How to configure and what about Security here? cicsts:link-1.0 feature required Security o Any access to CICS resources runs under the user ID of the CICS task o When cicsts:security-1.0 feature is also configured, the userid of the CICS task is propagated to the Java EE application o Recommend using SAF registry 34

35 Let s cross our fingers for a quick Link into Liberty in 5 Minutes 35

36 WebSphere Liberty Profile JEE7 36 Enterprise Technologies concurrent-1.0 (JSR 236) cdi-1.2 (JSR 346) beanvalidation-1.1 (JSR 349) ejb-3.2* (JSR 345) ejblite-3.2 (JSR 236) jca-1.7 (JSR 322) jpa-2.1 (JSR 338) jms-2.0 (JSR 343) jta-1.2 (JSR 907) javamail-1.5 (JSR 919) batch-1.0 (JSR 352) Interceptors 1.2 (JSR 318) Dependency Injection 1.0 (JSR 330) Common Annotations 1.2 (JSR 250) JEE 7 full platform javaee-7.0/javaeeclient-7.0 (JSR 342) Management and Security jaspic-1.1 (JSR 196) jacc-1.5 (JSR 115) j2eemanagement-1.1 (JSR 77) Java EE Specs in Java SE jdbc-4.1 (JSR 221) jndi-1.0 JMX 2.0 (JSR 255) JavaBeans Activation Framework - JAF 1.1 (JSR 925) Java API for XML Processing - JAXP 1.4 (JSR 206) Streaming API for XML - StAX 1.0 (JSR 173) * sub-features not shown jaxrs-2.0 (JSR 339) jaxws-2.2 (JSR 224) jaxb-2.2 (JSR 222) jsonp-1.0 (JSR 353) servlet-3.1 (JSR 340) jsf-2.2 (JSR 344) jsp-2.3 (JSR 245) el-3.0 (JSR 341) JEE 7 Web profile (webprofile-7.0) Web-services web-socket-1.0 (JSR 356) web-socket-1.1 (JSR 356) Enterprise Web services 1.4 (JSR 109) JWSDL (JSR 110) Web-services Interoperability (Basic Profile 1.2, 2.0) Web services metadata (JSR 181) SOAP attachments SAAJ (JSR 67) Web-Applications Debug support (JSR 45) JSTL 1.2 (JSR 52) Key: Liberty feature Implicit capability Spec. increase New JEE7 capability

0 (JSR 330) Common Annotations 1.1 (JSR 250) Management and Security Java EE Specs in Java SE jdbc-4.0 (JSR 221) jndi-1.0 JMX 2.0 (JSR 255) JavaBeans Activation Framework - JAF 1.

37 CICS Liberty Profile v5.3 - JEE6 (at announcement) Enterprise Technologies cdi-1.0 (JSR 299) beanvalidation-1.0 (JSR 303) ejblite-3.1 (JSR 318) jca-1.6 (JSR 322) jpa-2.0 (JSR 317) jms-1.1 (JSR 914) jta-1.1 (JSR 907) Interceptors 1.1 (JSR 318) * * Dependency Injection 1.0 (JSR 330) Common Annotations 1.1 (JSR 250) Management and Security Java EE Specs in Java SE jdbc-4.0 (JSR 221) jndi-1.0 JMX 2.0 (JSR 255) JavaBeans Activation Framework - JAF 1.1 (JSR 925) Java API for XML Processing - JAXP 1.4 (JSR 206) Streaming API for XML - StAX 1.0 (JSR 173) JEE 6 platform partial support (JSR 316) Web-services jaxrs-1.1 (JSR 311) jaxws-2.2 (JSR 224) jaxb-2.2 (JSR 222) servlet-3.0 (JSR 315) jsf-2.0 (JSR 314) jsp-2.2 (JSR 245) JEE 6 Web profile (webprofile-6.0) Enterprise Web services 1.4 (JSR 109) JWSDL (JSR 110) Web-services Interoperability (Basic Profile 1.2, 2.0) Web services metadata (JSR 181) SOAP attachments SAAJ (JSR 67) Web-Applications * Debug support (JSR 45) JSTL 1.2 (JSR 52) Key: Liberty feature Implicit capability * restrictions strike = not directly tested, but supported 37

38 Convergence Of features, fix packs and timing 38

Liberty Advanced Integration into CICS V5.

Java global transactions JNDI naming DB2

Interceptors Security Liberty Integrated

39 Liberty Advanced Integration into CICS V5.2 Things that required more effort JTA JDBC Java global transactions JNDI naming DB2 DataSource JEE Roles RACF keyrings LTPA single signon Form based security SSL client authentication Trust Association Interceptors Security Liberty Integrated and optimized for CICS Web workloads IBM Java SDK V7.1 or V8 39

Standard mode Liberty https://developer.

40 Standard mode Liberty 40

41 Standard mode Liberty Standard-mode provides a way for Java EE 7 full profile applications to be run in CICS, with all the benefits of running on z/os Threads used in Liberty are not integrated with CICS o No direct access to JCICS o No native CICS access to DB2 or MQ o Improved ziip eligibility JVM server lifecycle and CICS bundles are still supported In essence a fully functional Liberty environment managed by CICS 41

42 Comparison Capability integrated-mode standard-mode Supported feature set Java EE 7 Web Profile Java EE 6 Web Profile Java EE 7 Full Platform Java EE 7 Web Profile Java EE 6 Web Profile Java CICS API (JCICS) Yes Yes under runascics() API only Native driver for DB2 Yes Yes under runascics() API only Ease of app migration to CICS Liberty Moderate Easy Asynchronous operations and nested transactions Some restrictions Yes CICS bundle deployment of app? Yes Yes CICS Liberty autoconfigure available? Yes Yes JVM server creates and controls the Liberty server? Yes Yes ziip eligibility Up to 90% Up to 99% CP Integration overhead Minimal overhead CICS thread-pool optimisations Yes No 42

43 Standard mode Liberty II Configured by the JVM profile variable: o CICS_WLP_MODE=STANDARD Alternatively, the cicsts:standard-1.0 feature can be installed in place of the cicsts:core-1.0 feature. o These features are mutually exclusive: CWWKF0033E: The singleton features cicsts:core-1.0 and cicsts:com.ibm.cics.wlp.core-0.0 cannot be loaded at the same time. The configured features cicsts:core-1.0 and cicsts:standard-1.0 include one or more features that cause the conflict. Your configuration is not supported; update server.xml to remove incompatible features. JCICS can still be access in standard-mode Liberty, through the CICS executor service o CICSExecutorService.runAsCICS Limited context propagation from Liberty o SAF identities will be propagated onto the CICS task, if cicsts:security-1.0 is enabled o Classloaders and transaction contexts are not propagated to the CICS thread 43

44 Liberty Essentials Enhancements to RunAsCICS API 44

45 How to use a future object 45 public static void main(string[] args) { // Submit a new Callable to the CICSExecutorService, and receive a Future object Future<String> future = CICSExecutorService.runAsCICS(new TSQCallable("TEST", "HelloWorld")); // Wait for the test to complete (optional) while(!future.isdone()) { try { Thread.sleep(500); } catch (InterruptedException e){ e.printstacktrace(); } } // Print the return data from the Callable try { System.out.println("ExecutorTest: '" + future.get() + "' from the Callable"); } catch (InterruptedException ExecutionException e) { e.printstacktrace(); } } }

46 Enhancements to RunAsCICS API The RunAsCICS API has been enhanced to handle Callable types as well as Runnable types. Callable is a modern interface for running multithreaded work which can return data via, and be synchronized by, a Future object. Available for all modes of Liberty JVM servers and to OSGi JVM servers. CICSTransactionCallable interface allows the transaction ID to be modified for Callable types 46

47 CICS and Java - A successful Story continues DB2 Type 2 Connection - Performant DB2 access beyond JDBC The CICS TS V5.3 release added support for features which interact with data sources without using JDBC directly: o JPA o Session database These features were restricted to type 4 drivers Type 2 connections to DB2 are now supported for the jpa-2.0 and sessiondatabase- 1.0 features in integrated-mode 47

48 DB2 Type 2 Connection - Performant DB2 access beyond JDBC FF..FF FF..FF... DB2 IMS Batch... TCP IP... DB2 IMS Batch... TCP IP CICS zos Kernel CICS zos Kernel

49 CICS and Java - A successful Story continues IBM MQ Support - Easily connect to IBM MQ through JMS and CICS Liberty 49

50 CICS and Java - A successful Story continues IBM MQ Support - Easily connect to IBM MQ through JMS and CICS Liberty MQ base classes can be used in Liberty JVM servers JMS 2 can be used in both modes of Liberty JVM servers o Client mode is the only supported mode of transport for CICS integrated-mode Liberty o Client and bindings mode transport are both supported in CICS standard-mode Liberty Bindings mode must use a different queue manager to those specified in installed CICS MQCONNs. 50

51 Building a JEE application with Liberty Connectors Application Frameworks Data Access Web Blueprint EJB JPA JCA Restful JDBC Web Services Managed Beans CDI JMS MDB JMX JNDI Mongodb QoS SSL HTTP Session persistence OAuth Plugin LDAP 51

52 Why use Liberty in CICS? JVM Server DB2 Web Client RESTful Client Web services Client HTTP CICS region Liberty Web App Liberty JDBC JCICS JCICS VSAM COBOL Program 1. Porting web application to z/os JEE6 Web profile and JCA local ECI - lift and shift porting from other JEE servers 2. New integration logic for existing CICS services Restful services or SOAP Web services interfacing existing CICS components 3. Java business logic in CICS Access to DB2 data JDBC, EJBs, JPA or VSAM/JCICS 52

Adapter LINK COBOL Program DB2 EJB VSAM Usage of JCA enables porting

53 Liberty in CICS scenarios - 1 Porting Web applications to z/os CICS region HTTP Liberty JVM server Web Application local ECI JCA Resource Adapter LINK COBOL Program DB2 EJB VSAM Usage of JCA enables porting of applications that use CICS Transaction Gateway JCA ECI resource adapter 53

Liberty in CICS scenarios - 2 Integration with existing CICS

Web Services Liberty JVM server JAX-RS Application JCICS Link

service (JAXWS) applications can be easily built to provide

54 Liberty in CICS scenarios - 2 Integration with existing CICS services CICS region 3 rd Party Application HTTP RESTful or Web Services Liberty JVM server JAX-RS Application JCICS Link COBOL Business Logic Program DB2 VSAM RESTful (JAXRS) or Web service (JAXWS) applications can be easily built to provide new service interfaces to existing business process applications 54

Liberty in CICS scenarios - 3 Java business logic on z/os CICS region

Web client JTA JPA JCICS VSAM JEE offers ability to use wide variety of

business applications which integrate with existing CICS applications or

55 Liberty in CICS scenarios - 3 Java business logic on z/os CICS region HTTP Liberty JVM server Web Application EJB T2 database driver JDBC DB2 Web client JTA JPA JCICS VSAM JEE offers ability to use wide variety of frameworks including EJB, JTA, JDBC, JPA, ManagedBeans to create new business applications which integrate with existing CICS applications or relational databases. JCICS COBOL Program JDBC T4 database driver DB2 Multiplatform 55

56 The Goal Today (sample scenario) Modernisation Possible Target Szenario How to implement? Efficient programming model New functions Standard interfaces New functions realised with Java Reduced maintenance costs Stepwise integration Cobol-Modules How to use services of other systems? Java-Modules Java Modul Cobol-Modules Hard to maintance/change? DB2 Java Modul DB2 System z External Systems System z 56

57 Programming languages Trends and Future If (time=available) { //please give us your insights into which new languages excite you } 57

58 Questions? Tobias Leicher IT Specialist for CICS & zchampion for Modernization IBM Allee 1 D Ehningen Mobil: Mail: tobias.leicher@de.ibm.com Many Thanks for your Attention! 58

Architecting Java solutions for CICS

Architecting Java solutions for CICS Architecting Java solutions for CICS Course introduction Course introduction Reasons for hosting Java in CICS Requirements: Knowledge of transaction processing Experience