Overwriting a Default Notifications Template

19 Managing WebCenter Personalization 19-1 19 Managing WebCenter Personalization This chapter describes how to configure and manage the WebCenter Personalization services for WebCenter Portal applications. This chapter includes the following sections: ■ Section 19.1, What You Should Know About WebCenter Personalization ■ Section 19.2, WebCenter Personalization Prerequisites ■ Section 19.3, Configuring the WebCenter OPSS Trust Service ■ Section 19.4, Configuring Providers ■ Section 19.5, Configuring Coherence ■ Section 19.6, Configuring Content Presenter ■ Section 19.7, Configuring Single Sign-on ■ Section 19.8, Overriding the Default Security Settings Audience The content of this chapter is intended for Fusion Middleware administrators users granted the Admin or Operator role through the Oracle WebLogic Server Administration Console. See also, Section 1.8, Understanding Administrative Operations, Roles, and Tools.

19.1 What You Should Know About WebCenter Personalization

WebCenter Personalization provides a dynamically derived user experience for your WebCenter Portal application. WebCenter Personalization evaluates defined sources of input data, generates a decision based on that evaluation, and applies this information to a declaratively defined personalization scenario. WebCenter Personalization, for example, can return content or change application flow based on information about a user in a Human Resources database, targeting the application experience for that specific user. WebCenter Personalization is installed as an application in the wc_domain on the WC_Utilities server. Client applications access WebCenter Personalization remotely over HTTP using RESTful services. To make access easy, Java applications can use a set of provided POJO client libraries. Design-time JDeveloper tools are used to create Property Service and Conductor artifacts to be executed remotely using REST calls. WebCenter Personalization is also available in the JDeveloper integrated domain for projects that include the Personalization technology libraries when you first create 19-2 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter your application. For evaluation purposes and iterative development, this domain offers the quickest and easiest way to explore WebCenter Personalization. For more information about WebCenter Personalization architecture and services, see Personalizing WebCenter Applications in Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

19.2 WebCenter Personalization Prerequisites

This section describes the system requirements and dependencies for WebCenter Personalization in the following sections: ■ Section 19.2.1, WebCenter Personalization Installation Requirements ■ Section 19.2.2, WebCenter Personalization Configuration Requirements ■ Section 19.2.3, WebCenter Personalization Security ■ Section 19.2.4, WebCenter Personalization Limitations ■ Section 19.2.5, WebCenter Personalization Configuration Options

19.2.1 WebCenter Personalization Installation Requirements

If you are using the CMIS or Activity Graph data providers, or the People Connection locator within a Personalization Conductor scenario, then WebCenter Spaces must be installed. For High Availability environments only, Coherence is also required.

19.2.2 WebCenter Personalization Configuration Requirements

If you are using the CMIS provider, Activity Graph provider, PeopleConnections locator, or custom providers you must configure them as shown in Section 19.4, Configuring Providers. If you are using Content Presenter to present content in WebCenter Spaces or in your WebCenter Portal application, then you must also configure Content Presenter to display the results of your scenarios as described in Section 19.6, Configuring Content Presenter. WebCenter Personalization relies on WebCenter Trust Services to provide single sign-on SSO between different managed servers within the WebCenter domain. Trust Services must be configured using the WLST scripts configureTrustWCPS.py and configureConnectionsWCPS.py provided in the user_projectsapplicationswc_domain directory. For JDeveloper’s integrated domain, only a single script configureWCPS.py located in the DefaultDomainscrpts-wcps directory is used. For more information about configuring the WebCenter Trust Services and single sign-on using this script see Section 19.7, Configuring Single Sign-on.

19.2.3 WebCenter Personalization Security

WebCenter Personalization is compatible with whatever source of user authentication services are configured within the WLS security realm. That is, it can use the default identity store and policy and credential store for the domain. If you are using the People Connections locator or Activity Graph data providers, users must also be configured as WebCenter Spaces users. WebCenter Personalization REST services are accessed though a pre-configured WebCenter Personalization Web application that requires authenticated access for all