SOA Integration of IMS Applications An Overview of the Options March 2012

Size: px

Start display at page:

Download "SOA Integration of IMS Applications An Overview of the Options March 2012"

Garey Dixon
5 years ago
Views:

1 Helene Lyon E, European Architecture Team Technical Executive SOA Integration of Applications An Overview of the Options March IM Corporation

esktop Channel Interaction Services usiness Services usiness Processes Integration Services JCA JMS Web Services

2 SOA Architecture - Principles External Systems External usiness Partners External Services Providers External Systems Applications User and Interaction omain Integration/Process omain Core and Information omain Channels esktop Channel Interaction Services usiness Services usiness Processes Integration Services JCA JMS Web Services Core usiness Services ata Services JC Enterprise Service us Presentation Tier usiness Tier Enterprise Tier IM Corporation

3 What assets in can be leveraged/ extended? Transaction No presentation layer Very simple design Get Input Message RM calls ISRT Output Message execute and forget atch MPs Msg riven or non Msg riven Standalone Access to Resource Managers (RM) database Hierarchical data model 2 database Relational data model MQ Queues Web Services using WOLA WebSphere Optimized Local Adapter Presentation Layer (MFS) escription of input and output messages and device map Not used in client/server implementations P VTAM (LU0 LU1 LU2 LU6.1 LU6.2) ata Comm. MFS P APPC/MVS Transaction Manager WMQ Appl. atch atch... APPC/ Telnet External Subsystem Attachments WOLA WMQ 2 2 SP TCP/IP for zos Open Transaction Manager Access Message Queues Msg riven WOLA Non M atabase Manager Connect Open atabase IM Corporation

4 TM in Perspective Native Quality of Services Optimized integration with a database manager to optimize throughput with low resource consumption Application evelopment 4 THE enhanced development platform Asset analysis Access to external resource managers (in addition to atabases) on same z/os platform usiness Integration Access to WebSphere MQ under Two-Phase Commit protocol IM Enterprise Service us & PM Integration with applications ecision Support Recognized usiness Logic Container High transactional throughput atch support High Availability Multi-language A support Access to 2 data under Two-Phase Commit protocol Access to Master ata directly when hosted in 2 for z/os Access to Web Services Universal access to Queue Access from any MQ Server Access from any WAS server Fast integration in Web 2.0 applications Optimized WAS for z/os & Integration Access to usiness Rules Generation of usiness Events TM since 40+ years Investment protection TM & as single subsystem for transaction and database management TM since 40+ years Online batch with MPs / Standalone atch Shared Queue (full function and fast path) COOL, PLI, C, JAVA Rational eveloper for zenterprise Using Rational Asset Analyser transactions, MPs using SQL or Java JC atchs using SQL MM Server Query Connect transactions and MPs using MQ API (explicit) transactions and MPs using WOLA API Open Transaction Manager Access / No change in applications MQ ridge MQ Trigger Monitor TM Resource Adapter for JCA, MQ ridge for JMS, SOAP Gateway for web service support in the 3 IM ESs: atapower, WES, WM Support inbound or outbound integration Mashup solutions WOLA Inbound and outbound TM & WOM integration TM & WOM integration 2012 IM Corporation

SOA with Applications When designing an SOA, much of the business logic to be deployed as services is already implemented in existing IT application systems And much of this runs on the mainframe -

5 SOA with Applications When designing an SOA, much of the business logic to be deployed as services is already implemented in existing IT application systems And much of this runs on the mainframe - ottom-up approach New services may also be written It might be appropriate to write this as an EJ or Web Service For example, using JC to directly access the atabases ut in many cases the best solution will be to create new transactions Top-own approach When the existing transaction does not exactly match the business requirement, the most efficient solution is to modify the existing transaction Modify or add COOL or PL/I logic Add JAVA classes to existing COOL or PL/I programs Take benefit of a usiness Rules management system usiness Rules mining using Rational Asset Analyzer Take benefit of usiness Event management system Generate events from application Study all Call in/callout capabilities e creative Rational eveloper for System z (Rz) provides the best platform for application program development, maintenance and renovation A study of 35 SOA projects across 11 industries worldwide revealed improved flexibility (100%), decreased costs (97%), reduced risk (71%), and increased revenue (51%). IM Institute for usiness Value IM Corporation

6 TM Options All input messages into go onto a queue There is one input queue for each transaction code Output messages traditionally get put onto a queue for the destination ut when OTMA is used (by MQ or Connect), client chooses a COMMIT MOE Send reply directly (synchronously), bypassing the queues (called Commit Mode 1 or Send then Commit ) If SEN fails, transaction program is backed-out. Synchronisation flow depends on sync-level (None, Confirm, Syncpt) Put reply on a named output queue and send it after application has committed (called Commit Mode 0 or Commit Then Send ) If SEN fails, reply is still on queue and can be retrieved later Assured elivery of replies is available Sync-level is always Confirm applications can create messages on any named output queue (using alternate PC) Client can create CM0 services to read these asynchronous messages Integration with usiness Event solutions IM Corporation

