What You Should Know About the Activity Graph Service

Managing the Activity Graph Service 12-5 Figure 12–4 Configuring the Activity Graph Service for WebCenter Portal Applications 12-6 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

12.3 Activity Graph Service Prerequisites

The Activity Graph service requires that the Activity Graph engines application has been installed and configured. For more information, see the Oracle Fusion Middleware Installation Guide for Oracle WebCenter. In addition, in your application you must create a connection to the WebCenter schema and to the Activities database. For more information, see the section Setting Table 12–2 Configuring the Activity Graph Service for WebCenter Portal Applications Actor Task Sub-task Notes Administrator 1. Install WebCenter and the back-end components for the Analytics and Activity Graph services Developer 2. Integrate the Activity Graph service in your WebCenter Portal application 2.a Configure a connection to the WebCenter schema in JDeveloper 2.b Configure a connection to the Activities database in JDeveloper 2.c Configure a connection to the Analytics Collector in JDeveloper 2.d Add an Activity Graph task flow to a page in JDeveloper Administrator 3. Optional Set up the Activity Graph Engines schedule Developer Administrator 4. Deploy the WebCenter Portal application using one of the following tools: ■ JDeveloper Developer ■ Fusion Middleware Control Administrator ■ WLST Administrator ■ WLS Admin Console Administrator Developer Administrator 5. Optional Addmodify connection parameters using one of the following tools: ■ JDeveloper, then redeploy the application Developer ■ Fusion Middleware Control Administrator ■ WLST Administrator End User Administrator 6. Test that activity graph data is available in the WebCenter Portal application 6.a Log in and interact with the WebCenter Portal application, for example, by adding content End User 6.b Run the Activity Graph Engines Administrator 6.c View recommendations in the Activity Graph task flow, for example, the Recommended Connections task flow on your Profile page End User Managing the Activity Graph Service 12-7 Up a Database Connection in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter. The application must be configured to send usage events to the Analytics Event Collector. For more information, see Section 13.5, Registering an Analytics Collector for Your Application. Before the Activity Graph service can make recommendations, the Activity Graph engines must have been run at least once to gather the data and calculate similarity scores. For more information see Section 12.4, Preparing Data for the Activity Graph Service. The items suggested in the Similar Items task flow depend on the services that are available in your application. For example, documents are only recommended if the Documents service is available. For information about making a service available in your application, refer to the appropriate chapter for that service. An item can also be filtered out of the recommendations by the Resource Authorizer of the service that owns the item. In a cluster environment, all instances of the Activity Graph engines application should be disabled except for one. For more information, see the section Configuring Activity Graph in the Oracle Fusion Middleware High Availability Guide.

12.4 Preparing Data for the Activity Graph Service

The Activity Graph engines consist of three separate engines for gathering data, calculating similarity scores, and calculating search rankings. These engines are: ■ The Gathering Engine—gathers activities from the Analytics tables and other repositories via a set of registered activity providers. ■ The Collaborative Filtering Engine CFE—calculates similarity scores on pairs of objects and stores them in the activity graph for later generation of similarity recommendations. It does this by performing a set of similarity calculations. Similarity calculations are objects that tell the Collaborative Filtering Engine how to calculate similarity scores on a given set of domain and background node classes. Each resulting similarity score is a number between 0 and 1 designating how similar two objects are to each other given a specific criterion. Similarity calculations are specified by the following properties: their domain and background classes, a distance function, and a relation combination. ■ The Rank Engine—calculates a measure of importance of every node in the activity graph. These activity ranks can be stored in a search index and combined at query time with a query-dependent score to order search results.For more information, see Section 12.7, Setting Up Activity Rank for Oracle Secure Enterprise Search. These scores are also useful in ordering context-free recommendations. For this reason, they are also stored in the Relation Store. Before the Activity Graph service can begin to recommend objects, these engines must be run at least once to gather the data and calculate similarity scores. After this initial run, the engines can be run on demand, or on a schedule to ensure that new activities are captured and analyzed. This section includes the following subsections: ■ Section 12.4.1, Running the Activity Graph Engines on a Schedule ■ Section 12.4.2, Running the Activity Graph Engines on Demand