Enterprise Java (EAI) WebSphere z/os & JCA

Size: px

Start display at page:

Download "Enterprise Java (EAI) WebSphere z/os & JCA"

Winifred Fields
5 years ago
Views:

1 WebSphere z/os and JCA. Enterprise Java (EAI) WebSphere z/os & JCA Bernd Kunrath Competence Center Application Integration and Middleware Global Computing Factory T-Systems ITS GmbH Fasanenweg 9 D Leinfelden-Echterdingen Phone: Fax: bernd.kunrath@t-systems.com Internet: Enterprise Optional: Java WAS (EAI) z/os WAS JUGS z/os 2002 & JCA Bernd , , Seite Seite 1 1

2 Enterprise Java using WAS for z/os. Agenda. 1. Product Overview 2. WAS z/os Architecture 3. Deploying/running appl. 4. JCA - Java Connector Arch. 5. Resumee , Seite 2

3 Product overview. WAS z/os product overview. Optional: WAS z/os JUGS 2002 Bernd Kunrath , Seite 3

4 Product overview. WebSphere for z/os V 4.01 Features.! J2EE 1.2 levels of JDK, Servlet, JSP (consistent with Family )! Common container for Web and EJB components.! Additional elements of the J2EE platform.! Common tooling for all WebSphere platforms.! Continued support for CORBA objects from 3.x releases.! Works with IBMs HTTP server 5.3 (ex Lotus Domino GO).! Available since end of 2001 and J2EE compliant.! Uses platform features, like Parallel Sysplex Technology for clustering, Workload Manager for Workload Distribution over Sysplex and Resource Recovery Services (RRS) for Transaction Handling over z/os based monitors like DB2, IMS/TM, CICS/TS.! WebSphere for z/os V 5 coming 4Q/2002 with J2EE , Seite 4

5 Why Java/J2EE or WAS on z/os? Mainframe attributes:! Availability, Scalability, Security.! Clustering Technology, etc...! Integrated and automated production environments. Development:! Use of modern application development tools and languages for mainframe development. Code Reuse (EAI):! Allows for integrating new applications based on J2EE with existing application code.! Existing application logic and data is local to new J2EE application , Seite 5

6 Homogeneous versa heterogenous Web Browser Web Browser NT Unix Application Server Application Server z/os Backend Systems IMS CICS IDMS DB2 z/os Backend Systems IMS CICS IDMS DB2 Advantage of a homogeneous environment:! Availablity! Scalability! Proven, continual security! Fewer hardware/components! Easier deployment! Easier Systems Management , Seite 6

7 Architecture. WAS z/os Architecture and differences to WAS on distributed platforms. Optional: WAS z/os JUGS 2002 Bernd Kunrath , Seite 7

8 Separation in adresspaces for stability. web server fat client daemon sms tcp ldap db2 naming ir wlm rrs appl2 appl1 cics ims Clientsoftware! other WebSphere! fat client WAS components like! daemon! naming! sysmanagement! interface repository Applicationregions! Controlregion! Serverregions System base infrastructure! TCP/IP, WLM, RRS! DB2, LDAP , Seite 8

9 Workload management using z/os WLM.! Performance characteristics defined in WLM application definition (serviceclass slow, fast, dog,...).! Includes view of complete parallel sysplex. Control region WLM queue Server region(s)! Shedules start of additional server regions on demand , Seite 9

10 A possible parallel sysplex configuration using multiple system images. Java Application on client system or same system z/os System A WAN RMI over IIOP Sessionbeans WLM supported Selection (DDVIPA) LOCAL, JMS z/os System B WebSphere Application Server LOCAL, JMS WebSphere Application Server MQSeries LOCAL, JDBC MQSeries LOCAL, JDBC LOCAL Persistence in DB2 LOCAL Persistence in DB2 Existing systems Existing systems Channel Shared DASD Channel Shared DASD DB DASD Active PPRC DB DASD Passive , Seite 10

11 Deploying a J2EE Application. Using the WAS z/os Deployment tools Optional: WAS z/os JUGS 2002 Bernd Kunrath , Seite 11

12 WAS z/os deploying a J2EE application. Different implementations different at deployment. Implementations on different platforms are different in their runtime environment and administration. 1.) Export it from development environment, i.e. from WebSphere Application developer or VisualAge for Java. 2.) Optionally change.ear file settings or assemble application with Application Assembly tool (different for z/os or multiplatform). 3.) Deploy the application with different deployment tools or wizards , Seite 12

