3
Administration and Provisioning

This chapter discuses how to administer Oracle9iAS Unified Messaging.

This chapter contains the following topics:

• Initial Administration Tasks

• Managing Domains

• Managing Users

• Managing Lists

• Managing Aliases

• Scanning and Removing Viruses

Initial Administration Tasks

To perform initial administration tasks for Oracle9iAS Unified Messaging, administrators must navigate to the following URL:

http://<machine name>:<port number>/um/admin/UMAdminLogin.uix

Once administrators have logged in, they can perform the following tasks:

• Create the initial domain

• Create the initial user

• Setup the Calendar server

• Change the administrator password

After performing initial administration tasks, Oracle Corporation disabling the initial administration pages to avoid inadvertent changes to the system.

Creating the Initial Domain

Perform the following steps to create the initial domain:

1. Navigate to the Administration page.

2. Enter the UMADMIN password. This is the password designated during configuration.

3. Select Domain > Domain Management > Create Domain.

4. Select the parent domain from the drop down list.

5. Enter the domain name.

6. Click Create Domain.

Creating the Initial User

Note: Oracle Corporation that the initial user created be an Oracle9iAS Unified Messaging system administrator.

Perform the following steps to create the initial user:

1. Navigate to the Administration page.

2. Select User > User Management > Create User.

3. Enter the user's ID.

4. Select the domain to which the user belongs.

5. Select the public user domain.

6. Select the mail store from the drop down list.

7. Enter the quota for the user

8. Select the user's role from the drop down list.

9. Click Create.

Setting Up the Calendar Server

Perform the following steps to set up the Calendar server:

1. On the Middle Tier machine, navigate to $ORACLE_HOME/j2ee/OC4J_UM/config/oc4j.properties file

2. Configure the following parameters:
   • calendar.cookie.domain: This is the domain name for the Calendar cookie. Cookie domains must have at least two periods, and the first character in the cookie domain must be a period. For example,.acme.com

   • calendar.mailstoredn: This is the mail store DN from the es_mail installation where es_cal is also installed. For example: a default installation is:

     calendar.mailstoredn=cn=IASDB.<fully qualified machine name of 
     infrastructure
     install>,cn=MailStores,cn=UM_SYSTEM,cn=EmailServerContainer,
     
     cn=Products,cn=oraclecontext 
     

3. Add the following line to the $ORACLE_HOME/Apache/modplsql/conf/plsql.conf file on the middle tier machine:

   Alias  /i/   '<ORACLE_HOME>/Apache/Apache/htdocs/calendar/images/' 

4. Verify if the following database access descriptor (DAD) is present on the middle tier machine, in the file $ORACLE_HOME/Apache/modplsql/conf/dads.conf:

   /pls/calapps
   

   If it is not present, a database access descriptor must be created to point to the database where Calendar server is installed. The database access descriptor name should be /pls/calapps. A database access descriptor can be created through Oracle Enterprise Manager, by navigating to the following URL:

   http://middletiersvrname:1810/emd 
   

   See Also: Oracle9i Application Server Administrator's Guide for more information on creating an authenticated DAD

5. Using Oracle Enterprise Manager, create a DAD /pls/calpalm. This is required for using Palm.

6. Navigate to the Oracle9iAS Unified Messaging administration tool, and log in as orcladmin and The URL for Oracle9iAS Unified Messaging administration tool is

   http://middletiersvrname:port/um/admin/UMAdminLogin.uix) 
   

   For each user entry, verify that the value specified for the orclMailSQLDAD attribute is calapps.

7. Navigate to the Administration Page.

8. Select Calendar > Calendar Server Setup.

9. Enter the following information in the corresponding fields:

   Parameter	Description
   Calendar Server Username	The name of the Calendar schema. The default is es_cal
   Calendar Server User Password	The password for the Calendar schema owner
   Connect String to Database	The connect string to the database where the Calendar schema is installed
   loginurl	The URL to log in to Calendar
   logouturl	The URL to log out of Calendar
   Calendar Server Locale	The default local time zone
   Calendar Server Administrator	The e-mail address of the Calendar server administrator. If there is more than one administrator, the e-mail addresses must be separated by a comma

