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. 

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.

Oracle includes several application program interfaces and Java class libraries in order to facilitate the interaction of Java-based applications with Oracle databases.  Oracle also allows you to dedicate a portion of the SGA, called Java Pool, as the location where session-specified Java code and application variables reside during program execution.  

Oracle provides the ability to create a optional area in the SGA (System Global Area), called the Large Pool to provide large memory allocations for the following. By allocating session memory from the large pool for shared server, Oracle XA, or parallel query buffers, Oracle can use the shared pool primarily for caching shared SQL and avoid the performance overhead caused by shrinking the shared SQL cache.