7 TM Options Messages can be segmented (input or output) Single segment or multi-segment messages application receives or sends individual segments transactions can be conversational A scratch-pad created by one transaction is passed on to the next transaction A service could call one transaction so a process would be a sequence of such services A single service could call a sequence of conversational transactions A different approach is to write a new transaction that combines the logic of an existing set of conversational transactions, and this could be called by a service Input Request can be for Asynchronous Retrieval of queued output Failed CM0 IOPC reply or ALTPC output Transactions can be Input Only (specified by client as an input parameter) If transaction does create a reply, a separate service will be needed to retrieve it IM Corporation

8 SOA Connectivity with TM - Inbound to Web Service Consumer WebSphere Servers WAS, WES, WTX, WM, PM SOAP over IP TM Resource Adapter SOAP Gateway JCA WAS WebSphere Application Server WOLA - WebSphere z/os Optimized Local Adapters WES WebSphere Enterprise Service us WTX WebSphere Transformation Extender WM WebSphere Message roker PM - IM usiness Process Manager (PM) Advanced WOLA Web 2.0 Client WebSphere atapower IM Mashup Center / WebSphere smash Connect O T M A & XML 2 RYO Client Connect API (Java, C) MQ Client JMS or MQ API MQ MQ ridge MQ Trigger Monitor 8 WM & atapower 2012 IM Corporation

9 SOA Connectivity with TM - Outbound from Asynchronous support with API (ISRT ALTPC) MQ API APPC API TCP/IP calls with Connect Appls. Appls. Output Gateway? Synchronous (not in 2PC scope) support with API - New ICAL with 10 MQ API APPC/ (also in 2PC scope) SQL calls to 2 stored procedures Appls. Output Gateway? IM Corporation

10 SOA Connectivity with TM - Outbound from Asynchronous and synchronous capabilities Web Service Provider Event Processing WE, WM RYO Server WAS TM Resource Adapter SOAP Gateway WAS WebSphere Application Server WOLA - WebSphere z/os Optimized Local Adapters WE WebSphere usiness Events WM WebSphere usiness Monitor WM WebSphere Message roker RYO Server -.Net, iztalk, Oracle SP, SAP, PayPal services, and any application server, etc. WOLA Connect O T M A & XML 2 MQ Server MQ WM IM Corporation

11 SOA Solutions & evelopment Tools WebSphere using Resource Adapter WebSphere Application Server (WAS) Rational Application eveloper (RA) WebSphere ES (WES) WebSphere Integration eveloper (WI) WebSphere Message roker (WM) WTX esign Studio IM usiness Process Manager (PM) Advanced, including IM Integration esigner WebSphere Transformation Extender (WTX) WTX esign Studio WebSphere Application Server Community Edition (WASCE) WebSphere atapower WTX esign Studio atapower offers many built-in functions, e.g. WS-security, WS-management, firewalling, XML performance, etc SOAP Gateway Rational eveloper for System z (Rz) irect SOAP connectivity for (not an Application Server) IM Corporation

12 Comparison of 3 Scenarii SOAP Gateway (ISG) WebSphere atapower Appliance WAS + JCA Connector Positioning Light weight solution, with "limited" functions Included in product For performance, security and MIPS reduction Full-fledge capability support Hardware & Software Platform Run on Windows, zlinux, z/os + Connect (ICON) Appliance, standalone or in zx + Connect (ICON) Run in any OS (Linux, Unix, Windows, zlinux, z/os) + Connect (ICON) ata Flow Synchronous access over HTTP Inbound and outbound Synchronous and Asynchronous Inbound Synchronous and Asynchronous Inbound and outbound Message size NO maximum message size: Connect supports multi segment message (32K limit for one single segment) NO maximum message size: Connect supports multi segment message (32K limit for one single segment) NO maximum message size: Connect supports multi segment message (32K limit for one single segment) OTMA Protocol Support No OTMA Commit Mode 0 support No OTMA Commit Mode 0 support OTMA Commit Mode 0 support OTMA Commit Mode 1 with synclevel=none OTMA Commit Mode 1 with synclevel=none and Confirm OTMA Commit Mode 1 support with synclevel= None, Confirm or Syncpt (Global Transactionality) Conversational transaction support No support for conversational transaction No support for conversational transaction Yes evelopment Tool Rational eveloper for System z (Rz) WTX esign Studio Rational Application eveloper (RA) Or IM Integration eveloper COOL Redefine support Yes Yes Yes Compatibility with CICS & No but comparable with CICS Web Services No, CICS support based on MQ today Yes ziip/zaap support Some N/A Yes Top-own Support Available for PL/I, planned for Cobol Planned Not planned IM Corporation

