BMC項(xiàng)目管理方法

1、BMC Performance Manager Console 7.x: Administering Part 2Module 2: Implementing a BPM Console Project 2006 BMC Software, Inc. All rights reserved.2Module ObjectivesDescribe the phases of an implementation projectPlan the implementation processLesson 1: Phases of Implementation 2006 BMC Software, Inc

2、. All rights reserved.4ObjectivesOverview of the implementation projectDescribe the phases of an implementation project 2006 BMC Software, Inc. All rights reserved.5Overview of the Implementation ProjectDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Ph

3、ase 3Phase 4Phase 5 2006 BMC Software, Inc. All rights reserved.6Phase 1 Design and PlanIdentify business processes and priorities Identify applications that support the business processes, transfer priorities Identify systems where various applications reside, include dependencies, and transfer pri

4、orities Design management processes, include tools and responsibilitiesUnderstand organizational constraintsUnderstand the technical environmentDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5Design and Plan 2006 BMC Software, Inc. All rights rese

5、rved.7Phase 2 Build and Test PrototypeInstall Agents on systems with applications that best represent the target environmentInstall PATROL Consoles Learn how to use the tools Develop configuration prototypes Develop any new Knowledge Modules (KMs) for un-instrumented applicationsDesign and PlanDeplo

6、yBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5 2006 BMC Software, Inc. All rights reserved.8Phase 3 DeployInstall the BMC Distribution Server (DS)Install the DS ClientsCreate installation packages Install production Agents Install KMs Start the Agent

7、s automaticallyVerify “vanilla” systems are operationalDeploy custom KMsDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5 2006 BMC Software, Inc. All rights reserved.9Phase 4 ConfigureConfigure PATROL Agents Parameters on Thresholds

8、off Agent operational parametersAccess and security Set up console Access Control Lists (ACLs) Set up aliases/impersonations to match Agent ACLs Set up event/alert managementDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5 2006 BMC

9、Software, Inc. All rights reserved.10Phase 5 Test, Improve, and MaintainPhase 5 lasts FOREVER! Your steady state processes are executingDuring this phase: Measure your processes Make improvements Look for ways to improveDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and Maintai

10、nPhase 1Phase 2Phase 3Phase 4Phase 5Lesson 2: Planning the Implementation 2006 BMC Software, Inc. All rights reserved.12ObjectivesPlan the implementation processAnalyze requirementsDefine a design solutionPerform a physical mapping of the proposed design solution for different serversDefine an imple

11、mentation plan 2006 BMC Software, Inc. All rights reserved.13Planning the Implementation ProcessAnalysisLogical designPhysical mappingImplementation planDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5Design and Plan 2006 BMC Software, Inc. All ri

12、ghts reserved.14AnalysisIdentify project stakeholdersDiagram the enterprise to be managed by BMC Performance Manager ConsoleCollect and record high-level sizing data for each management domain 2006 BMC Software, Inc. All rights reserved.15Project StakeholdersIdentify the people directly involved wit

13、h: Initial deployment and installation of BMC Performance Manager Console BMC Performance Manager Console manages node configuration and change management Ongoing user management, availability, and performance of PATROL Central infrastructure Handling events and exception conditions raised by BMC Pe

14、rformance Manager Console 2006 BMC Software, Inc. All rights reserved.16Diagram the EnterpriseFirewallFirewallFirewallHoustonNew YorkAustin100 Mbps (all)T1 (all) IT OPS 3 PC Windows users 500 managed nodes Secondary IT OPS 3 PC Windows users 2 PC Web users 40 managed nodes 400 managed nodes 2 causal

15、 PC Web usersMainCore, Inc. Enterprise 2006 BMC Software, Inc. All rights reserved.17Location AnalysisPATROL Location Analysis WorksheetLocation Name: HoustonIs this location isolated by a network firewall? YesSpeed and reliability of LAN/WAN connectivity to this location: T1, reliableManaged Node I

