BMC項目管理方法ppt課件

1、BMC Performance Manager Console 7.x: Administering Part 2Module 2: Implementing a BPM Console ProjectModule ObjectivesDescribe the phases of an implementation projectPlan the implementation process.Lesson 1: Phases of Implementation ObjectivesOverview of the implementation projectDescribe the phases

2、 of an implementation project.Overview of the Implementation ProjectDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5.Phase 1 Design and PlanIdentify business processes and prioritiesIdentify applications that support the business pr

3、ocesses, transfer prioritiesIdentify systems where various applications reside, include dependencies, and transfer prioritiesDesign management processes, include tools and responsibilitiesUnderstand organizational constraintsUnderstand the technical environmentDeployBuild and Test PrototypeConfigure

4、Test, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5Design and Plan.Phase 2 Build and Test PrototypeInstall Agents on systems with applications that best represent the target environmentInstall PATROL ConsolesLearn how to use the toolsDevelop configuration prototypesDevelop any new Knowled

5、ge Modules (KMs) for un-instrumented applicationsDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5.Phase 3 DeployInstall the BMC Distribution Server (DS)Install the DS ClientsCreate installation packagesInstall production AgentsInsta

6、ll KMsStart the Agents automaticallyVerify “vanilla systems are operationalDeploy custom KMsDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5.Phase 4 ConfigureConfigure PATROL AgentsParameters onThresholds offAgent operational parame

7、tersAccess and securitySet 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.Phase 5 Test, Improve, and MaintainPhas

8、e 5 lasts FOREVER! Your steady state processes are executingDuring this phase:Measure your processes Make improvementsLook for ways to improveDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5.Lesson 2: Planning the ImplementationObje

9、ctivesPlan the implementation processAnalyze requirementsDefine a design solutionPerform a physical mapping of the proposed design solution for different serversDefine an implementation plan.Planning the Implementation ProcessAnalysisLogical designPhysical mappingImplementation planDeployBuild and T

10、est PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5Design and Plan.AnalysisIdentify project stakeholdersDiagram the enterprise to be managed by BMC Performance Manager ConsoleCollect and record high-level sizing data for each management domain.Project StakeholdersIde

11、ntify the people directly involved with:Initial deployment and installation of BMC Performance Manager ConsoleBMC Performance Manager Console manages node configuration and change managementOngoing user management, availability, and performance of PATROL Central infrastructureHandling events and exc

12、eption conditions raised by BMC Performance Manager Console.Diagram the EnterpriseInternet / WANFirewallFirewallFirewallHoustonNew YorkAustin100 Mbps (all)T1 (all)IT OPS3 PC Windows users500 managed nodesSecondary IT OPS3 PC Windows users2 PC Web users40 managed nodes400 managed nodes2 causal PC Web

13、 usersMainCore, Inc. Enterprise.Location 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 InformationNumber of managed nodes at this location: 5

14、00KMs 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.Location Analysis (Continued)Additional Infrastructure ServicesWill BMC Performance Manager Reporting aggregate data from managed nodes at this locat

15、ion? 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 of KMs used on each managed node: 3 (OS, Oracle, KM for EM)Typical number of managed objects on eac

16、h 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 PATROL Central Operator console sessions: 3Typical number of managed nodes in each Management Profile

17、: 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 * 80)Estimated total number of concurrent managed objects: 432.000 (144.000 * 3).Location Analysis (Con

18、tinued).Analysis ToolsStakeholder Roster WorksheetStakeholder Roster Worksheet.docLocation Analysis WorksheetPATROL Location Analysis Worksheet.doc.Logical DesignLocation of PATROL Central infrastructure servicesNumber of services needed.RTcloud Logical DesignAgent Cloud500 managed nodesRTserverRTse

19、rver Console CloudConsole ServerRTserverRTserverPCWebBrowser UsersPCWin UsersMainCore, Inc. Houston Location.RTserver 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 RTcloud wil

20、l 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.RTserver Design Considerations (Continued).RTserver Design Considerations (Continued).Visua

21、lization DesignWhich PATROL Central console is appropriate?Which locations need PATROL Console Servers?Is one PATROL Console Server enough?.Which PATROL Central Console is Appropriate?PATROL Central Operator Microsoft Windows EditionVisualize larger numbers of managed nodesPATROL Central Operator We

22、b EditionNo more than 200 managed nodesLimit profiles to fewer than 100 managed nodes.Which Locations Need PATROL Console Servers?Location with the highest concentration of managed nodesLocation with console users.Which Locations Need PATROL Console Servers? (Continued).Is One PATROL Console Server

