Monday, September 2, 2013

APM 360 and APM 360 Advanced (Formerly, BAC Bundles)

The intention is that customers purchase these Application Performance Management 360 packages to manage specific applications (represented by configured application CIs
within the BSM Run-time Service Model) and the Application OS Instances for those applications.
APM 360 entitles the use of the following products (for each applicable application):
• BPM-SLM: Unlimited use of BPM software, with SLM (i.e. Business Process Monitor Transaction Unlimited Locations Advanced and Service Level Management for BPM licenses).
• RUM-SLM: Unlimited use of RUM software, with SLM (i.e. Real User Monitor for Applications Advanced and SLM for RUM licenses).
• Diagnostics-SLM: Use of Diagnostics software, with SLM, for a specified number of Application OS Instances (i.e. Diagnostics for Composite Application Instance and SLM for
Diagnostics licenses).
APM 360 Advanced entitles the use of the following products (for each applicable application):
• BPM-SLM: Unlimited use of BPM software, with SLM (i.e. Business Process Monitor Transaction Unlimited Locations Advanced and SLM for BPM licenses).
• RUM-SLM: Unlimited use of RUM software, with SLM (i.e. Real User Monitor for Applications Advanced and SLM for RUM licenses).
• Diagnostics-SLM: Use of Diagnostics software, with SLM, for a specified number of Application OS Instances (i.e. Diagnostics for Composite Application Instance and SLM for
Diagnostics licenses).
• SHA: Unlimited Use of Service Health Analyzer.
• SAM: 15 System Availability Management points (enabling SiteScope usage) per licensed Application OS Instance.


Application OS Instances for APM 360
APM 360 and APM 360 Advanced are licensed according to the number of Application OS Instances for each applicable application. The following conditions apply for Application OS
Instance licensing:
1. An Application OS Instance means an OS instance (physical or virtual machine) that runs an application component which is monitored by the APM product. APM 360 covers most
common application technologies. Here are some examples:
• One license is required for each Application OS Instance that runs Java, .Net, Python, etc.
• One license is required for each Application OS Instance that has any of the following software installed on it: Microsoft Servers (for example, MS Exchange, MS SharePoint); SAP;
Siebel; Citrix (includes both XenApp and the backend application; Oracle E-business; PeopleSoft.

2. If two application components are contained in one Application OS Instance, it should be counted as a single Application OS Instance.
3. Each licensed Application OS Instance corresponds to a single Diagnostics OS Instance license.

HP Business Availability Center Anywhere on HP SaaS

HP SaaS BAC Anywhere provides customers the ability to leverage their investment in on-premise deployment of HP Application Performance Management and extend their
Business Process Monitoring to points outside the firewall. Customers gain access to HP SaaS global network of Point os Presence (PoPs) through an easy-to-use application on the
HP SaaS portal and can quickly select locations from which to perform monitoring. Once selected and configured, customers can deploy scripts to HP SaaS PoPs just as they would
an Internal BPM.

Service Health Analyzer (SHA)

SHA analyzes metrics coming from HP or 3rd party sources and provides predictive analytics and anomaly detection. SHA is licensed by Nodes. Count OS Instances and other
network nodes whose metrics are being analyzed by SHA. For 3rd party metrics which are not associated with a network node (e.g. business metrics) count the number of
business\logical CIs which the metrics are associated with.
The base product comes with a pack of 50 nodes and customers can purchase additional capacity as needed.

Tuesday, August 27, 2013

The BSM 9 movie

Business Process Monitoring for mobile - best practices for you

New post from HP.

http://h30499.www3.hp.com/t5/Business-Service-Management-BAC/Business-Process-Monitoring-for-mobile-best-practices-for-you/ba-p/6171311#.UhzCSxsRClY


In rapidly changing and complex IT environments, monitoring of mobile application performance can be quite challenging task. HP Business Process Monitor (BPM) provides a quick and easy solution to deliver the visibility on your mobile application performance. Mobile application performance can be measured by HP BPM from multiple internal or external locations. Monitoring locations can be extended by the HP SaaS hosted global Points-of-Presence (PoP). These PoP's include mobile transaction monitoring Over-the-Air (OTA), which then will capture the impact of mobile carrier network (latency per carrier) to the end user response times. All BPM measured monitoring data can be reported in various perspectives, clearly indicating per application, user, location or SLA performance.   

HP BPM is an application performance management solution which runs monitoring scripts recorded by a Virtual User Generator (VuGen). The document in this blog provides best practices for using VuGen to record mobile native applications for BPM. The document provides general best practices, as well as explanations how to utilize a number of emulators in script creation. The document also provides a brief description of how to record scripts using the MobileTrue client protocol. Both of these recording technologies are supported by HP LoadRunner and HP Performance Center, so customers can seamlessly integrate the mobile application testing and monitoring solutions and reuse scripts from application performance test phase in production monitoring.

A typical mobile app (HTTP/HTML) uses protocols which enable you to develop scripts using mobile devices
or device emulators that communicate with servers over HTTP. It is easy to record network traffic to a
capture file (PCAP file) and create a VuGen script, or alternatively mobile emulator on your VuGen
machine can be used to develop monitoring scripts. Many mobile device emulators are available on the internet sites. Correct emulator version needs to be installed (supported by your application) and secure match to system requirements for each emulator software used. There is more information in the attached documenton on the best practices for mobile script creation.