Business Service Management (BAC/BSM/APM/NNM)
More than everything monitoring, BSM provides the means to determine how IT impacts the bottom line. Its purpose and main benefit is to ensure that IT Operations are able to reactively and proactively determine where they should be spending their time to best impact the business. This covers event management to solve immediate issues, resource allocation and through reporting performance based on the data of applications, infrastructure, networks and from third-party platforms. BSM includes powerful analytics that gives IT the means to prepare, predict and pinpoint by learning behavior and analyzing IT data forward and backwards in time using Big Data Analytics applied to IT Operations.

Get press exposure on your BSM/APM deployment

 - Are you attending our HP Software Universe event in Washington this year?


- Are you a current HP Business Service Management (BSM) customer - customer who has one or more products from


HP Business Availability Center (any of these products Business Process Monitor/Real user monitor/Sitescope/Diagnostics/Service Level Management/Transaction Vision)



HP Operations Management Center (Operations Manager, Operations Manager i, any of our SPIs)


 HP Network Management Center (NNMi, Performance SPIs, etc)



- Are you happy with your BSM deployment and want to talk about it?



- Do you want to be seen as a leader and innovative company by having your BSM story quoted in press articles?



If you answered yes, to all of the above, then send an email to: aru@hp.com with your contact information (your name, company, email and phone number). I’ll call you and we can discuss how to give you and your BSM deployment some great exposure.



Thanks
Aruna Ravichandran
Group Product Marketing Manager
Application Performance Management ( part of BAC)
aru@hp.com


 

HP APM partner in crime with HP's Application Lifecycle Management

Did you know that HP's application performance management is part of HP's application lifecycle management (ALM)? HP has a lifecycle approach to application performance and availability management that focuses on integration, collaboration, and resource sharing—from pre-deployment application development to production application management and back again. For example, the ability to reuse scripts has been available, but collaboration among teams did not occur, because each team did not know what existed among the other teams. The HP approach bridges the gap among development, QA, and IT operations so that your teams can work together more effectively, understand and meet end-user performance requirements, and cut cost, complexity, and deployment time frames. Examples of HP this lifecycle approach with End User Management (EUM) are:  



  • Bi-directional script reuse: You can use reuse artifacts between production environment and QA. Real User sessions can be used generate more realistic test scripts, which can help strengthen testing suite so that you can catch most of the application performance in pre-production, rather than in production. LoadRunner and Quality Center scripts can be used in HP Business Process Monitor allowing you to leverage testing scripts to monitor a production environment, reducing the time required to roll out application into production.  

  • Load modeling analysis: You can create an accurate load test that reflects real-life conditions, using HP Real User Monitor session data.   • Impact analysis: You can measure the impact of changes on the system in production (“before and after” snapshots) or during load testing. You can compare production results with synthetic load results or reproduce production results in the QA lab.  

  • Cross-environment analysis: You can differentiate between code and configuration issues so problems can move to and from production and synthetic load environments  

  • Root-cause analysis: You can identify the underlying cause of performance degradation related to one or more tiers in the system, both in production using real load data or in pre-production using synthetic load data using HP's Diagnostics software.


    • HP Diagnostics software helps identify transaction paths, which makes it very easy for QA or production support to quickly identify and triage application performance problems. It is single tool which can be shared between both production and pre-production environment.



    • HP Diagnostics software helps you improve application availability and performance in pre-production and production environments helping to significantly compress testing and tuning cycles, increase productivity, and accelerate performance problem diagnosis and repair.



    • You can utilize HP Diagnostics software to drill down from the end user into application components and cross-platform service calls to pinpoint and resolve the toughest problems. This includes slow services, methods, SQL, out-of-memory errors, threading problems, and more.



    • It also extends HP LoadRunner and HP Performance Center software capabilities to address the unique challenges of testing and diagnosing even the most complicated, composite applications. It allows you to identify issues early that are often hidden in testing but show up in production, such as a slow memory leak.





 Thanks,


Aruna Ravichandran
Group Product Marketing Manager, APM
aru 'at' hp.com

How Deloitte drives service excellence with HP BAC