10. Click Setup.

Changing Administrator Password

Perform the following steps to change the administrator password:

1. Navigate to the Administration Page.

2. Select Preferences> Change Password.

3. Enter the following information in the corresponding fields:
   • Old Password

   • New Password

   • Confirm Password

4. Click Submit.

Managing Domains

Using the Thin Client, administrators can perform domain management tasks, such as create domains, modify domain settings for users, and modify domain settings for lists.

To perform administration tasks for Oracle9iAS Unified Messaging, administrators must navigate to the following URL:

http://<machine name>:<port>/um/traffic_cop

Creating Domains

Perform the following steps to create domains:

1. Using the Thin Client, navigate to the Administration page.

2. Select Domain > Create Domain.

3. Select the installation name.

4. Select the parent domain from the drop down list.

5. Enter the new domain name in the corresponding field.

6. Click Submit.

Modifying Domain Settings for Users

Note: When the preferences for a domain are modified using the Thin Client administration tool, only the new entries created after the modifications contain the new set of preferences. For example, if the administrator changes the default mail quota of mail users of the oracle.com domain to 60MB, the new users created in the oracle.com domain have the new 60MB quota. The existing users in oracle.com retain the old mail quota.

Perform the following steps to modify domain preferences for users:

1. Using the Thin Client, navigate to the Administration page.

2. Select Domain > Domain Settings for Users.

3. Select the installation name from the drop down list.

4. Select the domain you want to modify.

5. Click Submit.

6. Modify the preferences you want to change.

   The following is a list of user domain parameters:

   Note: These parameter is present at the domain level preferences for users. The values set here are inherited by all new users in the domain during user creation time.

   Mail Store

   This parameter stores the DN of the mail store the user belongs to. The mail store for a user is the database that contains mail user information.

   E-mail Quota

   This parameter stores the e-mail quota of a mail user in megabytes. This parameter is present at the domain level preferences for users.

   Voice Quota

   This parameter stores the quota for the voice mail user in megabytes. This parameter is present at the domain level preferences for users.

   Number of Email Display (Web Mail)

   This parameter displays the number of message headers displayed on a single page of the Thin Client.

   Mail User Index Type

   This parameter is associated with individual users and is present at the user level in Oracle Internet Directory, enabling OracleText configuration on a per user basis.

   Domain Control ACI

   This parameter specifies the domains a user can access.

   Document Binary

   This parameter is associated with individual users and is present at the user level in Oracle Internet Directory, enabling OracleText configuration on a per user basis. This parameter enables binary attachment search for users

   Allow External Access (Web Mail)

   This is an end user parameter that enables account access from outside a firewall. This preference is only used when the client has been configured to check for this preference before enabling users to connect. Typically, the WebMail client is configured in this manner when it is facing outside the firewall. This configuration can be used in conjunction with another WebMail client that is inside the firewall and not configured to check for this preference so that a user can log in from within the firewall, enable, or disable the preference, and then subsequently log in or prevent log in from outside the firewall. For security purposes, this preference is set to disabled by default.

   View in New Window (Web Mail)

   This is an end user parameter that specifies whether the message view display should occur in a new browser window. When disabled, the application displays message views in the same window.

   Display All Headers (Web Mail)

   This is an end user parameter that specifies whether a message view displays all the headers that a message contains. If disabled, only the common headers are shown. The commom headers are:

   • From

   • To

   • CC

   • Subject

   • Date

   • Priority

7. Click Submit.

Modifying Domain Settings for Lists

Perform the following steps to modify domain preferences for lists:

1. Using the Thin Client, navigate to the Administration page.

2. Select Domain > Domain Settings for Lists.

3. Select the installation from the drop down list.

4. Select the domain you want to modify.

5. Click Submit.

