best practices for managing and monitoring websphere message broker
DESCRIPTION
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 BrokerTRANSCRIPT
![Page 1: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/1.jpg)
Best Practices for Managing and Monitoring WebSphere Message Broker
June 25, 2013Amir Gabrieli, Vice President of Solution Engineering, Correlsense
![Page 2: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/2.jpg)
1. WMB’s role today2. Challenges to managing WMB3. Best practices 4. Correlsense approach5. Summary and Q&A
Agenda
![Page 3: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/3.jpg)
Housekeeping
• Presentation will last 45 minutes• Submit questions via the chat window• Slides will be made available tomorrow
![Page 4: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/4.jpg)
Featured Speaker
Amir GabrieliVP, Solution EngineeringCorrelsense
![Page 5: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/5.jpg)
WMB’S ROLE IN TODAY’S COMPLEX SOLUTIONS
![Page 6: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/6.jpg)
Market Example: Rede D’Or São Luiz
• Largest private hospital network in Brazil with 27 hospitals and 25,000 employees
• Needed to integrate multiple systems and ensure easy access to information
• Uses WMB to:– Automate communication between operational units
– Exchange information between hospitals and with backend operations
– Handle a high volume of information
Case study from IBM: http://www-01.ibm.com/software/success/cssdb.nsf/CS/KPES-97JPWS?OpenDocument&Site=default&cty=en_us
![Page 7: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/7.jpg)
CHALLENGES AROUND MANAGING WMB-BASED SOLUTIONS
![Page 8: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/8.jpg)
Managing WMB in Production is 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 Flows and transactions
![Page 9: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/9.jpg)
The Challenges
• Organizational• Change Management • Transactions Accountability • Production Monitoring
![Page 10: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/10.jpg)
Organizational Challenge
• Different owners … one business service • Often the WMB developer sits in a different
department from the application owner• Message Flow “code” is not always under the
application owner’s control
![Page 11: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/11.jpg)
Organizational Risks/Challenge
• Message Flow code is prone to logical errors • May result in unexpected/unsupported
transaction flows • Message Flows are more complicated than
assumed• Not enough QA/ testing invested for new Message
Flows
![Page 12: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/12.jpg)
Change Management Challenge
• Making and deploying changes in Message Flows is easy … too easy– Dependencies with event sources, event consumers and
other services are not always obvious
– Hard to determine which components will be affected by a change
![Page 13: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/13.jpg)
Change Management Risks/Challenge
• Small/last-minute changes may cause flow incompatibilities
• Often the test cycles for Message Flows are not well defined
![Page 14: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/14.jpg)
Transactions Accountability
• Making sure each transaction is successful and having the ability to explain why other transactions fail
• Risks/challenges:– Typically you won’t be alerted to lost transactions and
Message Flows
– These may result in lost revenue and complications with business partners
![Page 15: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/15.jpg)
Monitoring Challenge
• Existing monitoring solutions provide limited coverage
• WMB’s internal monitoring and standard solutions do 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
![Page 16: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/16.jpg)
Monitoring Risks/Challenge
• Long and complex troubleshooting sessions• Less control over the environment and solution
![Page 17: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/17.jpg)
BEST PRACTICES APPROACH TO MANAGING AND MONITORING WMB-BASED APPLICATIONS
![Page 18: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/18.jpg)
1. Write Logs for Easy Back-Tracking
• Production issues are unavoidable– Provide and use better tracking and logging functionality
• Why?– Easier to track and
troubleshoot in production
– Provides a clear understanding
![Page 19: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/19.jpg)
1. Write Logs for Easy Back-Tracking
AddToInventory
AddToInventory_SOAPInput
InventoryServices
FindInventory_SetFunctionName
Reply_To_Queue
SetMQProperties
SetExpressionToLocalEnvironment
GetInventoryAvailabilityToFindInventoryInput_Transformation
Trace_GetInventoryAvailabilityToFindInventoryInput
SetMQProperties
JMS MQ Transform
SetSOAPReplyIdToJMSCorrelID
JMS Output
Example:• Log when Message Flow start/end/failed• Log when Message Nodes start/end/fail
![Page 20: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/20.jpg)
1. Write Logs for Easy Back-Tracking
Example: • Log which
messages were received/sent
• Log which queues are involved
![Page 21: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/21.jpg)
1. Write Logs for Easy Back-Tracking
Example: • Capture errors
![Page 22: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/22.jpg)
2. Keep Message Flows Lean
• Experienced WMB users tend to keep their Message Flows lean
• Why?– Message Flow syntax can get complicated and hard to
maintain
– Keeping simple Message Flows makes WMB easier to maintain and reuse
![Page 23: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/23.jpg)
3. Keep Logic in the Apps
• Complex logic associated with Message Flows should 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 develop in programming languages
![Page 24: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/24.jpg)
4. Manage the Inter-Dependencies
• Track and manage interdependency mapping between WMB, Message Flow, services and applications
• Why?– Understand who is impacted by changes
– Understand who is impacted by problems
– Increase control over the solution
![Page 25: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/25.jpg)
4. Manage the Inter-Dependencies
Example: • Interdependency between applications, Web-Services, and other
services using WMB
![Page 26: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/26.jpg)
5. No Code Changes in Production
• Changes should never be executed directly on the production environment
• They should be made on a test environment and then moved to production after approval
• Why?– Ensure all changes in production are controlled and
verified by QA
![Page 27: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/27.jpg)
6. Manage Transaction Accountability
• Errors and unexpected flow behaviors will result in lost messages– For business critical solutions, this could cause lost
revenue or complications with partners
• Each transaction should be tracked and audited through the entire IT stack and WMB flows
• Why?– Audit for historical review
– Ensure the application owner can quickly find and handle lost messages and errors
![Page 28: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/28.jpg)
6. Manage Transaction Accountability
![Page 29: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/29.jpg)
6. Manage Transaction Accountability
![Page 30: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/30.jpg)
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
![Page 31: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/31.jpg)
CORRELSENSE APPROACH
![Page 32: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/32.jpg)
SharePath for WMB
• Correlsense SharePath is an enterprise scale transaction centric application management and monitoring solution
• SharePath uses a unique monitoring technology for comprehensive monitoring of WMB-based applications
![Page 33: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/33.jpg)
SharePath WMB Agent
• Complete visibility into WMB Message Flow processing
OS
Core Collector
Execution Group Process
(DataFlowEngine)
WMB Flows/Nodes
WMB Collector
Captures Message Flow
and Message Flow
Node
activity
Captures TCP/IP activity –
incoming and outgoing requests
for a wide range of protocols –
the interaction of WMB with all
other servers
MQ ClientMQ Collector
Captures shared-mem
ory MQ
Activity (Message IDs, queues, etc)
![Page 34: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/34.jpg)
EXAMPLES
![Page 35: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/35.jpg)
Real Time Tracing and Monitoring ofMessage Flows
![Page 36: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/36.jpg)
Deep Dive for WMB Flows
• Log which SQLs and other API calls were called by nodes
![Page 37: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/37.jpg)
Find (Lost) Transactions and Message Flows
![Page 38: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/38.jpg)
Transaction Auto-Detection, Dependency and Topology Mapping
![Page 39: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/39.jpg)
Load and Volume Trending
By Message Flow By Execution Group / Process
By Node (Message Flow Step)
![Page 40: Best Practices for Managing and Monitoring WebSphere Message Broker](https://reader038.vdocuments.site/reader038/viewer/2022102804/54b99c804a7959a4738b4699/html5/thumbnails/40.jpg)
Summary
• WMB is a market leader service bus solution
• Like other service buses it has inherent monitoring challenges
• Best practices and appropriate monitoring solutions are critical