Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

End to End Management of Blackberry Enterprise Server


Published on

End to End Management of Blackberry Enterprise Server presented by Alex Ryals CTO of Pepperweed Consulting and Ryan Teichler HP Sales Manager of HP

Published in: Technology
  • Be the first to comment

  • Be the first to like this

End to End Management of Blackberry Enterprise Server

  1. 1. End to End Management of Blackberry Enterprise Server<br />Alex RyalsChief Technology Officer<br />Pepperweed Consulting<br />Ryan Teichler<br />HP Sales Manager<br />Carahsoft<br />
  2. 2. Has this Happened to You?<br />“Why is my email not coming through!!!<br />I need to hire a Blackberry Czar to fix this thing.”<br />
  3. 3. The Problem:Isolated Silos and Event Mgmt<br />Console 1<br />Console 2<br />Management of Blackberry Enterprise Servers<br />Management of everything else (AD, Exchange, SQL Server, etc)<br />There may be a server problem, BUT...<br />The BlackBerry management silo can’t see that<br />So you have two teams working on the problem<br /> Duplication of effort and more cost in IT Operations than there should be<br />Mobile Outage, but why? No visibility to AD issue.<br />Active Directory Issue<br />BES Application Events<br />Server, Network, Storage Events<br />
  4. 4. The Problem:Isolated Silos and Performance<br />Console 1<br />Console 2<br />The result:<br /><ul><li>Blackberry service depends on more than just a high performing Blackberry Enterprise Server
  5. 5. Inefficient IT Operations because no single console for all performance issues
  6. 6. Poor BlackBerry service levels to the business</li></ul>Management of Blackberry Enterprise Servers<br />Management of everything else (AD, Exchange, SQL Server, etc)<br />Mobile Email Slow? No visibility to Exchange issue.<br />Exchange very slow<br />BES Application Events<br />Server, Network, Storage Events<br />
  7. 7. The Customer Challenge Ensuring Dependable ‘Mission Critical’ Mobility<br /><ul><li>BlackBerry Enterprise Services (BESs) don’t exist in isolation
  8. 8. Fixing BlackBerry performance issues can be slow unless you can see whole picture
  9. 9. Costlyduplicate fix efforts if BESevents monitored in isolation
  10. 10. “Whole picture” must includerecent changes and compliance state
  11. 11. Need BES management tightly integrated into same service desk controlled incident process as everything else</li></ul>BlackBerry servers<br />Exchange servers<br />DB Servers<br />Active directory servers<br />Storage<br />Physical servers<br />Network<br />
  12. 12. BES Server ArchitectureComplex Set of Interconnected Systems<br />
  13. 13. We Need a Management and Control System that Provides…<br />End to end monitoring, policy setting and alert management<br />Correlation across BES system components<br />Deep monitoring & management of each BES system component<br />Auto-discovery and update of interrelationships<br />Performance benchmarking<br />“Single pane of glass” for monitoring & control<br />Remote alert and incident management for 7x24 coverage<br />Where can we find this type of end-to-end monitoring of our Blackberry infrastructure?<br />
  14. 14. HP and Research in Motion<br />Blackberry Enterprise Server 5.0<br />HP Operations Manager<br />With the recent partnership between HP and Research in Motion, HP is now providing a full end-to-end monitoring solution for Blackberry Enterprise Server so you are aware of potential issues before they occur.<br />
  15. 15. Blackberry Monitoring Architecture<br />Active Dir SPI<br />Exchange SPI<br />Topology based<br />Event Correlation<br />OS SPI<br />OS SPI<br />Event Mgmt<br />Agent<br />Agent<br />HP BSM<br /> (Operations Manager i & BAC)<br />HP Operations Manager<br />Collected BES discovered topology data and events <br />BES SPI<br />OS SPI<br />SQL SPI<br />OS SPI<br />Agent<br />OS SPI<br />Agent<br />Agent<br />Discovered Topology<br />OS SPI<br />Agent<br />HP Universal<br />CMDB<br />
  16. 16. Health <br />monitoring<br /><ul><li>General BES health
  17. 17. Event and Service monitoring
  18. 18. Log file monitoring and BES</li></ul>health analysis<br />Deploy<br /><ul><li>Allows deployment of BES</li></ul>related monitoring policies<br />Service views<br /><ul><li>HP Service Navigator maps of the</li></ul>Entire BlackBerry Domain<br /><ul><li>Highlight impact of events on</li></ul>the overall BES service<br /><ul><li>Helps focus on most important</li></ul>issues<br />Performance<br />monitoring<br /><ul><li>Messaging server response</li></ul>times<br /><ul><li>BES database response times
  19. 19. Response times per</li></ul>BlackBerry user<br /><ul><li>Delivery times for BlackBerry</li></ul>users<br /><ul><li>Link Latencies
  20. 20. Resource utilization</li></ul>Integration<br /><ul><li>Integrated with HP OMw
  21. 21. The data & alerts are sent to</li></ul>OM from BlackBerry SPI <br /><ul><li>OM can be integrated with </li></ul>other HP Software products to<br />provide a broader solution<br /><ul><li>HP Performance Manager</li></ul>graphs<br />Metrics<br /><ul><li>Graphs for current health &</li></ul>trend analysis<br /><ul><li>More than 30 Metrics to</li></ul>measure health and<br />Performance from SNMP or BMS<br />Functionality of the BlackBerry SPIWhat does the Blackberry SPI do?<br />
  22. 22. BlackBerry SPI:Service Discovery<br />View of discovered BES Services in HP Operations Manager for Windows<br />
  23. 23. BlackBerry SPI: Average Delivery Time Exceeded (Policy)<br />BESPI-00105.1<br />The time taken to deliver an email or calendar message to a BlackBerry device<br />The average delivery time is the difference between the time when a transaction is sent to the device and the time when the device returns an acknowledgement<br />In this example the user “Director” is not getting good service<br />
  24. 24. BlackBerry SPI: Hung Treads on Messaging Agent (Policy)<br />BESPI-00115.1<br />The number of user threads that are detected to be hung<br />In this example there are 30 hung threads. Hung threads can affect mail/calendar delivery performance<br />
  25. 25. BlackBerry SPI Reports:User Average Deliver Time<br />
  26. 26. BlackBerry SPI Reports:Messaging Server Average Response Time<br />
  27. 27. Blackberry SPI:HP Operations Manager Tools<br />
  28. 28. The BES SPI:Advanced Components with HP BSM<br />OMi Event Management Foundation (includes BSM Foundation)<br />OMi Health Perspectives<br />OMi Topology Based Event Correlation<br />HP BSM Platform<br />APM, EUM, BTM, Discovery, SLM, Problem Isolation, etc. <br />OMi Topology Based Event Correlation<br />OMi Health Perspective Views<br />BSM Dashboard Users<br />OMi Event Management Foundation<br />BSM Foundation : Dashboard, SLM, Alerting, MyBSM, UCMDB<br />HP Operations Manager<br />Operations Manager Console Users<br />
  29. 29. Blackberry SPI:HPOperations Manager I (OMi) with advanced correlation<br />HP Operations Manager<br /><ul><li>A client-server application console
  30. 30. Auto-discovery of all the BlackBerry Domain services
  31. 31. Displays performance graphs of collected metrics
  32. 32. Execute tools to manage the BES components</li></ul>HP Operations Manager i<br /><ul><li>Central console for all infrastructure events
  33. 33. Discovered infrastructure components (topology) stored in HP Universal CMDB
  34. 34. Topology based event correlation using causal and symptom events
  35. 35. Leverage Health Indicators to give you quick visibility to issues</li></ul>Discovery & Event Correlation<br />BES Monitoring<br />Collects the discovered topology data and events and sends it to OMi<br />
  36. 36. HP OMi Discovery: Topology View of BES System<br />Discovered components (server, network, applications, storage) from most HP solution are stored in one central CMDB.<br />
  37. 37. HP OMi: Event Management Foundation<br />Provides the core event management functionality in the BSM platform<br />Event lifecycle actions<br />Events Filtered by UCMDB CI views<br />Related CI<br />Dynamically updated CI views<br />Assignment can be automatic<br />
  38. 38. HP OMi: Topology Based Event Correlation<br />Not all problems are caused by the BlackBerry Enterprise Server !<br />Topology based event correlation allows you to pinpoint cause and symptom eventsand to reduce the number of events in the browser<br />Correlation rules can be easily added and modified using the Administration UI (Correlation Manager)<br />Topology based correlation rules make use of the existing topology in the UCMDB which includes not only Blackberry components, but other IT components as well.<br />
  39. 39. HP OMi example of slow database:Topology Based Event Correlation<br />Cause<br />Symptom<br />Issue<br /><ul><li>CPU is bottlenecked on SQL Server
  40. 40. Slow CPU causes slow database queries
  41. 41. BES Dispatcher is impacted by slow database queries</li></ul>Action<br /><ul><li>Assign Event to Database Specialist
  42. 42. BES Dispatcher health will return when database issue is resolved</li></li></ul><li>HP OMi example of Exchange issueTopology Based Event Correlation<br />Cause<br />Symptom<br />Issue<br /><ul><li>Exchange experiences a performance issue with a mailbox store
  43. 43. Mailbox store performance issue causes message delivery slowdown
  44. 44. BES Message Agent is impacted by slow Exchange server</li></ul>Action<br /><ul><li>Assign Event to Exchange Specialist
  45. 45. BES Message Agent health will return when Exchange mailbox store issue is resolved</li></li></ul><li>HP OMi Health Indicators:Blackberry Enterprise Server Message Agent Example<br />
  46. 46. The Blackberry SPI and You<br />Customer Needs<br />Best Practices<br />Customer Benefits<br /><ul><li>Easy to create /edit /deploy monitoring configurations
  47. 47. Monitoring health and performance of BlackBerry Domain in distributed environments
  48. 48. Get alerted before a critical situation happens, like hung threads
  49. 49. Status of SRP gateway and the relay connection
  50. 50. Performance data collection of critical BlackBerry metrics
  51. 51. BlackBerry topology discovery to find the root cause quickly
  52. 52. Color coding on service maps pin-points which services are down on what machines?
  53. 53. Monitor BES components actively to proactive prevent messages from being delayed.
  54. 54. Visualization of BlackBerry Domain
  55. 55. Continuous, nearly real-time monitoring of BlackBerry Enterprise server
  56. 56. Preconfigured alarms / events
  57. 57. Reduced downtime because of root cause capability
  58. 58. Central, easy-to use console for the distributed BlackBerry Domains</li></li></ul><li>The Solution: <br />The BlackBerry Enterprise Server Smart Plug-in<br />1<br />2<br />3<br />All events go to one place.<br />If using OMi, model used to group events and find cause event<br />cause<br />All performance data goes to one place.<br />Can view performance of each item on the model<br />Automatically generate a single topology model of your Blackberry infrastructure<br />symptoms<br />
  59. 59. Monitoring the Complete BES Environment Provides…<br />Simplified monitoring, control and reporting<br />Higher uptime due to early identification and fault detection<br />Lowered TCO to support the BlackBerry ecosystem<br />Single monitoring console for entire BlackBerry and applications environment<br />An End-to-End solution to proactively manage the whole BlackBerry environment<br />
  60. 60. Blackberry Enterprise Server 5.0<br /><br /><br />HP Operations Manager<br />^1745_4000_100__<br />HP Operations Manager I<br />^37673_4000_100__<br />HP Blackberry Smart Plug-In<br />^43278_4000_100__<br />Additional Resources<br />
  61. 61. Q & A<br />