Unicenter Notification Services provides an SDK, a user interface, a recipient and provider registry, the unsutil command line utility, reports, configuration, and commands.
The Client SDK provides libraries, include files, and samples using C and C++. It contains functions and methods to send one-way and two-way notifications, retrieve status, and administer recipients and providers. The Recipient plug-in SDK lets you create plug-ins to resolve recipient information in your directory services. For more information, see the Programming Guide and online CA SDK Reference.
Notification Services provides windows and dialogs in the classic Windows GUI that let you send messages, view message status, and define recipients and providers. To use the classic GUI, install the Administrative Client for Enterprise Management on a Windows machine.
Event Management provides the message actions NOTIFY and NOTIFYQ that let you define message policy for sending notifications and getting notification status.
The Notification Services recipient and provider registry lets you enter information about recipients, recipient groups, and service providers. It contains recipient addresses, protocols, and connection information so that you need not enter everything manually with each notification. You just enter the name (alias) for the information you want to use. This saves time and may hide sensitive information.
The registry has files that you can edit with a text editor, the Windows GUI, or the unsutil command-line utility described later in this section.
Each file contains an explanation of the file’s contents and includes sample templates to help you define your own recipients and providers. The files are:
Defines provider aliases with connection information for the protocols that service providers support. See the topic Connection Information for details about what is required for each protocol.
Defines recipient aliases and their default providers. Each recipient has one default provider.
Defines recipient groups.
Defines recipient addresses for each provider.
External recipient registries can be queried by the provided LDAP recipient plug-in or user-developed plug-ins. The file uns_source.ini defines the recipient plug-ins available to the Notification Services daemon for recipient resolution.
When a recipient alias cannot be found in the recipient registry (uns_recipient.ini), and a recipient plug-in is configured, active, and successfully loaded, the daemon tries to resolve the recipient alias in the plug-in.
The file uns_source.ini provides samples for the default installed LDAP servers:
Before you activate the source, customize the corresponding configuration file according to your environments. The files have comments that explain the values you can change.
The unsutil command-line utility lets you define, alter, delete, and list recipients, groups, providers, and addresses. This utility provides facilities similar to the user interface, and the syntax is similar to cautil. For more information, see the online CA Reference.
Statistical reports from the unsutil command-line utility display the following types of information: summary, provider, protocol, recipient, sender, and error.
Some features of the Notification Services daemon can be configured to reflect the way you use Notification Services in your enterprise. For example, you can specify whether the daemon should create a transaction log and what that log contains; indicate whether to store information about notifications on disk (checkpointing); and enter a default sender name for several protocols. To customize the daemon, update the file UNSDaemon.ini. This file has comments that explain the values you can change. Also, see the procedure Configure the Notification Services Daemon in the online help and CA Procedures.
The Unicenter Notification Services commands are:
Sends a one-way or two-way notification message using the Notification Services daemon. If a reply or other status is requested, the command waits for the status and displays it when received. If the wait times out, you can use the uquery command for future queries of that notification.
Sends a one-way or two-way notification message on the local node without using the Notification Services daemon. This command lets you send notifications when the daemon is not running. The unotifys command does not store notification information on disk because the daemon is not running.
Requests the status of one notification or all notifications from the Notification Services daemon. For a one notification, you can display the current status immediately, or wait until a requested status, like a reply, is received.
Requests the status of one notification sent by unotifys on the local node. It does not use the Notification Services daemon, so you can use this command when the daemon is not running.
Starts, stops, and queries the status of the Notification Services daemon.
Encrypts and decrypts a configuration file. Some connection information in the file uns_provider.ini requires a user name and password that you may want to protect. Only Notification Services applications can read an encrypted file.
Note: Before changing data in an encrypted file, decrypt it. After changing the file, encrypt it again.
|
Copyright © 2010 CA.
All rights reserved.
|
|