WAS7_Messaging II - ® IBM Software Group IBM® WebSphere®...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: ® IBM Software Group IBM® WebSphere® Application Server V7 The Value of WebSphere - Service Integration Bus © 2007 IBM Corporation Updated February 9, 2012 IBM Software Group Goal: Leverage Benefits of Service Integration Bus You want to … • IBM Solution Quickly configure high availability and scalability for the Service Integration Bus • Create flexible workload management policies for message-driven beans Administrative wizard for trouble-free configuration of high availability and scalability Additional options for message-driven bean connection in a cluster Finer control over sending messages to a service integration bus Messaging components 2 © 2007 IBM Corporation IBM Software Group Section Service integration bus connection Service behavior in WebSphere Application Server v6.x Server Messaging components 3 © 2007 IBM Corporation IBM Software Group WebSphere Cluster Client Cluster member A Cluster member B Cluster member C WebSphere cluster Messaging components J2EE HA is accomplished by running several copies of the same logic. 4 © 2007 IBM Corporation IBM Software Group Service Integration Bus - High Availability SIBus ME Failover Cluster member A ME Cluster member B Cluster member C The SIBus Messaging Engine is a singleton service. HA is accomplished by failing over the ME service to a different cluster member. WebSphere cluster Messaging components 5 © 2007 IBM Corporation IBM Software Group How a message-driven bean connects in a single cluster MDB SIBus ME MDB Failover Cluster member A MDB Only the MDB in Cluster Member A will receive messages. ME Cluster member B Cluster member C WebSphere cluster Messaging components 6 © 2007 IBM Corporation IBM Software Group MDB connection behavior: Between a cluster and a separate bus member MDB MDB MDB Cluster member A Cluster member B Cluster member C With MDBs in separate cluster, all MDBs receive messages. WebSphere cluster SIBus ME Failover Cluster member A ME Cluster member B WebSphere cluster Messaging components 7 © 2007 IBM Corporation IBM Software Group Service integration bus - Workload sharing or scalability configuration Multiple active messaging engines for the bus WebSphere cluster SIBus ME ME ME Server A Server B Server C Requires administrator to know core groups and match criteria to configure. Messaging components 8 © 2007 IBM Corporation IBM Software Group Section Enhancements for JMS consumers Messaging components 9 © 2007 IBM Corporation IBM Software Group JMS consumption options New options in V7: Start an MDB on each cluster member, whether or not a local messaging engine is present Message Visibility Allow the message consumer to simultaneously consume from all queue points of a service integration bus queue Messaging components 10 © 2007 IBM Corporation IBM Software Group SIBus MDB connection behavior: Within a single cluster bus member MDB SIBus ME MDB Failover Cluster member A MDB New feature -- Always activate MDBs in all servers. ME Cluster member B Cluster member C WebSphere cluster Messaging components 11 © 2007 IBM Corporation IBM Software Group Service integration bus – Message visibility By default, a message consumer consumes from only one queue point for the lifetime of the message consumer Message visibility allows a message consumer to simultaneously consume from all queue points Gathering messages from multiple queue points is a very performance intensive operation – significantly slower than consuming from a single queue point Consumer WebSphere cluster SIBus ME ME ME QP QP QP Server A Server B Server C Messaging components 12 © 2007 IBM Corporation IBM Software Group Section Simplified administration and cluster Simplified enhancements in V7 enhancements Messaging components 13 © 2007 IBM Corporation IBM Software Group Simplified cluster configuration New wizard simplifies configuring messaging engines in clustered environments - Messaging engine policy assistance Helps determine your needs and configure messaging engines for high availability or scalability Saves labor and frees the user from needing to know about core groups and policies Messaging components 14 © 2007 IBM Corporation IBM Software Group Simplified cluster configuration Messaging components 15 © 2007 IBM Corporation IBM Software Group Improved administrative control of MDBs Message-Driven Beans can be started and stopped independently Can be triggered manually or when a message failure threshold is reached Helps prevent failures of dependent resources from causing broader application failures Messaging components 16 © 2007 IBM Corporation IBM Software Group Improved administrative control of MDBs Visualization of relationships between MDBs and service integration bus destinations available in the admin console Messaging components 17 © 2007 IBM Corporation IBM Software Group Section New JMS clients Messaging components 18 © 2007 IBM Corporation IBM Software Group Thin JMS client V7 includes a new thin client JAR to enable client access from Java™ SE clients Requires Java SE 5 at a minimum Provides outbound communication from clients and 1-phase commit support Supports the Open Service Gateway Initiative Service Platform as instantiated by the Eclipse Rich Client Platform (RCP) level 3.2 com.ibm.ws.sib.client.thin.jms_7.0.0.jar Found in the ‘runtimes’ folder alongside the web services and administrative thin client JARs Client can now coexist with EJB, JAX-WS and JAX-RPC clients Messaging components 19 © 2007 IBM Corporation IBM Software Group Resource adapter for other application servers V7 provides a JCA resource adapter (RAR file) for use with third-party application servers WebSphere Application Server Community Edition (CE) JBoss Application Server 4.0.5 and later Enables first-class communication from with Service Integration Bus resources Inbound and outbound communications 2-phase commit support WebSphere Application Server CE WebSphere Application Server v7.0 RA for JMS Messaging components 20 © 2007 IBM Corporation IBM Software Group Section WebSphere MQ Enhancements WebSphere Messaging components 21 © 2007 IBM Corporation IBM Software Group Enhancements for WebSphere MQ WebSphere Application Server V7 contains a JCA RA for WMQ Enables message delivery to Message-Driven Beans using activation specifications, the standard Java EE delivery mechanism Listener port usage is deprecated Listener ports can be converted to activation specifications Messaging components 22 © 2007 IBM Corporation IBM Software Group Section Summary Messaging components 23 © 2007 IBM Corporation IBM Software Group Summary V7 includes several improvements to the Service Integration components Simplified configuration panels and new wizards Support for new client types Thin JMS client library for Java SE clients Resource adapter for WebSphere Community Edition and JBoss clients Enhancements for message-driven beans MDB start and stop capability Enhanced clustering options JCA connectivity to WebSphere MQ will be delivered by WebSphere MQ V7 Messaging components 24 © 2007 IBM Corporation IBM Software Group Trademarks, copyrights, and disclaimers The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: DB2 IBM Informix WebSphere SQL Server, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both. EJB, Java, JMX, Open Service, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This document could include technical inaccuracies or typographical errors. IBM may make improvements or changes in the products or programs described herein at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectual property rights, may be used instead. Information is provided "AS IS" without warranty of any kind. THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted, if at all, according to the terms and conditions of the agreements (for example, IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. IBM makes no representations or warranties, express or implied, regarding non-IBM products and services. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. © Copyright International Business Machines Corporation 2008. All rights reserved. Note to U.S. Government Users - Documentation related to restricted rights-Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract and IBM Corp. 25 Messaging components © 2007 IBM Corporation 2007 ...
View Full Document

This note was uploaded on 02/09/2012 for the course COMPUTER S a303 taught by Professor None during the Spring '11 term at BEM Bordeaux Management School.

Ask a homework question - tutors are online