Boosting Productivity by Providing Self-Service for WebSphere MQ
•
0 likes•766 views
The document describes how self-service access to WebSphere MQ can boost productivity by allowing stakeholders like application developers and support staff to perform tasks without involving the middleware team. It discusses designing self-service solutions that are safe, secure, simple and scalable. Examples of self-service capabilities include observing queue behavior, viewing messages, creating test data and managing objects like queues. The goal is to increase opportunities for stakeholders to serve their own needs while protecting the system.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Boosting Productivity by Providing Self-Service for WebSphere MQ
Similar to Boosting Productivity by Providing Self-Service for WebSphere MQ (20)
More from jKool
More from jKool (11)
Recently uploaded
Recently uploaded (20)
Boosting Productivity by Providing Self-Service for WebSphere MQ
- 1. How Self Service for WebSphere MQ Boosts Productivity
- 2. Introduction
- 3. AutoPilot® Company Overview Founded in 1994 by David Mavashev, CEO 3
- 4. AutoPilot® Company Overview Founded in 1994 by David Mavashev, CEO Vision: Built the first-to-market solution for management and monitoring of MQ Series Provide the best of breed solution for middleware-centric application performance management – with analytics baked-in 4
- 5. AutoPilot® Company Overview Founded in 1994 by David Mavashev, CEO Vision: Built the first-to-market solution for management and monitoring of MQ Series Provide the best of breed solution for middleware-centric application performance management – with analytics baked-in Global reach: Headquarters in Melville, NY Office in North America, EMEA, Latin America & South America 5
- 7. AutoPilot® Over 200 companies rely on Nastel since 1994 5
- 9. AutoPilot® Why customers chose Nastel AutoPilot® Best-of-Breed Middleware management solution We are the experts – 18 years of best practices built-in Single architecture across all middleware, distributed and mainframe: MQ family, DataPower, TIBCO & Solace Monitor Web Services in real-time 9
- 10. AutoPilot® Why customers chose Nastel AutoPilot® Best-of-Breed Middleware management solution We are the experts – 18 years of best practices built-in Single architecture across all middleware, distributed and mainframe: MQ family, DataPower, TIBCO & Solace Monitor Web Services in real-time Application Performance Analytics Detect problems before there is impact • Reduces ticket backlog, support costs and raises customer satisfaction • End “eyes-on-screen monitoring” • Solve the problem of too much data complexity – old-school analytics just can’t get it done Compliance – helping customers achieve Dodd-Frank Trade Reporting, HIPAA, internal 10
- 11. AutoPilot® Why customers chose Nastel AutoPilot® Best-of-Breed Middleware management solution We are the experts – 18 years of best practices built-in Single architecture across all middleware, distributed and mainframe: MQ family, DataPower, TIBCO & Solace Monitor Web Services in real-time Application Performance Analytics Detect problems before there is impact • Reduces ticket backlog, support costs and raises customer satisfaction • End “eyes-on-screen monitoring” • Solve the problem of too much data complexity – old-school analytics just can’t get it done Compliance – helping customers achieve Dodd-Frank Trade Reporting, HIPAA, internal Rationalization or Consolidation Reduce number of middleware monitoring vendors… 11
- 12. 12 Nastel APWMQ Capabilities APWMQ Configuration Management Configuration Management Database Change Management Message Management Find, Fix & Reroute View, Edit, Move & Replay Performance Monitoring Performance Automation History & Reporting Capacity Planning Accounting & Statistics Transaction Management Track, Audit & Monitor Transaction Management Database Extended Access Self Service Application Access
- 13. Self Service Presentation Watch the video
- 14. About the Presenter Richard G. Nikula VP of Product Development and Support Involved in “MQ” since early 90’s Primarily at the technology layer WebSphere MQ Certified Application and Administration 14
- 15. Overview In this session, you will learn how enabling various stakeholders with secure, role-based self-service access to WMQ leads to improved availability for applications, a reduction in the frequency and duration of incidents involving middleware, and a boost in the productivity of the entire Middleware Team. Agenda • Introduction to Self Service • Scenarios and examples using Self Service • Conclusion 15
- 16. Self Service
- 17. Self Service Self service is the practice of serving oneself... Common examples include many gas stations, where the customer pumps their own gas rather than have an attendant do it... Automatic Teller Machines (ATMs) in the banking world have also revolutionized how people withdraw and deposit funds; most stores in the Western world, where the customer uses a shopping cart in the store, placing the items they want to buy into the cart and then proceeding to the checkout counter/aisles; or at buffet-style restaurants, where the customer serves their own plate of food from a large, central selection. Source: Wikipedia 17
- 18. Self Service Requirements Safe • Oregon and New Jersey do not allow self service gas and one key reason is safety • A survey conducted by the Petroleum Equipment Institute showed approximately two-thirds of the documented cases of gas pump fires involved returning to the driver's seat. Secure • ATM and online account security are obvious examples. • Only those authorized to complete the transaction should be able to. Simple • Stakeholders may have little or no training • Interface should be intuitive and guide them to the right actions Scalable • Have to be able to handle the volume of consumers • Higher usage can be expected 18
- 19. Why the Interest in Self Service in WebSphere MQ? Drivers for Self Service in WebSphere MQ • Decreasing middleware staff • Expanding duties of the middleware staff • Stakeholders Increasing (development, operations, support) • Increased complexity of the applications 19
- 20. Stakeholders and Benefits Application Support Application Support Application Development Application Development Middleware Team Middleware Team Enterprise Architect Enterprise Architect Application Owner Application Owner User Acceptance Testing Improve quality of new releases Compare real behavior with expectations 20 Monitor applications Improve processes Lower costs Prevent performance problems Identify root cause of performance issues Faster time to repair (MTTR) Proactive Middleware Monitoring in DEV, TEST and PROD
- 21. Types of Self Service Access Self service should provide application support, DevOps, or operations the ability to: • View queue status and depth, channel usage • Examine queues, channels, queue managers, and subscriptions • Browse and manipulate application messages • Act on application specific messages (move, copy, edit, route, replay, create) 21
- 22. Self Service Summary What is our Objective? To increase the number of opportunities for the stakeholders of WebSphere MQ (and related technologies) to service themselves as long as the methods that are: • Safe • Protect the systems from damage • Secure • Can only do what are authorized to do • Simple • Easy to deploy and use • Scalable • Large stakeholder population 22
- 24. WebSphere MQ 24 WebSphere MQ Input Output To most stakeholders, WebSphere MQ is a black box…
- 25. WebSphere MQ is Broken 25 WebSphere MQ Input “WebSphere MQ is broken…, can you fix it?”
- 27. Disadvantages for Using for MQ Explorer for Self Service • Eclipse client required • Can potentially see and do more than needed • Problems not easily visible • Opening ports and client channels required27 SimpleSimple SafeSafe SecureSecure ScalableScalable
- 28. Using a Self Service Dashboard 28
- 29. Using a Self Service Dashboard 29
- 30. Advantages for Using for Self Service Dashboard • Web enabled • Restrict view and actions to required functions only • Typical problems highlighted • Describe the expected results • Link to existing run books and information • If they still need to contact middleware team • Problem diagnosis already started 30 SimpleSimple SafeSafe SecureSecure ScalableScalable
- 31. WebSphere MQ is Slow 31 WebSphere MQ Input “WebSphere MQ is slow…, can you fix it?” OutputOutput
- 32. Using a Self Service Dashboard to Observe Behavior Real time observation… 32
- 33. Using a Self Service Dashboard to Observe Behavior To see the applications and queues… 33
- 34. Using a Self Service Dashboard to Observe Behavior In context… 34
- 35. Using a Self Service Dashboard to Observe Behavior And identify hot spots… 35
- 36. Using a Self Service Dashboard to Observe Behavior And problem areas. 36
- 37. Using a Self Service Dashboard to Observe Behavior With the ability to observe behavior over time 37
- 38. What Kind of Requests Are Being Processed 38 Input “What kind of requests are being processed?”
- 39. Secure Access to Just the Queues Needed Facilities needed - Secure access - Observe queue depth - View message details 39
- 40. Secure Access to Just the Queues Needed Facilities needed - Secure access - Observe queue depth - View message details 40
- 41. Secure Access to the Information Needed Facilities needed - Quick access to objects required - View queue status - View definition information if required 41
- 42. I Need a New Queue Created 42 Input “I need a new queue created to test with…”
- 43. Secure Access to Actions Facilities needed - Secure access to the actions needed - Easy navigation and usage 43
- 44. Secure Access to Actions Facilities needed - Secure access to the actions needed - Easy navigation and usage 44
- 45. I Need a New Queue Created 45 Input “I need to simulate test data…”
- 46. Secure Access to Messages Facilities needed • Create new messages • Copy Messages to another queue • Move Messages to another queue • Edit Message Content • Delete Messages • Find Messages based on content • Save Messages to File • Read Messages from File (formatted or simple text) 46
- 47. Secure Access to Messages Facilities needed • View Payload • Restrict Payload • Edit Payload 47
- 48. Secure Access to Messages Facilities needed • Create new messages • Copy Messages to another queue • Move Messages to another queue • Edit Message Content • Delete Messages • Find Messages based on content • Save Messages to File • Read Messages from File (formatted or simple text) 48
- 50. Full Function Facilities needed • All WebSphere MQ object • Secure access • Stakeholder specific view 50
- 51. Summary
- 52. Self Service Summary Increase the opportunities for the stakeholders of WebSphere MQ (and related technologies) will reduce the effort required from the middleware team but must be: • Safe • Doesn’t make things worse • Secure • Doesn’t compromise the systems • Simple • Your mother could understand it • Scalable • Scale shouldn’t limit usage 52
- 53. w w w . n a s t e l . c o m Thank You! Questions: info@nastel.com