Oracle® Fusion Middleware Developer's Guide for Oracle WebCenter 11g Release 1 (11.1.1.4.0) E10148-12 |
|
![]() Previous |
![]() Next |
This chapter describes how to integrate the Analytics service into WebCenter Portal applications. The Analytics service enables you to display usage and performance metrics for WebCenter Portal applications.
This chapter includes the following sections:
Section 42.2, "Basic Configuration for the Analytics Service"
Section 42.3, "Advanced Information for the Analytics Service"
For information about using any of the Analytics task flow, see Chapter "Working with the Analytics Service" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Spaces.
The Analytics service offers real-time usage and activity reporting for your portal. This section provides an overview of the Analytics service, its task flows, and its usages. It includes the following subsections:
The Analytics Service allows administrators and users to track and analyze traffic and usage in WebCenter Portal applications. The Analytics Service provides the following basic functionality:
Usage Tracking Metrics: The Analytics Service collects and reports metrics for common portal functions, including community, page, portlet, and document hits.
Behavior Tracking: The Analytics Service can be used to analyze WebCenter Spaces metrics to determine usage patterns, such as Space visit duration and usage over time.
User Profile Correlation: The Analytics Service can be used to correlate metric information with user profile information. Usage tracking reports can be viewed and filtered by user profile data such as country, company or title.
Custom Reporting: Developers and business users can build custom reports that query the analytics data. For more details, see Section 42.3.1, "Building Custom Analytics Reports".
Table 42-1 lists the Analytics task flows available with Oracle WebCenter. For detailed information about these task flows and how to use them in WebCenter applications, see "Understanding Analytics Task Flows in WebCenter Spaces" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Spaces.
Table 42-1 Analytics Task Flows Available in JDeveloper
WebCenter Analytics Task Flows | Description |
---|---|
A summarized view for common events within the portal. |
|
Displays the number of page hits and the number of unique users that visited any page within the portal. |
|
Reports portal logins. |
|
Displays usage data for a portlet. |
|
Displays performance data for a portlet. |
|
Displays usage data for a portlet instance*. |
|
Displays performance data for a portlet instance*. |
|
Tracks portal searches. |
|
Tracks document views. |
|
Tracks most popular/least popular wikis. |
|
Tracks most popular/least popular blogs. |
|
Tracks most popular/least popular discussions. |
* If the same portlet displays on several different pages, each placement is known as a portlet instance.
The Analytics service requires that the analytics schema (ACTIVITIES
) is installed and up and running. In addition, the Oracle WebCenter Analytics Collector must be up and running on the WC_Utilities
managed server. For detailed installation instructions, see Oracle Fusion Middleware Installation Guide for Oracle WebCenter.
On install, the Analytics Collector is configured to receive events out-of-the-box, using installation defaults. If the default values are not suitable for your installation or you want to deploy Analytics Collectors in a cluster, you may need to configure different values using WLST or Fusion Middleware Control. For more details, see "Configuring Analytics Collector Settings" Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
To display usage and performance metrics through Analytics task flows you must enable event generation for your WebCenter Portal application and configure a connection to the Analytics database (ACTIVITIES
). For details on how to do this in JDeveloper, see Section 42.2.1, "Setting up Connections for the Analytics Service".
At runtime, user activity in your WebCenter Portal application generates event data. For example, every time a user logins in, reads a discussion topic, views a document, and so on, the event is recorded. The OpenUsage API sends event metrics to the Analytics Collector using UDP (User Datagram Protocol) and the event data is stored in the analytics database (ACTIVITIES).
In a non clustered environment the WebCenter Portal application is configured with the location of the collector, and all events are transmitted to that location.
In a clustered environment both the WebCenter Portal application and Analytics Collector are configured with a cluster-specific channel name. Each collector periodically broadcasts a heartbeat with its location to the cluster-specific channel. The WebCenter Portal application listens to the channel for these collector heartbeats, and when it hears one, adds the collector to its list of known collectors. When the WebCenter Portal application sends an event it randomly selects a collector from its list and sends the event to that collector. If a collector stops (either being stopped purposefully or failing) it stops broadcasting a heartbeat. When the WebCenter Portal application stops hearing the heartbeat it removes the collector from its list and stops sending events to that collector. If the WebCenter Portal application does not hear any collector heartbeats it does not send any events.
Analytics task flows and custom analytics reports (based on SQL data controls) that are included in WebCenter Portal applications display the metrics collected for standard events by querying the analytics database at runtime. For more information about the task flows at runtime, see "Working with Analytics Task Flows" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Spaces.
This section describes how to include the Analytics service in your WebCenter Portal application.
This section contains the following subsections:
Section 42.2.1, "Setting up Connections for the Analytics Service"
Section 42.2.2, "Configuring a Namespace for Analytics Customizations in MDS"
Section 42.2.3, "Adding Analytics Task Flows at Design Time"
Section 42.2.4, "Setting up Security for Analytics Task Flows and Usage Data"
See also, Section 42.1.2, "Requirements for the Analytics Service".
The Analytics service requires that the WebCenter Portal application is connected to the analytics database (ACTIVITIES
). You must also configure the WebCenter Portal application to send event information to a specific Analytics Collector.
Note: While you can set up the connections to back-end servers at design time in JDeveloper, you can later add, delete, or modify connections in your deployed environment using Enterprise Manager Fusion Middleware Control. For more information, see "Managing the Analytics Service" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter. |
This section includes the following subsections:
Section 42.2.1.1, "How to Set Up a Connection to the Analytics Database"
Section 42.2.1.2, "How to Set Analytics Collector Properties"
Section 42.2.1.3, "How to Set Up a Connection to the Analytics Collector"
The Analytics service requires a connection to the analytics database (ACTIVITIES
) where analytics event data is stored.
To set up the analytics database connection:
Ensure that the ACTIVITIES
database is up and running.
See Section 42.1.2, "Requirements for the Analytics Service".
In the Application Navigator, expand the Applications Resources panel.
Right-click Connections, then choose New Connection, and then Database.
In the Create Database Connection dialog, enter the following information for the database connection:
Connection Name: connectionName
(for example, myAnalyticsDatabaseConnection
Connection Type: Oracle (JDBC)
Username: username
(a user with access to the database)
Password: password
(the specified user's password)
Host Name: host
(where the Analytics database is installed, for example localhost
)
JDBC Port: port
(for example, 1521
)
SID: sid
(system identifier for the database)
Click Test Connection, and if it is successful, then click OK.
In the Associate to Data Source dialog, choose ActivitiesDS (Figure 42-1).
This creates a data-source to the ACTIVITIES
schema so that you can test analytics in your WebCenter Portal application at design-time.
Click OK.
The connection appears as a node in the Application Resources pane, under Connections.
Out-of-the-box, the Analytics Collector is installed on the WC_Utilities
managed server and is configured to receive events using the following default values:
Analytics Collector Configuration | Default Value |
---|---|
Collector Host Name | localhost |
Default Port | 31314 |
Maximum Port Number | 31314 |
Broadcast Type | Multicast |
Clustering
Cluster Name Cluster Broadcast Frequency |
Disabled
- - |
If these default are not suitable for your installation, your administrator can configure suitable values using WLST or the Fusion Middleware Control. For more information, see "Configuring Analytics Collector Settings" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
The Analytics service requires a connection to the Analytics Collector that is collecting WebCenter events and OpenUsage must be enabled in the WebCenter Portal application.
Use the following OpenUsage JVM properties to set properties for the Analytics service:
oracle.wc.openusage.
enabled
- Specifies whether to send analytics events raised using OpenUsage APIs to the Analytics Collector. Valid values are true
and false
. The default value is false
.
oracle.wc.openusage.
unicast
- Specifies whether events are sent to a clustered Analytics Collector in multicast mode or whether a single Analytics Collector using unicast communication is required. Valid values are true
and false
. The default value is true
(unicast).
oracle.wc.openusage.
clustername
- Name of the collector cluster or the host name of an Analytics Collector (if unicast
is enabled). Default value is localhost
.
oracle.wc.openusage.
collectorport
- Port on which the Analytics Collector listens for events. The default value is 31314
.
oracle.wc.openusage.
timeout
Period of time (in seconds) used to determine availability of the collector service in multicast mode. The default value is 30 seconds.
To set Analytics Collector JVM properties:
In JDeveloper, choose Run, Active Run Configuration, and then Manage Run Configurations from the main menu.
In the Project Properties dialog, select the Default run configuration, and then click Edit.
In the Launch Settings section, add the following OpenUsage options to the Java Options field as follows:
-Doracle.wc.openusage.enabled=true -Doracle.wc.openusage.clustername=localhost-Doracle.wc.openusage.collectorport=31314 -Doracle.wc.openusage.unicast=true -Doracle.wc.openusage.timeout=30
Ensure that the values you provide, shown here in bold, match your Analytics Collector installation.
Click OK to save the default run configuration, and then click OK again.
These steps enable OpenUsage in the Integrated WebLogic Server for the current WebCenter Portal application. If the Integrated WebLogic Server is currently running you must restart it to pick up the new settings. See also, Section 64.2, "Deploying a WebCenter Portal Application to the Integrated WebLogic Server".
Analytics task flows use MDS to store customizations made by the user and these customizations are stored in an MDS namespace specific to analytics. If you want to enable user customizations for analytics task flows in your WebCenter Portal application, you must configure a namespace for the analytics metadata in adf-config.xml
.
Note: In addition, each task flow must specify a unique MDS document in which to its store user customizations details. See Section 42.2.3.4, "How to Allow End Users to Customize Analytics Task Flows at Runtime". |
To configure a namespace for analytics metadata:
Open adf-config.xml
.
Use the Application Resources panel to navigate to this file. The file is located in the Descriptors
\ADF META-INF
folder.
Under the <metadata-namespaces>
element, add the following XML fragment:
<namespace path="/oracle/webcenter/analytics/scopedMD" metadata-store-usage="WebCenterFileMetadataStore"/>
Save the file.
See also, Chapter 22, "Performing Oracle Composer-Specific MDS Configurations".
This section describes the Analytics service task flows and how to add Analytics task flows to your application. It includes the following subsections:
Section 42.2.3.2, "How to Add Analytics Task Flows to a Page"
Section 42.2.3.3, "How to Modify Analytics Task Flow Parameters"
Section 42.2.3.4, "How to Allow End Users to Customize Analytics Task Flows at Runtime"
Section 42.2.3.5, "Analytics Task Flows and Task Flow Parameters"
Table 42-2 lists the Analytics task flows available with Oracle WebCenter. For detailed information about these task flows and the type of information that users can see at runtime, see "Understanding Analytics Task Flows in WebCenter Spaces" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Spaces.
Table 42-2 Analytics Task Flows Available in JDeveloper
WebCenter Analytics Task Flows | Description |
---|---|
WebCenter Traffic |
A summarized view for common events within the portal. |
Page Traffic |
Displays the number of page hits and the number of unique users that visited any page within the portal. |
Login Metrics |
Reports portal logins. |
Portlet Traffic |
Displays usage data for a portlet. |
Portlet Response Time |
Displays performance data for a portlet. |
Portlet Instance Traffic |
Displays usage data for a portlet instance*. |
Portlet Instance Response Time |
Displays performance data for a portlet instance*. |
Search Metrics |
Tracks portal searches. |
Document Metrics |
Tracks document views. |
Wiki Metrics |
Tracks most popular/least popular wikis. |
Blog Metrics |
Tracks most popular/least popular blogs. |
Discussion Metrics |
Tracks most popular/least popular discussions. |
To add an Analytics task flow to your WebCenter Portal application:
Prepare your application as described in Section 42.1.2, "Requirements for the Analytics Service".
Ensure that your application includes the services for which analytics event data is available, that is, portlets, discussions, documents, and search.
Note: If no usage data exists when you run the application, analytics task flows displays the message:No data to display |
Open the JSF page (.jspx) on which you want to add the task flow.
In the Resource Palette, open the WebCenter Services Catalog, then open the Task Flows folder (Figure 42-2).
Drag and drop an Analytics task flow onto your page inside the <af:form>
tag.
Choose Region from the Create context menu.
You may be prompted to add the ADF library for the Analytics service (analytics-reporting-service-view.jar
) to the project. Confirm by clicking Add Library (Figure 42-3).
In the Edit Task Flow Binding dialog, enter values for analytics task flow parameters:
applicationName
- Required
analyticsResourceId
- Required
analyticsReportTitle
- Optional
maxDataPointsPerSeries
- Optional
For more information, see Section 42.2.3.5, "Analytics Task Flows and Task Flow Parameters".
Click OK.
The task flow is added to the page, and the ViewController project's libraries are configured to run the task flow.
Save your project and run the page to see the task flow running in the WebCenter Portal application.
If no usage data exists when you run the application, analytics task flows display the message: No data to display
If you want, create some data for the analytics task flow to display by performing actions that relate to the task flow you are testing. For example, to test discussion analytics, create and view discussions, to test page analytics, create and view pages, and so on.
Each analytics task flow has a set of required and optional task flow binding parameters. Required parameters are not mandatory but enable you to capture information that is essential to the task flow's successful function. For example, if you want user customizations for a particular task flow instance to be stored in MDS you must specify the MDS document required.
In addition, you can use task flow binding parameters to customize the appearance and behavior of a task flow instance. For example, you can use parameter values to specify a display title above your analytics data.
You can provide task flow binding parameter values when you drag and drop a task flow onto an application page. Doing so opens the Task Flow Bindings dialog (for more information, see Section 42.2.3.2, "How to Add Analytics Task Flows to a Page").
You can also adjust task flow binding parameter values after you have placed a task flow on a page at run time. For details, see "Setting Analytics Task Flow Properties" in the Oracle Fusion Middleware User's Guide for Oracle WebCenter Spaces.
To access the Edit Task Flow Binding dialog:
Click the Bindings tab at the bottom of the page (next to the Source tab) to go to the Bindings view.
Under Executables, you'll see a list of task flows added to the page. Select the analytics task flow (Figure 42-4).
Next to the Executables heading, click the Edit selected element icon (a pencil).
In the Edit Task Flow Binding dialog (Figure 42-5), specify the binding parameter values as required
For more information, see Section 42.2.3.5, "Analytics Task Flows and Task Flow Parameters".
When you are finished, save the page and run your page to see the results.
If you want to enable user customizations for a particular task flow instance you must specify the MDS document where customizations are stored using the Analytics Resource Id
parameter.
The ID must be unique, so consider using a consistent naming pattern such as <app_name>_<page_name>_<task_flow>_<sequence>
. For example, set the analyticsResourceId
parameter for a Page Traffic task flow to myapp_analyticspage_pagetraffic_1
.
For details, see Section 42.2.3.3, "How to Modify Analytics Task Flow Parameters".
Table 42-3 lists and describes task flow binding parameters applicable to the Analytics service.
Table 42-3 Analytics Task Flow Binding Parameters
Parameter (* = required) | Task Flows | Description |
---|---|---|
Specifies the display title that appears above the analytics data, that is, you can override the default report title. See also, Figure 42-6, "analyticsReportTitle - Example". |
||
Specifies the MDS document that will be generated to store user customizations/application customizations for the task flow instance in MDS. For example: |
||
Specifies the name of the WebCenter Portal application for which you want to display analytics data. For example: The analytics database can be used to store event data from multiple applications so this parameter is required to identify which application data to display. If omitted, the task flow display analytics data for all applications. |
||
Indicates the maximum number of data points to be displayed in a bar or line chart. Enter a value between 1 and 1000. The default value is 25. Increasing the number of data points can increase the time it takes to display the chart. See also, Figure 42-7, "maxDataPointsPerSeries - Example". |
AAnalytics task flows are intended to make usage metrics visible to a limited set of administrative users who perform particular business functions, such as capacity planning, quality of service (QoS) analysis, return on investment (ROI) analysis, "best bet" customization for Search, and so on.
Analytics usage data is valuable for portal analysis but might be regarded as private or sensitive to portal users. For example, the Search, Document, and Portlet reports can be configured to display activity metrics for a particular user, based on user properties such as E-mail Address, First Name, or Last Name.
To protect security and privacy interests associated with Analytics task flows and custom reports:
Manage administrative access to the Analytics task flows, custom reports, and any page that displays sensitive usage data
To ensure that only a limited number of administrative users can add Analytics task flows to pages, create reports based on custom analytics data controls, or view pages set up to display sensitive usage metrics, create a new administrative group and manage group membership accordingly.
Manage user access to Analytics task flows.
Ensure Analytics task flows and custom reports do not contain private or sensitive data unless such a view is particularly intended. If the metrics in the report do contain private or sensitive data, configure security so that only appropriate, specified users have access to the task flow or the page.
For example, at design-time, developers can expose the analytics task flows to non-admin users by granting them appropriate privileges to the page. In addition, developers can customize the reports pre-deployment, to hide/show or predefine certain report options (such as time frame, chart type, user property filter, group by option, and so on). Administrators will be able to perform the same tasks at runtime, that is, grant page access and customize the information that displays. Non-admin users can still personalize the reports they are allowed to see, but they cannot change customizations made by the administrator.
Ensure that unauthenticated users are never allowed to add Analytics task flows to pages or see sensitive data.
This section explains that in addition to the task flow parameters, you can further refine the behavior of the Analytics service.
This section contains the following subsections:
Out-of-the-box Analytics task flows present common analytics event metrics in a specific display format. If you want to present analytics data in a different way or display custom event data, you can build a custom analytics report that is based on an SQL data control.
Use SQL data controls to define, in a SQL query statement, the information you want to retrieve from the analytics database. When you expose data controls on a page you can choose whether the analytics data presents in a graph, table or a form, and you can also configure the bind parameters and other display options.
You can use JDeveloper to build SQL data controls at design-time. For details, detailed information about data controls, see Oracle Application Development Framework Developer's Guide.
You can also create data controls in a running WebCenter application if runtime resource management features are enabled. To do this in WebCenter Spaces, see "Creating a SQL Data Control for WebCenter Spaces" in the Oracle Fusion Middleware User's Guide for Oracle WebCenter Spaces. To create a data control in other WebCenter Portal applications, see "Managing Application Resources" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
Sample - Analytics SQL Query
SELECT space.name_, page.name_, space.id, page.id, count(1), fact.page_, page.resourceid_ FROM asfact_wc_pagevie_0 fact , asdim_wc_groupsp_0 space , asdim_wc_pages_0 page , asdim_wc_applica_0 app WHERE space.id = fact.groupspace_ and page.id = fact.page_ and app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and page.personal_ = :ispersonal and space.name_ is not null and page.name_ is not null and space.id is not null and page.id is not null and fact.page_ is not null and page.resourceid_ is not null GROUP BY space.name_, page.name_, space.id, page.id, fact.page_, page.resourceid_ ORDER BY count(1) desc
Sample - Analytics SQL Data Control
Use a SQL data control to fetch data from the analytics database and display analytics data in your WebCenter application. Figure 42-8 shows the sample SQL statement in an the Create/Edit SQL Data Control dialog in WebCenter Spaces. A database connection to the analytics database (ActivitiesDS
) is required, and you must provide a valid database password.
You can add as many bind parameters as required. When you add parameters, you can restrict the data retrieved from the data source based on the parameter values you specify. As this example is for WebCenter Spaces, the name of the application is set to webcenter
and personal pages (pages in the Home Space) are included in the report Figure 42-9.
Table 42-4 Report Parameters
Parameter | Default Value | Description |
---|---|---|
|
|
The corresponding application name—always |
|
|
For WebCenter Spaces, determines whether or not pages created in the Home Spaces are included in the report. |
|
|
Any valid pattern for dates in an Oracle database. Every component of the pattern is optional since it depends on the data you want to retrieve |
|
|
Determines a start date for the data required. |
|
|
Determines an end date for the data required. |
Sample - Custom Analytics Report
Figure 42-8 shows the custom report displayed as a graph.
You can use the following WebCenter Spaces SQL statements as a starting point for you own custom reports, that is, you can provide additional filters, groupings, and so on.
SELECT 'Spaces' Name, count(1) Hits FROM asfact_wc_groupsp_0 fact , asdim_wc_groupsp_0 space , asdim_wc_applica_0 app WHERE space.id = fact.groupspace_ and app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and space.personal_ = :ispersonal UNION ALL SELECT 'Pages' Name, count(1) Hits FROM asfact_wc_pagevie_0 fact , asdim_wc_pages_0 page , asdim_wc_applica_0 app WHERE page.id = fact.page_ and app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and page.personal_ = :ispersonal UNION ALL SELECT 'Portlets' Name, count(1) Hits FROM asfact_wc_portlet_0 fact , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname UNION ALL SELECT 'Logins' Name, count(1) Hits FROM asfact_wc_logins_0 fact , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname UNION ALL SELECT 'Searches' Name, count(1) Hits FROM asfact_wc_searche_0 fact , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname UNION ALL SELECT 'Wikis' Name, count(1) Hits FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.document_ = doc.id and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and doc.objecttype_ like '%WIKI%' UNION ALL SELECT 'Blogs' Name, count(1) Hits FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.document_ = doc.id and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and doc.objecttype_ like '%BLOG%' UNION ALL SELECT 'Documents' Name, count(1) Hits FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.document_ = doc.id and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and doc.objecttype_ like '%DOCUMENT%' UNION ALL SELECT 'Discussions' Name, count(1) Hits FROM asfact_wc_discuss_1 fact , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname
SELECT space.name_, page.name_, space.id, page.id, count(1), fact.page_, page.resourceid_ FROM asfact_wc_pagevie_0 fact , asdim_wc_groupsp_0 space , asdim_wc_pages_0 page , asdim_wc_applica_0 app WHERE space.id = fact.groupspace_ and page.id = fact.page_ and app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and page.personal_ = :ispersonal and space.name_ is not null and page.name_ is not null and space.id is not null and page.id is not null and fact.page_ is not null and page.resourceid_ is not null GROUP BY space.name_, page.name_, space.id, page.id, fact.page_, page.resourceid_ ORDER BY count(1) desc
SELECT count(1) FROM asfact_wc_logins_0 fact , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname
SELECT space.name_, space.id, count(1), fact.groupspace_, space.resourceid_ FROM asfact_wc_groupsp_0 fact , asdim_wc_groupsp_0 space , asdim_wc_applica_0 app WHERE space.id = fact.groupspace_ and app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and space.personal_ = :ispersonal and space.name_ is not null and space.id is not null and fact.groupspace_ is not null and space.resourceid_ is not null GROUP BY space.name_, space.id, fact.groupspace_, space.resourceid_ ORDER BY count(1) desc
SELECT space.name_, space.id, avg(fact.response_time_), fact.groupspace_, space.resourceid_ FROM asfact_wc_groupsp_0 fact , asdim_wc_groupsp_0 space , asdim_wc_applica_0 app WHERE space.id = fact.groupspace_ and app.id = fact.application_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and space.personal_ = :ispersonal and space.name_ is not null and space.id is not null and fact.groupspace_ is not null and space.resourceid_ is not null GROUP BY space.name_, space.id, fact.groupspace_, space.resourceid_
SELECT portlet.default_title_, portlet.id, count(1), fact.portlet_, portlet.resourceid_ FROM asfact_wc_portlet_0 fact , asdim_wc_portlet_0 portlet , asdim_wc_applica_0 app WHERE app.id = fact.application_ and portlet.id = fact.portlet_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and portlet.default_title_ is not null and portlet.id is not null and fact.portlet_ is not null and portlet.resourceid_ is not null GROUP BY portlet.default_title_, portlet.id, fact.portlet_, portlet.resourceid_
SELECT space.name_, space.id, page.name_, page.id, portletinst.title_, portletinst.id, count(1), fact.portlet_instance_, portletinst.resourceid_ FROM asfact_wc_portlet_0 fact , asdim_wc_groupsp_0 space , asdim_wc_pages_0 page , asdim_wc_portlet_1 portletinst , asdim_wc_applica_0 app WHERE space.id = fact.groupspace_ and page.id = fact.page_ and app.id = fact.application_ and portletinst.id = fact.portlet_instance_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and space.name_ is not null and space.id is not null and page.name_ is not null and page.id is not null and portletinst.title_ is not null and portletinst.id is not null and fact.portlet_instance_ is not null and portletinst.resourceid_ is not null GROUP BY space.name_, space.id, page.name_, page.id, portletinst.title_, portletinst.id, fact.portlet_instance_, portletinst.resourceid_
SELECT portlet.default_title_, portlet.id, avg(fact.response_time_), fact.portlet_, portlet.resourceid_ FROM asfact_wc_portlet_0 fact , asdim_wc_portlet_0 portlet , asdim_wc_applica_0 app WHERE app.id = fact.application_ and portlet.id = fact.portlet_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and portlet.default_title_ is not null and portlet.id is not null and fact.portlet_ is not null and portlet.resourceid_ is not null GROUP BY portlet.default_title_, portlet.id, fact.portlet_, portlet.resourceid_
SELECT space.name_, space.id, page.name_, page.id, portletinst.title_, portletinst.id, avg(fact.response_time_), fact.portlet_instance_, portletinst.resourceid_ FROM asfact_wc_portlet_0 fact , asdim_wc_groupsp_0 space , asdim_wc_pages_0 page , asdim_wc_portlet_1 portletinst , asdim_wc_applica_0 app WHERE space.id = fact.groupspace_ and page.id = fact.page_ and app.id = fact.application_ and portletinst.id = fact.portlet_instance_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and space.name_ is not null and space.id is not null and page.name_ is not null and page.id is not null and portletinst.title_ is not null and portletinst.id is not null and fact.portlet_instance_ is not null and portletinst.resourceid_ is not null GROUP BY space.name_, space.id, page.name_, page.id, portletinst.title_, portletinst.id, fact.portlet_instance_, portletinst.resourceid_
SELECT search.phrase_, search.id, count(1) FROM asfact_wc_searche_0 fact , asdim_wc_applica_0 app , asdim_wc_searche_0 search WHERE app.id = fact.application_ and search.id = fact.searched_phrase_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and search.phrase_ is not null and search.id is not null GROUP BY search.phrase_, search.id
SELECT doc.name_, doc.id, count(1), fact.document_, doc.resourceid_ FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.document_ = doc.id and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and doc.objecttype_ like '%DOCUMENT%' and doc.name_ is not null and doc.id is not null and fact.document_ is not null and doc.resourceid_ is not null GROUP BY doc.name_, doc.id, fact.document_, doc.resourceid
SELECT doc.name_, doc.id, count(1), fact.document_, doc.resourceid_ FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.document_ = doc.id and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and doc.objecttype_ like '%WIKI%' and doc.name_ is not null and doc.id is not null and fact.document_ is not null and doc.resourceid_ is not null GROUP BY doc.name_, doc.id, fact.document_, doc.resourceid_
SELECT doc.name_, doc.id, count(1), fact.document_, doc.resourceid_ FROM asfact_wc_doclib__0 fact , asdim_wc_documen_0 doc , asdim_wc_applica_0 app WHERE app.id = fact.application_ and fact.document_ = doc.id and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and doc.objecttype_ like '%BLOG%' and doc.name_ is not null and doc.id is not null and fact.document_ is not null and doc.resourceid_ is not null GROUP BY doc.name_, doc.id, fact.document_, doc.resourceid_
SELECT forum.name_, forum.id, count(1), fact.topic_, forum.resourceid_ FROM asfact_wc_discuss_0 fact , asdim_wc_discuss_0 forum , asdim_wc_applica_0 app WHERE app.id = fact.application_ and forum.id = fact.topic_ and fact.occurred between to_date(:startdate, :dateformat) and to_date(:enddate, :dateformat) and app.name_ = :appname and forum.name_ is not null and forum.id is not null and fact.topic_ is not null and forum.resourceid_ is not null GROUP BY forum.name_, forum.id, fact.topic_, forum.resourceid_