Many of you have asked for HP Business Availability Center (BAC) lessons learned and customer success stories. Here’s one from Deloitte Australia, a member of Deloitte Touche Tohmatsu, one of the world’s leading professional services firms.


Deloitte is using HP BAC to monitor the health of its business services and the entire underlying infrastructure including servers, operating systems, network, Internet services, and applications.


Aligned with ITIL processes, HP BAC has streamlined incident and problem management and reduced mean time to resolution from a few hours to a matter of minutes. In addition, Deloitte has decreased downtime of external systems (client business systems), enriching the customer experience. These results, among others, contributed to the service excellence that made Deloitte the 2008 Accountancy Firm of the Year.


Read how Deloitte achieved their exceptional outcomes.

Australias largest superannuation administrators achieve amazing ROI with HP's Application Performance Management Solution (BAC)

Last week,I saw this article from a online AUstrialian IT newspaper, and I was amazed to see so many tangible improvement and ROI metrics realized by a company called SuperPartners, who is one of the largest superannuation administratos in Australia, while using our Application Performance Management solution ( End user management (RUM/BPM), Diagnostics, Sitescope) .


SuperPartners services 6.1 million member accounts and 687,000 employee accounts and has more than $68 billion in funds under administration!


Some of the key lines from the article which really stuck me include: For three years running, Superpartners' systems have had an average uptime of 99.7 per cent. Three years ago the figure was 97 per cent. One of the main benefits has been reduced incidents. Between 2005 and 2008, Superpartners experienced a 65 per cent reduction in "severity one" incidents. In 2008 alone, it achieved a 73 per cent reduction in support queues.  They said that Superpartners was expected to begin achieving return on its investment within 15 months, and to have 58 per cent ROI after three years.


If you are interested in reading the whole article, please check out:


http://www.theaustralian.com.au/australian-it/it-business/hands-free-monitoring-cuts-superfund-glitches/story-e6frganx-1225828007689


 Thanks


Aruna Ravichandran
Sr. Manager, Business Availability Center Product Marketing
aru@hp.com

Operations: application performance sucks, what do I do now?

by Michael Procopio


In my IT days (it has been a while) as still happens today this is the question many have asked. It’s more complicated today, applications are more distributed now. However, you still have to go through the triage process. The topic these days is named “Application Performance Management” or APM.


APM has two parts, the traditional looking at infrastructure resources and measuring performance from the end user perspective.


You probably detected this problem in one of two ways. You are ahead of the curve and have end user monitoring in place or the user called the help desk to complain.


A typical web based application today uses a web server, application server and a backend, typically a database. Though the backend might actually have multiple parts if service oriented architecture, (SOA) is used. Good news, Operations Manager, agent based, and SiteScope, agentless, will provide status on condition of those servers.


These tools can also look at how packaged applications are doing on the server. Oracle, WebSphere, MS Exchange, MS Active Directory, to name a few, can be monitored by either Operations Agents or have SiteScope templates (a SiteScope template is a prepackaged set of monitors). These tools might point to something as detailed as database locks being far higher than normal and beyond the current setting on the database. A quick parameter change might fix this.


Next, we have the code. We hope this isn’t the case because this typically moves the problem from operations to development. However, Operations is still responsible for pinpointing the problem area. This is typically the domain of application support and in some organizations that’s inside Operations, in others a different group.


Here Business Transaction Management (BTM) tools can help. BTM manages from a transaction point of view. BTM includes transaction tracing. TransactionVision and Diagnostics work in a complimentary fashion to give you the next level of detail although each is usable separately. TransactionVision traces individual critical transactions (as you define them) through multiple servers; it gives you information on a specific transaction including the value of the transaction.


Diagnostics provides aggregate information on all transactions in a composite application giving you timing information. It can pinpoint:


· where time is spent in an application; either processing data or waiting for a response from another part of the application.


· the slowest layers.


· the slowest server requests which are the application entry points.


· outliers to help diagnose intermittent problems.


· threads that may be contributing to performance issues.


· memory problems and garbage collection issues.


· the fastest growing and largest size collections.


· leaking objects, object growth trends, object instance counts, and the byte size for objects.


· the slowest SQL query and report query information.