13 Deploying a J2EE Application. 1.) Exporting the.ear file from WSAD , Seite 13

14 Prepare deployment descriptor (optional). 2.) using Application Assembly Tools to modify.ear file - different on platform! , Seite 14

15 Deploying on WAS AE Single Server Edition. 3a.) Creating application browser based wizard dialogs , Seite 15

16 Deploying on WAS AE full edition. 3b.) Creating application with wizard dialogs , Seite 16

17 Deploying on WAS z/os. 3c.) Validating & activating the conversation with the new configuration and application , Seite 17

18 Running AimSamp WebApplication , Seite 18

19 Running AimSamp Client Application! Needs IBM JRE.! Needs special WAS z/os runtime for namespace reasons.! factory and url needs to be set , Seite 19

20 Running AimSamp Client Application needs full IP Names in hosts file or nameserver! # WebSphere needs full names too sxgezsd1.st1bs.debis.str.daimler-benz.com syx1.st1bs.debis.str.daimler-benz.com , Seite 20

21 Running AimSamp Client Application , Seite 21

22 Using JCA connectors. Using the WAS Beta JCA Connectors. Optional: WAS z/os JUGS 2002 Bernd Kunrath , Seite 22

Java Connector Architecture (JCA). Overview. JCA specifies contracts for Application server and Enterprise information systems: Application contract!

23 Java Connector Architecture (JCA). Overview. JCA specifies contracts for Application server and Enterprise information systems: Application contract! Common Client Interface (CCI)! Between application and resource adapter. System contract! Server provided Interfaces (SPI)! Between application server and resource adapter , Seite 23

24 JCA Connectors. Beta Connectors from IBM. By the time this presentation was created, only two JCA adapters where available in Beta form from IBM: CICSEXCI IMSAPPC for connecting to a CICS Transaction Server via local interface (External Call Interface). for connecting to an IMS Transaction Manager via APPC (Advanced program to program communication - SNA LU 6.2) interface. IMS does not need to run locally, SNA Networking can be used , Seite 24

strategic by IBM: CICS IMS CTG (CICS Transaction Gateway) 4.02 for connecting to a CICS Transaction Server.

25 JCA Connectors. Supported Connectors from IBM. There a additional connectors for IMS and CICS available with the Transaction server/manager products, which are strategic by IBM: CICS IMS CTG (CICS Transaction Gateway) 4.02 for connecting to a CICS Transaction Server. JNI based solution using ECI interfaces, but no need for a real Gateway running. IMS Connect 1.2 for connecting to an IMS Transaction Manager, using TCP/IP from remote systems , Seite 25

26 VisualAge for Java Enterprise, EAB & CCF Enterprise Access Builder (EAB):! Tools for generating Java classes which use CCF or JCA connectors.! I.e. generates code on basis of COBOL copybooks. Common Connector Framework (CCF):! Common Interaction with an Enterprise Information System (EIS).! IMS, CICS, SAP R/3, HOD, MQSeries, Encina, C++,...! Connectors deliver different levels of security and transaction support.! ConnectionSpec, InteractionSpec, Record, Command orientiented paradigm. J2EE JCA Connectors (JCA):! Same paradigm like CCF, uses Connection, InteractionSpec, Record, ix.execute! Beta in Fixpack VisualAge for Java EE or , Seite 26

27 WAS z/os & VisualAge for Java. Generated input recordtype for IMS application , Seite 27

28 WAS z/os & VisualAge for Java. Setting addressing infos for IMS in command, transaction & resource reference name , Seite 28

29 Sessionbean accessing remote IMS transaction (1) // Update PhoneBookEntry in Data Base PhoneBookCmd cmd = new PhoneBookCmd(); cmd.setin FILL(" "); cmd.setin LAST NAME(phonebookEntry.getLastName()); cmd.setin FIRST NAME(phonebookEntry.getFirstName()); cmd.setin EXTENSION(phonebookEntry.getPhoneNumber()); cmd.setin ZIP CODE(phonebookEntry.getZipCode()); cmd.setin COMMAND("UPDATE"); cmd.execute(); String msg = cmd.getout MESSAGE(); if (msg.trim().equals("entry WAS UPDATED")) { // Successful System.out.println(">>>> updatephonebookentry: Exited...Update Successful -->" + " firstname = " + phonebookentry.getfirstname() + " lastname = " + phonebookentry.getlastname() + " phonenumber = "+phonebookentry.getphonenumber()+ " zipcode = " + phonebookentry.getzipcode()); return phonebookentry; } , Seite 29

