The document provides an overview of enterprise service buses (ESBs). It defines an ESB as a software architecture that provides integration services through messaging and standards-based integration. The key capabilities of an ESB are described as routing, transformation, choreography, orchestration, transaction management, and security. The document outlines the typical components of an ESB including a mediator, service registry, choreographer, and rules engine. It discusses how process choreography relates to the mediator and considerations for their relationship. Open source ESB projects like Mule and ServiceMix are also mentioned.

1. ESB Enterprise Service Bus

3. The ESB as a pattern for SOA

4. Exploring the capabilities of an ESB

5. ESB components

6. Process Choreography and the ESB

7. JSR-208 JBI (Java Business Integration) Specification and the Impact on an ESB

9. Worked on lot of popular frameworks

10. Clients worked so farin USA ….

11. Roadway Express

12. DaimlerChrsyler

13. FreightLiner – A DaimerChrysler company

14. Nissan North America

15. Toyota Motor Sales

16. and finally now @ UCLA

18. I did not create the entire presentation content all by myself.

19. Like java re-usability, I gathered information around the www

20. Presentation is an extract from my fav architect  Mark Richard, an IBM Consultant /Architect. So thanks to all the resources available on the internet … and thanks to Google my favorite search engine.

22. Some questions to consider:

23. Is it a Pattern?

24. Is it a Product?

25. Is it an Architectural Component?

26. Is it a Hardware Component?

27. From Wiki “An enterprise service bus (ESB) consists of a software architecture construct which provides fundamental services for complex architectures via an event-driven and standards-based messaging-engine (the bus)”

30. Sharing of services across the enterprise

31. Ability to separate Business Services from the service implementation.

32. Business Service vs. Implementation ServiceBusiness Service Def Make Payment WSDL Make Payment Business Services are exposed to client as a service name and specified input and output structures. (example: through WSDL) Implementation Services are coded within the Service Providers (example: through Webservices) Process Payment Post BAR Payment Post Housing Payment Java

33. ESB Core capabilities Routing Message Transformation Message Enhancement Protocol Transformation Service Mapping Message Processing Process Choreography Service Orchestration Transaction Management Security

35. Content-based Routing

36. Policy-based Routing

38. XML  XML

39. XML  COBOL Copybook

41. Supplement data not included in original message

42. Data conversion(i.e. spaces to zero)

44. Has both physical connection attributes as well as logical connectivity attributes

45. Examples:

46. SOAP/JMS  IIOP

47. XML/HTTP  CICSMQ

48. XML/HTTP  RMI/IIOP

49. SOAP/MQ ATMI (Application-to-Transaction Monitor Interface)

51. Usually contains the following core information

52. Implementation Service Name

53. Service Protocol and binding information

54. Protocol specific info (i.e. timeouts, failover location)

57. Process Choreography can be though of as a manifestation of a use case or business processEach of the business process nodes can be an Independent business service.

59. Difference between Service Orchestration and Process Choreography is based on the type of service being coordinated

60. Process Choreography  Business Services

62. WS-Coordination

64. The 4 “A’s” of Security

65. Authentication

66. Authorization

67. Auditing

68. Administration

69. ESB should provide authentication, authorization, and auditing

71. An ESB can be broken down into the following components

72. Mediator

73. Service Registry

74. Choreographer

76. Routing

77. Communication

78. Message Transformation

79. Message Enhancement

80. Protocol Transformation

81. Message Processing

82. Error Handling

83. Service Orchestration

84. Transaction Management

87. Message Processing

88. Process Choreography

89. Transaction Management

91. Routing

92. Message Transformation

93. Message Enhancement Specifically Rule based Routing, Message Transformation and Message Enhancement.

95. Advantages

96. Good Performance

97. Good Scalability

99. Choreography as the ESB entry point

100. Mediator as the ESB Entry point

101. Either as an ESB Entry point

102. Recommendation

103. Mediator as the ESB Entry point (Choreography Below)

104. Based on small % of services that must be choreographed

105. Better performance

106. Better Scalability

108. Advantages

109. Good Performance

110. Good Scalability

112. Considerations

113. Performance Issues

114. Maintenance Issues

115. Complexity Issues

117. Considerations

118. Client responsible for determining service characteristics

119. Capabilities shared by multiple ESB components

120. Message Processing

121. Transaction Processing

122. SecurityNo good separation of responsibility within ESB components

124. Advantages

125. Good Performance

126. Good Scalability

128. ESB is an infrastructure component

130. Avoids “Vendor Lock-in”

131. Allows for “Best of Breed” technologies and solutions

132. We can mix Open Source and Commercial solutions

133. We can swap in and out integration services (i.e capabilities) we don’t need, creating a light-weight solution that meets out specific needs

136. Reviewed 10 Core capabilities and what they really mean

137. Reviewed the components that make up an ESB and the capability mapping for each component

138. How Choreography can play a part within an ESB

139. What is JBI all about (Standards based pluggable Architecture)