What you need to know about CICS, Java and Liberty. Mark Cocker Senior Software Engineer, Java Hill Lead, IBM CICS Development

Size: px

Start display at page:

Download "What you need to know about CICS, Java and Liberty. Mark Cocker Senior Software Engineer, Java Hill Lead, IBM CICS Development"

Rosamund Stone
6 years ago
Views:

1 What you need to know about CICS, Java and Liberty Mark Cocker Senior Software Engineer, Java Hill Lead, IBM CICS Development

2 Agenda What is Liberty? CICS Liberty Profile Why run Liberty in CICS? How to run CICS Liberty CICS Liberty Features 4

3 Agenda What is Liberty? CICS Liberty Profile Why run Liberty in CICS? How to run CICS Liberty CICS Liberty Features 5

4 Liberty is... A composable, lightweight, fast, profile' of WebSphere Application Server 6

5 Developers first - composable Composability is based on features Liberty profile server config is a simple xml file, server.xml: <server description= Test server ALISON1 > <featuremanager> <feature>servlet-3.0</feature> </featuremanager> <! Remote client access --> <httpendpoint host= * httpport= 4055 id= defaulthttpendpoint /> <application id= BasicTests location= BasicServlet.war name= BasicTests type= war /> </server> 7

6 Lightweight Configuration Features Featurescontrol controlwhat s what s available availableininthe theruntime. runtime. Instance Instanceconfigurations configurationsallow allowmultiple multiple instances of resources and instances of resources and applications applicationstotobebedeclared declared Includes Includescan canbebeused usedtotoimplement implement ananextensible configuration extensible configurationmodel model References Referencescan canbebeused usedininmultiple multiple elements elementstotopoint pointtotoand andshare sharea a common definition common definition 8

7 Java EE Support Developers first but not just for development Liberty is enterprise ready - supports Java EE, built to run large-scale, multi-tiered, scalable, reliable, and secure network applications Supports Java EE 7 Full Platform Java EE 6 Web Profile 9

8 Agenda What is Liberty? CICS Liberty Profile Why run Liberty in CICS? How to run CICS Liberty CICS Liberty Features 10

9 What is the CICS TS Liberty Profile Subset of the WAS for z/os v8.5.5 Liberty profile Independently enabled extensions (features) to exploit CICS facilities RESTful Client DB2 JVM Server Web Client Liberty HTTP Web App Liberty Web services Client JDBC JCICS VSAM JCICS COBOL Program CICS region 11

10 Agenda What is Liberty? CICS Liberty Profile Why run Liberty in CICS? How to run CICS Liberty CICS Liberty Features 12

11 Non-Liberty CICS JVM servers CICS and Java isn t all about Liberty Non-Liberty JVM servers can be used to: Run threadsafe Java applications in an OSGi framework For standard Java SE then this is a more lightweight approach which offers more flexibility and control over OSGi bundle deployment and versioning Process web service requests in the Axis2 web services engine For Web or Java EE APIs and EJBs use Liberty 13

12 Why run Liberty in CICS? Liberty running in a JVM Server within CICS has the same benefits of any other Java app running inside CICS such as Access to CICS resources OSGi etc Some common use cases and scenarios follow 14

13 15

14 Update remote data sources in same logical UOW as other CICS TS managed resources CICS region Liberty JVM server TP T H Web Application JTA DB2 EJB JCICS JPA JAX-RS Web client river d 2 T JDBC JCICS Link COBOL program VSAM JDB C T4 driv er z/os or distributed platform DB 16

15 LINK to Liberty application CICS region Liberty JVM server TP HT Web Application JTA DB2 EJB JCICS JPA JAX-RS EXEC CICS LINK Web server river d 2 T JDBC COBOL program VSAM JDB C T4 driv er z/os or distributed platform DB 17

16 LINK to Liberty application 18

17 21

Access existing CICS programs / data CICS region RESTful RESTful(JAX-RS) (JAX-RS)ororWeb Webservice service (JAX-WS) (JAX-WS)applications applicationscan canbe beeasily easily built builttotoprovide

18 Access existing CICS programs / data CICS region RESTful RESTful(JAX-RS) (JAX-RS)ororWeb Webservice service (JAX-WS) (JAX-WS)applications applicationscan canbe beeasily easily built builttotoprovide providenew newservice serviceinterfaces interfaces totoexisting existingbusiness businessprocess process applications applications Liberty JVM server 3rd Party Application HTTP JAX-RS Application JCICS VSAM JCICS Link Existing COBOL program DB2 22

