|
|
Personal Mailbox Administration (PMA) is a web-based tool that subscribers use to set up options for their uOne mailboxes.For instance, subscribers can choose how to be notified when new messages arrive in their mailbox, manage distribution lists, and set up various mailbox preferences.
There are six uOne Administration/PMA .ini files that need to be configured. These files include:
Before you start uOne Administration/PMA, ensure that the following tasks have been completed.
You can install the uOne Administration application on any Solaris HTTP Server. In large configurations, it is recommended that you install it on a standalone HTTP Server with at least one backup server for standby. To switch to the standby server, a DNS administrator would switch the HTTP name to the second box and the .ini files would have to be copied to the new system.
When uOne Administration is installed, the .ini files are placed in the MSGdata/Samples directory. The installer must copy the files to the MSGdata directory and then edit them appropriately.
uOne Administration and PMA are first set up during the initial configuration of your uOne system with the Quick Configuration tool. The uOne Administration/PMA configuration files may be edited at any time, if necessary.
To edit the schemaConfig.ini, follow these steps:
Step 2 Login as spmaster.
Step 3 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata.
Step 4 Change the parameters as desired. (See the parameters listed in Table 2-1. Defaults are used for schemaConfig.ini parameters not listed in this table.)
| Parameter | Description | Valid Values |
|---|---|---|
[lastLDAPHostAccessed] | The current directory server label. | Should not be edited. |
host=<LDAP Server Address> | The domain name of the current directory server. | A valid domain name. |
[<LDAP Hostname>] | A directory server information section label. | A valid domain name. At least one directory server information section must match the directory server stated in the [lastLDAPHostAccessed] section. |
port=<LDAP Server Port Number> | The port on which the slapd (LDAP daemon) is running. | Default=389 |
rootPasswd=<Root Password> | The password of the root DN. | Must be the same as the password that was entered when the directory server was configured. Default=N/A |
rootDN=<Root DN> | The DN of the authority to bind to the directory and to have sufficient privileges to perform all the operations required for the server. | Typically, cn=Directory Manager Must be the same as the root DN that was entered when the directory server was configured. |
searchBase=<Search Base> | The DN of the root node of the subscriber directory tree managed by the server. | For example, o=Organization Default=N/A |
Indicates the DN of the root of the tree that contains authority name entries. | For example, ou=Root, o=Organization Default=N/A | |
Indicates the DN of the root of the tree that contains mail server entries. | For example, o=NetscapeRoot Default=N/A |
When an administrator set up a subscriber account, the administrator can assign a preferred language for speaking prompts and e-mail over the telephone. Administrators use the Preferred Language field on the Add a Subscriber and Modify a Subscriber pages to assign a preferred language. This field displays in a drop-down list box with the language options. Typically, these options in the languageData.ini file are set up during the initial configuration of the system. The languageData.ini may be edited, if necessary.
Step 2 Login as spmaster.
Step 3 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata.
Step 4 Edit languageData.ini files and set the following parameters (Table 2-2).
[preferredlanguage]
numOfOptions=<XX>
option<YY>=<value>,< location>
defaultValue=<value>
| [preferredlanguage] numOfOptions=3 option1=eng, English option2=fre, French option3=spa, Spanish defaultValue=eng |
| Parameter | Description | Valid Values |
|---|---|---|
The options list label. | Should not be edited. | |
NumOfOptions=<XX> | The number of language options that will be displayed in the options list. Ensure that this value matches the number of listed language options. | XXthe number of languages to be displayed. |
option<XX>=<Value>, <text string> | <XX> indicates the order in which the options will appear in the drop-down list box for the Preferred Language field on the uOne Administration screen. <Value> is the data that is going to be stored in the LDAP database. <Text string> is the name of the language that will appear in the drop-down list box for the Preferred Language field. | XXA number. Must be no gaps in the numbering of options. Must start with the number 1 and increase. Valuealphanumeric characters. Do not use commas in the value. This value must conform to the ISO639 Standard and entries with this language must be created in various UM agent tab files. Text stringalphanumeric characters. Do not use commas in the name. |
DefaultValue=<Value> | The <Value> of the option to be used for the default. This field can be edited, but should not be removed. | A <Value> listed in this file. |
To set up logging for uOne Administration/PMA, you perform the following tasks:
All uOne Administration/PMA log messages are written to the umsa_pma.log file in the home2/spmaster/ADMIN/logs directory.
To turn on uOne Administration/PMA logging, follow these steps:
Step 2 Login as spmaster.
Step 3 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata.
Step 4 Edit schemaConfig.ini file and set the following attribute to yes.
[FeatureSet]
Logging=yes
Step 2 Login as spmaster.
Step 3 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata.
Step 4 Edit loggingData.ini files and set up your logging choices (Table 2-3). Figure 2-2 shows a sample loggingData.ini file.
![]() |
Note You must add these parameters for uOne Administration/PMA logging to work. |
| [logging] billing=yes informational=yes logheader=yes [informational] badlogincount=yes mailquota=yes |
| Parameter | Description | Valid Values |
|---|---|---|
[logging] | A section label. This section determines which features are enabled or disabled for logging. | Should not be edited. |
billing | Determines whether billing log messages are written to the umsa_pma.log file. | yes/no Default=no |
informational | Determines whether informational log messages are written to the umsa_pma.log file. | yes/no Default= no |
logheader | Determines whether log headers are prepended to the log messages. | yes/no Default=no |
[informational] | A section label. This section lists the LDAP attributes to be tracked and logged. | Should not be edited. |
attributes for the informational section | This is an optional section. If informational logging is set to yes and there are no entries under the [informational] section label, all LDAP attributes are tracked and logged when their values are changed | attribute=yes/no A valid attribute from the schemaData.ini or the Amteva_data.ini files. If the attribute is set to "no," that attribute is not tracked and no informational logging is written to the log file. Examples: |
To access uOne Administration, follow these steps:
Step 2 Type the URL for uOne Administration:
http://<hostname>:<port>/MSGadmin
For example, http://host1:280/MSGadmin (see Table 2-4).
The uOne Administration login screen displays (Figure 2-3).
.
| Component Value | Description | Valid Values |
|---|---|---|
Hostname | The host machine on which the uOne Administration software resides. | A valid host name. |
Port | The port on the host machine on which the uOne Administration software resides. This port is assigned in the /home2/spmaster/ADMIN/conf/http.conf file. | By convention, port 280 is used for accessing the uOne Administration. |

Step 3 Click in (or Tab to) the Email Address field and enter the e-mail address for your administrator account.
Step 4 Click in (or Tab to) the Email Password field and enter the e-mail password for your administrator account.
Step 5 Click on (or Tab to) Login.
The Welcome screen for the uOne Administration interface displays (Figure 2-4).

![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon Sep 25 20:08:51 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.