5. Incentivos para la calidad y la permanencia
3.4 METODOLOGIA
3.4.1 Fases de la investigacion
In case you are using the SMD data collector, have completed all configuration steps described in section
‘Setup Procedure’ and still do not get any alerts (or correctly measured values), the following hints might help to analyze the problem.
How to log on to the relevant part of Solution Manager Diagnostics?
Call transaction /nSOLMAN_WORKCENTER on the SAP Solution Manager system to access the Root Cause Analysis work center (role SAP_SMWORK_DIAG required). Additionally, ensure that your user has role SAP_J2EE_ADMIN assigned to allow access to the template.
Within the work center choose ‘Common Tasks’ ‘Administration’ ‘Agent Administration’.
This will open a new window for the agent administration. Here, choose tab ‘Applications Configuration’. In this tab, open the tree on the left hand side to ‘Agent Applications’ ‘Configuration’
‘com.sap.smd.agent.application.wilyhost’ ’ Application Resources’ ‘WilyHostAgentTemplate.xml’.
Does the SMD data collector return any values?
Follow the instructions in section ‘Check the SMD data collector results’ in the previous chapter to verify if the SMD data collector returns any values at all.
How to check if the SMD agent is configured correctly?
Additionally to the configuration steps described in section ‘Setup Procedure’ the following steps might be helpful to check further SMD customizing:
Check the overall host agent configuration. In the screen opened for the agent administration (see section
“How to log on to the relevant part of Solution Manager Diagnostics?” in this chapter) go to tab ‘Applications Configuration’ and open the tree to ‘com.sap.smd.agent.application.wilyhost’ ‘Application Resources’
‘SapAgentConfig.xml’. Here, check the entries for Resource Customization.
A configuration file for the SAP Agent must exist for every individual managed system. The configuration file can be downloaded here (area ‘Resource Customization’).
The qRFC data collector is only triggered if the configuration file contains an entry for the ‘AbapSystem’.
Where to find the SMDs Agent Log Files?
The SMD Agent writes a log file to document error situations that the agent has encountered. Such error situations could be ‘Failed LogOns to the host system’ etc. You can check these log files in case of problems with the collection of metrics via the SMD. To do so, call the Root Cause Analysis work center and navigate to the Agent Administration as described above. There, go to tab ‘Agent Log Viewer’.
Navigate to ‘Diagnostics Administration’ -> ‘Managed Systems’ -> ‘Agent Administration’ -> ‘Agent Log Viewer’. Choose ‘Display’ to display the log files.
Check the log file for error entries.
6 Monitoring of Background RFC (bgRFC)
6.1 Background Information
The Background RFC (bgRFC) is offered as a replacement for the classic tRFC and qRFC. It is available with SAP NetWeaver 2004s (SAP Basis 7.0).
bgRFC is a superordinate term for the new version of tRFC and qRFC. A parallel run of classic tRFC/qRFC and bgRFC is possible.
The Background RFC works on the basis of units and performs better compared to the classic tRFC and qRFC versions. It comes with a new Application Programming Interface (API) and a new data model.
Terminology:
o The term "unit" for the bgRFC can be compared with the term "Logical Unit of Work (LUW)" for classic tRFC/qRFC.
• A unit is a recorded sequence of collected function calls to be performed remotely.
• The recorded unit data is persisted in the database at COMMIT WORK.
• A unit can be locked. Such a locked unit cannot be processed until it is unlocked again.
o The term "destination" for a bgRFC unit defines either a remote system for outbound scenarios, or a distinct name for an application in an inbound scenario.
• Outbound destinations are maintained via the standard transaction SM59.
• Inbound destinations are maintained via the specific transaction SBGRFCCONF.
The bgRFC is based on a scheduler-driven queuing framework. This means that remote function calls are recorded, and execution takes place at a later point in time, which is controlled automatically by a scheduler process. Several schedulers can be started to process bgRFC units.
It supports the following scenarios:
o Processing on a remote system (outbound scenario)
• Use case: Asynchronous transactional processing of function calls in a remote system; processing is controlled by the caller system (inter-system communication for SAP to SAP and SAP to non-SAP) o Processing remotely by the inbound scheduler (outbound-inbound scenario)
• Use case: Asynchronous transactional processing of function calls in a remote system; processing is controlled by the receiver system (inter-system communication for SAP to SAP)
o Processing on the same system (inbound scenario)
• Use case: Asynchronous transactional processing of function calls in the same system (intra-system communication = same system and same client)
Outbound Scenario
Outbound - Inbound Scenario
Inbound Scenario Outbound Scheduler
Inbound Scheduler
In addition, there is a successor to the qRFC's "No-Send" scenario, where outbound calls are recorded, but not sent by the outbound scheduler (pull principle). Instead, the receiving system is supposed to fetch its RFC records itself. In the bgRFC context this is called Local Data Queue (LDQ).
The bgRFC provides two qualities of service (QoS) for remote function calls, offering an asynchronous transactional system-to-system communication:
o exactly once (EO) => transactional units (like the classic tRFC)
• Each unit is an independent thread
o exactly once in order (EOIO) => queue units (like the classic qRFC)
• Units with sequence dependencies
Valid Combinations of QoS and Scenario:
QoS Inbound Outbound Outbound to
Inbound
(No-Send)
tRFC (EO) X X - -
qRFC (EOIO) X X X X