6. Modify the preferences you want to change.

   The following is a list of parameters for list domains:

   Maximum Message Size

   This parameter indicates the maximum size (in bytes) of a message delivered to the list. Any message larger than this size is rejected.

   Group Admin Mail ID

   This parameter is the mail ID to which all commands to the list should be sent. The default is <listname>-admin@domain.

   Group Type

   This parameter specifies the type of the list. Possible values are announcement, discussion, edited, or moderated.

   Group Subscription Type

   This parameter denotes the type of subscription control on this list. Valid values are open, restricted, or closed.

   Group Topic

   This parameter is a single line phrase describing the topic of discussions on this list.

   Group Information Text

   This parameter is a multi-line field that owners can use to include descriptive text about the list.

   Group Auto Reconfirm

   This parameter is set to true if the owner wants all subscription requests to be reconfirmed with the user.

   Group Invite Text

   This parameter is a multi-line text sent in e-mail to users invited by a list owner to join their list.

   Group Post Type

   This parameter is defines the level of control a list owner wants on who can post messages to their list. Valid values are open or subscriber.

   Group Editor's List

   This parameter contains the list of users (mail IDs) who are the editors of the list.

   Group Moderator's List

   This parameter contains the list of users (mail IDs) who are the moderators of the list.

   Group Merge Tag

   This parameter enables a list owner to support mail merge or scheduled mail delivery, this attribute contains the tag that is used for specifying mail merge and scheduler tags.

7. Click Submit.

Managing Users

Using the Thin Client, administrators can perform user management tasks, such as create, delete, and modify e-mail, voice mail, and fax users.

To perform administration tasks for Oracle9iAS Unified Messaging, administrators must navigate to the following URL:

http://<machine name>:<port>/um/traffic_cop

Creating E-mail Users

Perform the following steps to create e-mail users:

1. Using the Thin Client, navigate to the Administration page.

2. Select User > E-mail User Management > Create User.

3. Select the domain from the drop down list.

4. Enter the user ID in the corresponding field.

5. Enter the base user domain.

6. Select the mail store from the drop down list.

7. Enter the quota value in the corresponding field.

8. Select the role from the drop down list.

9. Click Create.

Modifying E-mail User Parameters

Perform the following steps to modify e-mail user parameters:

1. Using the Thin Client, navigate to the Administration page.

2. Select User > E-mail User Management > Modify User.

3. Enter the user ID in the Search Criteria field.

4. Select the user's domain from the drop down list.

5. Click Go.

6. Modify the parameters you want to change.

7. Click Modify.

E-mail User Parameters

The following is a list of e-mail user parameters:

User ID

This parameter specifies the user ID.

Mail Store

This parameter stores the DN of the mail store the user belongs to. The mail store for a user is the database that contains mail user information.

E-mail Quota

This parameter stores the e-mail quota of a mail user in megabytes.

Auto Reply Text

This parameter stores auto reply text to be used by the user for the auto reply feature.

Auto Reply Expire

This parameter stores the auto reply expiration date in the following format:

MMDDYY:HH24:MI:SS:TZH:TZM

Forward Address

This parameter stores the e-mail addresses for the auto forward feature.

Telephone Number

This parameter is a local phone number for an Oracle9iAS Unified Messaging user. This parameter must be set because the voice mail application plays this number as part of the standard greeting when there are no greetings present. This value should be same as the telephone number in the base user entry

Mail User Index Type

This parameter is associated with individual users and is present at the user level in Oracle Internet Directory, enabling OracleText configuration on a per user basis. This parameter is present at the domain level preferences for users. The values set here are inherited by all new users in the domain during user creation time.

Document Binary

This parameter is associated with individual users and is present at the user level in Oracle Internet Directory, enabling OracleText configuration on a per user basis. This parameter is present at the domain level preferences for Users. The values set here are inherited by all new users in the domain during user creation time.

SQL DAD

This parameter stores the database access descriptor for the Calendar server.

Server Control ACI

This paramenter specifies the domains a user has access to.

Voice Quota

This parameter stores the quota for the voice mail user.

Deleting E-mail Users

Note: When a mail user is deleted, any shared folders and public shared folders owned by that user are also deleted

Perform the following steps to delete e-mail users:

1. Using the Thin Client, navigate to the Administration page.

2. Select User > E-mail User Management > Delete User.

3. Enter the search criteria

4. Select the domain to which the user belongs to.

