Successfully reported this slideshow.

IMS04 Accelerate IMS Appl Modernization - IMS UG June 2013 Melbourne


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

IMS04 Accelerate IMS Appl Modernization - IMS UG June 2013 Melbourne

  1. 1. IMS Technical Conference Accelerate IMS application modernization © 2013 IBM Corporation modernization Greg Vance IBM STSM, IMS Development IBM Silicon Valley Laboratory
  2. 2. Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Acknowledgements and Disclaimers The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. © 2013 IBM Corporation2 © Copyright IBM Corporation 2013. All rights reserved. – U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM, the IBM logo,, IMS, DB2, CICS, WebSphere, InfoSphere, Rational, Cognos, and System z are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at Other company, product, or service names may be trademarks or service marks of others.
  3. 3. Agenda IMS modernization overview IMS database solutions – Integration opportunities and futures IMS transaction management solutions © 2013 IBM Corporation3 IMS transaction management solutions – Integration opportunities and futures DataPower and IMS connectivity – Current and future
  4. 4. • IMS access anywhere • Standards-based data server and TM • Open systems access z/OS TM access RYO Java API DB Access Universal JDBC TM access DataPower IMS SOAP Gateway IMS IMS Modernization Solutions 4 TCP/IPTCP/IP C API Java API Universal DLI driver Universal JDBC Driver Web 2.0 (Mashup Center) IMS TM and DB Resource Adapters WebSphere TM/DB Access Java Catalog 4
  5. 5. 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 © 2013 IBM Corporation5 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) JDBC
  6. 6. IMS Open Database IMS z/OS JavaEE Universal Universal drivers JavaEE DLI JDBC Direct © 2013 IBM Corporation6 DRDA over TCP/IP DRDA over TCP/IP z/OS IMS z/OS Open Systems (e.g.; LUW) JDBC DLI Universal drivers DRDA over TCP/IP
  7. 7. Solution highlights – JEE deployment Universal DB resource adapter JCA 1.5 – XA transaction support • Manage multiple datasource connections in a single UOW – Local transaction support © 2013 IBM Corporation7 • 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 interactions
  8. 8. Solution highlights – JDBC Universal 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 © 2013 IBM Corporation8 – Concurrency control • Control release of distributed locks – Updatable result set support – Batching support • Fetch multiple rows in a single network call – JDBC metadata discovery support Standard SQL and metadata discovery enables significant integration opportunities for IMS
  9. 9. Solution highlights – DLI Universal DLI driver – Java implementation of DL/I API – Complete DL/I support for database access © 2013 IBM Corporation9 – All IMS command codes supported – Can mix usage of JDBC and DLI drivers in the same application • SQL cannot always express what DLI offers
  10. 10. Open Database and the Universal drivers Deep 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 support © 2013 IBM Corporation10 – Mapping support Deep synergy with Java z/OS and z196 – Significant performance improvements – Continued partnership with Java z/OS lab Continued SQL standardization and support – Including similar connection parameters as DB2 for commonality across IBM drivers – More to come Continued integration across the IBM portfolio
  11. 11. Data types Data 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] © 2013 IBM Corporation11 • 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 element
  12. 12. Maps Mapping 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 © 2013 IBM Corporation12 – 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 H Single Family 5 500K 555 Disk Drive Way, 95141 - - - - -
  13. 13. Additional enhancements SQL – FETCH FIRST <n> ROWS ONLY – INNER JOIN <table2> ON <table1.col1> = <table2.col2> Connection properties – currentSchema – maxRows – fetchSize – Tracing © 2013 IBM Corporation13 – 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 calls
  14. 14. IMS Open Database environment LPAR Az/OS IMS DB CTL IMS PC Open Systems Universal DB Resource Adapter J T C P I WebSphere S O A LPAR B S C I O D B A ODBM © 2013 IBM Corporation14 C A 1.5 I P P LPAR C XCF DRDA IMS Connect T C P I P S C I
  15. 15. IMS Open Database environment Universal DB Resource adapter J C T C P I WebSphere S O A LPAR Az/OS Open Systems IMS LPAR A IMS DB CTL IMS PCS C I O D B A ODBM LPAR B XCF WAS z/OS Universal DB Resource adapter J C A 1.5 T C P I P O D B A PCS C I Traditional ODBA IMS Universal drivers Traditional ODBA JEE © 2013 IBM Corporation15 C A 1.5 I P P LPAR C IMS DB CTLPC S C I O D B A DLI JDBC RYO DRDA Appl. IMS DB CTL IMS PCS C I O D B A IMS Universal drivers IMS Connect T C P I P S C I ODBM ODBM DLI JDBC IMS Universal drivers Java SE DRDA
  16. 16. 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 © 2013 IBM Corporation16 Enables broad IMS integration into the IBM and non-IBM portfolio of tools (Optim Development Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc) ACBLIB Catalog PSB source PSBLIB DBD source DBDLIB PSBGEN DBDGEN ACBGEN IMS Explorer IMS
  17. 17. IMS catalog – intended support PSBLIB CatalogIMS Explorer DDL ACBLIB PSB source © 2013 IBM Corporation17 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 DBDLIB DBDLIB DBD source IMS
  18. 18. 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 © 2013 IBM Corporation18 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 IMS
  19. 19. Intended SQL engine investment Current SQL engine is Java-based – As a result only supports Java clients IMS intends to invest in a native SQL engine © 2013 IBM Corporation19 – Could support COBOL and PLI clients • Dynamic and even static SQL could be supported – Engine would require the IMS catalog
  20. 20. IMS user interface enhancements IMS Explorer for Administration (Web Browser) IMS Explorer for Development (Eclipse) © 2013 IBM Corporation IMSISPF AdministratorsDevelopers
  21. 21. IMS Explorer for Development © 2013 IBM Corporation21
  22. 22. IMS Explorer for Development © 2013 IBM Corporation22
  23. 23. IMS Explorer for Development © 2013 IBM Corporation23
  24. 24. IMS Explorer for Development © 2013 IBM Corporation24
  25. 25. IMS Explorer for Administration (intended direction) Provide IMS system programmers and DBAs a state-of-the-art user interface to manage, configure, and deploy IMS systems Full operational control over all IMS address spaces © 2013 IBM Corporation25 Full command of IMS resources – Programs, transactions, databases, etc Immediately react to and resolve issues in the system Cloud-style IMS system management – IMS region profiling, application profiling, application deployment
  26. 26. IMS Explorer for Administration (intended support) IMSplex at-a-glance Immediate insight into properties of any given IMSplex Drill-down for advanced insight and action © 2013 IBM Corporation26
  27. 27. IMS Explorer for Administration (intended support) Transaction insight Transaction and program status immediately available Operate directly on transactions © 2013 IBM Corporation27
  28. 28. IMS Explorer for Administration (intended support) Database insight Status and attributes immediately available React and resolve issues © 2013 IBM Corporation28
  29. 29. IMS Explorer • Catalog integration • zExplorer • Relationship discovery InfoSphere Discovery Database Modeling & Discovery • Data privacy • Data management Optim Designer Governance • Operational BI • Extending value of IMS data Cognos 10 BI Analytics Data Studio • SQL authoring • pureQuery Access Intended portfolio integration © 2013 IBM Corporation29 • zExplorer integration • Advanced data type support • 360 degree view of data assets and relationships • Data management IMS data • pureQuery • Query explain •Physical modeling & resource discovery •Database resource creation
  30. 30. Intended runtime integration WebSphere Message Broker – Leverage the JDBC driver support in WMB in order to offer access to IMS DB via the Universal JDBC driver SAP © 2013 IBM Corporation30 SAP – SAP support for Java deployment accessing IMS DB using JDBC and SQL via the Universal drivers .NET – .NET data provider offering SQL access to IMS from the .NET platform
  31. 31. Java dependent region deployment Java 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 © 2013 IBM Corporation31 • Deferred and immediate – Transaction demarcation – GSAM support – Additional IMS call support necessary for IMS transactions • INQY • INIT • LOG • Etc Shipped with type 2 Universal drivers
  32. 32. IMS TM Connectivity and Integration WebSphere Application Server or Java EE Server** SOAP Gateway Datapower WebSphere Message Broker WebSphere Enterprise Service Bus IBM Process Server WebSphere Transformation Extender Java EE Enterprise Service Bus BPMWeb Service Complex Data Transformation Many IBM application servers already provide built-in support for IMS transaction access today © 2013 IBM Corporation32 Enterprise Service Bus • Full SOA and Java EE Services • Inbound and Outbound from IMS • Direct IMS SOAP endpoint for Web Services • Inbound and Outbound from IMS • SOA appliances • Fast Web services and XML transformat- ion • Inbound to IMS • Transform complex data types • Inbound to IMS • Business process automation and choreography • Inbound and Outbound* from IMS • Java based Enterprise Service Bus • Inbound and Outbound* from IMS • Interoperate heterogeneous services and data environments • Inbound to IMS *Additional coding may required. **Subset of functions supported with conditional support
  33. 33. Inbound connectivity to IMS TM IMS O T IMS IMS App WebSphere Servers WAS, IPS, WESB, WTX Connect API (Java, C) RYO Client IMS TM Resource Adapter (TM RA) IBM Mashup Center / WebSphere sMash Web 2.0 Client WOLA WAS z/OS WAS – WebSphere Application Server IPS – IBM Process Server WESB – WebSphere Enterprise Service Bus WTX – WebSphere Transformation Extender WMB – WebSphere Message Broker WOLA – WebSphere z/OS Optimized Local Adapters © 2013 IBM Corporation IMS Connect T M A IMS DB & XML DB IMS App IMS SOAP Gateway WebSphere DataPower MQMQ Client Web Service Consumer DB2 WMB TM RA MQ
  34. 34. Outbound Connectivity from IMS TM IMS IMS TM Resource Adapter WebSphere e.g. WAS Web Service Provider WAS – WebSphere Application Server WBE – WebSphere Business Events WBM – WebSphere Business Monitor RYO Server - .Net, BizTalk, Oracle SP, SAP, PayPal services, and any application server, etc. WOLA - WebSphere z/OS Optimized Local Adapters WOLA WAS z/OS © 2013 IBM Corporation IMS Connect O T M A IMS DB & XML DB IMS App IMS SOAP Gateway MQMQ Server RYO Server Event Processing WBE, WBM DB2 Connect API (Java)
  35. 35. IMS TM Resource Adapter Access IMS transaction with full Java EE and SOA support – Customer-proven IMS modernization solution for over a decade – Industry-standard Java EE Connector Architecture (JCA/J2C) compliant – Integrate with a variety of Java EE or WebSphere-based servers with built-in QoS support (2PC, connection pooling, security management) – Support both call-in and callout from IMS – Support rapid application development with Rational tooling © 2013 IBM Corporation35 – Support rapid application development with Rational tooling – Recommended to use with Java EE or WebSphere servers Recent key enhancements – Support non-IBM Java EE server (e.g. Weblogic, JBOSS) and WebSphere Application Server Community Edition – Callout enhancements • Retrieve callout messages from more than one IMS data stores with a single message-driven bean (MDB) • Auto reconnect for both IMS data store and IMS Connect connection failures
  36. 36. IMS Enterprise Suite SOAP Gateway Enable IMS transactions as both web service providers and consumer – Web Container – Support industry web service standards • HTTP(S), SSL, SOAP, WSDL, WS-Security – Support both call-in and callout from IMS – Run on z/OS, zLinux, Windows © 2013 IBM Corporation36 Recent key enhancements – Simplified installation with SMP on z/OS and IM (IBM Installation Manager) on distributed platforms – Top-Down PL/I Provider support – Enhanced Management Utility with task automation – Major security enhancements: AT-TLS, Custom Authentication Module, SAML 1.1 Unsigned/Signed, SAML 2.0 Unsigned – Significant performance improvement
  37. 37. IMS Enterprise Suite 2.2. SOAP Gateway enhancements Advanced installation – Consistent installation story using IBM Installation Manager (IM) on all supported platforms – Make the post-SMP installation process flexible using IM on z/OS End-to-end transaction tracking and monitoring – Provide server “Health Check” statistics and log – Provide transaction tracking log © 2013 IBM Corporation37 – Provide transaction tracking log – Enable end-to-end transaction tracking • Allow client applications to pass in user-specified or SOAP Gateway generated unique transaction message ID and propagate to IMS Connect and IMS OTMA WS-Security – Inbound with SAML 2.0 (signed), Outbound with SAML 1.1, 2.0 (unsigned) Enhanced server shutdown options – Immediate or Graceful (process all in-flight messages and come down gracefully)
  38. 38. Top-down, WSDL-first application development Develop new IMS applications starting from a Web Services Description Language (WSDL) file Generate traditional programming language data constructs from WSDL or complex XML documents Top-down for IMS PL/I inbound request (available today) – Rational Developer for System z (RDz) 8.0.3 © 2013 IBM Corporation38 – Rational Developer for System z (RDz) 8.0.3 – Support top-down development scenario – Generate PL/I IMS application template, language structures and XML input/output converters Intended support for Top-down PL/I Outbound and COBOL Inbound/Outbound
  39. 39. IMS Enterprise Suite Connect API Simple callable interfaces to send/receive messages to/from IMS Connect – Java, C and C++ support – Normally use in Roll-Your-Own application that does not run in an application server – Extensible profiles that define connections and interactions not © 2013 IBM Corporation39 – User does not have to understand: • Sockets programming • IMS Connect IRM headers and flags – Support all IMS Connect functions Simplifies development of new IMS Connect client applications to access IMS transactions
  40. 40. Sample Connect API Java application // Create connection ConnectionFactory myCF = new ConnectionFactory(); myCF.setHostName(myConnectHost); myCF.setPortNumber(myConnectPort); myCF.setClientId(myClientId); Connection myConn = myCF.getConnection(); myConn.connect(); // not required with Java API © 2013 IBM Corporation40 myConn.connect(); // not required with Java API // Create Interaction myTmInteraction = myConn.createInteraction(); myTmInteraction.setImsDatastoreName(“IMS1”); myTmInteraction.setTrancode(“XXXX "); myTmInteraction.setInteractionTypeDescription( ApiProperties.INTERACTION_TYPE_DESC_SENDRECV); // Set input, execute, get output InputMessage inMsg = myTmInteraction.getInputMessage(); byte[] inputData = new String(“Hello”).getBytes(); inMsg.setInputMessageData(inputData); myTmInteraction.execute(); OutputMessage outMsg = myTmInteraction.getOutputMessage(); String outDataString = outMsg.getDataAsString();
  41. 41. IMS Callout IMS application callout to external application and web services – New DL/I ICAL to synchronously callout from IMS – Enable IMS to synchronously and asynchronously callout to Java applications and web services • IMS TM Resource adapter, SOAP Gateway and Connect API Recent enhancements © 2013 IBM Corporation41 Recent enhancements – Better diagnostics information for ICAL failure – Immediate Resume TPIPE timeout when no message available for Nowait and NoAuto modes – Notify client with an error when a late or invalid ACK received by OTMA after ICAL timeout – Clean up unused ICAL TPIPEs after two IMS checkpoints – Enhanced /DISPLAY command to display accumulated ICAL count
  42. 42. IMS 13 Callout enhancements Synchronous program switch – Extend IMS Synchronous Callout to invoke another IMS Application – DL/I ISRT continues to be used for asynchronous program switch – OTMA Descriptor enhanced to recognize an IMS transaction destination – Messages can be multi-segment – Value © 2013 IBM Corporation42 – Value • Provides a single DL/I call interface to request a service regardless of where that service resides • Simplified integration and usability OTMA Destination descriptor for WebSphere MQ asynchronous callout – Expanded the current destination descriptor to support WebSphere MQ for asynchronous callout function – Value • Enhanced usability such that customer does not have to code OTMA routing exits
  43. 43. Premier System z web service enablement through DataPower SOA appliances IBM 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 New support for IMS DB access New support for top-down service approach for inbound and outbound IMS © 2013 IBM Corporation43 New support for top-down service approach for inbound and outbound IMS transactional requests XI52 XI50z DataPower Processing Flow Protocol transformation WS Monitoring Native z transports Transaction distribution Network-level HA and distribution RACF-centric security IMS CICS DB2
  44. 44. IMS modernization - moving forward Continued aggressive investment in – Application modernization – Database modernization Continued investment in integration opportunities Continued synergy with both software and hardware stack updates to maximize exploitation © 2013 IBM Corporation44 exploitation Continue to invest in solutions and technology which reduce the overall cost
  45. 45. © 2013 IBM Corporation45