I IBM Software Group IBM Web Sphere Application Server v6 Service integration Technologies: Architecture 叫 ND: DBI%删E IBM Proof of Technology O2005 3M Corporasan IBM Product Introduction Exploration IBM Software Group I Web Sphere software Service Integration Bus Components High Availability and scalability Interoperability Service Integration and JMS Managing Bus Re Managing JMS Resources
1 ® IBM Software Group © 2005 IBM Corporation IBM Proof of Technology IBM Product Introduction + Exploration IBM WebSphere Application Server v6 Service Integration Technologies: Architecture IBM Software Group | WebSphere software WebSphere Application Server v6 2 Agenda Overview Service Integration Bus Components High Availability and Scalability Interoperability Service Integration and JMS Managing Bus Resources Managing JMS Resources Summary
Section Overview IBM Software Group I Web Sphere software Service Integration Technologies as part of ESB WebSphere MQ Backbone nterprise Service Bus provider application requestorapplication
2 IBM Software Group | WebSphere software WebSphere Application Server v6 3 Overview Section IBM Software Group | WebSphere software WebSphere Application Server v6 4 Service Integration Technologies as part of ESB WebSphere MQ Backbone MQI application JMS application WBI adapter Event Broker Enterprise Service Bus Web Services JCA adapter Web Service provider WebSphere Application Server Web Service requestor JMS application Web Service requestor JMS application Mediation Mediation Web Service provider Message Broker Service Integration Bus Service Integration Bus JCA adapter WebSphere Application Server
BM Software Group WebSphere software IBM Service Integration Technologies IBM Service Integration Technologies provide the framework needed to support a Service Oriented Architecture(SoA)and Messaging Oriented Architecture Its an important component of the Enterprise Service Bus (ESB)architecture JMS messaging and Web Services integration are implemented using the Service Integration Technologies IBM Software Group I Web Sphere software Features Multiple messaging APIs and protocols Default messaging provider is a J2EE 1.4 compliant JMS pre >SupportforSoap/jms,Soap/http Flexible qualities of service(QOS)for message delivery Clustering enablement for scalability and High Availability( HA)
3 IBM Software Group | WebSphere software WebSphere Application Server v6 5 IBM Service Integration Technologies IBM Service Integration Technologies provide the framework needed to support a Service Oriented Architecture (SOA) and Messaging Oriented Architecture Its an important component of the Enterprise Service Bus (ESB) architecture JMS messaging and Web Services integration are implemented using the Service Integration Technologies IBM Software Group | WebSphere software WebSphere Application Server v6 6 Features Multiple messaging APIs and protocols Default messaging provider is a J2EE 1.4 compliant JMS provider Support for SOAP/JMS, SOAP/HTTP Flexible qualities of service (QOS) for message delivery Clustering enablement for scalability and High Availability (HA)
BM Software Group WebSphere software Section Service Integration Bus Components IBM Software Group I Web Sphere software Service Integration Bus Integrated asynchronous messaging capability for the leb Sphere platform The"Default JMS Provider"is a J2EE 1.4 compliant JMS provider implemented through the Service Integration Bus WebSphere component that implements bus-style Interoperates with Web Spher re Provides Web Services integration ) Soap/Http SOAP/JMS
4 IBM Software Group | WebSphere software WebSphere Application Server v6 7 Service Integration Bus Components Service Integration Bus Components Section IBM Software Group | WebSphere software WebSphere Application Server v6 8 Service Integration Bus Integrated asynchronous messaging capability for the WebSphere platform The “Default JMS Provider” is a J2EE 1.4 compliant JMS provider implemented through the Service Integration Bus WebSphere component that implements bus-style (interconnected) messaging Interoperates with WebSphere MQ Provides Web Services integration SOAP/HTTP SOAP/HTTPS SOAP/JMS
BM Software Group WebSphere software Bus Members The members of a service integration bus are the application servers within which messaging engines for that bus can run Application Server Cluster When a new Bus Member is defined, one Messaging Engine is automatically created in the corresponding server or Cluster Cluster Messaging Server 1 Server 2 Server 3 IBM Software Group I Web Sphere software Messaging Engines A ME runs inside an Application Server and manages messaging resour Messaging Engines are transparent to application code v6 Application Server Each server or cluster has at least one me for each Bus with which it is associated ME unique within Bus The me has an associated data store for message persistence and overflow Data Store is a jDBC Data Source Store
5 IBM Software Group | WebSphere software WebSphere Application Server v6 9 Bus Members The members of a service integration bus are the application servers within which messaging engines for that bus can run Application Server Cluster When a new Bus Member is defined, one Messaging Engine is automatically created in the corresponding server or Cluster Bus Server 1 Messaging Engine Server 2 Messaging Engine Server 3 Messaging Engine Cluster IBM Software Group | WebSphere software WebSphere Application Server v6 10 Bus Messaging Engines A ME runs inside an Application Server and manages messaging resources Messaging Engines are transparent to application code Each server or cluster has at least one ME for each Bus with which it is associated ME unique within Bus The ME has an associated data store for message persistence and overflow Data Store is a JDBC DataSource v6 Application Server Messaging Engine Dest. Data Store
Buses and Messaging Engines in a Cell Standalone Application Server Network Deployment Cell BuS-1 Server 1 Server A BUs-2 Web Sphere Application Server topology can have multiple buses Each bus can have servers or clusters or both as bus members When a server/cluster is made a bus member, a Messaging Engine is created IBM Software Group I Web Sphere software Destinations Destination Producer Messag Messag Cons Destinations are points of communication for messaging n Producers send messages to destinations Consumers get messages from destinations
6 IBM Software Group | WebSphere software WebSphere Application Server v6 11 Buses and Messaging Engines in a Cell WebSphere Application Server topology can have multiple buses Each bus can have servers or clusters or both as bus members When a server/cluster is made a bus member, a Messaging Engine is created Bus Server 1 Messaging Engine Bus-2 Bus-1 Server A Server C Server B Standalone Application Server Network Deployment Cell Messaging Engine Messaging Engine Messaging Engine Messaging Engine IBM Software Group | WebSphere software WebSphere Application Server v6 12 Destinations Destinations are points of communication for messaging Example: JMS Queues, Topicspace, Web Service endpoints Producers send messages to destinations Consumers get messages from destinations Producer Message Message Consumer Destination
BM Software Group WebSphere software Bus Destinations Bus destination is a virtual place within an SIBus, to which applications(producers, consumers)attach to exchange Types of destinations b Queue-for point-to-point messaging Alias-destination that is an alias for another target destination Foreign-destination that identifies a destination on another bus Temporary-Created and deleted automatically for API specifi created programmatically usually to specify a JMSReply Todestination b Permanent-Created by Administrator Deleted only when Administrator deletes it IBM Software Group I Web Sphere software Destinations and Buses Standalone Application Server Network Deployment Cell Server 1 Server A Messager Destinations are created on the bus and hosted on a Messaging Engine . a queue is hosted by a single Messaging Engine Topic Spaces are hosted by all Messaging Engines on a bus
7 IBM Software Group | WebSphere software WebSphere Application Server v6 13 Bus Destinations Bus destination is a virtual place within an SIBus, to which applications (producers, consumers) attach to exchange messages Types of destinations Queue - for point-to-point messaging Topicspace - for publish-subscribe messaging Alias - destination that is an alias for another target destination Foreign - destination that identifies a destination on another bus Bus destinations can be permanent or temporary Temporary -Created and deleted automatically for API specific destinations created programmatically usually to specify a JMSReplyTodestination within a message Permanent –Created by Administrator Deleted only when Administrator deletes it. IBM Software Group | WebSphere software WebSphere Application Server v6 14 Destinations and Buses Destinations are created on the bus and hosted on a Messaging Engine A queue is hosted by a single Messaging Engine TopicSpaces are hosted by all Messaging Engines on a bus Bus Server 1 Bus-2 Bus-1 Server A Server C Server B Standalone Application Server Network Deployment Cell Messaging Engine Messaging Engine Messaging Engine Messaging Engine Messaging Engine
Quality of Service(QOS)specification Qos can be specified on )A Destination Maximum QOS can be defined on a Destination(e. g. this Destination can only accept non-persistent messages A message By individual Producers, typically under application control via a combination of API calls( e.g. JMS Persistent or Non-persistent) and the Connection Factory used (which defines the Persistent/NonPersistent IBM Software Group I Web Sphere software Destination Quality of Service for Reliability BEST EFFORT NONPERSISTENT b Messages are never written to disk b throw away messages if memory cache over-runs EXPRESS NONPERSISTENT cache overruns, but are not kept over server restarts b No acknowledgement that the ME has received the message RELIABLE NONPERSISTENT sage that the client raits for. before turning to the application with an OK RELIABLE PERSISTENT rmal processing, and stay persisted over server restarts. aung b If the server fails, messages are lost if they are held in the cache at the ASSURED PERSISTENT b Highest degree of reliability where assured delivery is supported
8 IBM Software Group | WebSphere software WebSphere Application Server v6 15 Quality of Service (QOS) specification QOS can be specified on A Destination Maximum QOS can be defined on a Destination (e.g. this Destination can only accept non-persistent messages) A message By individual Producers, typically under application control via a combination of API calls (e.g. JMS Persistent or Non-persistent) and the Connection Factory used (which defines the Persistent/NonPersistent Mapping) IBM Software Group | WebSphere software WebSphere Application Server v6 16 Destination Quality of Service for Reliability BEST_EFFORT_NONPERSISTENT Messages are never written to disk throw away messages if memory cache over-runs EXPRESS_NONPERSISTENT Messages are written asynchronously to persistent storage if memory cache overruns, but are not kept over server restarts No acknowledgement that the ME has received the message RELIABLE_NONPERSISTENT Same as Express_Nonpersistent, except, we have a low level acknowledgement message that the client code waits for, before returning to the application with an OK or not OK response RELIABLE_PERSISTENT Messages are written asynchronously to persistent storage during normal processing, and stay persisted over server restarts. If the server fails, messages are lost if they are held in the cache at the time of failure. ASSURED_PERSISTENT Highest degree of reliability where assured delivery is supported High Low Performance Low High Reliability
BM Software Group WebSphere software Foreign Bus An enterprise might deploy multiple interconnected beg, separately administered buses for each department Gateway link A bus nect to oth buses which are known foreign buses By way of a gateway link CELL Gateway links are created dministrative IBM Software Group I Web Sphere software Mediation The ability to manipulate a message at a destination b Transforming a message from one format into another Routing messages to one or more target destinations that were not specifie by the sending application Augmenting messages by adding data from a data source Mediation attached administratively to a Destination Built from Mediation subcomponents(Mediation Beans) Messa Message Mediation Handler List
9 IBM Software Group | WebSphere software WebSphere Application Server v6 17 Foreign Bus An enterprise might deploy multiple interconnected messaging buses for organizational reasons e.g., separately administered buses for each department A bus can connect to other buses which are known as foreign buses By way of a gateway link Gateway links are created administratively Bus B Gateway link Bus-1 Server A ME Bus A Bus-2 Server D ME Server C ME Server B ME IBM Software Group | WebSphere software WebSphere Application Server v6 18 Mediation The ability to manipulate a message at a destination Transforming a message from one format into another. Routing messages to one or more target destinations that were not specified by the sending application. Augmenting messages by adding data from a data source. Distributing messages to multiple target destinations. Mediation attached administratively to a Destination Built from Mediation subcomponents (Mediation Beans) Mediation Handler List Destination Messages Messages
BM Software Group WebSphere software Section High Availability and Scalability IBM Software Group I Web Sphere software High Availability Destinations can be associated Service Integration Bus with a Bus Member of type Cluster Server1 Server2 In the case of failure . a Messaging Engine can started on another cluster member and recover the For messaging to continue, the data store must be accessible from the server to which the me fails
10 IBM Software Group | WebSphere software WebSphere Application Server v6 19 High Availability and Scalability High Availability and Scalability Section IBM Software Group | WebSphere software WebSphere Application Server v6 20 Service Integration Bus High Availability Destinations can be associated with a Bus Member of type “cluster” In the case of failure, a Messaging Engine can be started on another cluster member and recover the destination For messaging to continue, the data store must be accessible from the server to which the ME fails over Cluster Server1 Server2 Data Store Bus Destination Messaging Engine Messaging Engine