Implementing SiteScope with LoadRunner
Posted: April 22nd, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: LoadRunner, SiteScope | 7 Comments »For every LoadRunner installation CDs/DVDs, a reduced version of SiteScope is provided in the “Additional Component” folder. Locate and run the SiteScope installer to install SiteScope.
Before we start (running the installer), lets get some basic understanding of how SiteScope works. For SiteScope to integrate with LoadRunner or communicate as per say, it’s very simple. SiteScope has a default port 8888 that displays the collected monitoring data as a XML page, and what LoadRunner does (same concept behind native monitors, refer to “How does the monitoring work in LoadRunner?“), is to retrieve the statistics off the SiteScope XML page via port 8888.
Note:
SiteScope’s default port can be changed at the administration console. Refer to the “SiteScope Administration Guide” for more information on this. If you changed the ports in SiteScope, you will need to change the port which LoadRunner connects to SiteScope as well. This is covered in “How to specify the information in the Controller if SiteScope is not running on the default port (8888)”.
Therefore, before you start the integration, you need to ensure two things:
- 1. Port 8888 (default) is opened two way between SiteScope and LoadRunner machines.
2. XML page is displaying monitoring data.
3. SiteScope is already collecting statistics from the SUT (System Under Test) and displaying it on it’s machine
Take note, SiteScope and LoadRunner works the same way in monitoring. (Refer to “How does the monitoring work in LoadRunner?“). SiteScope utilizes Perfmon to collect statistics from Window servers. As such, the same thing apply, you will need an account in the Windows server and port 139 to be opened two-way from the SiteScope machine to the Windows machine. Once, you’re able to see the monitoring data in SiteScope, you can move on to the LoadRunner portion. I will leave the configuration of the connecting the SiteScope to Windows server to the SiteScope User Guide.
The following illustrates an implementation of a load test on the monitoring via SiteScope. Click on it to view the enlarge version.
Using Windows server as an overview example, you will have to go through the following steps:
- 1. Ensure that Perfmon is working on the Windows machine.
2. Ensure that SiteScope has an account to access the Windows machine.
3. Ensure that port 139 is opened between Windows and SiteScope machine.
4. Ensure that SiteScope is receiving monitoring data.
5. Connect the SiteScope to LoadRunner in Controller.
6. Ensure that LoadRunner is displaying the statistics in Controller.
We’ve covered briefly but should be sufficient for you to know the requirements needed when implementing SiteScope as the monitoring mechanism for LoadRunner. For the actual details of the setup, you may like to consult the user manuals as they provide details of step-by-step procedures.
Can you elaborate on how you get the XML page to display the performance data for the monitors you have in SiteScope? I can load the XML page, but no counters/performance information is shown (it’s pretty much an empty XML doc). If you could refer to the specific SiteScope documentation that would be great, I seem to get lost in their multiple PDFs and finding specific info is cumbersome at best.
SiteScope itself actually collects the monitoring results from the XML page as well. Have you configured any monitoring on SiteScope in the first place? Nothing should be displayed without first configuring SiteScope to collect statistics.
Just wanted to ask if we require a separate license for sitescope that comes by default with LoadRunner?
Do we need to install site scope on client side (or) server side? Which will be give more effective and accurate?
SiS “light version” (incl. in HP LR) is free of charge, bundled in HP LR 9.x ISO image. No additional expenditures with licenses are needed. But you can download SiS 10 with eval. license. There is possibility to register through HP BTO SW pages, create own HP passport and get the bundle of 500 measurement points (again .. free of charge).
HTH
i like the article above,can somebody tell me the differences between mercury diagnostics and sitescope?.I am aware of few but would like to know all if possible.
Sitescope should live on it’s own machine, and yes, you need a license to run sitescope, you will need to contact HP licensing and request a SiteScope license, each copy of LoadRunner you have a license for includes a 500 point sitescope license. However you CANNOT use that Sitescope instance for production use, only for monitoring related to testing.