16、nformationNumber of managed nodes at this location: 500KMs to be used at this location:1. KM for UNIX6.2. KM for Windows7.3. KM for Oracle8.4. KM for Event Management9.5. KM for MS Exchange (2 servers)10. 2006 BMC Software, Inc. All rights reserved.18Location Analysis (Continued)Additional Infrastru

17、cture ServicesWill BMC Performance Manager Reporting aggregate data from managed nodes at this location? YesWill PATROL Agents at this location forward events to an event management tool? YesIf so, indicate which event management tool: PATROL Enterprise ManagerVisualization InformationTypical number

18、 of KMs used on each managed node: 3 (OS, Oracle, KM for EM)Typical number of managed objects on each managed node: 1800 (2 * 900)Number of PATROL Central Operator Microsoft Windows Edition consoles: 3Number of PATROL Central Operator Web Edition users (daily / infrequently): 0Number of concurrent P

19、ATROL Central Operator console sessions: 3Typical number of managed nodes in each Management Profile: 80Will Management Profiles include nodes at other locations? YesIf so, indicate which other locations: Austin, New YorkTypical number of managed objects in each Management Profile: 144.000 (1800 * 8

20、0)Estimated total number of concurrent managed objects: 432.000 (144.000 * 3) 2006 BMC Software, Inc. All rights reserved.19Location Analysis (Continued) 2006 BMC Software, Inc. All rights reserved.20Analysis ToolsStakeholder Roster Worksheet Stakeholder Roster Worksheet.docLocation Analysis Workshe

21、et PATROL Location Analysis Worksheet.doc 2006 BMC Software, Inc. All rights reserved.21Logical DesignLocation of PATROL Central infrastructure servicesNumber of services needed 2006 BMC Software, Inc. All rights reserved.22RTcloud Logical Design500 managed nodesRTserverRTserverConsole ServerRTserve

22、rRTserverPCWebBrowser UsersPCWin UsersMainCore, Inc. Houston Location 2006 BMC Software, Inc. All rights reserved.23RTserver Design ConsiderationsDesign a self-contained RTcloud for each location with 50 or more managed nodesNo RTcloud should include more than 500-700 managed nodesTypically, an RTcl

23、oud will need no more than two RTservers (a primary and a backup)RTservers should be geographically close to the client computers they supportPlace RTservers on the same side of a firewall as their connected clients 2006 BMC Software, Inc. All rights reserved.24RTserver Design Considerations (Contin

24、ued) 2006 BMC Software, Inc. All rights reserved.25RTserver Design Considerations (Continued) 2006 BMC Software, Inc. All rights reserved.26Visualization DesignWhich PATROL Central console is appropriate?Which locations need PATROL Console Servers?Is one PATROL Console Server enough? 2006 BMC Softwa

25、re, Inc. All rights reserved.27Which PATROL Central Console is Appropriate?PATROL Central Operator Microsoft Windows Edition Visualize larger numbers of managed nodesPATROL Central Operator Web Edition No more than 200 managed nodes Limit profiles to fewer than 100 managed nodes 2006 BMC Software, I

26、nc. All rights reserved.28Which Locations Need PATROL Console Servers?Location with the highest concentration of managed nodesLocation with console users 2006 BMC Software, Inc. All rights reserved.29Which Locations Need PATROL Console Servers? (Continued) 2006 BMC Software, Inc. All rights reserved

27、.30Is One PATROL Console Server Enough?Number of concurrent console sessions Max. 25 (32-bit) Max. 100 (64-bit)Number of managed objects in concurrent Management Profiles Max. 3 million (32-bit) Max. 10 million (64-bit) 2006 BMC Software, Inc. All rights reserved.31Is One PATROL Console Server Enoug

28、h? (Continued) 2006 BMC Software, Inc. All rights reserved.32PATROL Console Server Failover ConsiderationsTwo ways to provide redundancy Install on high-availability cluster hardware Store the configuration files on a shared disk Define a cluster failover package Install a secondary PATROL Console S