30 Sessionbean accessing remote IMS transaction (2) else { // Unsuccessful System.out.println(">>>> updatephonebookentry: Update Failed --> " + msg); if (msg.trim().equals("specified PERSON WAS NOT FOUND")) { throw new com.ibm.ws390.connectors.common.notfoundexception("lastname Not Found: " + phonebookentry.getlastname()); } else { throw new java.lang.error("unexpected message from IMS request: " + msg); } } , Seite 30

31 WAS z/os & VisualAge for Java. Exporting EJB Sessionbean accessing IMS , Seite 31

32 Importing EJB Sessionbean into AAT for z/os , Seite 32

33 Add a resource reference pointing to the IMSAPPC connector! , Seite 33

34 Deploy and export the Enterprise Application using AAT z/os , Seite 34

35 Deploy the Enterprise Application on z/os, adding a new conversation , Seite 35

36 Define a J2EE resource for IMS via APPC , Seite 36

37 Define a J2EE resource instance for specific IMS , Seite 37

38 Install J2EE enterprise application , Seite 38

39 Resolve JNDI names and resources , Seite 39

40 Put the JCA adapter into the classpath , Seite 40

41 Commit, validate and activate the new configuration , Seite 41

42 IMS Connector. verifying IMS transaction is running , Seite 42

43 Export the EJB client jar to test the server , Seite 43

44 IMS Connector. Accessing IMS transaction IVTNO via connector... =============================================== >>>> PHONEBOOK SESSION CLIENT STARTED!!!!!!!!! =============================================== >>>> Initialize Access Bean >>>> Instantiate PhoneBookSession Bean >>>> Creating PhoneBook entry for: WATSON >>>> PhoneBook entry created for: WATSON >>>> Retrieve PhoneBook entry for: WATSON >>>> PhoneBook entry retrieved: >>>> First Name... TOMMY >>>> Last Name... WATSON >>>> Phone Number >>>> Zip Code... >>>> Update PhoneBook entry for: WATSON >>>> PhoneBook entry updated: >>>> First Name... THOMAS >>>> Last Name... WATSON >>>> Phone Number >>>> Zip Code >>>> Delete PhoneBook entry for: WATSON >>>> PhoneBook entry deleted for: WATSON >>>> After deletion try to retrieve PhoneBook entry for: WATSON >>>> Deleted PhoneBook Entry Not Found for: WATSON ================================================== >>>> PHONEBOOK SESSION CLIENT SUCCESSFUL!!!!!!!!! ================================================== , Seite 44

45 Our findings. Results from the Evaluation. Optional: WAS z/os JUGS 2002 Bernd Kunrath , Seite 45

46 Our findings, results from evaluation (1).! It is a complex piece of software, because of it s deep integration into the platform z/os - not a simple software port.! Expect no wonders from performance or in other words: WebSphere is hungry - you have to feed it!! It is not a transaction monitor like CICS or IMS, running native assembler/cobol code - it s running Java.! It is different! The administration of it, is different from the multiplatform versions , Seite 46

47 Our findings, results from evaluation (2).! Compatible! The deployed J2EE applications as.ears worked without problems, some problems found with compatibility of DB2 statements - you need to test on target platform.! Good solution for EAI - running WAS & existing apps on same platform!! Support! Exceptional support by IBM, like Mainframe products!! Product maturity gets better every week, due to a lot of effort from IBM! , Seite 47

IBM WebSphere Application Server. Web & Docu Hints. Documentation of WAS for z/os & OS/390 http://www-4.ibm.com/software/webservers/appserv/library_390.

48 IBM WebSphere Application Server. Web & Docu Hints. Documentation of WAS for z/os & OS/390 WAS Beta JCA Connectors download Sun JCA Connectors Book: J2EE Connector Architecture and Enterprise Application Addison Wesley, , , Seite 48

Introduction. Enterprise Java Instructor: Please introduce yourself Name Experience in Java Enterprise Edition Goals you hope to achieve

Introduction. Enterprise Java Instructor: Please introduce yourself Name Experience in Java Enterprise Edition Goals you hope to achieve Enterprise Java Introduction Enterprise Java Instructor: Please introduce yourself Name Experience in Java Enterprise Edition Goals you hope to achieve Course Description This course focuses on developing