What You Should Know About Overwriting Default Notification Templates

18-14 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter For example: tmprepositoryoraclewebcenternotificationcustomtemplatedefaultTemplate.x ml 4. Upload the custom file into the WebCenter MDS repository by running the importMetadata WLST command. For example: importMetadataapplication=webcenter, server=WC_Spaces, fromLocation=template-file-location, docs=oraclewebcenternotificationcustomtemplatedefaultTemplate.xml The template-file-location points to the directory under which the fully qualified custom file is located. The fully qualified custom file is typically placed under the directory structure equivalent to its namespace. For example, consider a file that is created under the following namespace: tmprepositoryoraclewebcenternotificationcustomtemplatedefaultTemplate.x ml In such a case, the fromLocation is tmprepository because the remaining sub-directory consists of the namespace for the XML file. The namespace must have at least the path oraclewebcenternotificationcustom. 5. Restart the portal application.

18.4 Testing the Notifications Connection

In general, Notifications depends on the underlying Mail or BPEL connection to be valid when the administrator sets it. If these connections prove to be valid, then, by extension, the Notifications connections requirements are met.

18.5 Troubleshooting Issues with Notifications

Problem No notifications are received. Solution ■ If the log indicates that the Notification Sender is not configured, then it means the service is unable to find the connection to use. ■ Ensure that Notifications is configured to use either a valid BPEL or MAIL connection. This can be verified through the getNotificationsConfig WLST command see Section 18.2.4, Setting the Connection Type for Notifications Using WLST or through the Fusion Middleware Control user interface see Section 18.2.3, Setting the Connection Type for Notifications Using Fusion Middleware Control . See Also: For information about the importMetadata command and other WLST commands, see the section, importMetadata, in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. Tip: For information about testing Mail connections, see Section 17.9, Testing Mail Server Connections. Managing Subscriptions and Notifications 18-15 Problem Notifications is configured BPEL or MAIL correctly, but still no notifications. Solution Notifications relies on a valid BPEL or MAIL connection. Run the respective connection validations and troubleshooting scenarios as described in Chapter 17, Managing the Mail Service, or Chapter 22, Managing the Worklist Service. Problem MAIL or BPEL connections are set up appropriately, but still do not receive notifications. Solution Notifications are generated based on user subscriptions. Apart from notification for invitations to connect, which is configured out of the box, other notifications are generated only when a user has specifically subscribed. Ensure that the user has created subscriptions through his or her personal Preferences or through Space- or object-level subscriptions. For more information, refer to the section, Subscribing at the Application, Space, and Object Level, in Oracle Fusion Middleware Users Guide for Oracle WebCenter. Problem Users have set up their subscriptions, but still receive no notifications. Solution ■ Depending on how it is configured, Notifications delegates the delivery of notifications to BPELUMS or the Mail service. For the Mail service, ensure that the user’s email address is configured. For UMS, look in Fusion Middleware Control under the Message Status section of User Messaging Service. Here you see the status of each outgoing message from UMS. For more information, see the chapter Monitoring Oracle User Messaging Service, in the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle Business Process Management Suite. ■ For UMS, this problem could also mean that the configuration of the sender on the WebCenter side does not match or find a corresponding driver on the UMS side. Ensure that the sender address domain allows UMS to match at least one driver for outbound messages. ■ For the Mail service, ensure that the mail connection points to a shared connection as described in Section 18.2.1, What You Should Know About Connection Types. Problem For UMS configurations, users receive notifications on some channels but not on others. Solution This is most likely due to the way the user’s messaging channels and filters are configured. For more information, see the section, Establishing and Managing Your Messaging Channels and Filters, in Oracle Fusion Middleware Users Guide for Oracle WebCenter. 18-16 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter Problem For UMS configurations, only mail-channel notifications are delivered, the Worklist channel does not work. Solution Ensure that the SOA domain is extended with the Worklist driver template as described in the chapter Configuring Oracle User Messaging Service, in the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle Business Process Management Suite. 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