29、erver on a separate node Use the online backup feature to periodically snapshot data from the primary PATROL Console Server 2006 BMC Software, Inc. All rights reserved.33PATROL Console Server Failover Considerations (Continued) 2006 BMC Software, Inc. All rights reserved.34PATROL Central Operator We

30、b Edition PlacementInstall PATROL Central Operator Web Edition on the same node as the PATROL Console ServerAllow no more than 20 concurrent browser sessionsOnly one instance of PATROL Central Operator Web Edition may be installed on any single node 2006 BMC Software, Inc. All rights reserved.35Visu

31、alization Performance ConsiderationsPATROL Agent managed nodes should always be configured to preload the KMs used to manage themProduction managed nodes should be configured to run only preloaded KMs 2006 BMC Software, Inc. All rights reserved.36Visualization Performance Considerations (Continued)

32、2006 BMC Software, Inc. All rights reserved.37Centralized Customization ManagementThe PATROL Configuration Manager (PCM) is a GUI-based tool used to define and distribute BMC Performance Manager Console configuration settings from a central location to some or all managed nodes.The PCM can be used t

33、o manage configuration options, such as: Preloading KMs Poll times Disabling selected application classes 2006 BMC Software, Inc. All rights reserved.38Centralized Customization Management (Continued) 2006 BMC Software, Inc. All rights reserved.39Designing for BPM Console Management/Upgrade/Patching

34、Use PATROL Infrastructure Monitor to ensure the health of PATROL Central infrastructureUse the DS to centralize BMC Performance Manager Console deployment to managed nodes 2006 BMC Software, Inc. All rights reserved.40Designing for BPM Console Management/Upgrade/Patching (Continued) 2006 BMC Softwar

35、e, Inc. All rights reserved.41Physical MappingAssign PATROL Central infrastructure components to specific servers 2006 BMC Software, Inc. All rights reserved.42Single Server EnvironmentsSingle server hosting An RTserver PATROL Console Server PATROL Central Operator Web EditionManage an environment o

36、f up to 3 million managed objects in a single RTcloud (with no more than 700 Agents) 2006 BMC Software, Inc. All rights reserved.43Single Server RequirementsSmall Single-Server(Up to 500,000 managed objects)ResourceRecommendationProcessorLinux and Windows Dual Processor Intel Pentium III at 800 MHzS

37、olaris Dual Processor SUN 420R UltraSPARC II at 450 MHzAIX Dual Processor IBM pSeries POWER 3 II at 375 MHzServer Memory1 GBDisk Space300 MBMedium Single-Server(Up to 3 million managed objects)ResourceRecommendationProcessorLinux and Windows Quad Processor Intel Pentium III at 900 MHzSolaris Quad Pr

38、ocessor SUN V480/880 at 900 MHzAIX Quad Processor IBM pSeries POWER 4 at 1000 MHzServer Memory4 GBDisk Space2 GB 2006 BMC Software, Inc. All rights reserved.44RTserver HardwareOne RTserver(Up to 750 RTclients)ResourceRecommendationProcessorLinux and Windows Single Processor Intel Pentium 4 at 1.4 GH

39、zSolaris Single Processor SUN UltraSPARC IIe at 500 MHzAIX Single Processor IBM pSeries POWER 3-II at 500 MHzServer Memory1 GBDisk Space300 MBTwo to Four RTservers(Up to 2000 total RTclients)ResourceRecommendationProcessorLinux Dual Processor / Intel Pentium 4 at 1400 MHz Solaris Single Processor /

40、SUN V210 UltraSPARC IIIi at 1 GHz or Dual Processor / SUN 280R UltraSPARC III at 750 MHzAIX Single Processor / IBM pSeries POWER 4 at 1200 MHz or Dual Processor / IBM pSeries POWER 3 II at 375 MHzWindows No more than two RTserversServer Memory1 GBDisk Space300 MB 2006 BMC Software, Inc. All rights r

