What Is Sonic Bus?

In earlier versions of BAC like 7.5 it was called BUS. Back then, it was Mercury's creation and BUS was based on C. After HP's acquisition, they decided to use an external, third-party product called Sonic BUS - based on java.

What you need to know about bus:

* Sonic bus is the bridge between your BSM Gateway and Data Processing servers

* Data from your Data Collectors (BPM, RUM, SiteScope, Diagnostics, OMW/U etc.) comes to your Gateway server and goes to the Sonic BUS. From there, different components catch the data and use it for their own purpose:

    - db_loader inserts this raw data in your Profile database, so it can be used for reports for example. Based on this data, you get aggregated data. No data from db_loader, no reports.

    - the MARBLE (former online_engine) components of BSM use the Sonic BUS to catch your data and color your views (Dashboard/Service Health).

* Sonic BUS mainly consists of two parts - Message Broker and Domain Manager. MB is located on both Gateway and Data Processing servers, whereas the DM resides only on the Data Processing one. Your data is being transferred between the MB of the two servers.

* Message Broker and Domain Manager work by default on respectively ports 2507 and 2506. Sonic BUS also uses a wide range of dynamic ports.

* Sonic BUS has its own local database (on the BSM file system) - the information that goes to it is not stored in the Database server!

* If you access your BSM servers, go to Start > Programs > Progress, you will find the Sonic BUS management console (press ok to login). From here, you can manage and view the data that is in the Sonic BUS queues.


The Sonic BUS application is a very sensitive one. Always proceed with caution when working with it and avoid any modification, unless you are 100% aware of what you are doing or you are instructed by Support.

Tracking Login Attempts and Logged In Users in HP BSM/BAC

We can always track the user activity in HP BSM/BAC very easily and it is very important too. Follow the below process for doing the same:

There are lots of log file in BSM root folder but below are the stuffs we are concerned here;

See \log\EJBContainer\UserActions.servlets.log.

The appender for this file is located in \conf\core\Tools\log4j\EJB\topaz.properties.

It can also be done by the JMX console as stated below;

To display a list of users currently logged in to the system:
1 Open the JMX console on this machine. For detailed instructions, see
"Using the JMX Console" in the Platform Administration guide.
2 Under the Topaz section, select service=Active Topaz Sessions.
3 Invoke the java.lang.String showActiveSessions() operation.

Type of Logs in Load Runner Runtime settings

While creating and debugging the script which generated in LoadRunner always create various types of logs which appear in Virtual user generator screen. These logs are very useful when it’s come to debugging your script.

There are four types of log available in LoadRunner:
Recording Log
Generation Log
Replay Log
Co-relations Results



1. Recording Log: This log is generated when user records any script. This log mainly contains client server communication information which is nearly non-readable format. This is not very useful for us since we cannot map many things of this log with our script. This log contains all protocol communication information which used by application on which we are recording.
This Log is useful when we re-generate the script using “Regenerate Script” option of Vugen. Recording log is traces created during the recording Vugen
User cannot re-generate script if this log is not available.


2. Generation Log: The time user stop recording, recording log traces converts into readable format and create a log which is known as “Generation Log”. This log is very useful to see request and response captured by LoadRunner during recording. This log can be refer in script folder by accessing the file “CodeGenerationLog.txt “


3.Replay Log: Now this is the log which helps us a lot while modifying the script. This log generated when user replay the recorded script. In this log we can see what request has been sent to server and which kind response we have received during replay. It’s become very handy when we need to find the problem where script is getting fail during replay. We can increase/decrease the reply log contents by changing the settings in “Run time setting” by selecting standard log or extended log section.


4.Co-relations Results: This log is an interesting log as correlation is very import part of performance testing. This log represents a form of auto correlation. This compares “recording log” and “reply log” and finds dynamic values received any server. We can directly correlate the values from this log. It works like F9 function. Make sure “Data” folder exists in “Script” path.

Introduction to Business Service Management Gateway, DPS and Database servers

BSM Gateway server takes various responsibilities like connecting to the Data Collector, distributing data to other BSM component, running BSM applications, Operating BSM Administration Console, providing BSM interface & Repots.

BSM Data Processing server is takes various responsibilities like Aggregating and partitioning data, running business logic engines & controlling CMDB- related services.

Database server consists of Management Database & Profile database, Business Process Insight Database, Operations Management Database, RTSM, RTSM history.

Management database: For storage of system-wide and management related Metadata for the HP Business Service Management environment. HP Business Service Management requires one management database. You can create this database manually, or by using the Server and Database Configuration utility.

