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.

How HP Sitescope works!

How HP SiteScope works

HP SiteScope provides a centralized, scalable architecture. HP SiteScope is implemented as a Java server application and runs on a single, central system as a daemon process. The HP SiteScope Java server supports three key functions: data collection, alerting, and reporting. All user interaction is accomplished through a Web-based user interface that enables configuration, installation, administration, real-time status, and reporting from one seamlessly integrated console.

Sitescope Architecture

Sitescope consists of following components:

·         Browser based interface – Manages end user status information requests, configuration changes requests and access control.

·         Scheduler – Coordinates the running of monitors, alerts creation and report generation.

·         Monitors – Collects performance and availability information about the system being monitored.

·         Alerts – Notifications of exceptions, failures and status changes events in the system being monitored.

·         Reports – A historic representation of monitored data for trending and analysis purpose.

Sitescope Unix CPU script monitor

CPU script monitor created after building a script and deploying the same in scripts.remote folder.

Script used:

Idle=`mpstat -P ALL 2 3 | grep ^Average | awk '{print $11}' | head -n 2 | tail -n 1`

Wait=`mpstat -P ALL 2 3 | grep ^Average | awk '{print $6}' | head -n 2 | tail -n 1`

echo "scale=2; 100-"${Idle}+${Wait}"" |  bc –l

Note : Here print $ value positions may change

Logic:

Here the 1^st command fetches the 11^th value in the average row say “A”

Second command fetches the 6^th value in the average row say “B”

Third command adds the above two values (A+B) and subtracts the results from 100 to give the %utilization.

Formula:

%Utilization = 100 – (%Idle + %Wait)

Using Netstart and Netstop Commands for SiteScope on Windows/Solaris and Linux OS

Windows:

You can also start and stop the SiteScope service by using the netstart and
netstop commands.

To start the SiteScope service using netstart:
1 Open a command line window on the server where SiteScope is installed.
2 Run the netstart utility using the following syntax:
net start SiteScope

To stop the SiteScope service using netstop:
1 Open a command line window on the server where SiteScope is running.
2 Run the netstop utility using the following syntax:
net stop SiteScope

Solaris/Linux:

To start the SiteScope process on Solaris and Linux:
1 Open a terminal window on the server where SiteScope is installed.
2 Run the start command shell script using the following syntax:
/SiteScope/start

To stop the SiteScope process on Solaris and Linux:
1 Open a terminal window on the server where SiteScope is running.
2 Run the stop command shell script using the following syntax:
/SiteScope/stop

General ports required for making connection with Sitescope tool

Below is the prerequisite we require for the new servers in order to establish the connection with Sitescope tool.

WMI/NETBIOS	135-139
Sitescope Web server	8080
FTP Monitor	21
Mail Monitor	25 (SMTP), 110 (POP3), 143 (IMAP) News
Monitor	119
Ping Monitor	packets
SNMP Monitor	161 (UDP)
URL Monitor	80,443
Remote Windows Monitoring	139
Email Alert	25
Post Alert	80,443
SNMP Trap Alert	162 (UDP)
Remote UNIX ssh	22
Remote UNIX Telnet	23
Remote UNIX rlogin	513

Sitescope Monitor Output Error Codes

Below are some of the error code which we get as a monitor run output on Sitescope dashboard:

• URLPermissionDenied = -982               "Permission denied"
• SOAPFaultError = -983 
• XMLElementNotFoundError = -986     "XML element not found"
• XMLFormatError = -987                      "XML format error"
• XMLElementMatchError = -988           "XML element value mismatch"
• URLContentErrorFound = -989             "content error found"
• URLContentElementMissing = -990       "content element missing"
• URLNoStatusError = -991                    "no status in reply from server"
• MonitorSpecificError = -992; 
• URLNoRouteToHostError = -993        "unable to reach server"
• DLLCrashedError = -994                     "internal error in WinInet library"
• URLContentChangedError = -995        "content changed"
• URLTimeoutError = -996                     "timed out reading"
• URLBadHostNameError = -997           "unknown host name"
• URLNoConnectionError = -998           "unable to connect to server"
• URLContentMatchError = -999            "content match error"
• URLUnknownError = -1000
• DNSIPAddressMismatch = -1001        "ip address does not match"
• URLRemoteMonitoringError = -1002    "unable to connect to remote monitoring server"
• URLConnectionClosedError = -1003    "connection reset"

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.