IMS SOA Solutions - IMS UG September 2012 Omaha


Published on

  • 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 SOA Solutions - IMS UG September 2012 Omaha

  1. 1. IMS SOA SolutionsRichard © 2012 IBM Corporation
  2. 2. IMS Modernization Solutions IMS access anywhere Standards-based data server and TM Open systems access IMS TM and DB Web services Resource Adapters WebSphere TM/DB access Universal JDBCJava API driver T IMS C P Java Universal DLI / C API driver Catalog ITM Access DB access P RYO z/OS DataPower IMS SOAP Gateway TM access © 2012 IBM Corporation
  3. 3. IMS TM ModernizationSOA TM Connectivity– IMS as a SOA provider and consumer– Inbound and Outbound from IMS applications– SOAP, Java, HTTP, TCP/IP © 2012 IBM Corporation
  4. 4. Modernizing IMS Applications and Data with IMS SOA solutionsBring IMS to SOA at no additional cost– Enable IMS as both provider and consumer– Access IMS transaction and data from remote platforms– Allow IMS applications to callout to remote applicationsLeverage on standards and use modern programming languages– SOAP, HTTP(S), XML, WS-*, Java EE/JCAImprove integration and lower operating costs– Through Host MIPS/CPU reductions and reuse resourcesEase IMS application development with Rational tooling– Lower skills and increase application development productivity © 2012 IBM Corporation
  5. 5. Open access to IMS transaction (Calling into IMS) © 2012 IBM Corporation
  6. 6. Inbound connectivity to IMS TM WAS – WebSphere Application Server IPS – IBM Process Server WESB – WebSphere Enterprise Service Bus Connect API WTX – WebSphere Transformation Extender RYO Client (Java, C) WMB – WebSphere Message Broker WOLA – WebSphere z/OS Optimized Local Adapters Web 2.0 WebSphere sMash Client WAS z/OS WebSphere Servers WAS, IPS, WESB, WTX WOLA IMS IMS TM Resource O Adapter (TM RA) T IMS M IMS App Web IMS SOAP Connect A Service Gateway Consumer IMS DB & WebSphere XML DB DataPower DB2 WMB TM RA MQ MQ Client MQ © 2012 IBM Corporation
  7. 7. WebSphere and IMS TM Resource AdapterAccess IMS transaction with full Java EE and SOA support • 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) • Supports both call-in and callout from IMS • Recommended when Java EE server (e.g. WAS) is already in-use • Supports rapid application development with Rational tooling Java EE application server IMS Web TCP/IP O Service IMS TM T Enterprise IMS IMS App Bean resource M Web Connect Component adapter A IMS DB * GeneratesIMS app * Binary, text or XML data Rational ApplicationSource Developer (RAD) or(COBOL, PLI, WebSphere IntegrationC, MFS) Developer (WID) © 2012 IBM Corporation
  8. 8. IMS TM Resource AdapterRecent 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 © 2012 IBM Corporation
  9. 9. A component of the IMS Enterprise SuiteIMS Enterprise Suite SOAP Gateway Light-weight SOAP server Supports industry web service standards • HTTP(S), SSL, SOAP 1.1, WSDL 1.1, WS-I BP 1.0, WS-Security Enable IMS transactions as both web service providers and consumers Run on z/OS, zLinux, Windows Windows/zLinux/ IMS zOS SOAP Envelope O Web with XML message IMS XML message IMS T IMS IMS App services Enterprise Enterprise Connect M HTTP / SOAP TCP/IP / XML (.NET, SAP, Suite SOAP Suite SOAP A etc.) Gateway Gateway IMS DB * © 2012 IBM Corporation
  10. 10. IMS Enterprise Suite SOAP GatewayRecent 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 © 2012 IBM Corporation
  11. 11. Top-down, WSDL-first application developmentDevelop new IMS applications starting from a Web ServicesDescription Language (WSDL) fileGenerate traditional programming language data constructs fromWSDL or complex XML documentsTop-down for IMS PL/I inbound request (available today)– 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 convertersIntended support for PL/I Outbound and COBOLInbound/Outbound © 2012 IBM Corporation
  12. 12. SOAP Gateway Intended supportAdvanced installation – Consistent installation story using IBM Installation Manager (IM) on all supported platforms – Make the post-SMP installation process flexible using IM on z/OSEnd-to-end transaction tracking and monitoring – Provide server “Health Check” functionality to monitor JVM, connection resources, traffic, etc – Provide transaction tracking to pass unique message ID from client to IMSWS-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) © 2012 IBM Corporation
  13. 13. IMS Connect APIProvides simplified API to build User-written IMS Connect client applicationto invoke IMS transactions from Java and C environmentsShields users from IMS Connect protocol (IRM, CSM, RSM, etc.) and low-level socket communicationsRecommend to use in RYO client application that does not run in anapplication serverValue – Extends the value of IMS resources by allowing easy access from new Java or C-based applications – Simplifies migration of existing applications from SNA to TCP/IP – Simplifies development of new applications to access IMS transactions © 2012 IBM Corporation
  14. 14. Connect API Flow DiagramFigure 1: Communication is made easier by IMS Enterprise Suite Connect API © 2012 IBM Corporation
  15. 15. Sample Connect API Java application// Create connectionConnectionFactory myCF = new ConnectionFactory();myCF.setHostName(myConnectHost);myCF.setPortNumber(myConnectPort);myCF.setClientId(myClientId);Connection myConn = myCF.getConnection();myConn.connect(); // not required with Java API// Create InteractionmyTmInteraction = myConn.createInteraction();myTmInteraction.setImsDatastoreName(“IMS1”);myTmInteraction.setTrancode(“XXXX ");myTmInteraction.setInteractionTypeDescription( ApiProperties.INTERACTION_TYPE_DESC_SENDRECV);// Set input, execute, get outputInputMessage inMsg = myTmInteraction.getInputMessage();byte[] inputData = new String(“Hello”).getBytes();inMsg.setInputMessageData(inputData);myTmInteraction.execute();OutputMessage outMsg = myTmInteraction.getOutputMessage();String outDataString = outMsg.getDataAsString(); © 2012 IBM Corporation
  16. 16. IMS accessing external applications (Calling out from IMS) © 2012 IBM Corporation
  17. 17. Outbound Connectivity from IMS TM WAS – WebSphere Application Server WBE – WebSphere Business Events WBM – WebSphere Business Monitor WOLA - WebSphere z/OS Optimized Local Adapters WebSphere e.g. WAS RYO Server - .Net, BizTalk, Oracle SP, SAP, PayPal services, and any application server, etc. IMS TM Resource Web Adapter WAS z/OS Service Provider WOLA IMS IMS SOAP O Gateway T Event IMS App IMS M Processing WBE, WBM Connect A IMS DB & XML DB Connect API RYO Server (Java) DB2 MQ Server MQ © 2012 IBM Corporation
  18. 18. IMS CalloutEnable IMS applications as clients or Web Service requesters – Interoperate with business logic outside the IMS environment – Callout to Java EE apps and Web Services using WebSphere Application Server and IMS TM Resource Adapter – Callout to Web services providers (e.g. Microsoft .NET) using SOAP Gateway – IMS Connect API (Java) supports Callout for RYO applicationsIMS 10: Asynchronous Callout – IMS application invokes external applications without waiting for response Response can be received by another IMS applicationIMS 10 SPE: Synchronous Callout – IMS application invokes external application and synchronously waits for the response – new DL/I call ICALIMS 11: Dynamic Change for OTMA Descriptors – Can roll out new application changes without an IMS outage © 2012 IBM Corporation
  19. 19. Customers using Callout Customer: A insurance company in Europe – Callout to SAP application package running in WAS on distributed platform – MDB to retrieve IMS callout requests from IMS datastores Customer: Very large Banking and Financial corporation in Europe – IMS applications remain to be strategic core banking system on z/OS – Want to modernize their IMS-based core banking system using SOA – Strong standardization, and slim middleware – Planning to use IMS SOAP Gateway for both inbound and outbound requests, with Rational Developer for System z as the development tooling Customer: A banking company in Europe – IMS application callout to JBOSS on distributed platform Customer: An insurance company in Europe – IMS application callout to Weblogic on distributed platform – POC shows >400 ICALs per second © 2012 IBM Corporation
  20. 20. Example: Synchronous Callout to WAS using IMS TM RA Initiating Client WebSphere Application Server IMS Connect IMS Message Driven HWS1 Bean (MDB) TPIPE IMS Application ICOPIPE1 IMS TM Resource Adapter Activate 1 OTMA Descriptor 2 ICAL SENDRECV ICODEST1 ICODEST1 onMessage HELLO FROM IMS ICOTPIPE1 HWS1 Web HELLO FROM IMS IWAITServiceor EJB HELLO FROM Response 3 HELLO FROM WEBSPHERE MDB WEBSPHERE MDB © 2012 IBM Corporation
  21. 21. Example: Callout with IMS SOAP Gateway Initiating Client z/OS IMS SOAP Gateway IMS Connect IMS HWS1 TPIPE IMS Application Server start 1 SGPIPE02 Request OTMA DescriptorWeb Service 2 ICAL SENDRECV OTMDEST1 OTMDEST1 JOHN BANKER 100000 SGPIPE02 HELLO FROM IMS XML HELLO HWS1 Adapter FROM IMS 3 HWSXMLA0 HELLOD XML Converter Response 4 HELLO FROM WEB SERVICE HELLO FROM HELLO WEB SERVICE FROM WEB SERVICE Correlator © 2012 IBM Corporation
  22. 22. Recent IMS callout enhancements IMS TM resource adapter – Enable a single message-driven bean (MDB) to pull callout messages from more than one IMS data stores – Auto reconnect for both IMS data store and IMS Connect connection failures Connect API (Java) performance evaluation in progress – IMS application calling out to a local Java z/OS application shows more than 8000 ICALs per second ICAL enhancements – More precise information for ICAL failures especially for timeout situation – Enhanced command to also show number of queued RT request – Enhanced OTMA Log Record Diagnostics – Improved Resume TPIPE management. Cleaned up unused TPIPE requests © 2012 IBM Corporation
  23. 23. IMS TM and Application Server integration © 2012 IBM Corporation
  24. 24. IMS TM Connectivity and Integration Many IBM application servers already provide built-in support for IMS transaction access today for various environment and needs Complex Data Complex Data Java EE Java EE Web Service Web Service BPM BPM Transformation TransformationWebSphereApplication WebSphere WebSphere WebSphere SOAP IBM Process Server Datapower Message Enterprise Transformation Gateway Serveror Java EE Broker Service Bus Extender Server** Enterprise Service Bus• Full SOA • Direct IMS • SOA • Interoperate • Java based • Business • Transform and Java SOAP appliances heterogeneous Enterprise process complex data EE endpoint services and Service Bus automation types • Fast Web data and Services for Web Services services and environments • Inbound and choreography • Inbound to IMS• Inbound XML Outbound* and • Inbound transformat- • Inbound to from IMS • Inbound and Outbound and ion IMS Outbound* from IMS Outbound from IMS • Inbound to from IMS IMS*Additional coding may required. **Subset of functions supported with conditional support © 2012 IBM Corporation
  25. 25. Premier System z web service enablement through DataPowerSOA appliancesIBM 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 Support Inbound access to IMS transaction today 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 XI52 © 2012 IBM Corporation