HP SiteScope software helps you to agentlessly monitor the availability and performance of distributed IT infrastructure and applications including servers, operating systems, network services, virtualization software, applications, and application components. SiteScope continually monitors many types of IT components through a web-based architecture that is lightweight and highly customizable.
How to set up the SAP monitorSetting up the SAP monitorServer:The SAP monitor supports SAP R/3 server versions 3.1 to 4.6 (Kernel release 46D and below).Set up a user ID in SAP for LoadRunner. This user ID must have access to the st03 transaction (st04 if monitoring st04 transaction). Otherwise, no metrics will be returned even though LoadRunner is able to connect.Controller:You need to have LoadRunner7.02 or above.
For monitoring against st04 transaction, however, you need. LoadRunner 7.5 or higher.
QTSAP 7.3 build 170 or above. Install the Virtual User add-in on the Controller machine for LoadRunner 7.5 and 7.51.
This is not required for 7.6 or above. You need to have license for SAP monitor. If not, please contact your local Sales Representative. SAPGUI 6.2 client or below installed on the Controller machine. Make sure that you use the user ID with access permission (refer to the server section) to the st03 and/or st04 transaction:1. Open SAP and login with the user ID.2. There is a text box in the top left corner where you can type in a transaction.3.
Type in st03 or st04.4. If a screen comes up with metrics or choices for metrics, LoadRunner should be able to monitor SAP.Adding the SAP monitor from the Controller:1. In the Controller, look for the 'SAP' monitor in the ERP/CRM Server Resource Section.2. Display the graph by dragging it to the right.
Right-click in the graph and select 'Add Measurement(s).' You should see the 'SAP' monitor window.3. In the Monitored Server Machines section of the SAP dialog box, click to enter the server name or IP address of the machine you want to monitor. Select the platform on which the machine runs, and click.Note:You can also specify a system number and IP address in the Add Machine dialog box using the following format:Example:199.35.106.162:004 Click in the Resource Measurements section of the SAP dialog box. The SAP Monitor Logon dialog box opens.
Enter your Login Name, Password, Server Name, and Client.Note:If you want to connect to the SAP monitor through a router, you need to enter the router string into the Server Name field. A router string has the format:where RouterString has the format /H//H//H/. ServerIP is the application server IP address.
Xx is the system number.Example:router string = /H/199.35.107.9/H/204.79.199.244/H/application server IP address = 172.20.11.6system number = 00You should enter the following string into the Server Name field:/H/199.35.107.9/H/204.79.199.244/H/172.20.11.6/S/sapdp005. The Add SAP Monitor Measurements dialog box will open. Select the counters to add and add them.6 Click in the SAP dialog box to activate the monitor. How to set up the SiteScope – Unix/Linux monitor Requirements Server Resource monitor license LoadRunner 7.51 or above: For LoadRunner 7.6 or above, the SiteScope Unix monitor is built into the Controller. For LoadRunner 7.51 SP1, make sure that you install the Controller add-in, LRNewSiteScopeMonitor.exe.
This is available in the Patches database ® LoadRunner ® 7.51 SP1 ® Performance Monitor ® LR751SP1P2 ® LoadRunner 7.51 SP1 SiteScope Unix monitor for LoadRunner version 7.51. How to set up the Citrix monitorSetting up the Citrix monitorSupported Citrix Citrix MetaFrame versions MetaFrame XP MetaFrame 1.8Setup1.
LoadRunner uses the same username/password as the Controller machine to log into the Citrix server. Therefore, make sure you have the same set of username/password on the Citrix machine. You can also map a network drive from the Controller machine to the Citrix server to ensure that the required authentication is provided to the Controller to access the resource counters.2.
Sitescope Documentation
Make sure that 'Network DDE' service is started on the Citrix Server. To start the 'Network DDE' service:a. Go to Start - Settings - Control Panel - Control Panel - Administrative Tools - services.b. Right mouse click on 'Network DDE', and select.3. Make sure that 'Remote Registry' service is started on the Citrix Server. To start the 'Remote Registry ' service:a. Go to Start - Settings - Control Panel - Administrative Tools - services.b.
Sitescope Tutorial
Right mouse click on 'Remote Registry ', and select.VerificationLaunch PerfMon from the Controller machine to enable the counters on the Citrix server. Go to Start - Programs - Administrative Tool’s - Performance Monitor (PerfMon) from the Controller machine to enable the counters on the Citrix server. If you have problems with this, you need to contact your system/network administrator to make this object available to see from PerfMon. This allows you to monitor the same counters for the ICA Session object on LoadRunnenr’s Citrix monitor.MonitorTo provide the Controller with a list of measurements that will be available for monitoring, you must first initialize Vusers before running the scenario.
After you have initialized the Vusers, you can then configure the Citrix Monitor and add the ICA Session counters.Additional Information1. When monitoring a counter under the ICA Session object, please be sure that at least one session is currently connected to the server. Otherwise, you will not be able to add any counters.2.
Measurements that monitor instances are valid for the currently running Citrix session only. If you run this scenario again, you will need to reconfigure the measurements that are instance-oriented.3. For further details and step-by-step information, please refer to LoadRunner’s Controller’s books online. The Controller uses up all the memory though no scenario is runningThe Controller seems to be utilizing all the memory resources. Without any scenario running, the user noticed that the memory utilization for wlrun.exe increase drastically.Diagnosis: Some processes or services on the machine might be interfering with the normal Controller operation.Identifying processes that might interfere with the ControllerTo verify the processes or services that might interfere with the Controller, you can use the. This application helps to list all the DLLs that are loaded.Apart from that, it has been observed that the following might interfere with wlrun.exe:. VNC (Virtual Network Computing) client.
SPYWARE ( using software like Ad-Aware ). ExeSpy2000.