Web Sphere Application Integration Messaging Graham Oakes WW

Agenda § Web. Sphere MQ § File Transfer with Web. Sphere MQ § Message

ESB Transport Services – Web. Sphere MQ MQ Queue Manager § The Original ‘Middleware’ § Loose coupling – enables SOA componentization. § Asynchronous – workload processes faster because applications do not have to wait until the application is available; the application doe not even have to be on-line. § Industry leadership – Chosen by 4 out of 5 MOM buyers. A JMS API Queue 1 B Queue 2 Single Server MQ Queue Manager § Assured, Transactional, Manageable § Exactly once delivery – no duplicates. § End-to-end transactions. § Unparalleled industry support – all the leading systems management vendors. MQI API MQ Queue Manager B A Distributed Bus Q Mgr 1 § Single Server, Distributed Bus, or Cluster § Dynamic routing across servers -- Messages traverse the bus with no change to end applications. § Clustering -- Workload can be balanced across a network of queue manager. § “Universal Connectivity” § Multi-platform APIs -- MQI AND JMS in one § 43+ systems -- Supports more platforms than any other messaging system § Rich language choices -- C, C++, COBOL, . NET, VB, RPG, Perl. 4 Program B Queue 1 Q Mgr 2 Program B Q Mgr A Program A ? Queue 1 Q Mgr 3 Program B Clustered Systems Queue 1 Q Mgr 4 Program B Queue 1 © 2004 IBM Corporation

Application Programming… Program A MQCONN MQOPEN C, C++, C#, Java, PL/1, ASM, MQDISC MQCLOSE TAL, RPG, VB, COBOL, MQCONNX Perl, Small. Talk, Lotus. Script, REXX, … MQGET MQPUT 1 . Net MQINQ Java. MQSET Message MQBEGIN Service MQCMIT MQBACK Queue Manager Object Process Object Queues 5 © 2004 IBM Corporation

Web. Sphere MQ and High Availability System 1 System 2 Q Mgr 1 Queue 3 Program B Queue 1 Other system components High availability implemented by the operating environment • Primary/Secondary implementation model 6 © 2004 IBM Corporation

Web. Sphere MQ Messaging Platforms Ÿ OS/390, z/OS Ÿ AIX Ÿ Windows NT, 2000, XP, 2003 Ÿ Windows: 3. 1, 95, 98 Ÿ Sun Solaris: Intel & SPARC Ÿ HP-UX Ÿ i. Series Ÿ Compaq Open. VMS Ÿ Compaq NSK Ÿ Compaq Tru 64 UNIX Ÿ VSE/ESA Ÿ Data General DG/UX Ÿ Dynix/ptx Ÿ NCR Ÿ TPF + SCO: Open. Server, Unix. Ware + SGI IRIX + Pyramid DC/OSx 7 • NUMA-Q Ÿ Sinix Ÿ Linux (Intel, z. Series) Ÿ Palm. OS Ÿ Pocket. PC OS Ÿ Java « Unisys 2200, Clear. Path MCP « Hitachi Ÿ DOS Ÿ VM + Apple Mac. OS + Stratus VOS + 4690 OS + Unisys A-Series + HP 3000 MPE/ix © 2004 IBM Corporation

The Messaging Marketplace § More than 15, 000 Web. Sphere MQ customers § 10 years experience in the reliable messaging space § The de facto standard for reliable messaging § Hundreds of business partners § Even IBM business integration competitors use Web. Sphere MQ § Significant Web. Sphere MQ expertise in the marketplace 8 © 2004 IBM Corporation

Standards in Web. Sphere MQ Standards are very important to the market place as they allow for ease of integration and reuse. Web. Sphere MQ is rich in Standards. § Web Services (already available) § § Sender and listener support for Axis Host Web Services environment § § MA 0 R, SOAP over WMQ Sender and listener support for. NET Host Web Services environment JMS 1. 1 is fully supported (JMS 1. 0. 2 supported) (already available) § § 9 WMQ JMS always supported inside WAS and also in Web Logic § § Including a pub/sub engine New quality of service, non-persistent survive server restart SSL Supported (already available) © 2004 IBM Corporation

File Transfer over Web. Sphere MQ Commerce Quest – PM 4 Data A third

Managed Data Movement Source Platform MQSeries HTML/XML HTTP/S Managing Platform Target Platform Status MQSeries Queue Manager MQSeries Channel PM 4 DATA File End-to-end detailed transfer status 11 © 2004 IBM Corporation

End-to-end Transfer Status 12 © 2004 IBM Corporation

When to use PM 4 Data § To perform scheduled or ad-hoc centrally managed file transfers with assured delivery § To message enable file based integration at the logical record boundary and deliver to a messaging application or Message Broker § To optionally render the information in XML § To enable file based integration for WBI Servers § To allow for processing any file size without the 100 MB Web. Sphere MQ limit § To provide centralized Management and Monitoring for all participating platforms § To exploit the WBI Message Broker Pub/Sub using RFH 2 headers 13 © 2004 IBM Corporation

Message Mediation 14 © 2004 IBM Corporation

