Messaging Preferences

Your mail address is your default messaging channel. With no filters defined, a subscription is sufficient to trigger a mail notification, provided your system administrator has configured shared credentials and mail is the messaging default.

After you have subscribed to an application object, no additional configuration is required to receive a notification through your mail when that object changes.

However, if you want to receive notifications over your phone or from an alternate mail address, you can use Messaging preferences to configure messaging channels and define messaging filters for messages generated from the Oracle User Messaging Service:

  • Messaging channels are the channels over which messages, notifications, and alerts are received from the Oracle User Messaging Service. Channels include mail and text. Messages, notifications, and alerts come from the services that are registered with the Oracle User Messaging Service.

  • Messaging filters define sorting conditions for messages and specify the channels through which to send the messages that meet the conditions. For example, you can specify that messages from a named user should come to you as a text, while messages from a named service come to you as an email.

To configure and manage messaging channels and filters:

  1. On the Messaging page, click Manage Configuration to open the User Messaging Preferences login page.

    Note:

    The Manage Configuration button is active only when a BPEL server is configured with WebCenter Portal. If a BPEL server is not present, the button is grayed out, and mail, the default messaging channel, is used for notifications. Because the BPEL server provides notification features, the Manage Configuration button may be active even when your system administrator elects to use a mail server instead of a BPEL server for notifications. In environments where more than one BPEL connection is registered, the messaging preferences repository is shared by all. When you set messaging preferences for one BPEL connection, you set them for all.

  2. Log in to the User Messaging Server to open the Messaging Preferences panel.
    • The Messaging Channels tab provides controls for creating and managing messaging channels and a view of all configured messaging channels, such as EMAIL and SMS. The EMAIL channel is always available. By default, it uses your email address from the LDAP identity store.

    • The Messaging Filters tab provides a way to outline the conditions under which you are notified and to associate a messaging channel with a defined set of conditions.

Establishing a Messaging Channel

Establishing a messaging channel involves selecting the channel over which a notification is sent and providing the delivery address for that channel.

To establish a messaging channel:

  1. On the the Messaging Channels tab, click the Create icon to open the Add Channel dialog.
  2. In the Name field, enter a display name for the channel.

    For example, enter MyPhone.

  3. From the Type list, select the channel over which to send notifications:

    Tip:

    The presence of a channel is determined by your system administrator, who deploys them and makes them available.

    • EMAIL to specify that notifications are sent to you through your mail

    • SMS to specify that notifications are sent as text messages to your phone

  4. In the Address field, enter an address for the selected type:
    • For EMAIL, enter the address of the mail account to which to send notifications. For example, my.name@example.com.

    • For SMS, enter the phone number to which to send notifications in the format <country_code><area_code><number>/ For example, 14154444444.

  5. For the Default check box:
    • Select to identify one or more channels as the default channel over which to send notifications.

      Default channels are the channels over which all notifications that do not meet any of your defined filtering conditions are sent.

    • Deselect to prevent selected channels from being used as defaults.

  6. Click OK to save your changes and exit the dialog.

Creating and Applying Messaging Filters

Messaging filters enable you to qualify the types of notifications you want to receive and weed out the notifications of no interest. Filters also provide a means of associating a selected messaging channel with a particular type of notification. For example, using messaging filters, you can specify that all notifications about portal updates go to mail while all notifications about event changes go to your phone, provided your system administrator has configured Notifications to use multiple messaging channels.

Two important things to know about setting up messaging filters:

  • Text values in your filtering conditions are case-sensitive. For example, messaging filters differentiate between Event and event.

  • Create separate conditions for multiple terms. For example, for a Subject that contains Ari gave feedback, create three filtering conditions, one for each term.

