cc/td/doc/product/voice/uone/srvprov/r42s
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Web-based Administration Configuration

Web-based Administration Configuration

uOne requires an HTTP server for web-based administration tools such as uOne Administration and Personal Messaging Administration (PMA). Large operational environments should install this server on its own system. For availability reasons, a second HTTP server should be installed as a backup server for web administration. No other configuration requirements exist 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.

Prerequisites


Note   The quickconfig tool sets up the schemaConfig.ini.

A few configuration issues should be addressed in order to have a functional Web Administration tool. After ensuring the appropriate packages have been installed—uonewaenv, uoneumsa
, uonepma—perform the following steps:

Configuring the .ini Files

Five uOne Administration .ini files are user-configurable. Do not configure files other than those listed.

All of these configuration files are located in the same directory as the other UMSA configuration files—/home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata.

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 uOne Administration. 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 recognized by uOne. No other values are 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 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

where XX is a numeric value corresponding to its position within the options list. No gaps may exist in the numbering of options. Value is the data to be stored in the LDAP database, and Text string is the data to be displayed to the user.


Example 13-1: 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 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 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. No gaps may exist 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.

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


Example 13-2: Example of pagerData.ini



languageData.ini

The languageData.ini file contains a list of supported languages. The information in this file is displayed in a pull-down menu in UMSA under Subscriber Administration (Add/Modify Subscriber). This file is used only by UMSA.

loggingData.ini

The loggingData file defines the types of information and activities logged for UMSA and PMA.

bulktool.ini

The bulktool.ini file contains a common set of subscriber attributes such as the greeting message host, subscriber time zone, etc. It is used along with an input text file to create uOne subscriber entries in the LDAP database during the bulk add.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Sep 25 20:21:55 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.