Skip Headers
Oracle® Beehive Administrator's Guide
Release 1 (1.5)

Part Number E14836-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

9 Managing Oracle Beehive Subscriptions and Notifications

This module describes how to manage subscriptions and notifications in Oracle Beehive. Read this module if you are an Oracle Beehive System Administrator, an Oracle Beehive Business Administrator, or if you are responsible for creating or managing Oracle Beehive subscriptions and notifications. This module includes the following sections:

See Also:

For information on configuring the Notification Delivery Service, see "Managing the Notification Delivery Service"

Configuring User Subscriptions

By default, each newly-provisioned Oracle Beehive user is subscribed to recieve notifications about the following events:

Although users cannot set up new subscriptions, they can disable any of the default subscriptions provided to them, and they can control where the notifications are delivered.

Users make changes to their subscription preferences using the Oracle Beehive user preference pages, which can be accessed at http(s)://<beehive host>:<port>/uss.

Clicking on the Notifications link shows the My Notifications page, shown in Figure 9-1.

Figure 9-1 My Notifications Preferences Page

Surrounding text describes Figure 9-1 .

From the My Notifications page, users can click an edit link to enable or disable one of the default subscriptions, or to choose a particular delivery channel they would like the notification sent to. They can also specify the default delivery channel. By default, notifications are sent to the default delivery channel which in turn by default is the E-mail Inbox. Users can temporarily disable notifications to a particular delivery channel. For example, users could turn off SMS delivery if they are going to be unavailable for a day, and then re-enable it afterwards.

You can alter what a user is subscribed to after they are provisioned using the beectl add_user_subscription command. You must specify the type of entity subscription, a subscription rule, the container the subscription is being attached (applied) to, and the user:

beectl> add_user_subscription --source_entity_class <sourceEntityClass of template> --rule <rule name> --attach <identifier of attached entity> --subscriber <identifier of subscriber>

The following example shows how to subscribe a user to be notified whenever a new document is uploaded to a workspace:

beectl> add_user_subscription --source_entity_class Document --rule NOTIFY_ON_ANY_NEW_DOCUMENT --attach <Workspace identifier> --subscriber <User identifier>

Subscription has been created successfully. Identifier of the newly created subscription is: 05C1:7403:subs:D493EDCBB1B34A06B680C37A30288E8B000000000000

Note:

Make a note of the subscription identifier. You may need it if you decide to modify the subscription in the future.

Table 9-1, "User Subscription Entities and Rules" lists the entities that can be subscribed to and the subscription rules available for each entity.

Table 9-1 User Subscription Entities and Rules

Entity Rule

AddressBook

NOTIFY_ON_ANY_UPDATED_CONTACT

NOTIFY_ON_ANY_DELETED_CONTACT

NOTIFY_ON_ANY_NEW_CONTACT

Artifact

NOTIFY_ON_ANY_NEW_DISCUSSION_ARTIFACT

Assignment

NOTIFY_ON_ANY_UPDATED_ASSIGNMENT

NOTIFY_ON_ANY_NEW_ASSIGNMENT

NOTIFY_ON_ANY_DELETED_ASSIGNMENT

NOTIFY_ON_ANY_COMPLETED_ASSIGNMENT

DiscussionsMessage

NOTIFY_ON_ANY_NEW_DISCUSSION_MESSAGE

NOTIFY_ON_ANY_DELETED_DISCUSSION_MESSAGE

NOTIFY_ON_ANY_UPDATED_DISCUSSION_MESSAGE

Document

NOTIFY_ON_ANY_CREATED_DOCUMENT

NOTIFY_ON_ANY_MODIFIED_DOCUMENT

NOTIFY_ON_ANY_DELETED_DOCUMENT

Forum

NOTIFY_ON_ANY_NEW_DISCUSSION_FORUM

NOTIFY_ON_ANY_DELETED_DISCUSSION_FORUM

NOTIFY_ON_ANY_RENAMED_DISCUSSION_FORUM

NOTIFY_ON_ANY_UPDATED_DISCUSSION_FORUM

Invitation

NOTIFY_ON_ANY_NEW_INVITATION

NOTIFY_ON_ANY_UPDATED_INVITATION

NOTIFY_ON_ANY_DELETED_INVITATION

Resource