41、eserved.45PATROL Console Server HardwareMedium PATROL Console Server(Up to 3 million managed objects)ResourceRecommendationProcessorLinux and Windows Dual Processor Intel Pentium 4 at 2000 MHzSolaris Dual Processor SUN V240 UltraSPARC IIIi at 1 GHzAIX Dual Processor IBM pSeries POWER 4 at 1200 MHzSe

42、rver Memory4 GBDisk Space2 GBLarge PATROL Console Server(Up to 10 million managed objects)ResourceRecommendationProcessorLinux Quad Processor Intel/HP Itanium 2 at 900 MHzSolaris Quad Processor SUN V480/880 at 900 MHzAIX Quad Processor IBM pSeries POWER 4 at 1200 MHzWindows Cannot be hostedServer Me

43、mory6 GBDisk Space4 GB 2006 BMC Software, Inc. All rights reserved.46PATROL Central Operator Microsoft Windows Edition HardwareResourceRecommendationSmall Profiles (up to 100 managed agents)ProcessorSingle ProcessorIntel Pentium III at 500 MHzMemory128 MBMedium Profiles (up to 500 managed agents)Pro

44、cessorSingle ProcessorIntel Pentium III at 700 MHzMemory512 MBLarge Profiles (up to 1200 managed agents)ProcessorSingle ProcessorIntel Pentium III at 700 MHzMemory1 GB 2006 BMC Software, Inc. All rights reserved.47Co-Hosting BMC Performance Manager Console ComponentsAll infrastructure components can

45、 coexistA Common Connect client can be installed with PATROL Console Server and RTserverPlace PATROL Console Server and RTserver on a dedicated hostNever install PATROL Console Server or RTserver with: PATROL End-to-End Response Timer version 1.1.03 and earlier PATROL Central Alerts Web Edition (spe

46、cific to version 7.1.00 only)PATROL Central Operator Web Edition version 7.1.10 cannot be installed with PATROL Central Alerts Web Edition version 7.2.01 2006 BMC Software, Inc. All rights reserved.48Implementation PlanInstall the DSPerform the following steps for every RT cloud, one cloud at a time

47、:Install RTserversInstall PATROL Agents on all managed nodesUse the PCM to configure all PATROL AgentsInstall the PATROL Console Server and configure it to service the required RTcloudsConfigure the PATROL Console Server for usersUse PATROL Central Administrator to set user rights/permissions 2006 B

48、MC Software, Inc. All rights reserved.49BaseliningA specification or product that: Has been formally reviewed and agreed upon Thereafter serves as the basis for further development Can be changed only through formal change control proceduresA document or a set of such documents formally designated a

49、nd fixed at a specific time during the life cycle of a configuration itemAny agreement or result designated and fixed at a given time, from which changes require justification and approval. IEEE STD 610.12-1990 2006 BMC Software, Inc. All rights reserved.50Baseline in BMC Performance Manager Console

50、A defined set of Agent configuration variables, both thresholds and Agent setup Used to configure a PATROL Agent for a certain type of machine 2006 BMC Software, Inc. All rights reserved.51How to Get a Baseline?Review the Service Level Agreements, align the monitoring plan with the business Divide t

51、he application classes into two groups:InterestedNot interested Check parameters of interested application classes and sort intofour groupsPre-load interested KMs, disable non-interested onesInstall/Activate the parameter turn off all alertsSet History Retention Period to a minimum of 7 daysCollect

52、data measurements for a predefined period of time to get statisticsSet the thresholds based on normalized data collected in your environment and what has been agreed on in your SLA 2006 BMC Software, Inc. All rights reserved.52Parameter GroupsGroup 1 Parameters that are important for your SLA or machine performance They need to have a high frequency and an alarm1 and alarm2 These are paramet