
Introduction
In a business environment which utilizes the Enterprise Portal (EP) as a central platform as we know the number of users can vary from a few hundred to a few thousand depending on the business setup. In true essence the SAP NetWeaver Portal is a key cornerstone in the SAP NetWeaver architecture. Through web browser interfaces the EP is the conduit channel through which users begin going about their daily tasks and the portal itself provides such users with a central point of access for all work related procedures and processes.
Usage Statistics EP Environment:
With the EP offering users a single point of access to information, documents, enterprise applications, processes and services both inside and outside of an organization its understandably easy for a simple environment to become complex quite quickly in terms of a high level perspective. In short the Portal provides access to business processes and information, social collaboration and content management across various consumption channels. Also with the ever-growing number of mobile phone business users the Portal needs to be maintained in an optimal an efficient manner.
Portal Activity Report & Activity Data Collector - Are They Similar?
You can make use of the Activity Data Collector (ADC) or the Portal Activity Report depending on your core business requirements and operational preference. The Activity Data Collector (ADC) collects more detailed information about portal requests and saves this information into files with one line dedicated to each logged request. With the Activity Data Collector (ADC) you are given access to raw data which can be gathered and deciphered as required. Here it is a non-automated process and you (yourself) are responsible for analyzing the raw data and created subsequent reports upon it or graphical representation breakdowns.
The Portal Activity Report on the other hand is a dedicated statistical based tool for the Enterprise Portal (EP). The underlying functionality of the Portal Activity Report is focused upon gathering information pertaining to Portal visitors and the pages/iViews viewed during the user sessions of such visitors. This information is contained with a dedicated iView through which fundamental reports can be generated based upon the Portal's activity. Such data (contained within the report iView) is aggregated generated within predefined report types.
Activating the Portal Activity Report
Monitoring Pages of Interest
If you wish to monitor a certain core application iView or simply a page of interest this is indeed a feasible notion and can be achieved quite simply once the correct parameter settings are maintained. In order for such results to be firstly captured and then aggregated within the Portal Activity Report you need to ensure the following:
In summary iViews which need to be monitored need to be assigned to a role and then subsequently to the report itself.
Monitoring Page Hits
If you are using a configured Activity Report in the Enterprise Portal (EP) to gather and report findings on all of the pages that have been visited you may want to include page hits as a metric in the report listing.
Monitoring Certain Users
To monitor hits for a certain user types you need to ensure the property “Monitor Hits” is set to true. For additional guidance on this topic the following Wiki is a great source of reference.
Creating Portal Activity Report iViews
FAQ’s - Portal Activity Report Functionality
Issues - Portal Activity Report
Activity Report issues are often solved by applying the latest SDA release file.
Key Reference & Troubleshooting Documentation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 | |
5 |