13 Leveraging the est of Traditional and New Approaches Traditional Environment TM/ applications Existing applications New applications in Cobol, PLI, Java,... New Environment JavaEE applications ata server on 2 on z/os Integration Project for smooth evolution Taking the best of the 2 worlds! Traditional P New Trans JavaEE Trans IM Corporation

14 Coexistence of 2 Worlds - Solutions When building a new integration layer ES1 Integration layer to call both business logics For flexibility When is the integration focal point 1 Calling web service from the application (sync. or async) 2 Piloting the 2 update from the application When WAS is the integration focal point WAS1 Access to logic using JavaEE standards JCA for synchronous access JMS for asynchronous access IM Corporation

15 ES1 Running oth usiness Logics I Integration (ES) layer to access both environments Call transaction as a service Call JavaEE application as a service 3 scenarii: only, JavaEE only, both Capabilities In theory, Two phase commit between the 3 Logics Overhead due to TPC process, XA syncpoint manager, RRS In practice, possible if everything on z/os (same or different LPARs) WAS / WES / WPS TM RA TCP/IP Connect O T M A Appls. 2 I SOAP or? z/os WAS JavaEE Applications TCP/IP z/os IM Corporation

16 ES1 Running oth usiness Logics Transactionality support Thru distributed XA Transaction when WAS distributed Increase the length of the two-phase commit process Increase the time the z/os resources are locked ased on z/os Resource Recovery Services (RRS) on z/os when WAS and are on z/os Optimal distributed Two-Phase Commit WebSphere Application Server XA Transaction Enterprise Manager ean Call service Call new service JCA SOAP or? Transaction Attribute = TX_REQUIRE XA TM RA Proxy? TCP/IP WAS istributed JavaEE Appli. RRS RRS z/os Connect TCP/IP RRS RRS z/os O T M A Appls IM Corporation

17 1 Calling web service from the application Asynchronous Callout Enable applications to act as a client to asynchronously invoke Java EE applications and Web Services Receiving output from external application is possible Web Service Synchronous Callout Enable applications to invoke Java EE applications and Web Services, and synchronously wait for the response Web Service WAS WAS EJ/ M EJ/ M TMRA SOAP Gateway RYO TMRA SOAP Gateway RYO Connect Hold Q Connect O T M A * Initiating Client App 1 App 2 Response z/os (ISRT ALTPC) Request O T M A Initiating Client App L/I call z/os IM Corporation

18 2 Piloting the 2 update from the application Change in application to add a call to a 2 Stored Procedure Thru RA or thru MQ Capabilities with RA Sync interface (hard interface) Two phase commit capability Need a 2 on LPAR to transmit RA request Capabilities with MQ ASync interface (Soft interface) No need for 2 on LPAR MQ Listener to pass the messages to a stored procedure Appls. z/os 2 or MQ z/os Stored Proc IM Corporation

19 WAS1 Access to logic using JavaEE standards Starting an existing logic or creating a new one to update existing Synchronously using JCA Two-phase commit capability Asynchronously using JMS JCA Connector: Connect / TM Resource adapter WAS TMRA TCP/IP Connect O T M A Appls. JMS Connector: MQ to ridge WAS JMS to MQ MQ Queues MQ MQ- ridge (XCF) O T M A Appls IM Corporation

20 Summary - Architectural characteristics & Non Functional Requirements (some) ased Middleware Transactionality (TPC) Performance & Scalability ES1 Integration layer to call both business logics Connect & OTMA & RRS Yes No performance with TPC 1 Calling web service from the application (sync. or async Callout) Connect SOAP Gateway or WAS No Async: No impact Sync: resource contention 2 Piloting the 2 update from the application 2 ESAF for non-java apps or 2 RRSAF for java apps or MQ API support Yes with RA No with MQ With RA, 2 activity added With MQ, no impact on response time WAS1 Access to logic using JavaEE standards (sync. or async. Callin) JCA: Connect JMS: MQ ridge JCA: yes in theory JMS: No No performance with TPC IM Corporation

21 IM Corporation

22 Summary Core usiness applications are critical to enterprise customers usiness Integration need to consider them Maintain forward progress (preserve customer investments) Applications must live for a long time! ecosystem is ready to help you! An on demand business is an enterprise whose business processes integrated end-to-end across the company and with key partners, suppliers and customers can respond with speed to any customer demand, market opportunity or external threat IM Corporation

2014 IBM Corporation

2014 IBM Corporation Acknowledgements and Disclaimers 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. The