16
© 2007 IBM
Reduced maintenance costs and greater reliability and consistency through flexible, any-to-any linkages
Connect systems, users, and business channels based on standards
Greater innovation and flexibility through faster deployment and modification of business processes
Achieve business process innovation through treating tasks as modular services
Improved productivity and flexibility by enabling targeted user interactions for improved business operations and collaboration
Deliver role-based interaction and collaboration through services
Lower risk and faster time to market by leveraging proven, time-tested functionality
Service-enable existing assets and fill portfolio gaps with new reusable services
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
Process
People
Reuse
Connectivity
Information
ValueWhat is it?
SOA Entry Points Help Customers Get Started
Reduced maintenance costs and greater reliability and consistency through flexible, any-to-any linkages
Connect systems, users, and business channels based on standards
© 2007 IBM
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� http://www-306.ibm.com/software/info/supportlifecycle/
© 2007 IBM
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
© 2007 IBM
Added function for V6
© 2007 IBM
Extended Function Summary
� XMS (1Q06: SupportPacs)
� IBM Support Assistant (1Q06: 6.0.1.1)� 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 & 6.0.2.0 )� JMS Admin, Pub/Sub, Authorisations, Tests ("Best Practices"), Message Broker
� JCA for JMS (1Q07: 6.0.2.1)� 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: 6.0.2.1)� Windows "Toleration": no 64-bit application support
More Cat2 Plug-ins being written
© 2007 IBM
Tests: 6.0.2
© 2007 IBM
Extending the Reach
© 2007 IBM
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
© 2007 IBM
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: http://pecl.php.net/package/SAM� Binaries (limited binaries available for Windows from the SAM home page)
© 2007 IBM
Simple HTTP connectivity to WMQ
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
http://mq.com:1415/
queues/Qmgr/myQ
topics/stocks/IBM
HTTP to WMQ BridgeHTTP POST | GET |
DELETE
MQPUT() | MQGET()
libwww
Web Browser
JavascriptAJAX
HTTP client
© 2007 IBM
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
MQGET-MQPUTMQGET w.
browse
http://host/msg/queue/qname/
http://host/msg/topic/topic_path/Messages
DELETEPUTPOSTGETSample URIsResource
© 2007 IBM
Web Services over 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
client
app
SOAP
layer
HTTP
WMQ
sender
transport
WMQ
listener
SOAP
layer
HTTP
servertarget
object
HTTP
WMQ
SOAP
enabled
client
SOAP
deployed
service
user
SOAP
WMQ
key to
provider:
© 2007 IBM
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
© 2007 IBM
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
© 2007 IBM
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
