Messaging Server Configuration

Requirements

Installing uOne Software on Netscape Messaging Server

Installing Notification Services

Prerequisites

Installing Notification services

Installing MWI_PassOff

Configuring MWI_PlugIn

Installing SMS notification on the Netscape Messaging Server

uOne Messaging Server Configuration Requirements

Performance & Tuning

Messaging Server Configuration

uOne interfaces with the Messaging Server using IMAP and SMTP protocols. The primary use of the Messaging server is to store subscriber messages. It is also used for some administrative functions including: storing subscriber personal greetings and distribution list recorded names, temporarily storing faxes to be printed, and temporarily storing outbound AMIS-A messages. Administration of the Messaging server is accomplished through vendor-supplied tools and Cisco Web-based tools. Cisco tools include:

Subscriber Telephone Personal Administration—This feature within the uOne application allows subscriber's to administer their personal preferences using the telephone interface.
Unified Messaging System Administration (UMSA)—This web-based tool allows a System Administrator to manage special administrative accounts, administer Classes of Service, administer subscribers and AMIS-A users, manage broadcast lists, manage user mailbox security, and validate subscriber entries. UMSA updates both the Directory and Messaging servers.
Bulk Add Tool—This command line tool allows a Systems Administrator to conveniently add large groups of new users in a batch mode. Many times this tool is used when migrating users from a legacy system to uOne or if an existing profile resides in an existing database.

uOne provides two plug-ins for Netscape Messaging Server.

MWI_Plugin—used for Notification Services.
SMS_Plugin—notifier for SMS.

Note To allow notification with other vendors' messaging servers, some customization or extension may be necessary.

Requirements

The following information will be required when administering uOne. You should document this for every messaging server.

Table 4-1: Messaging Server Requirements

What Description Where to find it*

Host Name of Messaging server

The fully qualified domain name of the server.

/etc/hosts file

uname -n (appended with the domain suffix found in /etc/resolv.conf)

What	Description	Where to find it*
Host Name of Messaging server	The fully qualified domain name of the server.	`/etc/host`s file `uname -n` (appended with the domain suffix found in `/etc/resolv.conf`)

Installing uOne Software on Netscape Messaging Server

Installing Notification Services

Note This is required only if you implement Notification Services.

There are four components to Notification Services:
Table 4-2: Notification Service Components

Cisco Software Where is it located?

MWI_Plugin.so

Messaging Server

MWI_Passoff

Messaging Server

MWI_Notify

Notification Server

MWI_OnOff

Notification Server

Cisco Software	Where is it located?
MWI_Plugin.so	Messaging Server
MWI_Passoff	Messaging Server
MWI_Notify	Notification Server
MWI_OnOff	Notification Server

For notification services to work, you must administer all four components. This chapter will cover installing MWI_Plugin.so and MWI_Passoff , streaming and SMS notify plugins. For more information on administering these, see the uOne Administration Manual.

Prerequisites

Before you begin installation of the Notification Services software, the Netscape Messaging Server should be installed and configured properly.

The Netscape Messaging Server MWI component software is provided in a compressed format, located on the appropriate CD, or available via the network. The file name of this compressed file takes the format of

uc-41xs-<release>-plugins-<osver>.pkg.Z

where "osver" is the Solaris operating system version of the particular Netscape Messaging Server, and "release" will be the version number as assigned by Cisco. Assuming a version number of "2.6", there would be a server component file similar to the one listed below:

uc-41xs-rx-plugins-solaris26.pkg.Z

Installing Notification services

Step 1 Go to the appropriate Netscape Messaging Server.

Step 2 Login as the superuser.

Step 3 cd /tmp/scratch

Step 4 Transfer the uc-41xs-rx-plugins-solaris26.pkg.Z file into the directory (via ftp binary mode or other means).

Step 5 Within this directory, issue the command:
uncompress uc-41xs-rx-plugins-solaris26.pkg.Z

Step 6 This will produce the following file:
um-41xs-rx-plugins-solaris26.pkg

Step 7 Issue the command:
pkgadd -d uc-41xs-rx-plugins-solaris.pkg

Step 8 Dialogue will be provided for the install procedure.

Step 9 Once the installation is complete, stop the messaging server.

Step 10 Issue the command:./startconsole

Step 11 Via the Netscape Messaging Server console tool, add the following via the SMTP Plugin Configuration dialog box.

Installing MWI_PassOff

Step 1 Go to the Messaging Server where the MWI_PlugIn and MWI_PassOff components reside.

