Running the Activity Graph Engines on Demand

12-12 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter For more information, see the section Activity Graph in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

12.6.5 Renaming Actions and Node Classes

Use the WLST command renameAGNodeClass to change the URN of a node class currently registered with Activity Graph. For command syntax and examples, see the section renameAGNodeClass in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. Use the WLST command renameAGAction to change the URN of an action currently registered with Activity Graph. For command syntax and examples, see the section renameAGAction in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

12.7 Setting Up Activity Rank for Oracle Secure Enterprise Search

Enterprise content contributed through WebCenter and Fusion applications has a rich structure that lends itself to using the Markov Chain Analysis mathematical technique. This technique is used by the Rank Engine to produce an Activity Rank for each node that improves end user searches by producing more relevant result sets. This is achieved by introducing a measure of the importance of various objects into the Oracle Secure Enterprise Search Oracle SES search index. This importance can then be factored into how results are ordered in combination with more standard search criteria term frequency, and so on. The determination of an object’s importance is predicated on the history of users’ interactions with that object. With Activity Rank, the importance of a person depends on the number of items the person creates and edits; the importance of those items; the number of people who connect with the person; and the importance of those people. The importance of an item depends on the importance of its author; the number of people who view, tag, and edit the item; and the importance of those people. The Rank Engine process can be divided into four phases: ■ Gathering—The Rank Engine queries the Analytics store for data about the connections between users and documents. ■ Reshaping—The data is transformed into a matrix. ■ Multiplying—The matrix is used to calculate Activity Ranks. ■ Result storage—The Activity Ranks are stored in the Oracle SES search server so that they can be used at search time. Candidates for Activity Rank are limited to an intersection of WebCenter Spaces objects having Oracle SES crawler implementations, WebCenter Analytics instrumentation, and registration for Activity Graph rank calculation. Note: These delete methods delete metadata from the schema. As a result of this, any associated data in the Activities database is removed the next time the Activity Graph engines are run. Note: These commands do not delete any metadata associated with the affected node class or action Managing the Activity Graph Service 12-13 For an object to receive an Activity Rank that will affect search behavior, it must be eligible to have its event data collected from Analytics, a rank computation generated by Activity Graph, and an indexed entry in search with the value of the attribute wc_ serviceId matching one of the classes registered in Activity Graph. The currently supported objects are: ■ Users ■ Documents ■ Blog entries ■ Wiki pages The range of actions considered for computing Activity Rank are defined in the rankCalculation specified in the activityGraphMetaData.xml file. The out-of-the-box declaration includes the following user actions: component actionURN=connect weight=10.0 component actionURN=edit weight=20.0 inverse=true component actionURN=view-count weight=1.0 component actionURN=create weight=100.0 inverse=true component actionURN=create weight=100.0 component actionURN=edit-count weight=20.0 component actionURN=download weight=5.0 component actionURN=tag weight=10.0 component actionURN=comment weight=10.0 From this you can see that the single action of viewing a document conveys significantly less importance weight=1.0 to that document than the act of creating weight=100.0 or tagging weight=10.0 the document. Additionally, when the inverse attribute is set to true, a relationship from object-to-user is denoted. The effect of this relationship is to enable users to accrue authority from objects whose rank appreciates. For example, the author of a document a create relationship collects rank from that document as its rank appreciates from actions performed by other users on that document—tagging, viewing, downloading—which then amplifies the weight of the user’s future actions. When the Activity Graph Rank Engine completes its rank calculation for all of the affected objects, it sends a resulting set of identifiers with normalized ranks between 1 and 10 to a plug-in class, the SesRankResultAcceptor. This class simply pushes the ranks into the search index using the Oracle SES SOAP API. Once accepted by the SOAP API, the ranks, or docscores as they are known in Oracle SES, are immediately factored into the search ranking providing the DocScore feature is fully enabled. So, for two or more items within the same strata of a result set, those with higher docscores will receive higher search scores than they would otherwise, potentially raising them to a higher rank within that strata. Before You Begin Since Activity Rank works in conjunction with Oracle SES, you must make sure that Oracle SES is installed and configured correctly. Also, as Activity Rank only affects searchable items, the Rank Engine should be run after the SES crawler has finished a Note: Ranks are still calculated and used even in the case where the class of object is not searchable itself.