What is Message Mediation? Application Trader Name, Stock, Qty, Date, Price($) Application New York New Jersey Trader Name, Stock, Qty, Date, Price ($) Trader Name#Stock#Qty# Date#Price(£); Application London Application Leicester 15 © 2004 IBM Corporation

What is Message Mediation? Application Trader Name, Stock, Qty, Date, Price($) Application New York New Jersey Web. Sphere Business Integration Message Broker Trader Name#Stock# Qty#Date#Price(£); Application London Application Leicester 16 © 2004 IBM Corporation

What is Message Mediation? Application Trader Name, Stock, Qty, Date, Price($) Application New York New Jersey Web. Sphere Business Integration Message Broker <Trade> <TN> Trader Name </ TN> <Qty> NN </Qty> <Stock> SType </Stock> <Date> DD/MM/YY </Date> <Price> ££</Price> </Trade> Trader Name#Stock# Qty#Date#Price(£); Application London Web Application Leicester 17 © 2004 IBM Corporation

WBI Message Broker Mini Agenda • The Logical Message Model • Message Flows •

Mini Agenda - Three Constructs To Examine 1. The Logical Message Model 2. Message

Constructing a Logical Message Physical Representation Logical Representation XML format message <Trade> <TN> Trader Name </ TN> <Qty> NN </Qty> <Stock> SType </Stock> <Date> DD/MM/YY </Date> <Price> ££ ££</Price> </Trade> Trade Msg Name Stock Trade. Date. Time Delimited format message Name Stock Trader Name#Stock# Qty Date Price(£) Qty#Date#Price(£); ID Price Quantity . . . 20 © 2004 IBM Corporation

Logical Message Model Physical MQMD Other headers Travel Request Message Data Logical Root Properties MQMD Other headers Body Travel Request Message # of Travellers Destination Dates Car Required Hotel Traveller Details Last Name Start Date End Date Choice 1 Choice 2 First Name Address Choice 3 House # Street Town Postcode Root. Body. Travel. Request. Message. Traveller. Details[4]. Address. House# 21 © 2004 IBM Corporation

Message Flows Failure Input Write to DB Transform 23 Server Application 1 Server Application

Message Flow Development with Processing Nodes Compute Aggregate Request Extract MQInput Aggregate Reply MQe. Input SCADAInput Reset. Conent Descriptors XMLTransformation HTTPInput Mapping Real-time. Input Check Real-time. Optimized. Flow Database Data. Insert Data. Delete Data. Update MQOutput Route. To. Label MQReply Publication MQe. Output SCADAOutp ut HTTPReply HTTPRequest MQOptimizd. Flow 25 Aggregate Control Label Warehouse NEONRules. Evaluation Throw Try. Catch Flow. Order Filter Trace NEONFormatter NEONTransform NEONRules NEONMap User/Third Party © 2004 IBM Corporation

Complex (Composite) Event Processing with the WBI Broker CEP Nodes Scenarios: Stock Trading § Automatic identification of buy/sell opportunities. CEP Situation Manager Compliance Checks § Sarbanes-Oxley detection. Fraud Detection § Odd credit card purchases performed within a period. "Events in several forms, from simple events to complex events, will become very widely used in business applications during 2004 through 2008" --- Gartner July 2003 CRM § Alert if three orders from the same platinum customer were rejected. Insurance Underwriting § Identification of risk. 26 © 2004 IBM Corporation

Message Mapping 28 © 2004 IBM Corporation

System Architecture / Examples WBI Message Broker Components Great Scalability § Multithreaded § Multiple CPUs § WMQ Clustering § Windows to Mainframe ct a rtif A Configuration Manager Broker Adapter 30 © 2004 IBM Corporation

ESB Connectivity Services Mediation Services Event Services Transport Services Event Services Mediation Services ü Assured delivery ü Secure delivery ü Transactional delivery ü Manageable delivery ü Delivery replay ü Modifiable qualities of transport. ü Event detection ü Event triggering ü Event distribution ü Complex Event Processing (CEP). ü Routing ü Transport switching ü Programming model switching ü Transformation & content augmentation ü Customized communications. Supporting yesterdays, today’s… and tomorrow’s standards. 31 © 2004 IBM Corporation

Web. Sphere Integration Reference Architecture Development Services Business Performance Management Services The ESB Interaction Services WMQ Process Services Information Services WBI MB Connectivity Services Partner Services Business Application Services Application and Information Assets Infrastructure Management Services 32 © 2004 IBM Corporation

Next Steps To Explore ESB § Participate in an Integration Architecture Workshop § Attend an SOA/ESB Proof of Technology § Visit the IBM ESB Web Site – § www. ibm. com/software/integration/esb § Order IBM Books or view online such as – § “Implementing an SOA Using an ESB (SG 24 -6346)” § IBM Products Manuals § Conduct an ESB Integration Value Assessment § Buy IBM Quickstart Services for ESB. § Investigate IBM Training in the area of ESB 33 © 2004 IBM Corporation

Thai Hindi Traditional Chinese Russian Gracias Spanish Thank Obrigado You English Arabic Grazie Italian Brazilian Portuguese Danke German Simplified Chinese Merci French Japanese Tamil 34 Korean © 2004 IBM Corporation