5. Click Go.

6. Select the user you want to delete.

7. Click Delete.

Creating Voice Mail and Fax Users

Perform the following steps to create voice mail or fax users:

1. Using the Thin Client, navigate to the Administration page.

2. Select User > Voice/Fax User Management > Create User.

3. Select the installation.

4. Select the domain and click Get Mail Users.

5. Select the user.

6. Click Enable Voice/Fax.

7. Enter the following information in the corresponding fields:
   • Fax In Allowed

   • Phone Access Allowed

   • Web Access Allowed

   • Telephone Number

   • VPIM Mail

   • VPIM Text Name

     See Also: "Voice Mail and Fax Parameters" for parameter definitions

8. Click Enable.

Modifying Voice Mail and Fax Users Parameters

Perform the following steps to modify voice mail or fax user parameters.

1. Using the Thin Client, navigate to the Administration page.

2. Select User > Voice/Fax User Management > Modify User.

3. Select the group profile of the user.

4. Click Get Voice/Fax Users to select from a list of users, or click Select Voice/Fax Users to search for a specific user.

5. Select the user and click Edit.

6. Modify the parameters you want to change.

7. Click Modify.

Voice Mail and Fax Parameters

The following is a list of voice mail and fax user parameters:

Group Profile

This parameter corresponds to the domain the selected mail user belongs to. Oracle9iAS Unified Messaging supports one level sub-grouping to define local PBX settings or different language preferences. Administrators are allowed to select from pre-existing groups or enter a sub-group name to be created.

Fax In Allowed

This parameter enables a user to receive faxes into their inbox. This is for an inbound fax only.

Phone Access Allowed

This parameter enables a user to use the voice mail application to listen to their messages.

Web Access Allowed

This parameter enables a user to use the Thin Client to view their messages.

Telephone Number

This parameter is a local phone number for an Oracle9iAS Unified Messaging user. This parameter must be set because the voice mail application plays this number as part of the standard greeting when there are no greetings present. This value should be same as the telephone number in the base user entry. Whenever this value is changed, the VPIM Mail parameter must be also be changed to the same value.

VPIM Mail

This parameter is the international number for a Oracle9iAS Unified Messaging user. The voice mail application uses this number to look up users. This number is associated with a domain. Whenever this value is changed, the Telephone Number parameter must be also be changed to the same value.

VPIM Text Name

This parameter is an optional value that represents the sender's address.

Deleting Voice Mail and Fax Users

Perform the following steps to delete voice mail or fax users.

1. Using the Thin Client, navigate to the Administration page.

2. Select User > Voice/Fax User Management > Delete User.

3. Select the domain to which the user belongs.

4. Click Get Voice/Fax Users to select from a list of users, or click Select Voice/Fax Users to search for a specific user.

5. Select the user you want to delete.

6. Click Delete.

Managing Lists

Using the Thin Client, administrators can perform list management, such as create lists, modify list properties, delete lists, show lists, add and delete list members, show list members, and show all the lists a member is on.

To perform list management tasks for Oracle9iAS Unified Messaging, administrators must navigate to the following URL:

http://<machine name>:<port>/um/traffic_cop

Creating Lists

Perform the following steps to create a list:

1. Using the Thin Client, navigate to the Administration page.

2. Select List > Distribution List Management > Create a new list.

3. Select the domain from the drop down list.

4. Select SMTP or List Server from the Distribution List Type drop down list. The distribution list type defines the mailing list type.

5. Click Go.

6. Enter the following information in the corresponding fields and click Create.
   • Distribution List Name

   • Owner

   • Maximum Message Size

   • Group Topic

   • Group Invite Text

   • Group Editor's List

   • Group Moderator's List

   • Group Merge Tag

   • Group Auto Reconfirm

   • Group Type

   • Group Subscription Type

   • Group Post Type

     See Also: "List Server Parameters" for parameter definitions

Modifying Lists Properties

Perform the following steps to edit list properties:

1. Using the Thin Client, navigate to the Administration page.

2. Select List > Distribution List Management > Edit list properties.

3. Enter the list name, or enter * to display all available lists.

