Understanding WebLogic (JMX) monitoring

Posted: May 14th, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: , , , | 3 Comments »

What’s WebLogic (JMX) all about in LoadRunner? If you are not J2EE background professional and caught up in a load test for WebLogic servers, this article will be useful to you as we’ve put together information to help you get a better understanding of JMX (Java Management Extensions). We will be going through the fundamentals of JMX and how it works in together with LoadRunner. We will also be touching on the reference list of available counters provided by WebLogic. If you like to know the configuration details, look out the Monitor Reference that comes together with the installer (which is pretty easy to configure). Read the rest of this entry »


How-to configure MySQL database monitoring

Posted: April 28th, 2008 | Author: TnT Admin | Filed under: How-Tos | Tags: , , , | No Comments »

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.

Posted: April 24th, 2008 | Author: TnT Admin | Filed under: Errors | Tags: , , , | No Comments »

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 »


4 Monitoring Implementation Models

Posted: April 22nd, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: , | No Comments »

Let’s touch on the monitoring implementation model for now. A new topic that was not covered in the predecessor site. You will benefit in understanding how to implement the the monitors in the testing environment as well as provide the requirements to the network and server teams to set the monitoring.  In this article, we will be omitting the details of SiteScope and Diagnostics integration and the implementation for the moment and they will be discussed in future post! So stay tuned for that! Read the rest of this entry »


How does the monitoring work in LoadRunner?

Posted: April 22nd, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: , | 8 Comments »

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 »