Portal Analytics is the process of Collecting, Processing, and Reporting portal usage data.
Using Portal Analytics you can collect data about the usage of your portal site and send that data to a service for analysis.
There are two main approaches for collecting analytics data:
1. Server side data of your portal site. This consists mainly of technical data internal to the portal.
2. Data about the behavior of your client users. You analyze this data by using Active Site Analytics.
To retrieve data from portal we write Scripts which are called
Aggregators.
The aggregators typically submits the collected data to an external analytics service where the data is then recorded, processed, and formatted in the form of reports.
This aggregators are located in the PortalServer_root/doc/js-samples directory of your portal installation.
Portal supports several aggregator tags, like; asa.portlet.title etc...
Process for Active Site Analytics
1.
Collecting analytics data
Before we can send data about user behavior in our portal to a service for analysis, we need to collect that data.
2.
Displaying overlay analytic reports
Active Site Analytics show graphical statistics reports about individual portal resources, such as pages or portlets.
These reports are called Active Site Analytics overlay reports.
3.
Analytics tags and site promotion
1. Collecting analytics data
The data for the analysis of user behavior is retrieved from markup embedded in the portal pages.
The data is represented as a 'microformat' in portal page. An example of such microformat is:
<span class="asa.portlet.title">My Portlet</span>
Portal supports several aggregator tags, like; asa.portlet.title etc...
The aggregator typically submits the collected data to an external analytics service where the data is then recorded, processed, and formatted in the form of reports.
Portal administrators can manage the aggregators. They can assign an aggregator to one or more portal labels or pages.
How to add an ASA aggregator to a portal page
- Goto webDAV-->js folder-->take the name of the aggregator file. ex:- asa_sample.js
- Goto Portal administration-->Manage pages-->Page(to set aggreator)-->Page properties-->Advanced
options-->I want to set parameters
-->Add Parameter and Value(aggregator file name)-->ok-->ok
*In the field New parameter, type a string that starts with 'asa_aggregator' or 'asa_dependency' . asa_aggregator are added to the page body, asa_dependency are added to the head.
2. Displaying overlay analytic reports
The overlay analytic reports are shown as a statistics graph on a portal page.
The statistics are generated as follows:
-> The data collected by the portal site analytics are collected and forwarded to your business partners for portal analytics.
-> Your business partner analyses and evaluates the portal data and sends back a report to your portal.
-> The portal then displays the report as the overlay graph.
To setup active site analytics overlay report on portal, we have to follow these steps:
1. Enable data collection. For example, you can do this by adding an Active Site Analytics aggregator to a portal page:
-> Access the IBM® Coremetrics® Web Analytics web site or contact your Coremetrics
representative.
-> Retrieve the appropriate aggregator file from Coremetrics.
-> Upload the aggregator file to your portal theme folder, for example, by using WebDAV.
-> Add Active Site Analytics aggregator to a portal page.
-> As a result of these steps, analytics data is sent from browsers of your portal users to the
Coremetrics data collection servers.
-> You can log on to Coremetrics and analyze the portal usage.
2. Enable inline display of Coremetrics reports by enabling overlay reports:
-> Establish trust with Coremetrics servers.
To display overlay analytic report we have to configure/activate overlay reports for our
site :
- Goto Admin console-->Resources-->Resources Environment-->Resource
Environment Provider-->WP Config Services-->Custom Properties-->New
- Use the property name 'wp.proxy.config.urlreplacement.default_policy.1' and
the value https://welcome.coremetrics.com/*
- If this name is already in use increment the counter of key.
- Apply and Save.
- Next, Import the Coremetrics certificate into your server truststore.
- Goto Admin console-->Security-->SSL certificate and key management--
>SSL configurations-->NodeDefaultSSLSettings-->Key stores and
certificates-->NodeDefaultTrustStore-->Signer certificates-->Retrive form Port,
and fill the form with details
'NodeDefaultSSLSettings' is for Stand-alone environment
'CellDefaultSSLSettings' is for Portal Clustur environment
- For the host: welcome.coremetrics.com
For the port: 443
For the alias: coremetrics or another identifying string of your choice.
- Retrive Signer Information and Apply & Save.
-> Optional: Set up security for overlay reports.
- You can administer which users can view overlay reports.
- To do this, you use the virtual resource OVERLAY_REPORTS having USER
role assigned.
-> Configure your Coremetrics user ID.
- To access the IBM® Coremetrics® Web Analytics system, you have to store
user information in a Credential Vault slot.
- If you do not do this, the portal overlay reports cannot show data from the
Coremetrics system.
- To configure this we require,
Coremetrics client ID
Coremetrics user name
Coremetrics authentication key.
- Goto admin-->access-->credential vault-->add vault slot, and fill the portlet
with details
- name : com.ibm.portal.asa.coremetrics.slot
shared user ID : coremetrics_user_name#coremetrics_client_id
-> Display overlay reports by choosing Show Portlet Reports or Show Page Reports.
- To enable overlay statistics, the user opens the page actions menu and selects
either Show Portlet Reports or Show Page Reports.
- When the user clicks a report type in the actions menu, the display reports
setting is persisted in the navigational state.
- This means that the user can now navigate through the portal and view statistics
on every page that the user visits.
- To disable overlay statistics, the user opens the page actions menu again and
clicks the menu item Close Analytics Reports.
-> Optional: Customize the overlay report by providing additional configuration parameters.
3. Optional: To further customize the tagging of your site, assign site promotions to pages and portlets as required.
Ref :
http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=IBM+WebSphere+Portal+8+Product+Documentation#action=openDocument&res_title=Analyzing_portal_usage_data_wp8&content=pdcontent
Thanks,
MS
