Bru soa access-for_ims_db_customers

633 views
545 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
633
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Bru soa access-for_ims_db_customers

  1. 1. ® SOA Access for IMS DB Customers Jack Yuan – jackyuan@us.ibm.com © 2010 IBM Corporation
  2. 2. Acknowledgements Special thanks to – Suzie Wendler and Ken Blackman for sharing their IMS SOA knowledge and foils with me. 2
  3. 3. The Technology Evolution IMS Java EJB IMS Connect XML COBOL SOAP XML Open DB Database 3270 WWW 3270 COBOL 3270 3270 Integrate Integrate Adopt Access Publish Transact Simplification ……. Internally Externally Dynamically Access On Demand Web 2.0 Optimize operations… “ dynamically respond to Publish IMS resources as “Get on the Net ” ” the needs of customers, employees, partners. feeds 3
  4. 4. ..to Service Oriented Architecture (SOA) REQUIREMENTS • Provide access to IMS resources as web services • Provide access from IMS transactions to web services UDDI Registry Service Figuring out how to access IMS Broker – “Exposing” the IMS resources as web services publish WSDL find WSDL Deciding how to create the web service Service bind, invoke Requester Service ? Web Provider Service Client IMS SOAP Application Figuring how to access web services from IMS 4
  5. 5. IMS recognizes a variety of requirements Application requirements – Access to IMS transactions • Direct connection model • Messaging and Queuing model – Access to IMS data • Inquiry (read-only), Update, 2PC • Access across LPARs • Access from distributed environments – Access from IMS applications • To web services – Applications and data on distributed servers – Replicating IMS data 5
  6. 6. And provides a variety of new Web Solutions IMS Solutions Direct service Database clients WID RAD Solutions access Java/J2EE DLI Developers Client WebSphere IMS Model Java Utility dev IMS TM Resource IMS Connect TCP/IP WebSphere Web Service Adapter TCP/IP DRDA Java /J2EE Developer .NET IMS Database Universal Transaction Client manager ODBM MFS SOA manager DB Client Developer Resource ODBA /DRA Adapter SQL OTMA IMS SOAP Direct APP DL/I XQuery CICS SOAP DL/I SAP Developer Client IMS SOAP DB2 Application Gateway Java SP/CICS developer IMS class Database JDR Library IMS Resource Universal REST Service RDz Adapter JDBC Driver IMS DB2 WebSphere Universal JDBC DLI Developer InfoSphere Driver Model HTTP Mashup Utility Web 2.0 Mashup IMS Web 2.0 DLI Model Utility (includes new IMS 11 components) 6
  7. 7. IMS Integration Suite IMS TM Resource Adapter IMS Web 2.0 IMS MFS Web Enablement IMS Connect-based solutions for IMS transaction access IMS SOAP Gateway IMS DB Resource Adapter – IMS JDBC Connector IMS DB access IMS DLIModel utility IMS XML DB Open Database Manager (IMS 11) 7
  8. 8. Application Requirement – Access to Data Direct Connection (database) – Characteristics • Access to data without invoking an IMS transaction – ODBA interface (Open DataBase Access) • Programs that issue database calls must reside on the same MVS as IMS 8
  9. 9. IMS Solutions JDBC access to IMS DB (delivered by IMS) – WebSphere z/OS and IMS Java support WAS for z/OS IMS IMS HTTP EJB EJB IMS JDBC IMS JDBC DB adapter DB Server (JDBC calls) adapter (ODBA) (JDBC calls) (ODBA) z/OS – Support with IMS V9 – IMS Java Remote Data Services WAS Distributed WAS for z/OS Client side EJB EJB Client side Distributed Distributed (CM) IMS DB IMS DB (CM) IMS JDBC EJB EJB IMS JDBC IMS JDBC IMS JDBC (ODBA) adapter adapter (ODBA) application application adapter adapter EJB EJB (BM) (BM) z/OS CM: container managed (supports global transaction semantics) BM: bean managed (supports local transaction semantics) 9
  10. 10. … And XML DB Storage and retrieval of XML documents in IMS databases – Composition of XML documents from existing IMS databases • Creation of IMS segments from XML documents (decomposition) • Intact storage of XML documents (without decomposition) – Tooling assistance to define metadata for mappings – IMS Java application programming support Benefits – Easy exchange of data between IMS databases and XML documents • Existing IMS databases may be used to create XML documents • Existing applications are unaffected XML Document IMS Java IMS DB Application APIs: <?xml version=‘1.0’?> <customer xmlns= ‘http://www…/PSB/PCB’> IMS 9 – XML API <cust> … <name> … </name> XML Schema IMS 10 – XQUERY API </cust> <?xml version=“1.0”’ encoding=“UTF-8”?> <xsd:schema xmlns:xsd= … … <xsd:element name=“cust”> … 10
  11. 11. DLIModel Utility Generates the DB metadata and XML Schema COBOL Control statements OPTIONS PSBds=psbfiles DBDds=dbdfiles COBOL copybooks GenJavaSource=YES JavaSourcePath=test/tooling/f101/test Package=test.db.psb1 ReportPath=test/tooling/f101/test XMI’s GUI GenXMI=YES GenTrace=YES GENXMLSchemas=store XMLSchemaPath=testschema Outpath=test/tooling/f101 INCLUDE Dataset=include/dealerIncls PSB psbName=autpsb1 JavaName=NewPSB1DBView (Eclipse PCB pcbName=PCB1 JavaName=Dealer PCB pcbName=PCB2 JavaName=Employee Plug-in) (HFS or PDS) (HFS or PDS) DLIModel PSB Utility New DBD PSB IMS 11 Import (PDS) DBD XMI XML (HFS) Generate DLIModel IMS Java Report ======= ===== ==== ===== === Class: AU TPSB11DatabaseView in pac kage: sampl es.deal ership generated for PSB: AUTPSB11 ======= ===== ==== ===== ===== ===== ===== ==== ===== ===== PCB: Deal er ======= ===== ==== ===== ===== ===== ===== ==== ===== ===== Segment: Dealer Segment Field: DealerNo T ype=C HAR Start=1 Length=4 ++ Pri mar y Key Field + + Field: DealerName T ype=CHAR Start=5 Length=30 (Sear ch Field) DBD Field: DealerCity T ype= CHAR Start=35 Length=10 (Searc h Field) IMS Java Field: DealerZip T ype= CHAR Start=45 Length=10 ( Search Field) Field: DealerPhone T ype=CHAR Start=55 Length=7 (Sear ch Field) ======= ===== ==== ===== ===== ===== ===== ==== ===== ===== Segment: ModelSegment Field: M odelKey T ype=CHAR Start=3 Length=24 ++ Pri mar y Key Fiel d ++ Field: M odelT ype T ype=CHAR Start=1 Length=2 (Searc h Field) Field: M ake T ype=CH AR Start=3 Length=10 (Search Fi eld) Field: M odel T ype=C HAR Start=13 Length=10 (Search Field) Field: Year T ype=CH AR Star t=23 Length=4 (Search Fiel d) Field: M SRP T ype=C HAR Start=27 Length=5 (Search F ield) Field: C ount T ype=C HAR Start=32 Length=2 (Search Fi eld) ===== ===== ===== ===== ==== ===== ===== ===== ===== ==== == Segment: Or derSeg ment Field: Order No T ype=CHAR Start=1 Length=6 ++ Pri mar y Key Fiel d ++ Report Field: LastN ame T ype=CH AR Start=7 Length=25 (Search Fi eld) Field: FirstN ame T ype=C HAR Start=32 Length=25 (Search Field) Field: Date T ype=C HAR Start=57 Length=10 ( Search Field) Field: Ti me T ype= CHAR Start=67 Length=8 (Search Field) package samp les. deale rship ; ==== ==== ===== ===== ===== ===== ==== ===== ===== ===== === Segment: SalesSeg ment import com.i bm.i ms.db .*; Field: SaleN o T ype=CHAR Start= 49 Length=4 ++ Pri mar y Key Fiel d ++ import com.i bm.i ms.ba se.*; ... public class AUT PSB11 Datab aseVi ew ex tend s DLI Datab aseVi ew { // The f ollo wing DLITy peInf o[] a rray desc ribes Segm ent: DEAL ER in PCB: AUTO LPCB sta tic D LITy peInf o[] A UTOLP CBDEA LERA rray= { (HFS) new DLIT ypeIn fo("D ealer No", DLIT ypeIn fo.CH AR, 1 , 4, "DLR NO"), IMS Java new DLIT ypeIn fo("D ealer Name" , DL IType Info. CHAR, 5, 3 0, " DLRNA ME"), new DLIT ypeIn fo("D ealer City" , DL IType Info. CHAR, 35, 10, "CITY "), new DLIT ypeIn fo("D ealer Zip", DLI TypeI nfo.C HAR, 45, 1 0, " ZIP") , new DLIT ypeIn fo("D ealer Phone ", D LITyp eInfo .CHAR , 55, 7, "PHON E") }; sta tic D LISe gment AUTO LPCBD EALER Segm ent= new D LISeg ment ("De alerS egmen t","D EALER ",AU TOLPC BDEAL ERArr ay,61 ); ... // An ar ray of DL ISegm entIn fo ob ject s fol lows to de scrib e th e vie w for PCB: AUTO LPCB sta tic D LISe gment Info[ ] AUT OLPCB arra y = { XML Schema(s) new DLIS egmen tInfo (AUTO LPCBD EALE RSegm ent,D LIDat abase View .ROOT ), new DLIS egmen tInfo (AUTO LPCBM ODEL Segme nt,0) , new DLIS egmen tInfo (AUTO LPCBO RDER Segme nt,1) , Metadata classes new DLIS egmen tInfo (AUTO LPCBS ALES Segme nt,1) , new DLIS egmen tInfo (AUTO LPCBS TOCK Segme nt,1) , new DLIS egmen tInfo (AUTO LPCBS TOCS ALESe gment ,4), new DLIS egmen tInfo (AUTO LPCBS ALES INFSe gment ,5) }; ... } (HFS) (HFS) 11
  12. 12. IMS Open Database Solution Statement – Offer scalable, distributed, and local access to IMS database resources Value – Business growth • Allow more flexibility in accessing IMS data – Market positioning • Enable IMS databases as a standards-based data server Key differentiators – Standards-based approach • Java Connector Architecture • JDBC • SQL • DRDA – Solution packaged with IMS Enables new application design frameworks and patterns – Java EE – Web 2.0 12
  13. 13. Open Database Topics Open Database consists of three components: – Open Database Manager – CSL component – IMS Connect – Open Database API 13
  14. 14. CCTL ODBA and DRA Application Review CICS A D Appl Pgm R Thread 1 JDBC A IMS D CCTL B R A Appl Pgm Application Thread 2 Program CTL DB TM DRA DB2 SP Services Appl Pgm Thread 1 Services Services RRS=Y|N JDBC O D Address Thread 2 B Space A Using RRS WAS z/OS O D Appl Pgm B Database JCA A Address Space Using RRS z/OS LPAR 14
  15. 15. Open Database Manager Open Database Manager (ODBM) is a Common Service Layer ODBM component – Receives database connection requests from IMS Connect – Translates incoming database requests from the DDM protocol into DLI calls expected by IMS – Translates responses to the client into the DDM protocol – Manages connections to IMS DB • Implements the DRA interface – Supports Two-phase commit semantics • RRS=Y RRS provides sync point coordinator role – Supports Single-phase commit semantics • RRS=N ODBM provides CCTL sync point coordinator role 15
  16. 16. ODBM OM SCI IMS Control Services Database manager DRA SCI SCI ODBM API API SCI ODBM Client Database z/OS 16
  17. 17. CSL ODBM CCTL ODBA and DRA OM SCI SCI ODBM IMSplex D API CCTL R A RRS=N Thread 1 Application CTL DB TM DRA Program Services Services Services RRS=Y|N Thread 1 SCI ODBM O D API RRS=Y B A Database z/OS LPAR 17
  18. 18. IMS Open Database Distributed Syncpoint (global transaction) requires RRS on z/OS Use of RRS with ODBM is optional – RRS=Y|N parm for ODBM start-up • If RRS=Y (also the default), ODBM will use the ODBA interface (i.e. AERTDLI) • If RRS=N, ODBM will use the DRA interface like CICS – Global transactions are not supported if RRS=N) LPAR A z/OS IMS Connect Parent UOR RRS T C S P C Distributed I I Coordinated Start UOW P WAS S J T LPAR B RRS C ODBM O D A B P IMS I S O IMS P C C D Child P I B DB A 18
  19. 19. ODBM auto-(re) connect IMSPLEX(NAME=PLEX1) SCI notification for IMS2 IMS1 ODBM re-connects No notification for IMS4 PLEX1 SCI ODBM does not re-connect must use an ODBM command ODBM PLEX1 ODBA IMS2 PLEX1 PLEX1 IMS4 LPAR 1 19
  20. 20. And … for Compatibility ODBA application programs can use the ODBM address space – “Compatibility Mode” – Gives protection from potential U113 abends when ODBA applications are stopped during DLI processing – No changes required to ODBA applications – Need to update and recompile DFSPRP macro to build new DRA Startup Table 20
  21. 21. ODBA Compatibility Support DFSPRP Macro //DFSIVP10 EXEC PROC=ASMDRA,MBR=DFSIMSA0 //ASM.SYSIN DD * DFSIMSA0 CSECT FUNCLV=2 DFSPRP DSECT=NO, X FUNCLV=2, ODBA FUNCTION LEVEL X DBCTLID= DDNAME=DFSDB2SP, DDNAME FOR DRA RESLIB X DSNAME=IMS110P.SDFSRESL, DSNAME FOR DRA RESLIB X MAXTHRD= DBCTLID=IMSA, DBCTL IDENTIFIER X USERID=, USER IDENTIFIER X MINTHRD= MINTHRD=1, MINIMUM NUMBER OF THREADS X . MAXTHRD=1, TIMER=60, MAXIMUM NUMBER OF THREADS IDENTIFY TIMER VALUE DEFAULT X X . FPBUF=, FPBOF=, NUMBER OF FP BUFFERS PER THREAD NUMBER OF FP OVERFLOW BUFFERS X X . SOD=A, TIMEOUT=60, SNAP DATASET OUTPUT CLASS DRATERM TIMEOUT VALUE X X IMSPLEX= IDRETRY=0, IDENTIFY RETRY COUNT X CNBA=, TOTAL FP NBA BUFFERS FOR CCTL X ODBMNAME = IMSPLEX=PLEXA, IMSPLEX NAME X (Optional) ODBMNAME=OD0A END Causes ODBA //* requests to be routed via ODBM 21
  22. 22. ODBM ODBA Compatibility Support IMSPLEX(NAME=PLEX1) DB2 SP IMS1 ODBA PK66020 V9 Client ODBMNAME=ODBM02 IMSPLEX NAME=PLEX1 WAS ODBM ODBA z/OS 02 IMS2 ODBA OR V10 PK66022 Client IMSPLEX NAME=PLEX1 CSL will choose an ODBM ODBM ODBA SCI 01 IMS3 V11 z/OS LPAR 1 22
  23. 23. ODBM – Security ODBM does not perform any user authentication or authorization – Assumes the end Client Userid associated with an allocate PSB request has been authenticated. – IMS Connect does the authentication – IMS does the authorization For ODBA DRA DFSPBxxx – ODBASE= APSB security and ISIS= IMS RAS security • ODBM creates ACEE for ODBM Thread TCB For CCTL DRA DFSPBxxx – ISIS= IMS RAS security • ODBM passes Client UserID/GroupName to access the PSBs 23
  24. 24. SAF APSB Security ODBASE=Y ACEE - Authenticated USERID The IMS application group resource class (AIMS or Axxxxxxx) IMS IMS ODBM Open DB API Connect RRS=Y Type 4 PSB Schedule Time ODBM Client TCP/IP Connection ACEE PSB 1 Userid USERID Authenticated Userid Password USERID 24
  25. 25. RAS PSB Security ISIS=R or A ACEE - Authenticated USERID The IMS application group resource class (IIMS or Ixxxxxxx) IMS IMS ODBM Open DB API Connect RRS=N ACEE Type 4 Userid ODBM Client TCP/IP USERID PSB Schedule Time Connection ACEE Group USERID Authenticated Userid Password USERID PSB 1 Userid 25
  26. 26. ODBA Enhancements New CIMS CONNECT call which allows ODBA applications to connect to multiple IMS subsystems with a single call – Previously CIMS INIT was the only function available, which only allowed the caller to connect to a single IMS • Multiple CIMS INIT calls were required to connect to multiple IMS DB systems ODBA application programs can use the ODBM address space to manage the ODBA interface – Gives protection from potential U113 abends when ODBA applications are stopped during DLI processing • No changes required for ODBA applications – Need to add the IMSplex and ODBMNAME keywords to DFSPRP macro • Recompile and rebind the DFSxxxx0 load module Reduces complexity and increases availability 26
  27. 27. ODBM ODBA Compatibility Support IMSPLEX(NAME=PLEX1) •DB2 •SP IMS1 ODBM PK66020 ODBA •ODBA 03 V9 •Client ODBMNAME=ODBM03 IMSPLEX NAME=PLEX1 •WAS ODBM ODBA •z/OS 02 IMS2 •ODBA V10 PK66022 •Client IMSPLEX NAME=PLEX1 ODBM ODBA SCI 01 IMS3 V11 27 LPAR 1
  28. 28. IMS Open Database – IMS Connect IMS Connect has the following enhancements in support of IMS Open Database: – IMS Connect Configuration member HWSCFGxx • New ODACCESS statement – DRDA ports, timeout value, IMSplex name etc. – Changes to existing commands • VIEWHWS, VIEWDS, VIEWPORT – New Commands • STARTOD, STOPOD, STARTIA, STOPIA, VIEWIA, SETOAUTO – New User Exits • HWSROUT0 – Routing Exit for ODBM – can override the IMS alias and/or select the ODBM target • HWSAUTH0 – Security Exit for ODBM – can perform the authentication of the userid 28
  29. 29. Timeouts ODBMTMOT= Defines the amount of time that IMS Connect waits:: – A response message on connections with ODBM – An initial input message from TCP/IP client application Type 4 TCP/IP IMS DRDA Application TCP/IP Program IMS DRDA Requestor Connect DRA ODBM DRDA PORT Type 4 HWSJ2530W TCP/IP TCP/IP DRDA DRDA Back out In-Flight work Application Program Requestor 29
  30. 30. IMS Connect and ODBM as DRDA Application Server IMS Control Services Database manager Open DB API Type 4 DRA IMS TCP/IP DRDA TCP/IP Connect ODBM Application DRDA DRDA Program PORT Requestor Database z/OS 30
  31. 31. IMS Connect HWSCFGxx Configuration Member . . . Example of ODACCESS statement HWS=(ID=HWS1,XIBAREA=100,RACF=N) TCPIP=(HOSTNAME=TCPIP,PORTID=(9999,9998,LOCAL), EXIT=(HWSSMPL1,HWSCSLO1,HWSSOAP1)) OTMA DATASTORE=(ID=IMS1,GROUP=XCFGRP1,MEMBER=HWS1, TMEMBER=IMS1,DRU=HWSYDRU0, APPL=APPLID1,RRNAME=RTPIPE) IMSPLEX=(MEMBER=IMSPLEX1,TMEMBER=PLEX1) ADAPTER=(XML=Y) OM ODACCESS=(ODBMAUTOCONN=Y,ODBMTMOT=6000, ODBM DRDAPORT=(ID=1111,KEEPAV=5,PORTTMOT=50), IMSPLEX=(MEMBER=ICON1,TMEMBER=PLEX2)) 31
  32. 32. IMSPLEX = CSLPLEX1 and CSLPLEX2 z/OS B OTMA •HWS1 OM SCI OM SCI •XCFGRP1 9999 9998 •B2OM •SCB2SC •B1OM •SCB1SC IMS •PLEX2 •PLEX2 •PLEX1 •PLEX1 CONNECT DRA/ODBA DRDA IMS IMS PORT CTL CTL 1111 ODBM •ICON1 •IMS2 •IMS1 DRA/ODBA •PLEX2 ODBM •PLEX2 •PLEX1 OM •XCFGRP1 •IMSPLEX1 •PLEX1 •ODBM01OD •PLEX2 32
  33. 33. IMS Open Database – IMS Connect IMS Connect Workload Distribution – ODBM clients can specify an IMS “ALIAS” in the message • Alias represents the IMS datastore that the client wants to access – Multiple Alias names for an IMS datastore can be defined in the ODBM configuration member – If the client sends a message with a blank alias, IMS Connect will route the message to all ODBM using a round robin algorithm – If an alias points to multiple ODBMs, IMS Connect will route the message to one of those ODBMs using a round robin algorithm 33
  34. 34. ALIAS Example ODBM(NAME=ODBMB1 DATASTORE(NAME=IMS1, ALIAS(NAME=IM1A, IO1A)) LPARA IMSPLEX1 DATASTORE(NAME=IMS2, IMS ALIAS(NAME=IM1A, IO2A)) ) Connect A •ALIAS IO1A only routes to IMS1 IMS1 TM/DB ODBA ODBMB1 DB IMS2 TM/DB •ALIAS IM1A is ACCESS DB routed to ODBMB1 •ALIAS IO2A only routes to IMS2 TCP/IP using for either IMS1 or ALIAS IMS2 IM1A •ALIAS IO3A only routes to IMS3) LPARB And using IMS ODBMB2 IMS3 DRA Connect DBCTL DB Hostname IMS port Connect B ODBM(NAME=ODBMB2 IMS4 DBCTL DATASTORE(NAME=IMS3, DB ALIAS(NAME= IO3A, IMS3)) DATASTORE(NAME=IMS4) ) •IMS4 has no alias, applications can use the DATASTORE name IMS4 34
  35. 35. No ALIAS Example ODBM(NAME=ODBMB1 DATASTORE(NAME=IMS1, ALIAS(NAME=IM1A, IO1A)) LPARA IMSPLEX1 DATASTORE(NAME=IMS2, IMS ALIAS(NAME=IM1A, IO2A)) ) Connect A IMS1 TM/DB ODBA ODBMB1 IMS2 TM/DB •A blank alias Data Sharing is routed to either Environment ACCESS DB ODBMB1 or ODBMB2 TCP/IP using a blank ALIAS (assumes that any route ODBMB2 IMS3 DRA DB can access the DB) DBCTL DB And using IMS IMS Connect Connect B ODBM(NAME=ODBMB2 IMS4 Hostname DATASTORE(NAME=IMS3, DBCTL and Port ALIAS(NAME= IO3A, IMS3)) DATASTORE(NAME=IMS4) ) LPARB 35
  36. 36. Java DL/1 Access The IMS Universal DL/1 Driver provides a DL/1 Call interface for java applications in a Non-JEE environment – Completely re-architected and rewritten – Rich in function – Usable in distributed or z/OS environments The IMS Universal DB Resource Adapter not only supports JDBC, but also fully supports the JCA 1.5 CCI DB interaction specification – SQLInteractionSpec class provides simple SQL calls – DLIInteractionSpec class provides simple DL/1 calls • RETRIEVE, CREATE, UPDATE, DELETE functions 36
  37. 37. IMS Open Database IMS Open Database offers access to IMS database resources anywhere in the IMSplex directly from z/OS and distributed environments – Using industry standard Distributed Relational Database Architecture (DRDA) to communicate with IMS Connect – Different API layers are provided to leverage the DRDA protocol • IMS Universal DB Resource Adapter - to use JDBC SQL access to IMS data in a JEE environment such as WebSphere Application Server (WAS) on any platform • IMS Universal JDBC driver - to use JDBC SQL access to IMS data in a Non-JEE environment such as stand-alone java, DB2 SP, IMS TM, CICS • IMS Universal DL/I driver - to issue calls that are similar to DL/I directly to IMS from a Non-JEE Java environment • RYO - Use a programming language of your choice to issue DRDA commands directly to IMS Connect – IMS Connect becomes the gateway to IMS Transactions and IMS Data Makes Application development and Connectivity much simpler! 37
  38. 38. IMS Open Database Comparison of programming approaches for accessing IMS: Approach Scenario Use the JCA 1.5-compliant IMS distributed Accessing IMS data through TCP/IP from a J2EE application DB resource adapter that resides on a distributed non-z/OS platform or a z/OS platform that is on a different LPAR from the IMS subsystem. Use the type-4 JDBC driver or the DL/I for Java Accessing IMS data through TCP/IP from a Java application API (non-J2EE) that resides on a distributed non-z/OS platform or a z/OS platform that is on a different LPAR from the IMS subsystem. Use your language of choice to issue DRDA Accessing IMS data through TCP/IP from a non-Java application DDM commands that resides on a distributed non-z/OS platform or a z/OS platform that is on a different LPAR from the IMS subsystem. 38
  39. 39. Universal Drivers System z Distributed Universal IFL Linux DB Resource WAS Adapter WAS (any platform) JCA 1.5 Linux z Type 4 Universal DB Resource Adapter z/OS A JCA 1.5 T IMS CICS Type 4 C P I Connect IMS Universal P JDBC ODBM DLI Type 2 IMS Universal Drivers IMS DB JDBC Type 4 DLI IMS DB2 WAS/z Type 4 Universal Any Java Runtime Platform DB ODBM Universal Resource JDBC Adapter IMS DB JCA 1.5 DLI Type 2 z/OS B Type 2 SNA IMS TM IMS Universal IMS DB TCP/IP JDBC Network Clients Appl Type 2 39
  40. 40. IMS DB as a service Web 2.0 support for IMS data – Develop an IMS RESTful service / feed • Generate Meta files from IMS DB • IMS Web 2.0 Editor in InfoSphere MashupHub 40
  41. 41. Running an IMS 11 database Feed Invoking an IMS 11 DB feed – IBM Mashup Center Enterprise database feed generator – Mashup editing tools in IBM Mashup Center – IMS 11 Universal DB resource adapter 41
  42. 42. IMS Open Database J2EE JDBC Universal drivers Mainframe DLI IMS IMS IMS IMS J2EE JDBC Universal drivers DLI Mainframe IMS IMS IMS IMS Demo 42
  43. 43. Summary Open Database Capabilities – Supports open-standards for connectivity to online IMS databases – Across z/OS LPARs – Across networks – Direct access from distributed platforms – Provides an environment that manages access to online IMS databases – Provides Open Database APIs • Ease application development access to IMS databases 43

×