Monitoring SAP in SilkPerformer

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).
Read the rest of this entry »

Monitoring SAP in LoadRunner

In LoadRunner SAP monitor, it requires the SAP CCMS (Computer Center Management System) for monitoring to be effective.  This is unlike the typical monitoring mechanism that is used for Windows or Oracle (refer to “How does the monitoring work in LoadRunner?”), which is directly querying the monitor data from Windows Perfmon or Oracle V$ dynamic views.  LoadRunner SAP monitor requires an additional component, SiteScope (refer to “What’s SiteScope”) to act as an intermediary between SAP CCMS and LoadRunner. Read the rest of this entry »

Introducing SAPGUI protocol in LoadRunner

Performance testing recording and execution for SAPGUI relies on the SAP Scripting API and ActiveX the SAP R/3 application server and on all SAP GUI clients that are participating in the load test. As of date of this article, LoadRunner documentation does not have updated details on configuring SAPGUI for scripting such as supported versions.  However, the configurations are somewhat similar to other performance testing product which in this article, we refered to IBM instead.

Read the rest of this entry »