19 23

20 Porting web applications to z/os External server CICS region Java EE server HTTP DB2 JCA Web Application ECI CICS Transaction Gateway EJB COBOL Program VSAM Java JavaEE EEapplications applicationscan canbe be migrated migratedfrom fromother otherjava JavaEE EE servers serversinto intocics CICS Java JavaEE EE66web webprofile profilesubset subsetisis supported supportedinincics CICSTS TSV5.3 V5.3 24

21 Porting web applications to z/os CICS region Liberty JVM server HTTP JCA Web Application DB2 LINK COBOL Program EJB CICS CICSTS TSV5.3 V5.3now now provides providesthe the cicsts:jcalocaleci-1.0 cicsts:jcalocaleci-1.0 feature feature VSAM Usage UsageofofJCA JCAenables enables porting portingofofapplications applicationsthat that use usecics CICSTransaction Transaction Gateway GatewayJCA JCAECI ECIresource resource adapter adapter 25

22 CICS remote development feature for Java Workstation CICS region Dev. Liberty server HTTP JCA Web Application EJB DB2 TCP/IP COBOL Program VSAM CICS remote development feature for Java Eclipse Released 18th April 2016 No requirement for CICS TG Development use only 26

23 Agenda What is Liberty? CICS Liberty Profile Why run Liberty in CICS? How to run CICS Liberty CICS Liberty Features 27

24 Running Liberty in CICS Start a Liberty JVM server in 4 easy steps 1. Prepare your CICS region by adding SDFJAUTH to STEPLIB and setting USSHOME 2. Prepare zfs for the required config files and log files 3. Create the JVM server Define a JVMSERVER resource Define and configure it s JVM profile properties in JVMPROFILEDIR to autoconfigure Liberty server WORK_DIR the working directory for Liberty WLP_INSTALL_DIR where Liberty is installed (usually &USSHOME;/wlp) -Dfile.encoding=ISO (Liberty runs in ASCII) -Dcom.ibm.cics.jvmserver.wlp.autoconfigure=true -Dcom.ibm.cics.jvmserver.wlp.server.name=ALISON1 -Dcom.ibm.cics.jvmserver.wlp.server.http.port=4055 -Dcom.ibm.cics.jvmserver.wlp.server.https.port=4056 This is the minimum config leaving much to default, you can configure paths for the config files etc 4. Install and start your JVM server 28

25 Starting up Liberty 29

26 Did it work CICS s view If all has gone well MSGUSR should show: DFHSJ0207 JVMSERVER ALISON1 is running Java version DFHSJ0919 JVMSERVER ALISON1 is processing any queued bundles. DFHSJ0915 JVMSERVER ALISON1 is now enabled and is ready for use. 30

27 Did it work Liberty s view By default Liberty s log written to WORK_DIR/IYK3ZAB4/ALISON1/wlp/usr/servers/ALISON1/logs/message.log CWWKE0001I: The CWWKO0219I: TCP for requests on CWWKF0011I: The server ALISON1 has been launched Channel defaulthttpendpoint has been started and is now listening host * (IPv6) port server ALISON1 is ready to run a smarter planet. SRVE0169I: Loading Web Module: com.ibm.cics.wlp.defaultapp. SRVE0250I: Web Module com.ibm.cics.wlp.defaultapp has been bound to default_host. CWWKT0016I: Web application available (default_host): SRVE0242I: [com.ibm.cics.wlp.defaultapp] [/com.ibm.cics.wlp.defaultapp] [com.ibm.cics.wlp.defaultapp.defaultservlet]: Initialization successful. 31

28 Did it work - Trying it out CICS supplies a default application Enabled by default if using autoconfigure Accessed by: Reports on runtime configuration Provides access to log files 32

29 Deploying your own app - Development environment Eclipse IDE for Java EE Developers V4.4 available from eclipse.org CICS Explorer V5.3 SDK (or as applicable) available from IBM.com Ensure you install the CICS Explorer SDK for Servlet and JSP support feature too Includes required features of WebSphere Development Toolkit (WDT) CICS Explorer V5.3 SDK CICS Explorer V5.3 SDK for Servlet and JSP support (includes Liberty libraries) Eclipse V4.4 (Luna) 33

30 Java EE Packaging Options Web App WAR Web Archive Non-OSGi applications EAR EBA Web App Web App EJB App OSGi bundle Enterprise Archive Enterprise Bundle Archive OSGi applications 34

