Best Practices for Managing and Monitoring WebSphere Message Broker


Published on

WebSphere Message Broker serves as a transactional backbone for many IT organizations yet introduces complexity around integrating, managing and monitoring messaging-based solutions. This results in lost message flows and stalled transactions. Join Correlsense for an online seminar which teaches holistic management and monitoring solutions for gaining visibility into and taking control of WMB. We discuss:

-How to identify key implementation and management challenges for WMB 6, 7 or 8
-A new approach to locating stalled transactions, understanding application dependencies and monitoring message flows
-Real world case studies and a live demo that illustrate ways to gain deeper visibility into your WebSphere Message Broker

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Best Practices for Managing and Monitoring WebSphere Message Broker

  1. 1. Best Practices for Managing andMonitoring WebSphere MessageBrokerJune 25, 2013Amir Gabrieli,Vice President of Solution Engineering,Correlsense
  2. 2. 1. WMB’s role today2. Challenges to managing WMB3. Best practices4. Correlsense approach5. Summary and Q&AAgenda
  3. 3. Housekeeping• Presentation will last 45 minutes• Submit questions via the chat window• Slides will be made available tomorrow
  4. 4. Featured SpeakerAmir GabrieliVP, Solution EngineeringCorrelsense
  6. 6. Market Example: Rede D’Or São Luiz• Largest private hospital network in Brazil with 27hospitals and 25,000 employees• Needed to integrate multiple systems and ensureeasy access to information• Uses WMB to:– Automate communication between operational units– Exchange information between hospitals and withbackend operations– Handle a high volume of informationCase study from IBM:
  8. 8. Managing WMB in Productionis Challenging• WMB comes with inherent challenges– Acts as a hub for business critical transactions– Mediates between services and protocols• Risks include:– Losing critical business transactions– Failing critical business transactions– General outages– Poor performance of Flowsand transactions
  9. 9. The Challenges• Organizational• Change Management• Transactions Accountability• Production Monitoring
  10. 10. Organizational Challenge• Different owners … one business service• Often the WMB developer sits in a differentdepartment from the application owner• Message Flow “code” is not always under theapplication owner’s control
  11. 11. Organizational Risks/Challenge• Message Flow code is prone to logical errors• May result in unexpected/unsupportedtransaction flows• Message Flows are more complicated thanassumed• Not enough QA/ testing invested for newMessage Flows
  12. 12. Change Management Challenge• Making and deploying changes in Message Flowsis easy … too easy– Dependencies with event sources, event consumers andother services are not always obvious– Hard to determine which components will be affected bya change
  13. 13. Change Management Risks/Challenge• Small/last-minute changes may cause flowincompatibilities• Often the test cycles for Message Flows are notwell defined
  14. 14. Transactions Accountability• Making sure each transaction is successful andhaving the ability to explain why othertransactions fail• Risks/challenges:– Typically you won’t be alerted to lost transactions andMessage Flows– These may result in lost revenue and complications withbusiness partners
  15. 15. Monitoring Challenge• Existing monitoring solutions provide limitedcoverage• WMB’s internal monitoring and standard solutionsdo not effectively address these challenges– Most focus on WMB and MQ performance– Do not directly monitor the run-time execution of flows– Or the interdependencies in the environment
  16. 16. Monitoring Risks/Challenge• Long and complex troubleshooting sessions• Less control over the environment and solution
  18. 18. 1. Write Logs for Easy Back-Tracking• Production issues are unavoidable– Provide and use better tracking and logging functionality• Why?– Easier to track andtroubleshoot inproduction– Provides a clearunderstanding
  19. 19. 1. Write Logs for Easy Back-TrackingAddToInventoryAddToInventory_SOAPInputInventoryServicesFindInventory_SetFunctionNameReply_To_QueueSetMQPropertiesSetExpressionToLocalEnvironmentGetInventoryAvailabilityToFindInventoryInput_TransformationTrace_GetInventoryAvailabilityToFindInventoryInputSetMQPropertiesJMS MQ TransformSetSOAPReplyIdToJMSCorrelIDJMS OutputExample:• Log when Message Flow start/end/failed• Log when Message Nodes start/end/fail
  20. 20. 1. Write Logs for Easy Back-TrackingExample:• Log whichmessages werereceived/sent• Log whichqueues areinvolved
  21. 21. 1. Write Logs for Easy Back-TrackingExample:• Capture errors
  22. 22. 2. Keep Message Flows Lean• Experienced WMB users tend to keep theirMessage Flows lean• Why?– Message Flow syntax can get complicated and hard tomaintain– Keeping simple Message Flows makes WMB easier tomaintain and reuse
  23. 23. 3. Keep Logic in the Apps• Complex logic associated with Message Flowsshould be pushed to the application components• Avoid developing complex logic within the flow• Why?– Keep your Message Flows lean– Keep your applications decoupled– Complex validation tests and logic are easier to developin programming languages
  24. 24. 4. Manage the Inter-Dependencies• Track and manage interdependency mappingbetween WMB, Message Flow, services andapplications• Why?– Understand who is impacted by changes– Understand who is impacted by problems– Increase control over the solution
  25. 25. 4. Manage the Inter-DependenciesExample:• Interdependency between applications, Web-Services, and otherservices using WMB
  26. 26. 5. No Code Changes in Production• Changes should never be executed directly on theproduction environment• They should be made on a test environment andthen moved to production after approval• Why?– Ensure all changes in production are controlled andverified by QA
  27. 27. 6. Manage Transaction Accountability• Errors and unexpected flow behaviors will resultin lost messages– For business critical solutions, this could cause lostrevenue or complications with partners• Each transaction should be tracked and auditedthrough the entire IT stack and WMB flows• Why?– Audit for historical review– Ensure the application owner can quickly find and handlelost messages and errors
  28. 28. 6. Manage Transaction Accountability
  29. 29. 6. Manage Transaction Accountability
  30. 30. 7. Have Proper Monitoring Solutions• You need to monitor:– WMB– MQ– Message Flows– Business Transactions• Why?– WMB-based solutions have many weak spots– Ensure smooth operation and fast reaction to issues
  32. 32. SharePath for WMB• Correlsense SharePath is an enterprise scaletransaction centric application management andmonitoring solution• SharePath uses a unique monitoring technologyfor comprehensive monitoring of WMB-basedapplications
  33. 33. SharePath WMB Agent• Complete visibility into WMB Message FlowprocessingOSCore CollectorExecution GroupProcess(DataFlowEngine)WMB Flows/NodesWMB CollectorMQ ClientMQ Collector
  34. 34. EXAMPLES
  35. 35. Real Time Tracing and Monitoring ofMessage Flows
  36. 36. Deep Dive for WMB Flows• Log which SQLs and other API calls were called by nodes
  37. 37. Find (Lost) Transactions andMessage Flows
  38. 38. Transaction Auto-Detection,Dependency and Topology Mapping
  39. 39. Load and Volume TrendingBy Message Flow By Execution Group /ProcessBy Node(Message Flow Step)
  40. 40. Summary• WMB is a market leaderservice bus solution• Like other service buses it hasinherent monitoring challenges• Best practices and appropriatemonitoring solutions are critical
  41. 41. Questions?More