What's Next?

What's Next?

This section introduces the notification types and describes the differences between the types. Each of the notification types follow a setup process similar to the e-mail notification (see "Using Notifications- A Simulation"). For procedures on how to create a notification of each type, see the Help system.

This section also describes the notification variables that can help you report information about a WS_FTP Server event.

SMS Notifications

SMS (Short Message Service) is similar to paging. However, SMS messages do not require the mobile phone to be active and within range and will be held for a number of days until the phone is active and within range. SMS messages are transmitted within the same cell or to anyone with roaming service capability.

SMS notification services are provided by a number of different providers in one of two ways: TAP, the protocol used in common pagers which requires a modem and the phone number of the provider and recipient, or via e-mail where a specifically formatted e-mail message is sent to an address.

Because multiple methods can be used to provide SMS service, there are no common settings for SMS notifications. Each notification is tied to a provider, which may support either or both of the delivery methods mentioned.

The SMS options have a list of all available countries that have configured providers. When a new country is selected, the list is re-populated with the providers for the country. Click the browse button to display a list of all providers organized by country. If your provider is not listed, you can create an entry for them here.

The following shows an example of the settings for an SMS notification.

See the help system for step-by-step procedures and descriptions of the options.

Pager Notifications

Pager messages are delivered via a terminal service provider. You can define a notification to send a message to a pager when an FTP event occurs. WS_FTP Server supports PageNet, TAP (Telocator Alphanumeric Protocol) , SMS-TAP, UCP-SMS (British Telecom), and NTT (Nippon Telegraph and Telephone) pager services.

The following shows an example of the settings for a Pager notification.

See the help system for step-by-step procedures and descriptions of the options

E-mail Notifications

E-mail messages are delivered via an SMTP gateway, which will probably be the same relay for all e-mail addresses. However, you can have notifications that use different SMTP servers.

The following shows an example of the settings for an e-mail notification.

See the help system for step-by-step procedures and descriptions of the options.

Program Notifications

When an FTP event occurs (such as a quota exceeded), you can send a notification that launches a program. The program must be on the same system as the WS_FTP Server.

Program notifications, depending on the program launched, could require an extensive amount of processing on the server. For this reason, only system administrators can configure them remotely.

The following shows an example of the settings for an Program notification.

See the help system for step-by-step procedures and descriptions of the options.

Using Variables to Report Event Details

You can use the following variables to report details about the event that triggers a notification. These variables can be used in the Message or Subject boxes.

Variable Description

%Event The event that triggered the notification, which means any of the rules: Directory Created, File Deleted, File Download, File Rename, File Upload, Failed Login, Quota Exceeded.

%Dir Inserts the name of the directory created or attempting to be created.

%File Inserts the name of the file the action was attempted on (available for upload, download, and deletion rules.

%ToFile Inserts the new name of a file in a file rename attempt (only available in rename rules.)

%FmFile Inserts the original name of a file in a file rename attempt (only available in rename rules

%User Inserts the User ID of the user that attempted the action (available for rules in all categories.

%Status Inserts whether the attempt was successful or not (available for rules in all categories).

%SimpleName The file name, without the path.

%Timestamp Date and time the notification was triggered.

About Notifications
Notification Server Manager
Configuring the Servers for Notifications
The Notifications Library
Using Notifications - A Simulation
What's Next?

Variable	Description
%Event	The event that triggered the notification, which means any of the rules: Directory Created, File Deleted, File Download, File Rename, File Upload, Failed Login, Quota Exceeded.
%Dir	Inserts the name of the directory created or attempting to be created.
%File	Inserts the name of the file the action was attempted on (available for upload, download, and deletion rules.
%ToFile	Inserts the new name of a file in a file rename attempt (only available in rename rules.)
%FmFile	Inserts the original name of a file in a file rename attempt (only available in rename rules
%User	Inserts the User ID of the user that attempted the action (available for rules in all categories.
%Status	Inserts whether the attempt was successful or not (available for rules in all categories).
%SimpleName	The file name, without the path.
%Timestamp	Date and time the notification was triggered.

About Notifications Notification Server Manager Configuring the Servers for Notifications The Notifications Library Using Notifications - A Simulation What's Next?

Ipswitch, Inc.
http://www.ipswitch.com


©Ipswitch 2004