© 2007 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice BAC 7.x Sizing April 2008

2 Monitoring Requirements Agenda Sizing Calc Overview BAC 7.0 Deployment Guidelines Results Other Sizing Considerations HP Restricted. For HP and Partner Internal Use.

Monitoring & BAC Requirements

BAC Sizing & Deployment Examples Case Study Major Financial Institution

5 Very Large Financial Company Customer business background One of the world's leading financial services companies. −Approximately 4000 domestic offices and 12,500 ATMs. −30 international offices serving clients in more than 160 countries. −Many millions of active users on its Web site, which provides online banking access. Monitored applications/networks −Hundreds of Web-based applications. −Many lines of business (business lending, card services, corporate information security, etc.) −SiteScope monitors are managed and grouped according to the different LOBs. HP Restricted. For HP and Partner Internal Use.

6 Monitoring Requirements Monitor the business critical applications with synthetic transactions (real user perspective could be added next year) from a subset of the office locations −Availability is the number one priority (~99.8% target) −Use analysis and trending reports to improve performance over time Monitor the systems and the infrastructure items −Basics on the servers (CPU, Memory, Disk Space, Processes) −DB query times for order payment −Monitor MQ logs for queue depth and latency −OVO is currently being used to as the central event console Develop service levels that align with the application owners and operations −Service Level Management reports for LOB owners, App owners HP Restricted. For HP and Partner Internal Use.

7 BAC Sizing Figures ~800 transactions - 20 Business Process Monitor servers ~12000 monitors - 6 SiteScope servers (3 active in production) 3.5 million events per day 1 million events per day from OVO 100 SLA’s 150 Offline reports, mainly custom reports, most are delivered via Future plans/goals −Maybe an additional application, like Real User Monitor plan on 1 engine and 2 probes −10% increase in transactions next year − 20 additional end users next year HP Restricted. For HP and Partner Internal Use.

8 Sizing Calculator Use the Excel for now Take the raw results and compare to the Deployment Guidelines New Calculator is in the works HP Restricted. For HP and Partner Internal Use.

9 Deployment Guidelines SectionStandardEnterprise Logged-in users 120(20 dashboard)150(40 dashboard) Dashboard CIs 100K (150K KPIs) 300K (500K KPIs) Hosts K EPS (1000 w/reduction) SLAs 2000 CIs, 25 SLAs25K CIs, 500 SLAs HP Restricted. For HP and Partner Internal Use.

10 SiteScope Guidelines 8000 Monitors max per instance of SiteScope Maximum run rate of 1,000 monitors per minute Run rate = Total # of monitors / Avg Interval Example: 5000 / 10 mins = 500 monitors per minute **Based upon standard HP equivalent h/w we recommend today (Single 3.0 GHz dual core Xeon processor, 2 GB Mem, Ultra SCSI 10K RPM drives) HP Restricted. For HP and Partner Internal Use.

11 RUM Guidelines 1 Probe −~ 40 Mbs http (w/ full Snapshot w/ full text pattern events) −~ 65 Mbs http (w/ full Snapshot, w/o text pattern events) −~120 Mbs http (without Snapshot/events) 1 RUM engine −~ 500 pages/sec (recommended splitting engine and repository) Rule of Thumb: 20 Mbs/Sec ~ 100 Pages/Sec ~ 50 samples/Sec **Based upon standard HP equivalent h/w we recommend today (Dual dual core 3.0 Ghz Xeon, 4 GB Mem, dual gig NIC cards, Ultra SCSI 10K RPM drives) HP Restricted. For HP and Partner Internal Use.

12 BAC Deployment BAC Components −Business Process Monitor −SiteScope, EMS EUM SLM Business Availability Center is deployed in two separate environments: Production −20 Business Process Monitor servers −6 SiteScope servers (3 are active, 1 is dedicated for OVO events) −High Availability and Load Balancing is required −2 Gateway servers −2 DPS servers −2 Database servers Staging/Testing −1 Business Process Monitor server −1 BAC Server −1 SiteScope server HP Restricted. For HP and Partner Internal Use.

13HP Restricted. For HP and Partner Internal Use.

14 Rule of Thumb Sizing Considerations Add additional Gateway Servers for: −More than 120 (40 Dashboard) simultaneous users −More than 350 events per second −More than 75 BPM’s −More than 8 SIteScope’s Use UCMD External Deployment −Environments with over 7000 hosts Database considerations −Use fastest disk array that is available, the very first bottleneck is the speed of the database disks −Use 64 bit Enterprise versions of Oracle or MS SQL 2005 −Separate the CMDB schemas to another instance if using Discovery HP Restricted. For HP and Partner Internal Use.

15 Items to be mindful of: Make sure Purging Manager is Enabled!!! Good judgment and consideration of: −PCBD −BPM Error Snapshots −Number of Agents −Monitoring Intervals HP Restricted. For HP and Partner Internal Use.

16 Impacts to the BAC System Components Gateway Server DPS Server Database Server UsersMediumNoneMinimal BPM TransactionsMedium RUM PagesMediumLarge SLA’sMinimalLargeMedium CMDB DiscoveryMediumLarge SiteScope MonitorsMedium Large Dashboard ViewsMedium J2EE DiagnosticsMinimal EMSMedium HP Restricted. For HP and Partner Internal Use.