IBM blue-and-black template with image


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
  • The Original ‘Middleware’ Loose coupling – separates applications from the complexity of the connection – enabling SOA componentization Asynchronous -- applications do not need to know about one another; they don’t even have to be “on-line”. “ Universal Connectivity” Easy to use, single multi-platform API (MQI) or JMS API (for J2EE environments) Supports more platforms than any other messaging system – 35+ systems Rich language choices -- C, C++, COBOL, .NET, VB, RPG, Perl Also supports SOAP over MQ. Assured, Scalable, Secure, Transactional Delivery Regulates and assures the flow of information between applications. Makes unattended operations reliable and manageable. Scales massively through clustering.
  • All of the popular languages and programming environments are supported: Assembler (zSeries), C, C++, C#, COBOL, PL/1, RPG (iSeries), TAL (Compaq NSK), Java, JMS, LotusScript, SmallTalk, Visual Basic, COM, Perl, … Powerbuilder, CICS, IMS, Encina, Tuxedo, TXSeries, WebSphere, MTS, ... While the two most popular development environments today are probably .Net and J2EE, it should be noted that much of the existing customer investment is in more traditional environments such as COBOL running under CICS on z/OS. WebSphere MQ support all of these environments equally well, providing support for traditional languages such as COBOL and also providing support for newer environments such as J2EE (with JMS support) and .Net (with C# support). Support for just one of these environments (such as J2EE) is not enough and WebSphere MQ (supporting the largest number of environments) is viewed as one of the key mechanisms for linking these environments at the transport level.
  • Depending on how one like to count platforms, the total comes to about 40. (This counts Windows as multiple platforms, for instance). WebSphere MQ is made available on (arguably) all of the commercially important platforms available today. Although there are many software platforms available today, it is the set that are of commercial importance that is of significance to the WebSphere MQ marketplace. As noted earlier, there is a client and a server implementation for WebSphere MQ. The first two columns in this diagram list the platforms for which a queue manager server is available. For most (but not all) of these server implementations a client is available as well, but this is not noted on the chart. The last column represents platforms for which there is a client implementation only . Not all of the implementations are provided by IBM. The platforms marked with a '+' sign are WebSphere MQ implementations provided by another vendor (usually Willow Technologies, but not always). These implementations are named WebSphere MQ for …. The platforms marked with a star are implementations from that platform vendor that are produced through IBM licensing formats, protocols and APIs to the platform owner. These implementations are not necessarily named WebSphere MQ. There are some anomalies in the chart. Java appears as a client only platform and as a server!! This is because the Java server implementation is a member of the WebSphere MQ Everyplace (MQe) 'sub-family' of queue managers and the Java client is not able to connect to it. Similarly the Windows 3.1 and 9x platforms appear in both sets. In common with the Java explanation, the Windows 3.1, 9x queue manager implementations are not capable of supporting clients.
  • Technology has been developed during the last 5 years in the Active Technologies Department (IBM Haifa Research Lab) within the AMiT (Active Middleware) project The core engine is publicly available As a product extension for WBI Message Broker (Cat 3 Supportpac) Also e mbedded in a Business Parter’s product (Bristol) As a stand alone engine from IBM Research on negotiated terms. The AMiT engine will be evolve to the next generation in 2005
  • The Enterprise Service Bus and the Service Oriented Architecture are closely linked. The ESB provides the connectivity infrastructure for a Service Oriented Architecture. This places the ESB in context as it’s reason for being is to support an open, standards based, service oriented architecture. As shown on the picture, the SOA provides the ‘users’ of the ESB – these are the orange/pink boxes on the diagram. Each of the interactions with the ESB (the white arrows) ideally makes use of a WSDL based service definition, invoking the required transport services and quality of service. This will frequently make use of a capability like WSIF to allow a standard service based interaction to invoke different implementation types. Note that the text on the left and at the bottom of the chart describes the characteristics of the ESB, not the Service Oriented Architecture.
  • Takeaway: The IBM Business Integration portfolio delivers capabilities required for all types of integration through a comprehensive architecture. These capabilities can be implemented on a build-as-you-go basis, and yet, because of the architecture and its service orientation, capabilities and project level solutions can be easily added as new requirements are addressed over time. Background: The IBM Business Integration Reference Architecture shows the key areas of integration capability that are required for comprehensive, enterprise wide strategies and solutions. Tools are an essential component of any comprehensive integration architecture. The Business Integration Reference Architecture includes development tools, used to implement custom artifacts that leverage the infrastructure capabilities, and business performance management tools, used to monitor and manage the runtime implementations at both the IT and business process levels. Development tools allow people to efficiently complete specific tasks and create specific output based on their skills, their expertise, and their role within the enterprise. Business Analysts who analyze business process requirements need modeling tools that allow business processes to be charted and simulated. Software Architects need tool perspectives that allow them to model data, functional flows, system interactions, etc. Integration Specialists require capabilities that allow them to configure specific inter-connections in the integration solution. Programmers need tools that allow them to develop new business logic with little concern for the underlying platform. Yet, while it is important for each person to have a specific set of tool functions based on their role in the enterprise, the tooling environment must provide a framework that promotes joint development, asset management and deep collaboration among all these people. A common repository and functions common across all the developer perspectives (e.g. version control functions, project management functions, etc) are provided in the Business Integration Reference Architecture through a unified development platform. Business performance management tools incorporate monitoring capabilities that aggregate operational and process metrics in order to efficiently manage systems and processes. Managing these systems requires a set of capabilities that span the needs of IT operations professionals and business analysts who manage the business operations of the enterprise. These capabilities are delivered through a set of comprehensive services that collect and present both IT and process-level data, allowing business dashboards, administrative dashboards, and other IT level displays to be used to manage system resources and business processes. Through these displays and services, it is possible for LOB and IT personnel to collaborate to determine, for example, what business process paths may not be performing at maximum efficiency, the impact of system problems on specific processes, or the relationship of system performance to business process performance. This collaboration allows IT personnel and assets to be tied more directly to the business success of the enterprise than they traditionally have been. One key feature of the IBM Business Integration Reference Architecture is the linkage between the Development Platform and the Business Performance Management Services. The ability to deliver runtime data and statistics into the development environment allows analyses to be completed that drive iterative process re-engineering through a continuous business process improvement cycle. At the core of the IBM Business Integration Reference Architecture is the Enterprise Service Bus. This architectural construct delivers all the inter-connectivity capabilities required to leverage and use services implemented across the entire architecture. Transport services, event services, and mediation services are all provided through the ESB. Transport services provide the fundamental connection layer; event services allow the system to respond to specific stimuli that are part of a business process; and mediation services allow loose-coupling between interacting services in the system. The ESB is a key factor in enabling the service orientation of the Business Integration Reference Architecture to be leveraged in implementing service oriented solutions and can be implemented today to meet the quality of service requirements of any integration solution. The IBM Business Integration Reference Architecture also contains a set of services that are oriented toward the integration of people, processes, and information. These services control the flow of interactions and data among people and automated application services in ways appropriate to the realization of a business process: - User Interaction Services provide the capabilities required to deliver IT functions and data to end users, meeting the end-user's specific usage preferences. - Process Services provide the control services required to manage the flow and interactions of multiple services in ways that implement business processes. - Information Services provide the capabilities required to federate, replicate, and transform data sources that may be implemented in a variety of ways. Automated application services, implementations of business logic in automated systems, are a critical part of any integration architecture or solution. Many of these services are provided through existing applications; others are provided in newly implemented components; and others are provided through external connections to third party systems. Existing enterprise applications and enterprise data are accessible from the ESB through a set of access services. These access services provide the bridging capabilities between legacy applications, pre-packaged applications, enterprise data stores (including relational, hierarchical and nontraditional, unstructured sources such as XML and Text), etc and the ESB. Using a consistent approach, these access services expose the data and functions of the existing enterprise applications, allowing them to be fully re-used and incorporated into functional flows that represent business processes. Existing enterprise applications and data leverage the Business Application and Data Services of their operating environments such as CICS, IMS, DB2, etc. As these applications and data implementations evolve to become more flexible participants in business processes, enhanced capabilities of their underlying operating environments, for example support of emerging standards, can be fully utilized. The IBM Business Integration Reference Architecture also contains a set of Business Application Services that provide runtime services required for new application components to be included in the integrated system. These application components provide new business logic required to adapt existing business processes to meet changing competitive and customer demands of the enterprise. Design and implementation of new business logic components for integration enables them to be fully re-useable, allowing them to participate in new and updated business processes over time. The Business Application Services include functions important to the traditional programmer for building maintainable, flexible, and re-useable business logic components. In many enterprise scenarios, business processes involve inter-actions with outside partners and suppliers. Integrating the systems of the partners and suppliers with those of the enterprise improves efficiency of the overall value chain. Partner Services provide the document, protocol, and partner management services required for efficient implementation of business-to-business processes and inter-actions. Underlying all these capabilities of the IBM Business Integration Reference Architecture is a set of infrastructure services which provide security, directory, IT system management, and virtualization functions. The security and directory services include functions involving authentication and authorizations required for implementing, for example, single sign-on capabilities across a distributed and heterogeneous system. IT system management and virtualization services include functions that relate to scale and performance, for example edge services and clustering services, and the virtualization capabilities allow efficient use of computing resources based on load patterns, etc. The ability to leverage grids and grid computing are also included in infrastructural services. While many infrastructure services perform functions tied directly to hardware or system implementations, others provide functions that interact directly with integration services provided in other elements of the architecture through the ESB. These interactions typically involve services related to security, directory, and I/T operational systems management. Wrap up: The IBM Business Integration Reference Architecture is a complete and comprehensive architecture that covers all the integration needs of an enterprise. Its services are well integrated and are delivered in a modular way, allowing integration implementations to start at a small project level. As each additional project is addressed, new integration functions can be easily added, incrementally enhancing the scope of integration across the enterprise. The architecture also supports Service Oriented Architecture strategies and solutions, given that the middleware architecture itself is designed using principles of service orientation and function isolation.
  • Thank You !
  • IBM blue-and-black template with image

    1. 1. Graham Oakes WW Business Integration Technical Sales [email_address] 212 493 2320 WebSphere Application Integration Messaging
    2. 2. Agenda <ul><li>WebSphere MQ </li></ul><ul><li>File Transfer with WebSphere MQ </li></ul><ul><li>Message Mediation </li></ul><ul><li>WBI Message Broker </li></ul>
    3. 3. WebSphere MQ
    4. 4. ESB Transport Services – WebSphere MQ <ul><li>The Original ‘Middleware’ </li></ul><ul><ul><li>Loose coupling – enables SOA componentization. </li></ul></ul><ul><ul><li>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. </li></ul></ul><ul><ul><li>Industry leadership – Chosen by 4 out of 5 MOM buyers. </li></ul></ul><ul><li>Assured, Transactional, Manageable </li></ul><ul><ul><li>Exactly once delivery – no duplicates. </li></ul></ul><ul><ul><li>End-to-end transactions. </li></ul></ul><ul><ul><li>Unparalleled industry support – all the leading systems management vendors. </li></ul></ul><ul><li>Single Server, Distributed Bus, or Cluster </li></ul><ul><ul><li>Dynamic routing across servers -- Messages traverse the bus with no change to end applications. </li></ul></ul><ul><ul><li>Clustering -- Workload can be balanced across a network of queue manager. </li></ul></ul><ul><li>“ Universal Connectivity” </li></ul><ul><ul><li>Multi-platform APIs -- MQI AND JMS in one </li></ul></ul><ul><ul><li>43+ systems -- Supports more platforms than any other messaging system </li></ul></ul><ul><ul><li>Rich language choices -- C, C++, COBOL, .NET, VB, RPG, Perl. </li></ul></ul>MQ Queue Manager Queue1 Queue2 MQ Queue Manager MQ Queue Manager MQ Queue Manager Single Server JMS API Distributed Bus Clustered Systems MQI API B A B A Q Mgr A Q Mgr A Q Mgr A Queue 1 Q Mgr 4 Queue 1 Q Mgr 3 Queue 1 Q Mgr 2 Program B Program B Program B Q Mgr A Queue 1 Q Mgr 1 Program A Program B ?
    5. 5. MQI Queue Manager Process Object Queue Manager Object Program A MQGET MQPUT MQPUT1 MQCMIT MQBACK MQINQ MQSET MQDISC MQOPEN MQCLOSE Queues Application Programming… MQCONNX MQCONN MQBEGIN Java Message Service .Net C, C++, C#, Java, PL/1, ASM, TAL, RPG, VB, COBOL, Perl, SmallTalk, LotusScript, REXX, …
    6. 6. WebSphere MQ and High Availability Queue 1 Q Mgr 1 Program B Queue 3 Other system components System 1 Queue 1 Q Mgr 1 Program B Queue 3 Other system components System 2 <ul><li>High availability implemented by the operating environment </li></ul><ul><ul><li>Primary/Secondary implementation model </li></ul></ul>
    7. 7. <ul><li>OS/390, z/OS </li></ul><ul><li>AIX </li></ul><ul><li>Windows NT, 2000, XP, 2003 </li></ul><ul><li>Windows: 3.1,95,98 </li></ul><ul><li>Sun Solaris: Intel & SPARC </li></ul><ul><li>HP-UX </li></ul><ul><li>iSeries </li></ul><ul><li>Compaq OpenVMS </li></ul><ul><li>Compaq NSK </li></ul><ul><li>Compaq Tru64 UNIX </li></ul><ul><li>VSE/ESA </li></ul><ul><li>Data General DG/UX </li></ul><ul><li>Dynix/ptx </li></ul><ul><li>NCR </li></ul><ul><li>TPF </li></ul><ul><li>SCO: OpenServer, UnixWare </li></ul><ul><li>SGI IRIX </li></ul><ul><li>Pyramid DC/OSx </li></ul><ul><li>NUMA-Q </li></ul><ul><li>Sinix </li></ul><ul><li>Linux (Intel, zSeries) </li></ul><ul><li>PalmOS </li></ul><ul><li>PocketPC OS </li></ul><ul><li>Java </li></ul><ul><li>Unisys 2200, ClearPath MCP </li></ul><ul><li>Hitachi </li></ul><ul><li>DOS </li></ul><ul><li>VM </li></ul><ul><li>Apple MacOS </li></ul><ul><li>Stratus VOS </li></ul><ul><li>4690 OS </li></ul><ul><li>Unisys A-Series </li></ul><ul><li>HP 3000 MPE/ix </li></ul>WebSphere MQ Messaging Platforms
    8. 8. <ul><li>More than 15,000 WebSphere MQ customers </li></ul><ul><li>10 years experience in the reliable messaging space </li></ul><ul><li>The de facto standard for reliable messaging </li></ul><ul><ul><li>Hundreds of business partners </li></ul></ul><ul><ul><li>Even IBM business integration competitors use WebSphere MQ </li></ul></ul><ul><li>Significant WebSphere MQ expertise in the marketplace </li></ul>The Messaging Marketplace
    9. 9. Standards in WebSphere MQ <ul><li>Standards are very important to the market place as they allow for ease </li></ul><ul><li>of integration and reuse. WebSphere MQ is rich in Standards. </li></ul><ul><li>Web Services ( already available ) </li></ul><ul><ul><li>MA0R, SOAP over WMQ </li></ul></ul><ul><ul><li>Sender and listener support for Axis Host Web Services environment </li></ul></ul><ul><ul><li>Sender and listener support for .NET Host Web Services environment </li></ul></ul><ul><li>JMS 1.1 is fully supported (JMS 1.0.2 supported) ( already available ) </li></ul><ul><ul><li>Including a pub/sub engine </li></ul></ul><ul><ul><li>WMQ JMS always supported inside WAS and also in Web Logic </li></ul></ul><ul><ul><li>New quality of service, non-persistent survive server restart </li></ul></ul><ul><li>SSL Supported ( already available ) </li></ul>
    10. 10. File Transfer over WebSphere MQ Commerce Quest – PM4Data A third party product from CommerceQuest in the USA under a reseller agreement under the WebSphere brand
    11. 11. Managed Data Movement PM4DATA MQSeries Queue Manager MQSeries Queue Manager PM4DATA File Managing Platform End-to-end detailed transfer status Source Platform Target Platform MQSeries Channel File Status HTML/XML HTTP/S
    12. 12. End-to-end Transfer Status
    13. 13. When to use PM4Data <ul><li>To perform scheduled or ad-hoc centrally managed file transfers with assured delivery </li></ul><ul><li>To message enable file based integration at the logical record boundary and deliver to a messaging application or Message Broker </li></ul><ul><ul><li>To optionally render the information in XML </li></ul></ul><ul><li>To enable file based integration for WBI Servers </li></ul><ul><li>To allow for processing any file size without the 100MB WebSphere MQ limit </li></ul><ul><li>To provide centralized Management and Monitoring for all participating platforms </li></ul><ul><li>To exploit the WBI Message Broker Pub/Sub using RFH2 headers </li></ul>
    14. 14. Message Mediation
    15. 15. What is Message Mediation? Application New Jersey Application New York Application London Trader Name, Stock, Qty, Date, Price($) Application Leicester Trader Name, Stock, Qty, Date, Price ($) Trader Name#Stock#Qty# Date#Price(£);
    16. 16. What is Message Mediation? Application New Jersey Application New York Application London Application Leicester WebSphere Business Integration Message Broker Trader Name, Stock, Qty, Date, Price($) Trader Name#Stock# Qty#Date#Price(£); Trader Name#Stock# Qty#Date#Price(£); Trader Name, Stock, Qty, Date, Price($)
    17. 17. What is Message Mediation? Application New Jersey Application New York Application London Application Leicester WebSphere Business Integration Message Broker <Trade> <TN> Trader Name </ TN> <Qty> NN </Qty> <Stock> SType </Stock> <Date> DD/MM/YY </Date> <Price> ££</Price> </Trade> Web Application Trader Name, Stock, Qty, Date, Price($) Trader Name#Stock# Qty#Date#Price(£); Trader Name#Stock# Qty#Date#Price(£); Trader Name, Stock, Qty, Date, Price($)
    18. 18. WBI Message Broker <ul><li>Mini Agenda </li></ul><ul><li>The Logical Message Model </li></ul><ul><li>Message Flows </li></ul><ul><li>Message Manipulation </li></ul><ul><li>Then… </li></ul><ul><li>System Architecture / Examples </li></ul>
    19. 19. Mini Agenda - Three Constructs To Examine <ul><li>The Logical Message Model </li></ul><ul><li>Message Flows </li></ul><ul><li>Message Manipulation </li></ul><ul><li>Then… </li></ul><ul><li>System Architecture / Examples </li></ul>
    20. 20. Constructing a Logical Message TradeDateTime Name Stock Trade Msg Quantity ID Price <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(£); Trader Name NN SType DD/MM/YY ££ Price(£) Stock Qty Trader Name Date XML format message Delimited format message Physical Representation Logical Representation . . .
    21. 21. Logical Message Model Physical MQMD Other headers Travel Request Message Data Logical First Name Other headers MQMD Properties Body Root Travel Request Message # of Travellers Destination Dates Start Date End Date Car Required Traveller Details Choice 1 Choice 3 Choice 2 Hotel Last Name Address House # Street Town Postcode Root.Body.TravelRequestMessage.TravellerDetails[4].Address.House#
    22. 22. Mini Agenda - Three Constructs To Examine <ul><li>The Logical Message Model </li></ul><ul><li>Message Flows </li></ul><ul><li>Message Manipulation </li></ul><ul><li>Then… </li></ul><ul><li>System Architecture / Examples </li></ul>
    23. 23. Message Flows Failure Input Server Application 1 Transform Server Application 2 Write to DB
    24. 25. Message Flow Development with Processing Nodes Filter FlowOrder TryCatch Throw Label RouteToLabel Trace MQOptimizdFlow SCADAInput MQeInput MQInput HTTPInput Real-timeInput Real-timeOptimizedFlow SCADAOutput MQeOutput Publication MQReply MQOutput HTTPReply HTTPRequest ResetConent Descriptors Extract Compute XMLTransformation Mapping Check Aggregate Request Aggregate Reply Aggregate Control DataUpdate DataDelete DataInsert Database Warehouse NEONMap NEONRules NEONTransform NEONFormatter NEONRulesEvaluation User/Third Party
    25. 26. Complex (Composite) Event Processing with the WBI Broker CEP Nodes <ul><li>Scenarios: </li></ul><ul><li>Stock Trading </li></ul><ul><ul><li>Automatic identification of buy/sell opportunities. </li></ul></ul><ul><li>Compliance Checks </li></ul><ul><ul><li>Sarbanes-Oxley detection. </li></ul></ul><ul><li>Fraud Detection </li></ul><ul><ul><li>Odd credit card purchases performed within a period. </li></ul></ul><ul><li>CRM </li></ul><ul><ul><li>Alert if three orders from the same platinum customer were rejected. </li></ul></ul><ul><li>Insurance Underwriting </li></ul><ul><ul><li>Identification of risk. </li></ul></ul>&quot;Events in several forms, from simple events to complex events, will become very widely used in business applications during 2004 through 2008&quot; --- Gartner July 2003 CEP Situation Manager
    26. 27. Mini Agenda - Three Constructs To Examine <ul><li>The Logical Message Model </li></ul><ul><li>Message Flows </li></ul><ul><li>Message Manipulation </li></ul><ul><li>Then… </li></ul><ul><li>System Architecture / Examples </li></ul>
    27. 28. Message Mapping
    28. 29. Mini Agenda - Three Constructs To Examine <ul><li>The Logical Message Model </li></ul><ul><li>Message Flows </li></ul><ul><li>Message Manipulation </li></ul><ul><li>Then… </li></ul><ul><li>System Architecture / Examples </li></ul>
    29. 30. System Architecture / Examples WBI Message Broker Components <ul><li>Great Scalability </li></ul><ul><ul><li>Multithreaded </li></ul></ul><ul><ul><li>Multiple CPUs </li></ul></ul><ul><ul><li>WMQ Clustering </li></ul></ul><ul><ul><li>Windows to Mainframe </li></ul></ul>Broker Adapter Adapter Configuration Manager Artifact
    30. 31. ESB Connectivity Services <ul><li>Transport Services </li></ul><ul><li>Assured delivery </li></ul><ul><li>Secure delivery </li></ul><ul><li>Transactional delivery </li></ul><ul><li>Manageable delivery </li></ul><ul><li>Delivery replay </li></ul><ul><li>Modifiable qualities of transport. </li></ul><ul><li>Event Services </li></ul><ul><li>Event detection </li></ul><ul><li>Event triggering </li></ul><ul><li>Event distribution </li></ul><ul><li>Complex Event Processing (CEP). </li></ul><ul><li>Mediation Services </li></ul><ul><li>Routing </li></ul><ul><li>Transport switching </li></ul><ul><li>Programming model switching </li></ul><ul><li>Transformation & content a ugmentation </li></ul><ul><li>Customized communications. </li></ul>Mediation Services Event Services Supporting yesterdays, today’s… and tomorrow’s standards. Transport Services
    31. 32. WebSphere Integration Reference Architecture The ESB WMQ WBI MB Infrastructure Management Services Business Application Services Process Services Information Services Development Services Interaction Services Partner Services Connectivity Services Business Performance Management Services Application and Information Assets
    32. 33. Next Steps To Explore ESB <ul><li>Participate in an I ntegration A rchitecture W orkshop </li></ul><ul><li>Attend an SOA/ESB Proof of Technology </li></ul><ul><li>Visit the IBM ESB Web Site – </li></ul><ul><ul><li> </li></ul></ul><ul><li>Order IBM Books or view online such as – </li></ul><ul><ul><li>“ Implementing an SOA Using an ESB (SG24-6346)” </li></ul></ul><ul><ul><li>IBM Products Manuals </li></ul></ul><ul><li>Conduct an ESB Integration Value Assessment </li></ul><ul><li>Buy IBM Quickstart Services for ESB. </li></ul><ul><li>Investigate IBM Training in the area of ESB </li></ul>
    33. 34. Thank You Merci Grazie Gracias Obrigado Danke Japanese English French Russian German Italian Spanish Brazilian Portuguese Arabic Traditional Chinese Simplified Chinese Hindi Tamil Thai Korean