Analytics - Configuration Analytics Prerequisites

Managing the Analytics Service 13-9 5. To start using the new settings you must restart the managed server on which the Analytics Collector application is deployed WC_Utilities. For more information, see Section 8.2, Starting and Stopping Managed Servers for WebCenter Application Deployments.

13.5 Registering an Analytics Collector for Your Application

Events raised in WebCenter applications using OpenUsage APIs can be sent to an Analytics Collector for use by the Analytics service, Recommendations service, and the Activity Graph Engine. If your WebCenter application intends to use any of the features or task flows provided by these services you must connect the application to an Analytics Collector. While you can register multiple Analytics Collector connections for a WebCenter application, only one Analytics Collector is used - the default or active connection. To start using a new configuration you must restart the managed server on which the WebCenter application is deployed. This section includes the following subsections: ■ Section 13.5.1, Registering an Analytics Collector Using Fusion Middleware Control ■ Section 13.5.2, Registering an Analytics Collector Using WLST ■ Section 13.5.3, Disabling WebCenter Event Collection

13.5.1 Registering an Analytics Collector Using Fusion Middleware Control

To register an Analytics Collector for a WebCenter application: 1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the WebCenter Portal application. For more information, see: ■ Section 6.2, Navigating to the Home Page for WebCenter Spaces ■ Section 6.3, Navigating to the Home Page for WebCenter Portal Applications 2. Open the Service Configuration page: ■ For WebCenter Spaces - From the WebCenter menu, choose Settings Service Configuration . ■ For WebCenter Portal applications - From the Application Deployment menu, choose WebCenter Service Configuration. 3. From the list of services on the WebCenter Service Configuration page, select Analytics and Activity Graph . ClusterBroadcastFrequency Specify that the Analytics Collector broadcasts listening information every n seconds. The default frequency is 10 seconds. The Analytics Collector periodically broadcasts a heartbeat to advertise its location CollectorHostname. In a clustered environment, WebCenter applications use the heartbeat to determine which Analytics Collectors are available. Table 13–3 Cont. Analytics Collector - Configuration Properties Field Description 13-10 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

4. To connect to an Analytics Collector, click Add

Figure 13–4 . Figure 13–4 Configuring Analytics Collector Connections

5. Enter a unique name for this connection.

The name must be unique across all connection types within the WebCenter application.

6. Select Active Connection to use this connection for Analytics and Activity Graph

services. While you can register multiple Analytics Collector connections for a WebCenter application, only one connection is used—the default or active connection.

7. Select Enable WebCenter Event Collection to send analytics events raised using

OpenUsage APIs to the Analytics Collector. Deselect this option if you do not want to collect analytics data.

8. Enter connection details for the Analytics Collector. For details, see

Table 13–4 .

9. Click OK to save.

10. To start using the new active connection you must restart the managed server on

which the WebCenter application is deployed. For more information, see Section 8.2, Starting and Stopping Managed Servers for WebCenter Application Deployments.

13.5.2 Registering an Analytics Collector Using WLST

Use the WLST command createAnalyticsCollectorConnection to create an Analytics Collector connection for a WebCenter application. To update an existing Table 13–4 Analytics Collector Connection - Connection Details Field Description Messaging Mode Specify whether to send events to a clustered Analytics Collector in multicast mode or a single Analytics Collector using unicast communication. Valid values are Unicast and Multicast. The default setting is Unicast. Collector Host Name If the messaging mode is set to Unicast, enter the host name where the Analytics Collector is running. The default setting is localhost. Collector Port Enter the port on which the Analytics Collector listens for events. The default value is 31314. Cluster Name If the messaging mode is set to Multicast, enter the name of the cluster where a clustered Analytics Collector is running. Timeout Seconds If the messaging mode is set to Multicast, enter the length of time in seconds to wait for a response from the Analytics Collector. The default value is 30 seconds.