23、Enough?Number of concurrent console sessionsMax. 25 (32-bit)Max. 100 (64-bit)Number of managed objects in concurrent Management ProfilesMax. 3 million (32-bit)Max. 10 million (64-bit).Is One PATROL Console Server Enough? (Continued).PATROL Console Server Failover ConsiderationsTwo ways to provide re

24、dundancyInstall on high-availability cluster hardwareStore the configuration files on a shared diskDefine a cluster failover packageInstall a secondary PATROL Console Server on a separate nodeUse the online backup feature to periodically snapshot data from the primary PATROL Console Server.PATROL Co

25、nsole Server Failover Considerations (Continued).PATROL Central Operator Web 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 inst

26、alled on any single node.Visualization 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.Visualization Performance Considerations (Continued).Centralized Custo

27、mization 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 to manage configuration options, such as:Preloading KMsPoll time

28、sDisabling selected application classes.Centralized Customization Management (Continued).Designing for BPM Console Management/Upgrade/PatchingUse PATROL Infrastructure Monitor to ensure the health of PATROL Central infrastructureUse the DS to centralize BMC Performance Manager Console deployment to

29、managed nodes.Designing for BPM Console Management/Upgrade/Patching (Continued).Physical MappingAssign PATROL Central infrastructure components to specific servers.Single Server EnvironmentsSingle server hostingAn RTserverPATROL Console ServerPATROL Central Operator Web EditionManage an environment

30、of up to 3 million managed objects in a single RTcloud (with no more than 700 Agents).Single Server RequirementsSmall Single-Server(Up to 500,000 managed objects)ResourceRecommendationProcessorLinux and Windows Dual Processor Intel Pentium III at 800 MHzSolaris Dual Processor SUN 420R UltraSPARC II

31、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 Processor SUN V480/880 at 900 MHzAIX Quad Proce

32、ssor IBM pSeries POWER 4 at 1000 MHzServer Memory4 GBDisk Space2 GB.RTserver HardwareOne RTserver(Up to 750 RTclients)ResourceRecommendationProcessorLinux and Windows Single Processor Intel Pentium 4 at 1.4 GHzSolaris Single Processor SUN UltraSPARC IIe at 500 MHzAIX Single Processor IBM pSeries POW

33、ER 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 / SUN V210 UltraSPARC IIIi at 1 GHz or Dual Processor / SUN 280R UltraSPARC III at 750 MHzAIX

34、 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.PATROL Console Server HardwareMedium PATROL Console Server(Up to 3 million managed objects)ResourceRecommendationProcessorLinux

35、 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 MHzServer Memory4 GBDisk Space2 GBLarge PATROL Console Server(Up to 10 million managed objects)ResourceRecommendationProcessorLinux Quad Proce

36、ssor 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 Memory6 GBDisk Space4 GB.PATROL Central Operator Microsoft Windows Edition HardwareResourceRecommendationSmall Profiles (up to 100 managed

37、agents)ProcessorSingle ProcessorIntel Pentium III at 500 MHzMemory128 MBMedium Profiles (up to 500 managed agents)ProcessorSingle ProcessorIntel Pentium III at 700 MHzMemory512 MBLarge Profiles (up to 1200 managed agents)ProcessorSingle ProcessorIntel Pentium III at 700 MHzMemory1 GB.Co-Hosting BMC

38、Performance Manager Console ComponentsAll infrastructure components can 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 T

39、imer version 1.1.03 and earlierPATROL Central Alerts Web Edition (specific 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.Implementation PlanInstall the DSPerform the following steps for every RT clo

40、ud, one cloud at a time: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 ri

41、ghts/permissions.BaseliningA specification or product that:Has been formally reviewed and agreed uponThereafter serves as the basis for further developmentCan be changed only through formal change control proceduresA document or a set of such documents formally designated and fixed at a specific tim

42、e 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.Baseline in BMC Performance Manager ConsoleA defined set of Agent configuration variables, both thresholds and Agen

43、t setup Used to configure a PATROL Agent for a certain type of machine.How to Get a Baseline?Review the Service Level Agreements, align the monitoring plan with the business Divide the application classes into two groups:InterestedNot interested Check parameters of interested application classes and

44、 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 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.Parameter GroupsGroup 1Parameters that are important for your SLA or machine performanceThey need to have a high frequency and an alarm1 and al