WebSphere MQ Update. Paul Dennis WMQ Development 2007 IBM Corporation

Transcription

1 WebSphere MQ Update Paul Dennis WMQ Development Corporation

2 SOA Entry Points Help Customers Get Started People What is it? Deliver role-based interaction and collaboration through services Value Improved productivity and flexibility by enabling targeted user interactions for improved business operations and collaboration Process Achieve business process innovation through treating tasks as modular services Greater innovation and flexibility through faster deployment and modification of business processes Information Provide trusted information in business context by treating it as a service Better business operations, more informed decisions and reduced risk with information delivered in-line and in-context Reuse Service-enable existing assets and fill portfolio gaps with new reusable services Lower risk and faster time to market by leveraging proven, time-tested functionality Connectivity Connect systems, users, and and business channels based on on standards Reduced maintenance costs and and greater reliability and and consistency through flexible, any-to-any linkages

3 End of Service Dates for V5.3 Distributed V5.3 Announcement of EoS made in June 2006 Now withdrawn from marketing End of Service in September 2007 z/os V5.3.1 Now withdrawn from marketing End of Service in April 2008 Fee-based service extensions normally available for an extra 2 years Look at URL for most recent info

4 Highlights of WebSphere MQ V6.0 Improved Usability New Eclipse-based cross-platform configuration tooling Increased manageability Find out what the system is doing, and influence it Easier problem determination and problem avoidance Enhanced Availability & Performance Exploiting z/os services Improved performance, capacity and scalability Exploiting 64-bit address space Built-in Publish/Subscribe messaging Web services: carrying SOAP over MQ New platform support

5 Added function for V6

6 Extended Function Summary XMS (1Q06: SupportPacs) IBM Support Assistant (1Q06: ) Makes it easier to access product information and raise defects Cat 2 Plug-ins for the Explorer Search, Events/Statistics, Traceroute New Official Plug-ins for the Explorer (Sep/Oct 06: SupportPac & ) JMS Admin, Pub/Sub, Authorisations, Tests ("Best Practices"), Message Broker JCA for JMS (1Q07: ) Makes it easier to use WMQ JMS in any J2EE-compliant application server Support for 64-bit Windows on x86-64 and 64-bit JVM on z/os (1Q07: ) Windows "Toleration": no 64-bit application support More Cat2 Plug-ins being written

7 Tests: 6.0.2

8 Extending the Reach

9 Extending the Reach of Applications Using MQ New distributed programming models becoming widely adopted SOA & Web services Capital W Web services standards based, interoperable e.g. WS-* SCA Programmable web Small w web services simple, lightweight, pragmatic e.g. REST IBM is extending MQ to take advantage of these new models To Allow Access From Zero Footprint Clients and the Web Goal: Easy access to MQ from HTTP and the World Wide Web To Embrace Standards Based ( Enterprise ) Web Services SOAP/JMS standard Windows Communication Foundation channel WMQ Service Definition

10 SAM Simple Asynchronous Messaging Languages like PHP simplify creating dynamic web pages They are not over engineered but good enough The languages and runtimes are largely open-source They are lightweight and require no tooling No easy way to reach our messaging products from these scripting languages Aims of SAM: Develop a simplified messaging API for PHP Can be used uniformly across the WebSphere messaging family built on XMS Deliver as an open-source extension Availability Available for PHP 4 and 5 Source available from PECL: Binaries (limited binaries available for Windows from the SAM home page)

11 Simple HTTP connectivity to WMQ queues/qmgr/myq Web Browser Javascript AJAX MQPUT() MQGET() HTTP POST GET DELETE HTTP to WMQ Bridge HTTP client libwww Key features of HTTP bridge : Converts between HTTP(S) and WMQ Runs as servlet in app server Maps URIs to queues or topics Enables MQPUT and MQGET from Web Browser or lightweight client topics/stocks/ibm

12 HTTP-MQ Verb / Resource Mapping Define URI to identify queue (or topic) Modelled on REST principles Simple translation of HTTP to MQI Message Format: Header fields (MQMD) conveyed in HTTP headers Body is passed in HTTP entity body Message type is conveyed in HTTP Content-Type text/plain or text/html equate to MQ string messages (MQFMT_STRING) All other media types map to MQ binary messages (MQFMT_NONE) HTTP verb mapping Resource Sample URIs GET POST PUT DELETE Messages MQGET w. browse MQPUT - MQGET

13 Web Services over WMQ SOAP enabled client client app SOAP layer HTTP WMQ sender HTTP transport WMQ HTTP server WMQ listener SOAP layer target object SOAP deployed service key to provider: user SOAP WMQ Transport SOAP messages over a reliable transport instead of http Sender and listener support for Axis host Web Services environment.net host Web Services environment Client and server SOAP layers may be heterogeneous eg.net client to Java server If they interoperate using HTTP, they will interoperate using WMQ Also works with WAS SOAP/JMS and CICS SOAP/MQ Scripts for deployment assistance SupportPac MA0V for async services

14 SOAP/JMS Standardisation Other vendors have also implemented SOAP/JMS - interoperability is required Vendor solutions can not interoperate on the wire but should be able to interoperate at the API level e.g. WAS -> WebLogic IRI, Properties, Message Format A Standardisation effort is underway Initial participants: IBM, BEA, Sonic, and TIBCO In Oct 06 the specification reached v1.0 RC1 More vendors invited to provide feedback (WebMethods then joined core team) Standardisation will make it possible to have: JMS provider-neutral deployment of SOAP/JMS services Bidirectional HTTP - SOAP Bridging Maintaining integrity of SOAP message and protocol metadata Not restricted to Java implementations: COBOL app can build correct format

15 WCF (Indigo) Custom channel for MQ Windows Communication Foundation underpins.net WS and Messaging Built-in Transports e.g. MSMQ, HTTP(S), Named Pipes, TCP/IP, etc. Transports can be extended with custom channels Allows alternative transports (like MQ) to be slotted into WCF seamlessly IBM has built a prototype custom channel for MQ Released onto AlphaWorks Using SOAP/JMS message formats For interoperability with WAS, CICS SOAP/JMS services We are looking for feedback to assess demand for this feature

16 WMQ as an SOA Asset - Service Descriptions Need a standard to describe all WMQ apps as SOA assets (services) To be inventoried, and catalogued in Service Registry To be re-used as services in composite SOA applications To be managed and traced with SOA tools IBM is specifying the WMQ Service Definition and SOAP binding IRI for WMQ addresses ( wmq: ) Message destinations - Queues or Topics used by messaging applications Other resources - Qmgrs, channels, channel status etc. for use by admin tools WSDL bindings to define application properties Also defines the Message Exchange Pattern; Request queue; Response queue; Correlation style; Message format; Message persistence, priority etc. This will be a published specification in 2007 Publication mechanism TBD - probably a SupportPac No current plans for tools in WMQ itself But it defines what could be implemented by IBM and vendor tooling products