IMS Application Modernization - IMS UG June 2012 Phoenix


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

IMS Application Modernization - IMS UG June 2012 Phoenix

  1. 1. Kyle CharletSTSM, IMS SOA and Application Modernization © 2012 IBM Corporation
  2. 2. AgendaIMS modernization overview IMS database solutions IMS transaction management solutions DataPower and IMS connectivity IMS TM application development IMS TM connectivity2 © 2012 IBM Corporation
  3. 3. IMS Modernization Solutions IMS access anywhere IMS TM and DB Resource Standards-based data server and TM Adapters Open systems access Web services Web 2.0 (Mashup Center) WebSphere TM/DB access Universal JDBC Java API driver T IMS C P Java Universal DLI / C API driver Catalog I TM Access DB access P RYO z/OS DataPower IMS SOAP Gateway TM access3 © 2012 IBM Corporation
  4. 4. IMS Open Database Solution statement Extend the reach of IMS data – Offer scalable, distributed, and high-speed local access to IMS database resources Value Business growth – Allow more flexibility in accessing IMS data to meet growth challenges Market positioning – Allow IMS databases to be processed 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 JCA 1.5 (Java EE) JDBC4 © 2012 IBM Corporation
  5. 5. IMS Open Database JavaEE JDBC Universal drivers DLI Direct IMS JavaEE Universal DRDA over TCP/IP z/OS JDBC DRDA over TCP/IP drivers DLI DRDA over TCP/IP Open Systems (e.g.; LUW) IMS z/OS5 © 2012 IBM Corporation
  6. 6. Solution highlights – JEE deploymentUniversal DB resource adapter JCA 1.5 – XA transaction support • Manage multiple datasource connections in a single UOW – Local transaction support • Manage multiple datasource connections each in their own UOW – Connection pooling • Pool released connections for future use – Connection sharing – Multiple programming models available • JDBC (Universal JDBC driver incorporated) • CCI with SQL interactions • CCI with DLI interactions6 © 2012 IBM Corporation
  7. 7. Solution highlights – JDBCUniversal JDBC driver Significant enhancements to classic JDBC offered in IMS 9 and IMS 10 – Standardized SQL support – XA transaction support (type 4) – Local transaction support (type 4) – Concurrency control • Control release of distributed locks – Updatable result set support – Batching support • Fetch multiple rows in a single network call – JDBC metadata discovery supportStandard SQL and metadata discovery enables significant integration opportunities for IMS7 © 2012 IBM Corporation
  8. 8. Solution highlights – DLIUniversal DLI driver – Java implementation of DL/I API – Complete DL/I support for database access – All IMS command codes supported – Can mix usage of JDBC and DLI drivers in the same application • SQL cannot always express what DLI offers8 © 2012 IBM Corporation
  9. 9. Open Database and the Universal driversDeep synergy with the IMS catalog – Direct access to IMS metadata in the catalog – Virtual and cloud deployment capabilities • No longer file-system dependent for metadata – Industry-leading data type support • Complex and flexible – Mapping supportDeep synergy with Java z/OS and z196 – Significant performance improvements – Continued partnership with Java z/OS labContinued SQL standardization and support – Including similar connection parameters as DB2 for commonality across IBM drivers – More to comeContinued integration across the IBM portfolio9 © 2012 IBM Corporation
  10. 10. Data typesData types have multiple metadata elements – Application data type • Universal drivers use application data type to present data to clients – Physical data type • Universal drivers use physical data type to marshal/unmarshal data to and from the database – Example • Application data type is DECIMAL(10,2) [decimal with precision 10 and scale 2] • Physical data type is a signed packed decimal (AD community doesn’t need to know this)New data type support – Structs (nested n levels with no constraint on element data types) • Accessed via SQL and DLI – Arrays (nested n levels with no constraint on element data types) • Accessed via SQL and DLI – User-defined • Name of UDT can be defined to the catalog and intended to be used at runtime by Universal drivers to marshal/unmarshal data • Can be part of a Struct or Array element10 © 2012 IBM Corporation
  11. 11. MapsMapping support – A Map is metadata that describes how a field (or set of fields) are mapped for a particular segment instance – Metadata captures the various cases and for each case defines the set of fields to be used for that case – Maps can be defined to the catalog – Example •Insurance segment mapped multiple ways depending on value of a ‘Policy Type’ field Policy Type Property Type Rooms Value Address Make Model Year Value Color M - - - - Ford Escort 1989 2K Red 555 Disk Drive H Single Family 5 500K - - - - - Way, 9514111 © 2012 IBM Corporation
  12. 12. Additional enhancements SQL – FETCH FIRST <n> ROWS ONLY – INNER JOIN <table2> ON <table1.col1> = <table2.col2> Connection properties – currentSchema – maxRows – fetchSize – Tracing • traceFile, traceFileAppend, traceDirectory, traceLevel Variable length segment support – VL segments contain a two byte length (LL) field that will identify the size of the segment instance – Universal Drivers are now sensitive to the LL field of a VL segment and will manage the IO area of the segment instance on all CRUD calls12 © 2012 IBM Corporation
  13. 13. IMS Open Database environment z/OS LPAR A IMS Open Systems ODBM S O PC C D CTL IMS DB WebSphere I B Universal A T S DB Resource C O Adapter A P LPAR B J C I P A P 1.5 XCF DRDA LPAR C IMS Connect T C S P C I I P13 © 2012 IBM Corporation
  14. 14. IMS Open Database environment z/OS LPAR A IMS Universal Traditional ODBA WAS z/OS DB Open Systems Resource adapter O ODBM T D S PC S O PC CTL C J B C C D IMS DB WebSphere P C A I I B I Universal A A P JEE S DB Resource T 1.5 XCF adapter C O J P LPAR B IMS A Traditional ODBA P C I IMS Universal drivers A P JDBC ODBM PC 1.5 S O CTL IMS DB C D I B DLI IMS Universal drivers A JDBC LPAR CJava SE IMS IMS Connect ODBM DLI O S PC T S C D CTL IMS DB DRDA C C I B P I I A RYO DRDA Appl. P 14 © 2012 IBM Corporation
  15. 15. IMS 12 catalog Trusted IMS metadata information Comprehensive view of IMS database metadata (including application metadata) managed by IMS with standard access patterns (JDBC/SQL) Offers metadata discovery and exchange via IMS Open Database and the IMS Explorer for Application Development Scalable Open Database solution – large scale deployment into virtualized production and test environments Enables broad IMS integration into the IBM and non-IBM portfolio of tools (Optim Development Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc) PSB PSBGEN source PSBLIB ACBLIB IMS ACBGEN IMS Explorer DBD DBDGEN source DBDLIB Catalog15 © 2012 IBM Corporation
  16. 16. IMS catalog – intended support PSB PSBLIB source DDL IMS Explorer Catalog ACBLIB DBD DBDLIB source IMS • IMS DB changes start with catalog • IMS loads resource information from catalog • ACBLIB/PSBLIB/DBDLIB updates will be the by-product of catalog updates • Tools that use these libraries can continue to operate, but should migrate to catalog • PSB and DBD source can still be optionally generated from PSBLIB and DBDLIB16 © 2012 IBM Corporation
  17. 17. Dynamic database - Data Definition Language SQL incorporates DDL to modify the schema of a database Authoring DDL is straight-forward with sophisticated tooling support in the industry SQL/DDL can be used to update/add metadata in the catalog without the need of a GEN – Directly update the catalog IMS can be notified of such an update and load the new definitions It is our intention to offer this type of dynamic definition for IMS17 © 2012 IBM Corporation
  18. 18. IMS ModernizationIMS Explorer for Development IMS Explorer for Administration (Eclipse) (Web Browser) Developers Administrators ISPF18 IMS © 2012 IBM Corporation
  19. 19. IMS Explorer for Development19 © 2012 IBM Corporation
  20. 20. IMS Explorer For Development20 © 2012 IBM Corporation
  21. 21. IBM Portfolio Integration 2012-2013 Database Modeling & Creation Governance Access Analytics IMS Explorer InfoSphere Data Optim Designer Data Studio Cognos 10 BI Architect• Catalog integration • Logical & physical • Data privacy • SQL authoring • Operational BI modeling • Extending value of• zExplorer • Data management • pureQuery IMS data integration • Resource discovery • Query explain• Advanced data type • Model sharing support•Physical modeling &resource discovery•Database resourcecreation21 © 2012 IBM Corporation
  22. 22. IMS Modernization Solutions IMS access anywhere IMS TM and DB Resource Standards-based data server and TM Adapters Open systems access Web services Web 2.0 (Mashup Center) WebSphere TM/DB access Universal JDBC Java API driver T IMS C P Java Universal DLI / C API driver Catalog I TM Access DB access P RYO z/OS DataPower IMS SOAP Gateway TM access22 © 2012 IBM Corporation
  23. 23. Premier System z web service enablement through DataPower SOAappliancesIBM cross-brand initiative Deep synergy between DataPower, System z, Rational and Common Transformation tooling to support DataPower as the premier System z gateway for IMS, CICS and DB2 Intended support for IMS DB access Intended support for top-down service approach for inbound and outbound IMS transactional requests Native z transports Network-level HA and Protocol transformation distribution DataPower Processing Flow IMS RACF-centric XI50z CICS security DB2 WS Monitoring Transaction distribution XI5223 © 2012 IBM Corporation
  24. 24. Java dependent region deploymentJava dependent region resource adapter Allows new IMS transactions (JMP, JBP) to be written in Java and managed by the IMS transaction manager Complete Java framework for applications operating in an IMS container – Message queue processing – Program switching • Deferred and immediate – Transaction demarcation – GSAM support – Additional IMS call support necessary for IMS transactions • INQY • INIT • LOG • Etc Shipped with type 2 Universal drivers24 © 2012 IBM Corporation
  25. 25. IMS Enterprise Suite SOAP Gateway Web container Supports industry web service standards –HTTP(S), SSL, SOAP 1.1, WSDL 1.1, WS-I BP 1.0, WS-Security Asynchronous and synchronous callout to Web Services providers –Concurrency threading support Windows/zLinux/ z/OS zOS SOAP Envelope with XML message XML message IMS Web IMS IMS message services Enterprise IMS IMS HTTP / SOAP Enterprise TCP/IP / XML IMS IMS (.NET, SAP, Suite SOAP Connect Connect Suite SOAP etc.) Gateway Gateway25 © 2012 IBM Corporation
  26. 26. SOAP Gateway in Enterprise Suite V2.1 Supports IMS V12 and IMS V11 Supported platforms –z/OS –Linux on system Z –Microsoft Windows Tooling support –Required versions of Rational Developer for System z • RDz V8.0.2 or later is required –RDz V8.0.3 and later provides enhancements for the top-down web service provider scenario26 © 2012 IBM Corporation
  27. 27. New features in V2.1 Web service security enhancements Java separation Enhanced connection error recovery On Windows, SOAP Gateway can run as a Windows Service27 © 2012 IBM Corporation
  28. 28. Web service security enhancements - inbound SAML 1.1 signed sender-vouches tokens SAML 2.0 unsigned sender-vouches tokens – SAML 2.0 is a newer standard that introduces features such as session management, attribute profiles, encryption, metadata specifications, and pseudonyms.28 © 2012 IBM Corporation
  29. 29. Java separation SOAP Gateway server can execute on a separately installed IBM SDK Multiple SOAP Gateway server instances can share a single instance of the IBM SDK that is included in IMS Enterprise Suite Java ships in Enterprise Suite V2.1 Base Services29 © 2012 IBM Corporation
  30. 30. Enhanced connection error recovery Eliminates the need to restart SOAP Gateway when an IMS Connect outage occurs Stale connections are refreshed under the covers Requires the following: – IMS V12: APAR PM29137 – IMS V11: APAR PM27324 – The configuration of the HWSSMPL1 exit on IMS Connect30 © 2012 IBM Corporation
  31. 31. Futures WS-Security –Inbound - SAML 2.0 (signed) –Outbound - SAML 1.1, 2.0 (unsigned) Server Shutdown –Immediate –Graceful • Process all in-flight messages and come down gracefully31 © 2012 IBM Corporation
  32. 32. Futures Advanced installation support – Consistent installation story using IBM Installation Manager (IM) on all supported platforms – Make the post-SMP installation process flexible using IM on z/OS IMS transaction tracking support for SOAP Gateway – Provide server “Health Check” functionality using JMX monitoring • Monitor JVM, connection resources, traffic, etc – Provide transaction tracking • Allow client applications to pass in unique message ID or optionally generate it within SOAP Gateway • Propagate the transaction ID to IMS Connect and OTMA • Create transaction tracking log and/or send tracking information to other consumers32 © 2012 IBM Corporation
  33. 33. WebSphere and IMS TM Resource AdapterEnable IMS applications as clients or web service requestors Allows Java applications to invoke IMS transactions Integrate with Java EE or WebSphere-based servers with built-in QoS support (2PC, connection pooling, security management) Java EE Connector Architecture (JCA/J2C) compliant WAS/WPS/WTX/WMB/WESB IMS Web TCP/IP Service IMS TM Enterprise IMS IMS App Bean resource Web Connect Component adapter IMS DB * Generates IMS app Rational Application * Binary, text or XML data Source Developer (RAD) or (COBOL, PLI, WebSphere Integration C, MFS) Developer (WID)33 © 2012 IBM Corporation