Web-Based Administration

uOne requires an HTTP server for Web based administration tools such as Unified Messaging Systems Administration and Personal Messaging Administration. It is recommended that in large operational environments, this server is installed on its own system. It is also recommended that for availability reasons, a second HTTP Server be installed as a backup server for Web administration. There are no other configuration requirements for the HTTP server.

This section specifies the packages to install on the HTTP servers for Web-based administration, the order in which to install them and the procedures for installing packages.

Configuration

There are a few configuration issues that need to be addressed prior to having a functional Web Administration tool. After ensuring the appropriate packages have been installed - dapwaenvxx, dapumsaxx, dappmaxx - perform the following steps:

Configure the .ini files listed in the following section.
Access the UMSA screen via the browser - http://host.cisco.com:280/MSGadmin - and configure the LDAP server. This is available within the Global Configuration section.
Add an Administrator (Greeting, and others as needed). See the uOne Administration Manual for further details.

Configuring the .ini files

Five Unified Messaging System Administration (UMSA) .ini files are user-configurable. Do not configure files other than those listed. The defaultData.ini file contains the default notification for the telephone and pager (if added). The indexData.ini file contains a list of supported location indices and values to be used by the broadcast message feature. The pagerData.ini file contains a name of the paging provider that will be supported by your SNPP paging server. All of these configuration files are located in the same directory as the other UMSA configuration files; /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata.

Caution Removal of UMSA removes the .ini files and installation overwrites them. It is recommended to copy these files to a safe location and merge them with newly installed .ini files after upgrading UMSA files.

defaultData.ini file

This file contains the default (initial) notification values that will be set when a new subscriber and a pager are added through UMSA. The attribute list label is located between the brackets, followed by the number of attributes entry, the attributes, and a reference entry. The attribute list label and the reference entry should not be modified. The number of attributes entry can be changed just as long as it matches the number of attributes. The values listed below are all the valid modification attributes that will be recognized by uOne. There are no other values that will be recognized. There must be no gaps in the numbering of options. The attributes can be deleted or added, but only these six attribute names used in the example are valid and will be recognized.

Example of defaultData.ini (using all attributes)

[addNotifyforNewPager]numOfAttrs=6

attr1=notifyvoicenormal

attr2=notifyvoiceurgent

attr3=notifyfaxnormal

attr4=notifyfaxurgent

attr5=notifyemailnormal

attr6=notifyemailurgent

referenceAttr=pager
 
[addNotifyforNewSub]

numOfAttrs=6

attr1=notifyvoicenormal

attr2=notifyvoiceurgent

attr3=notifyfaxnormal

attr4=notifyfaxurgent

attr5=notifyemailnormal

attr6=notifyemailurgent

referenceAttr=cn

indexData.ini

This file contains the definition of locations that can be assigned to subscribers for use with broadcast messaging. The option list label is located between the brackets, followed by the number of options entry, the options, and a default value. The option list label should not be modified. The default value can be changed but the entry should not be removed. The number of options and the options themselves can be changed in the following ways. The number of options entry can be changed just as long as it matches the number of options. The values for the options must have the following format:

optionXX=Value,Text string

Example of indexData.ini

[filterindex]

numOfOptions=1

option1=l, location

defaultValue=location

 
[l]

numOfOptions=4

option1=0, Default

option2=1, Location 1

option3=2, Location 2

option4=3, Location 3

defaultValue=0

pagerData.ini

The pagerData.ini file contains the names of the paging providers that will be supported by your Paging Server. The option list label is located between the brackets, followed by the number of options entry, the options, and a default value. The option list label should not be modified. The default value can be changed, but the entry should not be removed. The number of options and the options themselves can be changed in the following ways. The number of options entry can be changed just as long as it matches the number of options. The values for the options must have the following format:

optionXX=Value,Text string

Where XX is a numeric value corresponding to its position within the options list. There must be no gaps in the numbering of options. Value is the data that is going to be stored in the LDAP database and Text string is the data that is displayed to the user. There is an additional configuration file, pagermap, located on the paging server that contains information needed to actually make the call for the pager. The configuration file has the following format:

Value-(.*)

Therefore, the value used in the options list must match the value of an entry in the pagermap file. Otherwise, the paging server will not know what number to dial for a subscriber's paging service. Note that the hyphen (-) is a very important part of the format. In addition, pagermap entries should be listed such that most specific (i.e., longest) matches are listed first.

The information in this file will be displayed in a pull down menu in UMSA under Subscriber Administration/Add Paging Information. This file is only used by UMSA.

Figure 13-1: Example of pagerData.ini

Table of Contents

Example of defaultData.ini (using all attributes)