Step 2 Provide MWI_PassOff with the MWI_Notify server name (Table 4-3):

/usr/local/bin/MWI_PassOff -h <dest_server_name>

Step 3 Make sure the FIFO (default = /tmp/spmwi) is read/write for both the Netscape Mail User (MWI_PlugIn) and MWI_PassOff.

chmod 666 /tmp/spmwi  

Table 4-3:  MWI_PassOff Attributes


Attribute
Description
Valid Values

 -d
 Indicates that debugging messages are to be granted.
 N/A

 -f <source_fifoname>
 This command should be used with caution. Use the default whenever possible. This changes the FIFO location and must be coordinated with the MWI_PlugIn, since one writes to the FIFO and the other reads from it.

 Default=/tmp/spmwi

 -h <dest_server_name>
 MWI_Notify server name.

 A valid server name

 -p<port_number>
 The TCP/IP port number is used for communications with MWI_Notify.

 Default=4077

 -q <dest_fifoname>
 Indicates the name of the FIFO, that is, the named pipe, used by the utility to communicate with the server process.

 A valid FIFO


 -r <retry_count>
 Indicates the number of times a server connection is retried before continuing with another server.
 Default=3

 -s <source_portno>
 Indicates the port number used to communicate with the client process.
 A valid port number

 -z
 Indicates that socket connections should have the socket option SO_DEBUG turned on.
 N/A

Attribute	Description	Valid Values
-d	Indicates that debugging messages are to be granted.	N/A
-f <source_fifoname>	This command should be used with caution. Use the default whenever possible. This changes the FIFO location and must be coordinated with the MWI_PlugIn, since one writes to the FIFO and the other reads from it.	Default=/tmp/spmwi
-h <dest_server_name>	MWI_Notify server name.	A valid server name
-p<port_number>	The TCP/IP port number is used for communications with MWI_Notify.	Default=4077
-q <dest_fifoname>	Indicates the name of the FIFO, that is, the named pipe, used by the utility to communicate with the server process.	A valid FIFO
-r <retry_count>	Indicates the number of times a server connection is retried before continuing with another server.	Default=3
-s <source_portno>	Indicates the port number used to communicate with the client process.	A valid port number
-z	Indicates that socket connections should have the socket option SO_DEBUG turned on.	N/A

Configuring MWI_PlugIn

See the Netscape documentation for more information on using Netscape's Web Admin for the Messaging Server and Plug-ins.

Step 1 Go to the Messaging Server where the MWI_PlugIn and MWI_PassOff components reside.

Step 2 Open the /etc/MWI.sample.conf file.

Step 3 Access Netscape's Web Admin for the Messaging Server .

Step 4 Select Plugins.

Step 5 Select Plugin Config.

Step 6 Click the Edit Config File Button.

Step 7 Copy and paste the text from the /etc/MWI.sample.conf file (from Step 2) into this area. The parameters are defined in Table 4-4. The entry should resemble the following format:

PostSmtpAccept <full_path_name_of_plugin_library> funcs=mwi_notify <optional parameters>  

Table 4-4: MWI_PlugIn Attributes 


Attribute
Description
Valid Values

 Funcs

 Name of application.
 Mwi_notify
 Default=mwi_notify
(do not change)

 Debug

 Specifies whether the plugin generates debugging messages to the /var/adm/syslog/user.log file on HP-UX. By convention, on IRIX they are located in the /var/adm/SYSLOG file.
 Syslog must be setup for user.log.
 On
 Off
 Default=Off

 FIFO

 Specifies the name of the FIFO where the plugin should send data.

 Default=/tmp/spmwi

 Timeout

 Specifies the number of seconds after which a notification should be dropped, if it cannot be delivered.
 Range=1-60 sec.
 Default=15 sec.

Attribute	Description	Valid Values
Funcs	Name of application.	Mwi_notify Default=mwi_notify (do not change)
Debug	Specifies whether the plugin generates debugging messages to the /var/adm/syslog/user.log file on HP-UX. By convention, on IRIX they are located in the /var/adm/SYSLOG file. Syslog must be setup for user.log.	On Off Default=Off
FIFO	Specifies the name of the FIFO where the plugin should send data.	Default=/tmp/spmwi
Timeout	Specifies the number of seconds after which a notification should be dropped, if it cannot be delivered.	Range=1-60 sec. Default=15 sec.

Installing SMS notification on the Netscape Messaging Server

