Configuration Roadmap for the Analytics Service

13-8 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter Figure 13–3 System MBeans Browser - Analytics Collector Properties

4. Modify configuration properties for the Analytics Collector. For details, see

Table 13–3 . Table 13–3 Analytics Collector - Configuration Properties Field Description BroadcastType Specify the network channel on which the Analytics Collector broadcasts a heartbeat to advertise its location to event producers. Valid values are Broadcast and Multicast: Broadcast - use the standard network broadcast channel. Multicast - use a special fixed multicast address. CollectorHostName Enter the name of the host on which the Analytics Collector is running. The default setting is localhost. CollectorDefaultPort Enter the default port number on which the Analytics Collector listens. The default value is 31314. CollectorMaximumPort Enter the highest port number that an Analytics Collector can use when allocating a listener. This property is mostly used in a clustered environment where multiple collectors run in the same box. Each collector listens for incoming UDP messages on a free port within a given port range. The range is from the default port number to the maxPort number. ClusterEnabled Specify whether the Analytics Collector is deployed in a cluster. Valid values are true and false. If set to true, clusterName must also be defined. ClusterName Enter the name of the Analytics Collector cluster. This property is only required when clusterEnabled=1. 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