Skip Headers
Oracle® Communications Order and Service Management Administrator Application User's Guide
Release 7.2.2

E35418-01
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

3 Managing Notifications

This chapter describes how to use the Oracle Communications Order and Service Management (OSM) Administrator to manage notifications.

About OSM Notifications

There are two types of notifications: polled and transitional. Polled notifications are based on rules that are evaluated at regular intervals as defined in Oracle Communications Design Studio. Transitional notifications are based on rules that are evaluated when an order moves to a specific state, status, or exception in a process. You use notifications to inform OSM users about actions that need to be taken to complete an order. See the Design Studio for OSM Processes online Help for information about defining notifications.

Notifications work as follows:

  1. An event occurs that triggers a notification. The event can be based on a schedule (for example, every seven days) or it can be a result of a task becoming jeopardized. See the Design Studio for OSM Processes online Help for more information about jeopardy notifications.

  2. A notification is sent by email to a specific user or to all users in a workgroup. You can see the email on the Notifications tab in the Task Web Client.

    The email informs you that the notification has been generated.

You use OSM Administrator to enable and disable notifications.

Note:

Notifications are created in Design Studio by a system administrator. See the Design Studio for OSM Processes online Help for more information.

Figure 3-1 shows the columns on the Notifications Tab.

Figure 3-1 Notifications Tab

Screen shot shows the columns on the Notifications Tab.

Table 3-1 lists the columns on the Notifications tab.

Table 3-1 Columns on the Notifications Tab

Column Description

Filtered By

A list that filters the notifications to display.

Description

The description of the notification.

Interval

The time interval between which the system checks for the notification event.

Priority

The priority of the notification between 1 and 255, with 1 being the highest priority.

Next Start

The time the system next evaluates the notification.

Last Start

The last time the system evaluated the notification.

Last Finish

The last time the notification evaluation was completed.

Execution Time

The total time in which it took to start and complete the evaluation of the notification.

Author

The user who created the notification.

Enabled

Whether or not the notification is enabled.

Count

The number of active notifications against that specific notification definition.

Email

Displays whether the user has subscribed to be notified by email (Yes) or not (No).


Setting Up Email Notifications

You can set up OSM to notify users by email. When a notification occurs, the system sends a notification ID number through email.

To assign email notification access:

  1. Add the user, oms-automation, to the workgroup/role that contains the user who will receive email notifications. See "Assigning Users to a Workgroup".

    oms-automation is the internal automation user account for the processing of OSM automation and e-mail notifications.

  2. Make sure that email_server_ssl and email_server_authentication parameters in oms-config.xml are set to true. (By default, both are already set to true.)

  3. The User Properties dialog box appears displaying the user and the workgroups to which the user belongs.

    1. In the OSM Administrator, click the Workgroup Administration tab.

    2. On the Workgroup Administration tab, in the list of workgroup items, select Users.

    3. Double-click a user to bring up the User Properties dialog box which displays the user and the workgroups to which the user belongs.

    4. In the Email field, type the email address of the user, and click OK.

      You can modify or delete the user's email address at any time. If you delete the user's email address, the user will not receive email notifications.

  4. If the user's email server requires server authentication, you must store the password for administrator's email user specified by admin_email_address in OSM credential store.

    Use credStoreAdmin and the following XML sample snippet to store the password. (See the discussion on credStoreAdmin in OSM System Administrator's Guide.

    <?xml version="1.0" encoding="UTF-8"?>
    <user:CredentialConfig
    xmlns:oms=" http://www.metasolv.com/OMS/OrderModel/2002/06/25"
    xmlns:user=" http://www.metasolv.com/Provisioning/CredentialConfig"
    xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation=" http://www.metasolv.com/Provisioning/CredentialConfig
    ../models/CredStoreAdmin.xsd ">
       <user:jpsPolicy operation="add">
         <user:mapname>osm</user:mapname>
       </user:jpsPolicy>
       <user:credential operation="create" overwrite="true">
         <user:mapname>osm</user:mapname>
         <user:keyname>osmUser_{OSM_ADMIN_EMAIL_ADDRESS}</user:keyname>
         <user:user>{OSM_ADMIN_EMAIL_ADDRESS}</user:user>
         <user:password>{OSM_ADMIN_EMAIL_PASSWORD}</user:password>
       </user:credential>
     </user:CredentialConfig> 
    
  5. Delete this snippet file after you are done using it.

See the discussion on email notifications in the Design Studio for OSM Processes online Help for more information.

Enabling and Disabling Notifications

You can enable and disable a notification in the OSM Administrator.

To enable or disable a notification:

  1. In the OSM Administrator, click the Notifications tab.

  2. On the Notifications tab, in the Filtered By list, select All.

  3. Right-click a notification and select Enable or Disable.