4. Select the domain of the list from the drop down list.

5. Select the list you want to make changes to.

6. Edit the properties you want to change.

7. Click Modify.

List Server Parameters

The following is a list of list server properties:

Distribution List Name

This parameter specifies the name of the distribution list.

Owner

This parameter specifies the person who owns or is responsible for the list.

Maximum Message Size

This parameter specifies indicates the maximum size, in bytes, of a message delivered to a list. Any message larger than this size is rejected.

Group Topic

This parameter is a single line phrase describing the topic of discussions on this list.

Group Invite Text

This parameter is a multi-line text that is sent in a mail to users invited by a list owner to join their list.

Group Editor's List

This parameter is contains the list of users (mail IDs) who are the editors of the list.

Group Moderator's List

This parameter is contains the list of users (mail IDs) who are the moderators of the list.

Group Merge Tag

This parameter enables a list owner to support mail merge or scheduled mail delivery, this attribute contains the tag used for specifying mail merge and scheduler tags.

Group Auto Reconfirm

This parameter is set to true if the owner wants all subscription requests to be reconfirmed with the user.

Group Type

This parameter specifies the type of the list. Possible values are:

• Announcement: Messages can only be sent to the list. Replies to the list are not accepted.

• Discussion: Messages can be sent and replied to on the list.

• Edited: Only certain people known as editors can post mails to the list. Messages from others are rejected.

• Moderated: Every mail posted to the list are sent to one or more persons known as moderators. The mail is delivered to the list only if at least one of the moderators approves the mail.

Group Subscription Type

This parameter denotes the type of subscription control on this list. Valid values are:

• Open: Anybody can subscribe to a list. No controls are imposed on who can subscribe

• Restricted: All subscriptions to the list need approval by the owner of the list.

• Closed: Users can subscribe to a list only if they are invited to join the list by the owner. All other subscription requests to the lists are automatically turned down.

Group Post Type

This parameter dines the level of control a list owner wants on who can post messages to their list. Valid values are open or subscriber.

• Open: Anybody can post a mail to the list.

• Subscriber: Only a subscriber to a list can post a mail to the list. Non-subscribers that send mails to the list are rejected.

Deleting Lists

Perform the following steps to delete a list:

1. Using the Thin Client, navigate to the Administration page.

2. Select List > Distribution List Management > Delete list(s).

3. Enter the list name, or enter * to display all available lists.

4. Select the domain of the list from the drop down list.

5. Click Go.

6. Select the list you want to delete.

7. Click Delete.

Adding and Deleting List Members

Perform the following to steps to add or delete list members:

1. Using the Thin Client, navigate to the Administration page.

2. Select List > Membership Management > Add/Remove Members.

3. Enter the list name, or enter * to display all available lists.

4. Select the domain of the list from the drop down list.

5. Click Go.

6. Select the list for which you want to add members.

7. Enter or remove information in the following fields:
   • Members (user) - Users on this system that are members of this list

   • Members (list) - Lists that are members of this sub-lists

   • Members (alias) - Aliases that are members of this list

   • Members (foreign) - Users foreign to this system who are members of this list

8. Click Modify.

Showing Lists

Perform the following steps to view all the lists belonging to a particular domain:

1. Using the Thin Client, navigate to the Administration page.

2. Select List > Distribution List Management > Show list(s).

3. Enter the list name, or enter * to display all available lists.

4. Select the domain of the list from the drop down list.

5. Click Go.

6. Select the list you want to view.

Showing Members

Perform the following steps to show list members:

1. Using the Thin Client, navigate to the Administration page.

2. Select List > Membership Management > Show Members.

3. Enter the list name, or enter * to display all available lists.

4. Select the domain of the list from the drop down list.

5. Click Go.

6. Select the list for which you want to view members.

Showing All the List a User is On

Perform the following steps to show all the lists a user is on:

1. Using the Thin Client, navigate to the Administration page.

2. Select List > Miscellaneous Functions > Show all memberships of a user.

3. Enter the user's name.

4. Select the user's domain from the drop down list.

5. Click Show Memberships.

Managing Aliases

