Usage Analysis is always a hot topic with the IT folks and it always finds itself on the desk of the Manager who asks the question ” Who’s doing what in my portal?” . This Blog series will attempt to collate all information about the SAP Netweaver Portal usage analytics. I will talk about integrating Web Trends with SAP Netweaver Portal and its different ways of doing so. It will also talk about Google Analytics and other existing resources in SDN.
1) Portal usage analytics : check this before you go for Web Trends.
Portal Out of the box already provided some basic User Activity Reporting with ” Portal Activity Reporting”
For more details click on the link by John Polus: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e07edaa8-70ae-2b10-2390-f068636c8b1e
The Portal Activity Reporting shows some basic features but does not support KM.
This was a buildup to the implementation of the Activitiy Data Collector which is
- better in performance
- captures a lot of extra parameters
- works with KM usage data capture too.
The above link by John Polus talks about this in detail.
2) Google Analytics Integration : Another alternative to Web Trend Integration
An excellent document by Craig has been submitted into SDN for Google integration for Analytics into SAP Portal.
3) Web Trends Integration with SAP Portal
Scenario 1 : Integration using HTTP Logs and ADC
Scenario 1 a : HTTP LOGS
The Portal runs atop the SAP Netweaver Application Server JAVA. As per standards of the Java Application Server , you can enable the J2EE HTTP application logs to contain some information about the requests it serves.
The generated Log files will store the following information in the common log file format. For more information you can visit the following link :
What is logged in CLF format?
What to do when you want to capture additional data?
At the end result, you will get a HTTP trace file in the CLF format. You can use this information and then do some data processing to get into the format in which Web Trends can recognise and the finally feed into Web Trends.
The steps are as follows:
- 1. Enable HTTP Logging and Trace in the Portal
- 2. Configure HTTP Provider Service to log the required information
- 3. Convert the data in the log file to the one suited to your Web Trends Information ( optional)
- 4. For KM content, you need to create a custom KM log file ( custom development) and the also include this into your Webtrends source.
- 5. Mount these documents to be available to the web trends server automatically
- 6. Build a schedule in Web Trends server to regularly check for this files and buid the Analytics report.
Scenario 1 b : ADC log file
The ADC service provides a log file with a lot of information and the best part is that it includes information from the KM usage statistics as well. So this will be a richer log file than the scenario for HTTP logging.
The detail for the information is provided in the above link under the ADC section by John Polus. This enables you to use even SAP BI for the analytics.
The steps are as follows:
- 1. Enable ADC service for Portal and KMC
- 2. Convert the data in the log file to the one suited to your Web Trends Information ( optional)
- 3. Mount these documents to be available to the web trends server automatically
- 4. Build a schedule in Web Trends server to regularly check for this files and buid the Analytics report.
Scenario 2 : Portal Usage Analytics with Web Trends through SDC
In my second part of the web log I will talk about how to use the SDC technology and methodology to integrate Portal Usage with Web Trends. I will discuss
- 1. Steps
- 2. Technology
- 3. Requirements
- 4. Pros and cons