Profile database(s): For storage of raw and aggregated measurement data obtained from the HP Business Service Management data collectors. Although only one profile database is required, you can store profile data in multiple databases, if required. You can create profile databases manually, or by using the Database Management page, accessible from Admin > Platform > Setup and Maintenance.

Business Process Insight Database: For storage of the Business Process Models created using the Business Process Insight Modeler.

Operations Management Database: For storage of operations management events and related data, such as annotations, as well as for storage of operations management configuration data, such as event Correlation rules

RTSM: The Run-time Service Model contains the following databases

RTSM: For storage of configuration information that is gathered from the various HP Business Service Management and third-party applications and tools. This information is used when building HP Business Service Management views.

RTSM History: For storage of changes, over time, of the CMDB configuration items (CIs). Users can view CI changes as well as view snapshots.

Review BSM 9.x

BSM 9 Overview: (Intro only)

The HP Business Service Management (BSM) portfolio provides a set of integrated, management-layer solutions, each employing a different combination of HP products and applications. The BSM portfolio enables integration of application, system, network, and business transaction monitoring, helping you to manage application performance and address issues before they impact customers; and connecting dynamic cloud and virtualized services to underlying infrastructure, to provide better visibility into services. The BSM portfolio enables effective problem-solving by the various IT teams and personas in your organization, and across the different systems, network tiers, and software layers in your IT architecture.

The BSM portfolio includes the following solutions:
➤ "Service and Operations Bridge"
➤ "Application Performance Management"
➤ "Network Management"
➤ "System Management"

Service and Operations Bridge:
BSM’s Service and Operations Bridge solution provides consolidated service and event management through a unified BSM console in the Operations Management (OMi) application, enabling you to monitor and manage the events that occur in your IT environment, and helping you restore disrupted services and minimize service disruptions.

The Service and Operations Bridge combines events from BSM components,such as SiteScope, Business Process Monitor, and Service Level Management, with events from the event-monitoring components of the BSM solution, such as Operations Manager and Network Node Manager i, and from relevant third-party products. This consolidation enables you to keep track of all the events that occur in your monitored environment.

In addition, the Service and Operations Bridge solution provides system performance management through the various dashboards available in the Service Health and MyBSM applications. The consolidation of event management with the metrics monitoring channel within BSM enables the translation of information from system events into service health resources. This consolidation is realized through usage of a shared entity called health indicators (HIs), creating a common terminology between event management and application management data.

Application Performance Management:
BSM’s Application Performance Management (APM) solution provides 24x7 application, service, and infrastructure monitoring, which enables you to manage your applications from an end-user perspective, realize the business impact of performance and availability issues, and diagnose application problems.

In addition, the Service Level Management application enables you to manage your SLAs and ensure that application performance and availability meet service level goals.
The APM solution also supports Web, J2EE, .NET, SAP, and Siebel performance management, and includes alerting, diagnostics, periodic health checks, capacity management capabilities, and trend analysis.

BSM’s End User Management software plays an important part in APM, by proactively monitoring application performance and availability from the end-user perspective, so that you can fix issues before customers experience problems. Real-time user information filtered to your development and QA teams can help reduce MTTR, improve service-level performance and availability, and decrease application downtime.

Network Management:
BSM’s Network Management solution provides unified network monitoring and management coverage across network fault, availability, performance, change, configuration, and compliance enforcement. This is achieved by a set of integrated products and tools that enhance network performance, availability, and security.

Network Management component Network Node Manager i (NNMi), offers fault, availability, and performance monitoring, with real-time network monitoring and network incident management, for physical and virtualized network infrastructure. This network monitoring solution is integrated with change, configuration, and compliance management provided by the HP Network Automation component.
This unified approach enables integrated remediation, and diagnostic automation capabilities for the technology process workflow. The solution supports multi-tenancy network management capabilities to help improve your network availability, and helps you quickly adapt to changing network environments, including data center virtualization, cloud computing, and supporting advanced services.

System Management:
BSM’s System Management solution consolidates and correlates fault and performance events across your entire physical and virtual IT infrastructure, enabling you to identify and resolve problems with full visibility into that IT infrastructure.
The System Management solution synthesizes a number of HP products and tools, including Operations Manager, Operations Management (OMi), SiteScope, Service Health Optimizer (SHO), and Service Health Reporter (SHR). The integration of data from across these products enables centralized, comprehensive IT operations management, eliminating the duplication of effort that can result from separate consoles for each IT silo.

Introduction

Hi Guys,

After a long wait and wait and wait and wait....finally we have a dedicated blog here for HP BAC/BSM (Business Availability Center/Business Service Management), HP Sitescope and HP Load Runner (Vugen). So lets get on with this....post your experiences and share your difficulties...lets make this a common platform to resolve,share and explore the world of Application Performance Management.