· exception counts and trace information which often go undetected.


TransactionVision and Diagnostics also integrate with Business Availability Center, which means you can start with a topology view and drill all the way down to find the status of the most valuable transaction running through you systems.


You can manage what you can’t measure. So what do I do now? If you are properly instrumented the problem will show itself. If you don’t find something you can fix, you can tell the app developers where they need to look to fix the problem.


   


Related Items:


· End User Monitoring


· Operations Manager


· SiteScope


· SiteScope Administrator Forum


· TransactionVision


· Diagnostics


· Business Availability Center





RUM the Real User Experience Manager

by Michael Procopio


RUM or Real User Monitor is a tool to monitor actual user traffic running over your network.


Its part of our EUM or end user management suite. In the area of EUM there are two primary ways to monitor 1/ synthetic, which is covered by BPM or Business Process Monitor and 2/ real user monitoring.


Each has its place in a monitoring strategy. BPM is good for making sure things are up 24x7, even when no users are using your applications. Real user monitoring can give you information down to the specific user.


When I first moved over to BAC group and heard about RUM, I was impressed. One of the things it can do is replicate a users web session click by click. This allows someone troubleshooting a problem to see exactly what happened and what the error message was the user saw – no guessing. (sensitive data like passwords and credit cards are filtered out in memory before writing to a disk). Further, if you do find a problem it can turn the session into a script that can be passed to the QA team to replicate the problem, if they are using LoadRunner.


How does it work? It starts by capturing packets as they go over the network. This is done by a RUM Probe, which is software that runs on a dedicated piece of x86 hardware (typically). The Probe passes the relevant data to the RUM engine.


The RUM engine stores the data and key performance metrics are aggregated before being sent up to BAC for reporting and alerting. For example, an alert might be round trip time for the Savings Deposit transaction is taking too long. Here are some of the reports RUM provides:



  • Global Statistics

  • Page Summary

  • Transaction Summary

  • End User Summary

  • End User Over Time

  • Server Over Time

  • Session Analyzer

  • TCP Application Summary

  • TCP Application Over Time

  • Event Summary

  • Business Process Distribution



Figure: Example RUM deployment configuration


Originally RUM strictly focused on HTTP/S traffic. But a while back support was expanded to due general tracking of TCP traffic, both streaming and non-streaming. In more recent releases additional upper level protocol analysis has been added. Beyond HTTP/S current support includes:



  • XML/SOAP

  • Siebel

  • WebSphere

  • MPLS


Related Items:



For Business Availability Center, Michael Procopio


Get the latest updates on our Twitter feed @HPITOps http://twitter.com/HPITOps


Join the HP Software group on LinkedIn and/or the Business Availability Center group on LinkedIn.


 

Fighting or friendly, Problem Isolation and OMi

by Michael Procopio


In the post  Event Correlation OMi TBEC and Problem Isolation What's the Difference, my fellow blogger, Jon Haworth, discussed the differences between TBEC and Problem Isolation. To be consistent, I'll use the acronyms PI for Problem Isolation and TBEC to refer to OMi (Operations Manager i series) Topology Based Event Correlation.


Briefly, he mentioned that TBEC works “bottom up”, that is starting from the infrastructure, with events. PI works “top down”, that is, starting from an end user experience problem, primarily with metric (time series) data.


Jon did an excellent job describing TBEC; I’ll do my best on PI because like Jon I have a conscience to settle.


Problem Isolation is a tool to:


1. automate the steps a troubleshooter would go through


2. run additional tests that might uncover the problem


3. look at all metric/performance data from the end user experience monitoring and all the infrastructure it depends


4. find the infrastructure metric the most closely matches the end user problem using behavior learning and regression analysis techniques (developed by HP Labs)


5. bring additional data such as events, help/service desk tickets and changes to the troubleshooter


6. allow the troubleshooter to execute Run books to potentially solve the problem


Potentially the biggest difference in the underlying technology is that Problem Isolation does not require any correlation rules or thresholds to be set for it to do the regression analysis to point to the problem. Like TBEC, it does require that an application be modeled in a CMDB.