31 Deployment Options CICS JVM server CICS Bundle Liberty install App App App Application definition Dropins directory App Bundle repository App 38

32 Packaging and Deployment WAR EAR EBA CICS bundle Liberty drop-ins Liberty application Liberty bundle repository 39

33 Shared repositories Shared bundle repository available to all OSGi bundles (i.e. bundles deployed in EBAs) <fileset dir="/mqm/v7r1m0/java/lib/osgi" id="mqosgilib" includes="com.ibm.mq.osgi.java_ jar" /> <bundlerepository filesetref="mqosgilib" /> Global library available only to standalone Web applications (WARs/EARs) <fileset dir="/mqm/v7r1m0/java/lib" id="mqlib" includes="*.jar" /> <library filesetref="mqlib" id="global" /> 40

Deploying your own app - CICS bundles 1. Using the CICS Explorer SDK create a new CICS Bundle project 2.Add the EAR/WAR/EBA and any CICS resources to be installed with the bundle e.g. URIMAPs, transactions etc 3.

34 Deploying your own app - CICS bundles 1. Using the CICS Explorer SDK create a new CICS Bundle project 2.Add the EAR/WAR/EBA and any CICS resources to be installed with the bundle e.g. URIMAPs, transactions etc 3.Export to zfs (or build toolkit) 4.Define and install a CICS BUNDLE resource with BUNDLEDIR attribute referring to the above CICS Bundle disable/enable will recycle application 41

35 Deploying your own app CICS build toolkit Built bundle project directory Source code system Checkout cics build toolkit Built artifacts Installed bundles zfs DFHDPLY CICS region(s) CSD 42

36 Deploying an application 43

37 Manually deploying your own app To manually deploy web applications you can: Dropping the application into a previously defined "dropins" directory Not defined by CICS auto-configure Placing the application into another location (not dropins) and manually defining it in the server.xml CICS not aware of the application Always run under transaction CJSA Don t benefit from additional qualities of service such as security 44

38 Agenda What is Liberty? CICS Liberty Profile Why run Liberty in CICS? How to run CICS Liberty CICS Liberty Features 45

39 What s in the CICS TS Liberty JVM server? CICS TS V5.1 Web/servlet/RESTful technology CICS TS V5.2 JEE integration with CICS security 5.2 Java transactions and CICS UOW integration Local and remote JDBC Java web services (JAX-WS) z/os Connect integration (APAR PI25503) CICS TS V5.3 Java EE 7 Web profile (APAR PI63877) 5.3 New New September September JMS WAS embedded messaging MongoDB JCA resource adapters, (and local ECI JCA support) LDAP security registry (and SAF integration) Standard-mode Standard-mode HTTP session persistence (also in V5.2) Liberty Liberty JMX monitoring (also in V5.2) (July (July2016) 2016) Java EE 7 Full profile (APAR PI58375) LINK to Liberty application (APAR PI63005) 5.3 CD Coming Comingsoon! soon! 46

CICS TS V5.3 Statements of Direction IBM intends to deliver support in CICS TS for Java applications that exploit Java EE 7 Full Platform features in integrated mode.

40 CICS TS V5.3 Statements of Direction IBM intends to deliver support in CICS TS for Java applications that exploit Java EE 7 Full Platform features in integrated mode. IBM intends to deliver support in CICS TS for IBM Cloud Provisioning and Management for z/os. This support will enable developers to provision services from a software catalog in a way that is consistent with the CICS provisioning toolkit technology delivered in the CICS TS V5.4 open beta offering. IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. 47

41 CICS TS V5.3 - New Liberty Features Supported Name Description Feature Java Persistence Architecture Java persistence architecture (limited to T4 d/b drivers) jpa-2.0 Enterprise JavaBeans Lite Support EJBs written to the EJB Lite subset of the EJB 3.1 specification ejblite-3.1 Java Management Extensions (JMX) Provides the ability to manage and monitor applications and system objects, either using the JMX client API, or remotely using the JConsole utility supplied with the SDK, as described here. monitor-1.0 * restconnector-1.0 * localconnector-1.0 * Database session persistence Provides high availability and recovery when using HTTP session data in web applications. This support is only for data sources that use a JDBC type 4 driver, due to a restriction preventing usage of a local database and the CICS DB2 attachment. session-database-1.0 * MongoDB Supports the use of a MongoDB Java Driver configured providing applications with the ability to interact with the popular no-sql database on a remote system mongodb-2.0 * Managed Beans and Contexts and Dependency Injection (CDI) Makes it easier to integrate different types of Java Enterprise Edition (EE) components cdi-1.0 & managedbeans-1.0* OSGi Console Helps with run time debugging of applications that use the OSGi framework osgiconsole-1.0 * JMS JMS messaging to local or remote WLP embedded messaging engine (not including MQ for z/os) jms-1.1, wasjmsclient-1.1, wasjmsserver-1.1, wasjmssecurity-1.0 JCA J2EE Connector Architecture resource adapters jca-1.6 LDAP LDAP security registry and support for mapping distributed identities to RACF userids ldapregistry

