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. 

LoadRunner TnT is a resources hub on working knowledge of software performance testing and engineering.  Specified topics covered here includes various concepts working with performance testing tools, troubleshooting, analyzing performance results and tuning of system resources (e.g. Windows or Oracle).  Although LoadRunner is our primary tool of discussion, we've also included articles covering other tools such as SilkPerformer, etc that are used in performance testing.  This site is constantly being updated, so be sure to check back again! 

If you are new to this site and feeling lost with the information here, start with "What's LoadRunner?" first to help you get a head start!

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.