To create and apply messaging filters:

  1. On the Messaging Filters tab, click the Create icon to open a filter-creation page.
  2. In the Filter Name field, enter a display name for the filter.
  3. Optionally, enter a filter description in the Description field.
  4. From the Matching list, select from:
    • All of the following conditions to require that all of the conditions you specify are met

    • Any of the following conditions to require that at least one of the conditions you specify is met

  5. From the first Add Filter Condition list, select from:
    • Subject to base a condition on words appearing in the message subject

      It is likely that the most useful filter condition option is Subject. The subjects of notification messages are standardized and can therefore be anticipated. This makes subjects ideal for setting up filtering conditions. See the second table below for a list of standard notification message subjects and examples of filter conditions.

    • From to base a condition on the message sender

      All notification messages are sent from the same entity—as configured by your system administrator.

    • Date to base a condition on when the message was generated

      Date and Time options may be useful for ad hoc situations, for example, you want to ensure that any notifications about events delivered on the day of the event are sent right to your phone.

    • Time to base a condition on the time the message was generated

    Note:

    Of all the filter conditions available on the Add Filter Condition list, Subject, From, Date, and Time are the options that are relevant to and work with the types of messages generated by Notifications. The other options have no effect.

  6. From the second Add Filter Condition list, select an operator for the condition.

    See the table below for an alphabetical list of operators that are relevant to the attributes Subject, From, Date, and Time.

  7. Click the Click to add new filter condition icon.
  8. From the Messaging Option list, select from:
    • Send No Messages to omit notification for the defined filter conditions

    • Send Messages to all Selected Channels to send notification through all channels selected from the Add Notification Channel list

    • Send to the First Available Channel to send notification through the first open channel of all the selected channels

  9. From the Add Notification Channel list, select the channel over which to send the notification messages that meet your defined filter conditions, and then click the Click to add channel to this filter icon.

    The Add Notification Channel list is populated with the channels that are defined on the Messaging Channels tab. You can add multiple channels in turn.

  10. Click OK to save and apply the messaging filter.

    Tip:

    If your defined filtering conditions do not match an incoming notification, the User Messaging Server will send notifications over all the channels you have identified as default channels.

The following table provides an alphabetical list of operators that are relevant to the attributes Subject, From, Date, and Time and describes the values they require.

Table 9-2 Operators Relevant to Subject, From, Date, and Time

Operator Value(1) Attributes

Between

In the fields provided:

  • For Date, enter a start date and end date between which to apply the filter

  • For Time, select a start time (hours and minutes) and end time between which to apply the filter

Date, Time

Contains

Enter a string that must be included in the message Subject or return address (From)

Separate multiple values with commas.

Subject, From

isEqual

Enter the literal value that must be used for the message Subject, Date, Time, or return address (From)

Subject, From, Date, Time

isGreaterThan

Enter the message delivery date beyond which to apply the filter

Date

isGreaterThanOrEqual

Enter the message delivery date on which to start applying the filter

Date

isLessThan

Enter the message delivery date before which to start applying the filter

Date

isLessThanOrEqual

Enter the message delivery date on which to stop applying the filter

Date

isNotEqual

Enter a literal value that must be ignored for the message Subject, Date, Time, or return address (From)

Subject, From, Date, Time

isWeekday

No value is required. This operator applies to messages sent on weekdays.

Date

isWeekend

No value is required. This operator applies to messages sent on weekends.

Date

NotContains

Enter a string that must be excluded from the message Subject or return address (From).

Separate multiple values with commas.

Subject, From

Footnote 1 String values are case sensitive. Multiple values in strings must be separated by a comma.

The following table provides a list of standard notification message subjects and examples of condition formulations.

Tip:

Messaging filters are case-sensitive. For example, they differentiate between Event and event.

You must create a separate condition for each term. For example, when you filter for Ari gave feedback, create three conditions—one for each term.

Table 9-3 Standard Notification Message Subjects

Standardized Notification Subject Example Filter Conditions

userName has invited you to become a connection

  • Subject Contains connection

  • Subject Contains Ari

    You can set the condition action to route or ignore all messages concerning a named user for any subject that includes a user name.

userName posted message on your message board

  • Subject Contains message

  • Subject Contains board

userName commented on your message board posting

Subject Contains commented

userName likes on your message board posting

Subject Contains likes

userName gave feedback to you

  • Subject Contains gave

  • Subject Contains feedback

Portal Membership Change

Subject isEqual Portal Membership Change

userName created the forum forumName

  • Subject Contains Monty

  • Subject Contains created

  • Subject Contains forum

userName created the event eventName

  • Subject Contains Java

  • Subject Contains Summit

userName changed the event eventName

  • Subject Contains Java

  • Subject Contains Summit

  • Subject Contains changed

userName deleted the event eventName

  • Date isEqual 5/31/10

  • Subject Contains event

  • Subject Contains Java

  • Subject Contains Summit

On the day of the event, all notifications concerning the Java Summit event are routed to a selected channel. You can omit the term event, and receive other related notifications.