Using the Thin Client, administrators can perform alias management tasks, such as create, modify, and delete aliases.

To perform administration tasks for Oracle9iAS Unified Messaging, administrators must navigate to the following URL:

http://<machine name>:<port>/um/traffic_cop

Creating a New Alias

Perform the following steps to create a new alias.

1. Using the Thin Client, navigate to the Administration page.

2. Select Alias > Alias Management > Create a new alias.

3. Select the domain from the drop down list.

4. Click Go.

5. Enter the alias name.

6. Enter the alias target.

7. Enter the description.

8. Click Create.

Editing Alias Properties

Perform the following steps to edit alias properties:

1. Using the Thin Client, navigate to the Administration page.

2. Select Alias > Alias Management > Edit alias properties.

3. Enter the search criteria.

4. Select the domain from the drop down list.

5. Click Go.

6. Select the alias you want to modify.

7. Click Modify.

8. Modify the properties you want to change.

9. Click Modify.

Deleting Aliases

Perform the following steps to delete aliases:

1. Using the Thin Client, navigate to the Administration page.

2. Select Alias > Alias Management >Delete alias(es).

3. Enter the search criteria.

4. Select the domain from the drop down list.

5. Click Go.

6. Select the alias you want to modify.

7. Click Delete.

Scanning and Removing Viruses

E-mail viruses typically have the form of an executable program as an e-mail attachment. The program gets executed on the client machine when the attachment is opened by an unsuspecting user, causing various forms of damage to the computer or the network. Oracle9iAS Unified Messaging server contains a PL/SQL utility package MAIL_AV that can scan and remove email viruses. To use this package, one simply writes a SQLPLUS script that uses this package or execute procedures in this package directly from SQLPLUS.

MAIL_AV package has three types of virus message identification methods. One identifies a message by either the subject, existence of an attachment with a certain name, or by the sender. Once messages with an attached virus are identified, the messages are moved to a designated folder away from their recipients. An administrator can manually examine the messages in the designated folder and remove them using any mail client. In cases where messages are wrongly identified as a virus, the MAIL_AV package provides functions to restore the message back to the original recipient's folder.

Because MAIL_AV has the ability to remove messages from regular users, it is considered a privileged package. Only sessions logged on as es_mail database user can execute this package.

Usage Examples

The following are summaries and usage examples for the procedures in the MAIL_AV package:

Quarantine

The quarantine procedure has the following syntax:

PROCEDURE quarantine (p_endday IN DATE,
                      p_dayrange IN NUMBER,
                      p_attribute IN NUMBER,
                      p_pattern IN VARCHAR2,
                      p_folder IN VARCHAR2);

The quarantine procedure identifies virus messages using a given pattern and moves them to a designated folder. The caller of the procedure must have write authorization to the folder. Authentication is done by using MAIL_SESSION package.

See Also: Oracle9iAS Unified Messaging Application Developer's Guide for more information

Parameters p_endday and p_dayrange can used to narrow down the virus search to within certain time frame. Parameter p_attribute takes one of the following three values:

MAIL_AV.ATTR_SUBJECT 
MAIL_AV.ATTR_ATTACHMENT 
MAIL_AV.ATTR_SENDER

Parameter p_pattern is the identifying string for the virus. Parameter p_folder is the designated folder name to which virus-infected messages are moved.

Declare

The following example logs in as user SYSADMIN, and scans the whole mail server for messages with an attachment name containing.exe within the last seven days, and moves them to the /infected folder.

  sessionid number;
begin
  mail_session.login('sysadmin', <password>, <ldaphost>, sessionid);
    mail_av.quarantine(sysdate, 7, mail_av.attr_attachment, '.exe', 
'/infected');
end;
/

Restore

There are two procedures to restore messages already quarantined back to their original folders:

PROCEDURE restore (p_messageid IN NUMBER);
PROCEDURE restoreall;

The restore procedure takes a given message ID and restore it back to its original folder. If the message ID does not exist, the procedure does nothing. The restoreall procedure restores all messages quarantined regardless which designated folders are used to store the messages. These procedures are useful when a message is wrongly identified as a virus message and must be restored back to its recipients.