An example: Presume a situation with a typical composite application - web server, application server and database. No infrastructure thresholds were violated; therefore, there are no infrastructure alerts. Again, as mentioned in the previous post, end user monitoring (EUM) is the back stop. EUM alerts on slow end user performance, now what?


Here is what Problem Isolation does:


1. determines which infrastructure elements (ITIL configurations items or CIs) support the transaction


2. reruns the test(s) that caused the alert – this validates it is not transient problem


3. runs any additional tests defined for the CIs


4. collects Service Level Agreement information


5. collects all available infrastructure performance metrics (web server, application server, database server and operating systems for each) and compares them to the EUM data using behavior and regression analysis



Problem Isolation screen show performance correlation between end user response and SQL Server database locks


-------------------------------------------------------------------------------------------


6. determines and displays the most probable suspect CI and alternates


7. displays run books available for all infrastructure CIs for the PI user to run directly from the tool


8. allows the PI user to attach all the information to a service ticket, either existing or create a new one


Another key differentiator of OMi/TBEC and PI is the target user. There is such a wide variance in how organizations work that it is hard to name the role but let me do a brief description and I think will be able to determine the title in your organization.


There are some folks in the organization whose job is to take a quick look (typically < 10 minutes, in one organization I interviewed < 1 minute) at a situation and determine if they have explicit instructions on what to do via scripts or run books. When they have no instructions for a situation they pass it on to someone who has a bit more experience and does some free form triage.


This person might be able to fix the problem or may have to pass it on to a subject matter expert, for example if they believe it is an MS Exchange problem to an Exchange admin. It is this second person that Problem Isolation is targeted at. This is helping automate her job, reducing what might take tens of minutes to hours and performing it in seconds. If it ends up she can’t solve the problem it automatically provides full documentation of all information collected. That alone might take someone five minutes to write-up.


OMi’s target is the operations bridge console user. Ops Bridge operators tend to be lower skilled and face hundreds if not thousands of events per hour. Jon described how OMi helps them work smarter.


TBEC and Problem Isolation both work to find the root cause of an incident but in different ways. Much like a doctor might use an MRI or CAT scan to diagnose a patient based on what the situation is, TBEC and Problem Isolation are complementary tools each with unique capabilities.


Problem Isolation will not find problems in redundant infrastructure that OMi will. Conversely, OMi can’t help with EUM problems when no events are triggered, where Problem Isolation will.


We know this can be a confusing area. We welcome your questions to help us do a better job of describing the difference. But these two are definitely friendly.


For Business Availability Center, Michael Procopio


Get the latest updates on our Twitter feed @HPITOps http://twitter.com/HPITOps


Join the HP Software group on LinkedIn and/or the Business Availability Center group on LinkedIn.


Related Items



  1. Advanced analytics reduces downtime costs - detection

  2. Advanced analytics reduces downtime costs – isolation

  3. Problem Isolation page

  4. Operations Manager i page

HP Business Availability Center 8.02 What's New

 by Michael Procopio


 BAC 8.02 is now generally available. Here are the highlights of what's new. There are also a number of defect fixes in this release.


 



  • Netuitive integration:

  • Enables integrating Netuitive alarms into Dashboard

  • System Availability Management (SAM) enhancement:

  • SAM administration now displays SAM points in use, enabling more effective management of SiteScope license points by increasing visibility into point consumption

  • Apache Web server upgrade:

  • Upgrade of Apache Web server to version 2.2.11 keeps Business Availability Center current with the latest industry release and compliant with security requirements

  • End User Management (EUM) enhancements, including:

  • Real User Monitor (RUM): Additional OS support for RUM probe (Windows 2003 and RHE5 64 bit); Improved SSL traffic handling for special environments; Seven protocol decoder packs for slow requests: MSSQL, LDAP, MySQL, IMAP, POP3, SMTP, FTP; Improved system health; Keystore management improvements

  • Business Process Monitor (BPM): Support for VuGen 9.5; BPM support for Windows Vista; New MSI installation replaces InstallShield on Windows platforms; New Solaris packaging (SPARC) installation replaces InstallShield on Solaris platforms

  • Business Process Insight enhancement:

  • Implemented a way to link sub-processes to parent processes.

  • Interactive integration documentation for Business Availability Center-Service Manager/Service Center integration:

  • New interactive document that enables selecting specific integration parameters and viewing only the documentation relevant for the integration specified


 


