1 / 14

Enterprise Performance Management

Enterprise Performance Management. End-to-end enterprise wide systems monitoring project. Kathy Moore Harley-Davidson Motor Company May 23, 2006. Outline. Project Drivers State of Performance Monitoring before EPM project Project Scope and Objectives Solution Design Architecture

clay
Download Presentation

Enterprise Performance Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Performance Management End-to-end enterprise wide systems monitoring project Kathy Moore Harley-Davidson Motor Company May 23, 2006

  2. Outline • Project Drivers • State of Performance Monitoring before EPM project • Project Scope and Objectives • Solution Design • Architecture • Implementation • Challenges and Lessons Learned • Questions • Demo

  3. Project Drivers • Harley-Davidson used multiple tools at various sites for performance monitoring • Capacity and availability information was often unavailable or difficult to gather • No mechanism for tying hardware or service related failures to key business processes • Interdependencies between various applications unavailable or difficult to gather • Current monitoring is reactive -- when systems are down, we are notified by end users • Not all servers were being monitored • Notifications and alerts were only sent to a small number of individuals

  4. Monitoring Before EPM Project • Juneau (Wisconsin) • BMC Patrol – selected servers, application monitoring • MOM – Active Directory, Exchange • Homegrown Monitoring Tools – applications • Various open source tools – network monitoring • York (Pennsylvania) • Spectrum – network monitoring • Other Sites • No form of monitoring for most servers No correlation of events between sites No sharing of monitoring information No end to end performance data

  5. Scope Single monitoring tool (suite of tools) for entire enterprise including subsidiaries All platforms and operating systems: iSeries, pSeries, Intel, virtual servers OS400, Unix, AIX, Windows, Linux Network components Validate and apply knowledge from BMC Patrol, MOM, and Spectrum tools to Tivoli toolset Objectives Proactive systems monitoring for all servers Systems availability reporting Historical performance data for trend analysis Capacity planning Enable measurement and reporting on SLA/OLA compliance Provide processes for developing application-specific monitoring Provide business view of service availability for key business processes Project Scope & Objectives

  6. Solution Design • Gathered requirements by listing capabilities that exist in tools that were to be replaced • Additional requirements gathered from realistic wish-lists from server support team, DBAs, others • Engaged IBM resources for formal solution design • Each of the requirements were mapped back to a IBM tool that was to address the requirement • Components identified for inclusion in the project: • IBM Tivoli Management Framework v4.1.1 (for ITEC) • IBM Tivoli Enterprise Console (ITEC) v3.9 • IBM Tivoli NetView (ITN) v7.1.4 • IBM Tivoli Monitoring (ITM) v6.1 • ITM for Messaging and Collaboration v6.1 • ITM for Databases v6.1 • ITM for Active Directory v6.1 • IBM Tivoli Composite Application Manager for Response Time Tracking v6.0 • IBM WebSphere Studio Application Monitor v3.2 • IBM Tivoli Data Warehouse 2.1

  7. Architecture • IBM Tivoli Monitoring • HUB and Remote TEMS are on AIX / pSeries • Remote TEM local to data center due to bandwidth availability

  8. Architecture • Tivoli Enterprise Portal • TEPS server is Windows 2003 server

  9. Architecture • Tivoli Data Warehouse • Database is DB2 on AIX • Also houses TEC database and CAMfRTT database • Warehouse proxy is windows 2003 server

  10. Architecture • Event Integration AlarmPoint: Events flow out of TEC and are routed to appropriate individuals via AlarmPoint integration

  11. Architecture • Hardware implemented as recommended in solution design • * Additional server was required for SNMP adapter • * Does not include hardware for high availability or fail over which are to be addressed after initial implementation

  12. Implementation • Phase 1 – 1st half of 2006 “focus on base monitoring” • IBM Tivoli Monitoring 6.1 • OS and Database • Tivoli Enterprise Console with alerts via AlarmPoint • NetView • SNMP integration with Insight Manager • SAP monitoring • Phase 2 – 2nd half of 2006 “focus on adding capability” • ITCAMfRTT • WebLogic and WebSphere application monitoring • IBM Service Bus monitoring • “Other” application monitoring • IBM Tivoli Monitoring • Active Directory, Exchange, Virtual Servers

  13. Challenges & Lessons Learned Challenges: • Aggressive timeline • New IBM product release • Limited skills in Unix and DB2 • Internal resource constraints Lessons Learned: Timeline was too aggressive; implementation of components took 3 x longer than planned. New product release resulted in IBM resource expertise shortages. Did not include test environment in the solution design and project scope - test environment should mimic production. Ensure availability of dedicated internal resources. Schedule IBM product training before implementation.

  14. Questions?

More Related