NOTIFY_ON_ANY_INVITATION_CREATED_FOR_RESOURCE_APPROVAL

NOTIFY_ON_ANY_INVITATION_UPDATED_FOR_RESOURCE_APPROVAL

Topic

NOTIFY_ON_ANY_NEW_DISCUSSION_TOPIC

NOTIFY_ON_ANY_UPDATED_DISCUSSION_TOPIC

NOTIFY_ON_ANY_DELETED_DISCUSSION_TOPIC

NOTIFY_ON_ANY_MOVED_DISCUSSION_TOPIC

Workflow

NOTIFY_ON_ANY_WORKFLOW_ADDED

NOTIFY_ON_ANY_WORKFLOW_COMPLETED

NOTIFY_ON_ANY_WORKFLOW_DELETED

Workspace

NOTIFY_ON_ANY_MEMBER_ADDED

NOTIFY_ON_ANY_MEMBER_REMOVED

NOTIFY_ON_WORKSPACE_LOCKED

NOTIFY_ON_WORKSPACE_UNLOCKED


You can enable or disable an existing user subscription using the beectl modify_user_subscription command:

beectl> modify_user_subscription --enable {true|false} --subscription <Subscription identifier>

Configuring Notifications to use SMS

Oracle Beehive can send users notifications as email messages, instant messages, or as mobile messages in the form of SMS. SMS notifications are only possible if the Oracle Beehive SMS delivery channel is enabled and configured to point to an SMS Aggregator.

You can configure SMS notifications in one of two ways:

See Also:

For information on configuring the SMPP Delivery Service, see "Managing the SMPP Delivery Service"

Configuring SMS using SMPP

The SMS delivery channel is configured by default to use SMPP (Short Message Peer-to-Peer). It will not be able to deliver SMS notifications until a subscription from an SMPP-compliant aggregator is secured. The Oracle Beehive SMS delivery channel has been tested with the following aggregators:

  • Verisign Intelligent Messaging Network (IMN)

  • Clickatell Gateway

Once you have received an SMS subscription from one of these two vendors, you must make the SMS delivery channel aware of your credentials and enable the delivery channel.

To configure SMS with SMPP, perform the following steps:

  1. Set the Notification Delivery Service to SMPP mode:

    beectl> modify_property --component _NotificationDeliveryService:SmsSettings --name SmsMode --value SMPP
    
  2. Update the Notification Delivery Service with the URL, system ID, and password for your SMS subscription:

    beectl> modify_property --component _SmppDeliveryService --name SmppServiceUrl --value <service url>
    
    beectl> modify_property --component _SmppDeliveryService --name SmppSystemID --value <system id>
    
    beectl> modify_secure_property --component _SmppDeliveryService --name SmppPassword -value <password>
    
  3. If you are using Clickatell Gateway, you must also set the SmppSystemType. The value is your assigned ID for the SMPP configuration with Clickatell via the Web interface:

    beectl> modify_secure_property --component _SmppDeliveryService --name SmppSystemType -value <assigned ID>
    
  4. Activate your proposed configuration using the beectl activate_configuration command:

    beectl> activate_configuration
    

Configuring SMS using XMS

You can configure SMS delivery with the Oracle iAS Wireless XMS Interface by using the Oracle Beehive SMS delivery channel's XMS mode.

To configure SMS with XMS, perform the following steps:

  1. Set the Notification Delivery Service SMS mode to XMS:

    beectl> modify_property --component _NotificationDeliveryService:SmsSettings --name SmsMode --value XMS
    
    
  2. Update the Notification Delivery Service with the user name, password, proxy host name, and proxy port for your XMS interface by issuing the following beectl commands:

    beectl> modify_property --component _NotificationDeliveryService:XmsSettings --name XmsUserName --value <username>
    
    beectl> modify_secure_property --component _NotificationDeliveryService:XmsSettings --name XmsPassword --value <password>
    
    beectl> modify_property --component _NotificationDeliveryService:XmsSettings:WebProxySettings --name ProxyHostName --value <host> 
    
    beectl> modify_property --component _NotificationDeliveryService:XmsSettings:WebProxySettings --name ProxyPort --value <port>
    
  3. Activate your proposed configuration using the beectl activate_configuration command:

    beectl> activate_configuration