For the Business Availability Center, Michael Procopio


 


Related items:



 


 

Search
Showing results for 
Search instead for 
Do you mean 
About the Author(s)
  • Doug is a subject matter expert for network and system performance management. With an engineering career spanning 25 years at HP, Doug has worked in R&D, support, and technical marketing positions, and is an ambassador for quality and the customer interest.
  • Dan is a subject matter expert for BSM now working in a Technical Product Marketing role. Dan began his career in R&D as a devloper, and team manger. He most recently came from the team that created and delivered engaging technical training to HP pre-sales and Partners on BSM products/solutions. Dan is the co-inventor of 6 patents.
  • This account is for guest bloggers. The blog post will identify the blogger.
  • Over 11 years of experience in design and development of NMS/EMS products and presently with the Device content support covering broad based features of multitude device vendors in NNMi.
  • Manoj Mohanan is a Software Engineer working in the HP OMi Management Packs team. Apart being a developer he also dons the role of an enabler, working with HP Software pre-sales and support teams providing technical assistance with OMi Management Packs. He has experience of more than 8 years in this product line.
  • HP Software BSM Social Media
  • Nimish Shelat is currently focused on Datacenter Automation and IT Process Automation solutions. Shelat strives to help customers, traditional IT and Cloud based IT, transform to Service Centric model. The scope of these solutions spans across server, database and middleware infrastructure. The solutions are optimized for tasks like provisioning, patching, compliance, remediation and processes like Self-healing Incidence Remediation and Rapid Service Fulfilment, Change Management and Disaster Recovery. Shelat has 21 years of experience in IT, 18 of these have been at HP spanning across networking, printing , storage and enterprise software businesses. Prior to his current role as a World-Wide Product Marketing Manager, Shelat has held positions as Software Sales Specialist, Product Manager, Business Strategist, Project Manager and Programmer Analyst. Shelat has a B.S in Computer Science. He has earned his MBA from University of California, Davis with a focus on Marketing and Finance.
  • Architect and User Experience expert with more than 10 years of experience in designing complex applications for all platforms. Currently in Operations Analytics - Big data and Analytics for IT organisations. Follow me on twitter @nuritps
  • 36-year HP employee that writes technical information for HP Software Customers.
  • Pranesh Ramachandran is a Software Engineer working in HP Software’s System Management & Virtualization Monitoring products’ team. He has experience of more than 7 years in this product line.
  • Ramkumar Devanathan (twitter: @rdevanathan) works in the IOM-Customer Assist Team (CAT) providing technical assistance to HP Software pre-sales and support teams with Operations Management products including vPV, SHO, VISPI. He has experience of more than 12 years in this product line, working in various roles ranging from developer to product architect.
  • Ron Koren is a subject matter expert for BSM / APM, currently in the Demo Solutions Group acting as a Senior Architect. Ron has over fourteen years of technology experience, and a proven track record in providing exceptional customer service. Ron began his career in R&D as a software engineer, and later as a team manager. Ron joined HP software in 2007 as an engineer in the Customer-Oriented R&D team. Prior to joining HP, Ron held a leadership development role at Israel’s largest bank. Ron holds a B.S. in Computer Science from The Interdisciplinary Center, Herzliya Israel.
  • Stefan Bergstein is chief architect for HP’s Operations Management & Systems Monitoring products, which are part HP’s business service management solution. His special research interests include virtualization, cloud and software as a service.
  • With 11 plus years of very broad experience as a deployment expert for all the NMC products, my deliverables includes helping the Sales and Pre-Sales team in sizing and architecting the solution and hardware, assisting the implementers in product deployment and helping the customers directly when the products are deployed in production setup. As part of Customer Assist Team, I participate in a lot of customer facing activities from R&D side and provides best practices of using HP SW NMC products for efficient network management and leverage my rich experience in Network Node Manager and related iSPIs products.
HP Blog

HP Software Solutions Blog

Featured


Follow Us
Labels
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.