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.

Before we are able to analyze and determine tuning areas, we need to understand Oracle Server Architecture and it's underlying mechanism. Oracle Server Architecture consist of two main categories: logical (memory) structures and physical (or file) structures. The Oracle memory structure is collectively known as Oracle Instance. While the physical file structures are collectively known as Oracle database. Together, they are call an Oracle Server.

In the previous article, "How-to record and replay ESRI ArcGIS Desktop (ArcMap)?" we proposed four techniques to record and replay ESRI ArcGIS Desktop, and how each techniques work generally with the application.  In this article, we will discuss particular business activities that will be recorded and what are the areas of concerns that will be affected during a load test.  We will be using Web (HTTP/HTML) protocol of LoadRunner for this discussion.

Typically, a user will launch ArcGIS Desktop, open a layer and perform zooming and panning activity throughout the usage of the application which is listed below:

This article provides a basic understanding that you can use in recording and replaying of the ESRI ArcGIS Desktop (ArcMap) communicating with ArcGIS Sever. GIS stands for Geographical Information System which examples are Google Maps and Yahoo Maps. There are four approaches I figured out to conduct the load testing using LoadRunner. Again, we need to grasp some concepts on how LoadRunner works in recording and replay in "Which protocol to use?" and how we can apply onto this technology. Basically, they consist of (1) loading of the SOAP/HTTP traffic, (2) replaying of the actual Web Service, (3) replaying of the methods and assemblies and (4) replaying of the scripts created in Visual Studio using Visual Studio AddIn and ArcGIS SDK.

We will go through the approaches in LoadRunner and briefly touch on the similar options available in SilkPerformer.