Step 1 Go to the appropriate Netscape Messaging Server.

Step 2 Login as the superuser.

Step 3 cd /tmp/scratch

Step 4 Transfer the uc-41xs-rx-plugins-solaris26.pkg.Z file into the directory (via ftp binary mode or other means).

Step 5 Within this directory, issue the command:
uncompress uc-41xs-rx-plugins-solaris26.pkg.Z

Step 6 This will produce the following file:
um-41xs-rx-plugins-solaris26.pkg

Step 7 Issue the command:
pkgadd -d uc-41xs-rx-plugins-solaris.pkg

Step 8 Dialogue will be provided for the install procedure.

Step 9 Once the installation is complete, stop the messaging server.

Step 10 Issue the command:./startconsole

From the Netscape console, double click on the messaging server for which you are installing the plugin.

Example 4-1: Messaging Server Console:ms.bmp

Select the configuration tab on the following screen.

Example 4-2: Messaging Server Configuration

Expand the Services tree until you get to the SMTP plugins and select the plugins node.

Example 4-3: Plug-in Configuration.

Note The installation script installs the SMS plugin (/opt/local/lib/notify.so)into the proper location.

Select the Edit button, and fill out the plugin information.

Example 4-4: Dialog box for plugin

information

Make the following entries:

Entry: PostSmtpAccept
Path: /opt/local/lib/notify.so
Functions: notify
Init: notify_init
Options: NotifyAddress=<notifier@yourdomain>

Note Ensure that the < > brackets are included in the Options field entry.

uOne Messaging Server Configuration Requirements

The following table (Table 4-5) introduces various configuration requirements for the Messaging Server.
Table 4-5: Messaging Server Requirements

Directory Enabled

If possible, the messaging server should ideally be "directory enabled"; i.e., it should use your directory server(s) to track profile information on subscribers.

Broadcast Messaging

To optimize disk storage utilization for broadcast messages, the single copy message store feature of the Netscape Messaging Server should be used. According to Netscape Messaging Server documentation, server performance is degraded somewhat in exchange for optimized disk storage utilization. The single copy message store feature deletes the single copy of the message automatically when all references to it are deleted.
Note It is important to delete messages only under Messaging Server control (e.g., don't delete them using rm from the shell), otherwise reference information will be corrupted.

Distribution List

See Example 4-5 for the proper SMTP configuration. This will ensure that when a subscriber has been deleted from a distribution list, the message will still be accepted by the Messaging server.

Example 4-5: SMTP configuration for distribution lists

Performance & Tuning

To support a large number of simultaneous IMAP or SMTP protocol sessions, it may be necessary to increase Messaging server or operating system configurable parameters that govern the maximum number of:

IMAP/SMTP sessions per Messaging server
Open files per processes
Processes a particular user can create
Open files on the system
Open Inodes in the system
Processes in the system

Note In addition, Disk Block Buffer Cache and semaphores may need modifications for optimum performance.

The following table (Table 4-6) provides a formula for how to calculate IMAP sessions:
Table 4-6: Tuning Requirements

IMAP sessions per Messaging server

The maximum simultaneous IMAP sessions per Messaging server equals:

(2 x maximum possible number of uOne processes that can be running at a time) + (expected number of simultaneous email client sessions) + (number of FaxPrint and amisaout processes)
Then the number of Netscape Network server processes must be set to at least this number.
Note The maximum number of uOne processes that can be running at a time is constrained by the MaxInstances and MaxGroupInstances parameters of the ALO, not by the number of TEL object ports. This is because the uOne application instances can remain running for short periods of time (performing cleanup activities) after their telephone connection has terminated.

Directory Enabled	If possible, the messaging server should ideally be "directory enabled"; i.e., it should use your directory server(s) to track profile information on subscribers.
Broadcast Messaging	To optimize disk storage utilization for broadcast messages, the single copy message store feature of the Netscape Messaging Server should be used. According to Netscape Messaging Server documentation, server performance is degraded somewhat in exchange for optimized disk storage utilization. The single copy message store feature deletes the single copy of the message automatically when all references to it are deleted. Note It is important to delete messages only under Messaging Server control (e.g., don't delete them using `rm` from the shell), otherwise reference information will be corrupted.
Distribution List	See Example 4-5 for the proper SMTP configuration. This will ensure that when a subscriber has been deleted from a distribution list, the message will still be accepted by the Messaging server.

Table of Contents

Messaging Server Configuration

Installing Notification services