Monitoring SAP in SilkPerformer
Posted: November 24th, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: SAP, SilkPerformer | No Comments »
SilkPerformer also offers monitoring solution to SAP during a load test. However, unlike LoadRunner that depends on SiteScope as an intermediary to monitor SAP, SilkPerformer uses the TCodes (Transaction Code) directly to query the monitoring statistics. (Refer back to “Monitoring SAP in LoadRunner” for more information on monitoring SAP using LoadRunner).
Comparing LoadRunner-SiteScope monitoring solution that utilizes CCMS (Central Computer Management System) which has more monitoring capabilities, SilkPerformer only retrieves monitoring statistics from four TCodes. They are ST02: SAP Buffers, ST03N: R/3 Workload and Perf. Statistics, ST04: Database Performance Monitor and ST06: Operating System Monitor.
From the TCodes, it does a reasonable job of monitoring the SAP system on the overall performance. The TCodes should cover (a) SAP Buffer performance, (b) Dialog Step performance (response time), (c) database performance at the database buffer cache and shared pool level and (d) operating system performance such as processor and memory.
Through this setup, SP Controller merely make a normal connection like a typical SAPGUI Front-end. Therefore, typical ports used by the SAPGUI Front-end such as TCP32## and TCP33## are required. Furthermore, the user account used for the monitoring should have sufficient privileges to access the mentioned TCodes.
Leave a Reply