How-to configure MySQL database monitoring

In LoadRunner (as of this writing which is version 9.0), the supported databases that can be monitored are mainly proprietary, such as, Microsoft SQL, Oracle, Sybase and DB2. Open sources such as MySQL are not supported. In order to monitor this type of databases, we have to employ alternative methods. And one of it, is to utilize SiteScope.

MySQL database monitoring will require SiteScope to be deployed acting as a bridging collector before it can be displayed in LoadRunner. The connection is illustrated in the following. Read the rest of this entry »

Parsing error. Details: host localhost,port 1112, line: 1. Reason: Invalid at the top level of the document.

Parsing error.
Details: host localhost,port 1112, line: 1.
Reason: Invalid at the top level of the document.
.
Contents: java.lang.Exception:java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogoc.admin.mbean, Administrators] [MsgId:MMSG-47587]

Background information: I’m monitoring 4 WebLogic servers using WebLogic (JMX) Monitor in LoadRunner and adding their JMX stats into Controller. Upon adding the subsequent server, the error appeared after entering the username and password to the Controller. I’m using LoadRunner 9.0 and Weblogic 8.1 in this context. Read the rest of this entry »

How does the monitoring work in LoadRunner?

The objective of LoadRunner is simple; to load an application (set upon a certain environment and hardware), monitor the servers that is in the environment housing the applications, and lastly collect the results for analysis. LoadRunner sells itself as a load testing tool that is not intrusive in any environment with the capability of not requiring installation of agent programs on the servers in the environment (anyway, most monitoring tools work in this way).  How is this achievable? Read the rest of this entry »

LoadRunner licenses

LoadRunner requires license to function. The license entitles to (1) the protocol the user is permitted to run, (2) the number of Vusers (or concurrent users it can generate) and (3) the type of monitors available to the user. After LR8.1 FP3 (standing version of this writing is LR9.0), the license model have changed from individual or group protocols to Bundle Licenses. In a Bundled License, the protocols of the same genre are grouped together (e.g. Web (HTTP/HTML), FTP, Winsock are grouped together into Web & Multimedia Bundle). This (in my opinion) provides a neater way to manage the licenses. Also, the all monitors are made available as “All Monitors” with exceptions to the diagnostics modules (e.g. J2EE, .NET, SAP, etc.). Read the rest of this entry »

How do we load test a 3-tier architecture using LoadRunner?

Hit on the spot! An interview question for newbies! Yes, we can load test a 3-tier architecture using LoadRunner. This is the purpose of the product. Usually in a 3-tier architecture, there will be one point of contact by the real user, the URL address of the web application. This is where LoadRunner access the web application too. Read the rest of this entry »