Monitoring SAP in LoadRunner

Posted: November 20th, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: , | No Comments »

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 itself does not have the capability to monitor SAP directly and solely depends on SiteScope to query/monitor SAP CCMS.  SAP CCMS is already a powerful component in SAP as it is able to monitor anything in the SAP system. This ranges from server resources (e.g. processor or memory utilization) to oracle databases (e.g. buffer efficiency).  You may not even require other tools to do monitoring in the first place!  No additional configuration needed for monitoring Windows resources (Windows Resources) as SAP CCMS handles it by a single channel through SiteScope.

For SiteScope to communicate to SAP CCMS, it will require SAP Java Connector (JCO) to be installed on the SiteScope box with some configurations to access the SAP system.  The detailed configuration can be found in Configuring Sitescope Monitors documentation (instead of LoadRunner).  To download SAP Java Connector, you can go to Connectors in SAP site.  You will need a valid SAP account to access the download page.

On the ports portion, you will need to have TCP32## between the SiteScope and the SAP system and TCP8888 between SiteScope and LoadRunner (Refer to “Implementing SiteScope with LoadRunner”).  TCP32## is the typical port number used by SAPGUI Front-end to talk to the SAP application servers while TCP8888 is used by LoadRunner to query the monitoring data displayed on the XML page of SiteScope.  Both port numbers are to be opened on a two-way traffic communication.
As SiteScope is querying monitoring data just like a normal user running the CCMS transaction from SAPGUI Front-end, a SAP account on the SAP system required.  The following information must be ready prior the setup of the monitoring.

  • SAP Client
  • System Number
  • Authorization User Name
  • Authorization Password
  • SAP Router String (Optional)

Do take note on this!  With all things mentioned about SAP CCMS with LoadRunner-Sitescope, there’s a catch (at least to me).  SiteScope requires an optional license to monitor SAP CCMS.  Which means, that if you are just having LoadRunner, it’s not sufficient to setup the monitoring environment.

Related Posts

Leave a Reply