What You Should Know About Connection Types Setting the Connection Type for Notifications Using Fusion Middleware Control

18-12 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter payload -- Any genericcommon footer to appear after service-specific payload -- -- Group Space footer - if applicable -- group-space-footer text-format html-format [CDATA[ p a href=tokengroupSpaceUrltoken target=_blank message-keyGO_TO_SPACEmessage-keynbsp;token groupSpaceNametoken a p ]] html-format group-space-footer -- Unsubscribe footers -- unsubscribe-footer text-format html-format [CDATA[ hr p class=note tokenunsubscribeMessagetoken p ]] html-format unsubscribe-footer notification-template Example 18–3 Default File defaultTemplate_rtl.xml ?xml version=1.0? notification-template xmlns=http:xmlns.oracle.comwebcenternotification -- The CSS Style of the Notification -- style text-format html-format [CDATA[ style type=textcss .title {font-size:1.2em; font-weight:bold; white-space:nowrap;} .label {text-align:left; margin-right:30px; padding-left:10px; white-space:nowrap;} .value {text-align:right; margin-left:20px; padding-right:10px; white-space:nowrap; width:100;} .note {font-size:0.8em; color:999999} .background {background-color:fcfcfc} style ]] html-format style Managing Subscriptions and Notifications 18-13 -- The Subject line of the Notification -- subject message-keyNOTIFICATION_SUBJECTmessage-key subject group-space-subject message-keyGROUP_SPACE_SUBJECT_SUFFIXmessage-key group-space-subject -- Actual srvc-specific data. ProvidedOverridden by srvc template -- payload text-format html-format payload -- Any genericcommon footer to appear after service-specific payload -- -- Group Space footer - if applicable -- group-space-footer text-format html-format [CDATA[ p a href=tokengroupSpaceUrltoken target=_blank message-keyGO_TO_SPACEmessage-keynbsp;token groupSpaceNametoken a p ]] html-format group-space-footer -- Unsubscribe footers -- unsubscribe-footer text-format html-format [CDATA[ hr p class=note tokenunsubscribeMessagetoken p ]] html-format unsubscribe-footer notification-template

18.3.2 Overwriting a Default Notifications Template

To overwrite an existing xml file to customize notification message formats: 1. Create a custom XML file with the name defaultTemplate.xml or defaultTemplate_rtl.xml, for right-to-left language template. 2. Populate the custom file with your revised version of one of these default files.

3. Overwrite the original file, placing the custom file where the absolute path to the

file contains the namespace oraclewebcenternotificationcustom. See Also: Example 18–2 and Example 18–3 show default file content. 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