Configuration to resolve WoC information in DSR stats
[ByD] [could not resolve] [DSR] [Java] [NWA] [resolve] [resolve now] [skip name resolve] [ST03G] [statistics]
Symptom
You don’t see any or only incomplete work center related information in transaction STATTRACE and/or you SAP Live Link data collector WORKCENTER_ACTUAL_USAGE doesn’t deliver any data.
You could check this by running transaction STATTRACE, selecting data from a suitable period and filtering on service type ‘Portal’.
If you don’t get any data in the work center column resolved or only ‘n/a’ is displayed, check below if all necessary configuration steps have been performed.
Other terms
ST03G, DSR, JAVA statistics, ByD, NWA
Reason and Prerequisites
This functionality is only valid for Business By Design 1.01 FP2.0. It is based on the standard Distributed Statistical Records (DSR) which is embedded into the JAVA stack within the SAP Portal.
All configuration steps need to be executed successfully in order to be able to store and analyze workcenter related information
Solution
All of these configuration steps should have been executed automatically by default. Please check carefully if the corresponding entries are available – only if they are missing these steps should be performed manually.
Prerequisite: General DSR configuration
As basis for any work center based analysis, a successful configuration of the whole DSR statistics framework is necessary. So if you face any general problems in retrieving DSR data within transactions STATTRACE or ST03G, please check the general FAQ note 1090526.
WoC Configuration steps in NetWeaver Administrator NWA
Please ensure that your user possesses the necessary authorizations to perform any changes in NWA.
STEP 1
PATH:
NWA: Operation Management – Systems – Start & Stop > Java EE ApplicationsACTION: start “_smart_usage_hook”
STEP 2
PATH:
NWA: Configuration Management – Infrastructure – Application Modules, select Web Module webdynpro/resources/sap.com/pb => WebDynpro properties – components/com.sap.portal.pb.PageBuilder/DefaultACTION: set “includePortalHooks” to “true”
WoC Configuration steps in ABAP backend
The Web Service proxy has to be configured in the ABAP backend. Please ensure that your user possesses the necessary authorizations to run this configuration step.
STEP 3
ACTION: run function module SAPWLN3_LP_PORTALMETADATA in client 000PARAMETER DESCRIPTION:
> HOSTNAME
> PORT
> USERNAME
> PASSWD
> URL_PATH /PortalStatisticsWS/Config1?wsdl&style=document
STEP 4
ACTION: register report RSN3PCD in table TCOLLENTRY DESCRIPTION:
> RNAME RSN3PCD
> RENUM 1
> SYTYP S
> ALTSY
> DAYOW XXXXXXX
> TIMOD XXXXXXXXXXXXXXXXXXXXXXXX