42 CICS TS V5.3 - New Liberty Features Supported Name Description Feature Java Batch 1.0 Enables support for the Java Batch 1.0 API specified by JSR-352. This feature does not support Java batch applications packaged in an Enterprise Bundle Archive (EBA). batch-1.0 Batch Management 1.0 Provides managed batch support for the Java batch container. This includes the Batch REST management interface, job logging support, and a command line utility for external scheduler integration batchmanagement-1.0 JavaMail 1.5 Enables applications to utilize the JavaMail 1.5 API javamail CD 50

43 CICS TS V5.3 CICS provided features Features Description cicsts:core-1.0 Core integration feature providing access to JCICS and JTA APIs cicsts:defaultapp-1.0 Alternative method to configure the default application. The default application verifies that the Liberty server is running and provides configuration details cicsts:jdbc-1.0 Provides support for applications to access a local CICS DB2 database using JDBC cicsts:jcalocaleci-1.0 Provides a locally optimized JCA ECI resource adapter for calling CICS programs cicsts:link-1.0 Provides support for running a Liberty application from an EXEC CICS LINK command in any CICS application program cicsts:security-1.0 CICS integration with SAF security cicsts:distributedidentity-1.0 Enabling LDAP security registry and distributed identity support cicsts:zosconnect-1.0 cicsts:zosconnect-2.0 Support for z/os Connect within CICS cicsts:standard-1.0 Enables you to port and deploy Liberty applications from other platforms to CICS without changing your application. Standard mode is ideal for hosting applications that are written for and rely on the Java Enterprise Edition (Java EE) Full Platform, but do not require full integration with CICS 51

Choosing between T2 and T4 www.redbooks.

44 Choosing between T2 and T4 59

45 cicsts:jcalocaleci

46 Interacting with CICS resources from Liberty - JCICS JCICS can be used to interact with CICS resources from CICS Liberty applications You can write Java applications that use the CICS Java class library (JCICS) to access CICS services JCICS is the Java equivalent of the EXEC CICS API e.g. EXEC CICS LINK Using JCICS stops your applications from being portable between CICS and other JEE application server environments 61

47 What is JCA? What is the JEE Connector Architecture (JCA)? JCA is a Java-based technology solution for connecting enterprise information systems (EIS) such as CICS to the JEE platform Like JDBC is specifically used to connect Java EE applications to databases, JCA is a more generic architecture for connection to EIS CICS Transaction Gateway (CTG) provides a set of JCA resource adapters to support the use of the JCA for connecting to CICS TS CICS TS V5.3 supports the Liberty JCA feature jca-1.6 Using this, to connect into a CICS program you need to go out of using JCA, then back in via CTG 5.3 Liberty CICS 62

48 With Liberty s JCA feature 63

49 Interacting with CICS resources from Liberty - JCA CICS now provides its own JCA Local ECI feature cicsts:jcalocaleci-1.0 feature 5.3 This is an optimized JCA adapter supporting CTG s JCA ECI interfaces Can be used to connect to CICS programs, passing data in either COMMAREAs or channels and containers in a non-proprietary manner 64

50 With CICS JCA Local ECI resource adapter 65

51 Interacting with CICS resources from Liberty - JCA JCA Local ECI feature Allows you to write new applications for CICS Liberty that link to CICS programs that can be ported to any JEE compliant application server Allows you to port existing JCA applications that use the JCA ECI interfaces from other JEE applications servers into the a CICS Liberty JVM server

52 Redbooks 93

53 Summary What is Liberty? CICS Liberty Profile Why run Liberty in CICS? How to run CICS Liberty CICS Liberty Features 94

54 95

16562: Liberté, Égalité, Fraternité a Mini CICS and WebSphere Revolution

16562: Liberté, Égalité, Fraternité a Mini CICS and WebSphere Revolution Phil_Wakelin@uk.ibm.com CICS Strategy & Design, IBM Hursley UK Abstract Liberté, Égalité, Fraternité (Liberty, Equality, Fraternity),