2
Getting Started

This chapter discusses the administration tools and explains how to configure, start up, shut down, and reinitialize the Oracle9iAS Unified Messaging system.

This chapter contains the following topics:

• Pre-Configuration Checklist

• Configuring Oracle9iAS Unified Messaging

• Using the Administration Tools

• Starting Up, Shutting Down, and Reinitializing Oracle9iAS Unified Messaging

Pre-Configuration Checklist

This section describes pre-configuration procedures that must be done prior to confuguring Oracle9iAS Unified Messaging.

This section contains the following topics:

• Applying the Oracle9iAS Interoperability Patch

• Applying the NetCA and DBCA Bug Fix Patches

• Verifying and Starting the Oracle9iAS Infrastructure and Application Servers

• Registering the Database with Oracle Internet Directory

• Installing the umbackend.tar File

• Installing the install_infra.sql File

• Creating Calendar and Mail Store Tablespaces and Schema

Applying the Oracle9iAS Interoperability Patch

Prior to configuring Oracle9iAS Unified Messaging, customers must apply the Oracle9iAS Interoperability Patch, Release 2, for 9.0.2 CD that is specific to the platform you are using.

Note: It is important to read the Oracle9iAS Interoperability Patch README prior to applying the patch.

Applying the Patch on the Oracle9iAS Infrastructure Database

If you are using the database that comes with the Oracle9iAS infrastructure, perform the following steps:

1. Install the Oracle9iAS infrastructure.

2. Install the Oracle9iAS application server with the Oracle9iAS Unified Messaging installation type.

3. Apply the Oracle9iAS Interoperability patch on the Oracle9iAS infrastructure and application server.

Applying the Patch on a Custom Database

If you are using a custom database and not the database that comes with the Oracle9iAS infrastructure, perform the following steps:

1. Install the Oracle9iAS infrastructure.

2. Install the Oracle9iAS application server with the Oracle9iAS Unified Messaging installation type.

3. Install the Oracle9i database.

4. Apply the Oracle9iAS Interoperability patch on the Oracle9iAS infrastructure and application server.

Applying the NetCA and DBCA Bug Fix Patches

Note: If you are using an Oracle 9.2 database, you need not apply the NetCA and DBCA bug fix patches.

If you installed an Oracle 9.0.1.3 database or higher, you must apply the NetCA and DBCA bug fix patches to create a database service name and register the database with Oracle Internet Directory.

Perform the following steps to apply the NetCA and DBCA bug fix patches:

1. Install the NetCA bug fix patch 2224723 on the database.

2. Install the DBCA bug fix patch 2227356 on the database.

Verifying and Starting the Oracle9iAS Infrastructure and Application Servers

Verify that the infrastructure and application servers are running:

% opmnctl startall

Registering the Database with Oracle Internet Directory

An Oracle9i database is required to install the mail store. Before a database can be configured as a mail store, it must be registered with the Oracle Internet Directory infrastructure. If the database is not already registered with the Oracle Internet Directory, it can be registered using the Oracle database configuration assistant . Once the database is registered with Oracle Internet Directory, at a later point any changes to the connect identifier can be made using Oracle Net Manager.

Installing the umbackend.tar File

Note: If the mail store database is on a different platform than the application server, the umbackend.tar file must be downloaded from the Oracle Technology Network website.

Perform the following steps to install the umbackend.tar file:

1. Copy the umbackend.tar file from $ORACLE_HOME/oes/bin directory on the application server to the $ORACLE_HOME on the mail store database. If the mail store is located on another system, the umbackend.tar file must be transferred from the application server to the mail store database as the database owner.

2. Untar the umbackend.tar file:

   tar xvf umbackend.tar
   
   

3. Run the following commands to run the installer:

   cd backend/disk1
   ./runInstaller
   
   

4. Follow the screen prompts to complete the Oracle9iAS Unified Messaging backend installation.

Installing the install_infra.sql File

Administrators must run <mailstore_database_oracle_home/
oes/install/sql/install_infra.sql on the mailstore database machine after installing the umbackend.tar file, if the Oracle9iAS Unified Messaging server middle tier and backend database are on different platforms. For example, the middle tier is on Solaris and the mail store database is on NT.

Creating Calendar and Mail Store Tablespaces and Schema

The Oracle9iAS Unified Messaging configuration wizard creates tablespaces and schema for Calendar and mail store. If you want to customize tablespace storage parameters or data files, you can create them before running configuration wizard.

For the name of mail store tablespaces and their default storage parameters go to $ORACLE_HOME/oes/install/sql/tblspc.sql directory.

Note: If you pre-create tablespaces, the Oracle9iAS Unified Messaging configuration wizard log shows some errors indicating tablespace creation failed. These errors can be ignored.

Configuring Oracle9iAS Unified Messaging

See Also: Oracle9iAS Unified Messaging Telephony Services Installation Notes for Windows 2000 for more information on configuring telephony and wireless

This section describes how to configure the Oracle9iAS Unified Messaging mail store, middle tier, and Calendar servers.

This section contains the following topics:

• Configuring the Oracle9iAS Unified Messaging Mail Store

• Configuring the Oracle9iAS Unified Messaging Middle Tier

• Configuring the Oracle9iAS Unified Messaging Calendar Store

Configuring the Oracle9iAS Unified Messaging Mail Store

Configuring the mail store database does the following:

• Creates tablespaces for the mail schema

• Creates mail tables and indexes

• Loads mail related PL/SQL packages

• Loads mail related stored java procedures

• Configures the mail store with Oracle Internet Directory

To configure the Oracle9iAS Unified Messaging mail store, perform the following steps on the middle tier server:

1. Set the database init.ora parameters on the mail store database to the following values:

   processes=150 or higher
   open_cursors=300 or higher
   dml_locks=200 or higher
   shared_pool_size=32000000 or higher
   java_pool_size=40000000 or higher
   
   

2. Run the umconfig.sh script located on the application server:
   • For UNIX, enter the following command:

     $ORACLE_HOME/oes/bin/umconfig.sh
     

   • For Windows, enter the following command:

     %ORACLE_HOME%\oes\bin\umconfig.bat
     

   The Unified Messaging Configuration screen appears.

3. Select Mail Store.

4. Click Next. The Mail Store Database Configuration screen is displayed.

5. Enter the following information in the corresponding fields:

   Field	Description
   Database Hostname	The name of the machine on which the database is located
   SID	The system identifier of the mail store
   Port Number	The port number on which the listener is listening
   System Password	The system password for the host database
   CTXSYS Password	The password for the OracleText account

   Note : To use OracleText with the Oracle9i database, the ctxsys account must be unlocked. Installation of OracleText requires the ctxsys account to be present.

6. Click Next. The ES_Mail password screen is displayed.

7. Enter the ES_MAIL password and confirm it. If an ES_MAIL password is not entered, the default is es.

   Note: The mail store schema is owned by the ES_MAIL database user.

8. Click Next. The UMADMIN password screen is displayed.

   Note: UMADMIN is an administrator account created in the Oracle Internet Directory server during the application server installation of Oracle9iAS Unified Messaging. It account owns specific Oracle9iAS Unified Messaging entries in the directory. After installation, administrators should log in to the administration tool using the UMADMIN account and create an initial Oracle9iAS Unified Messaging domain and user. Thereafter, they can delegate system and domain administration responsibilities to other users.

9. Enter the UMADMIN password and confirm it. If a password is not entered, the default value welcome is stored in Oracle Internet Directory and the database as the UMADMIN password.

10. Click Next. The Configuration Tools screen is displayed and the mail store configuration begins.

Once the mail store configuration is complete, the End of Installation screen is displayed.

Log files for umconfig.sh are located in the following directory:

$ORACLE_HOME/oes/log/

Manually Configuring the Oracle9iAS Unified Messaging Mail Store

Note: The manual steps described below are an alternative to running the mailstore.sh script through the user interface.

Enter the following command to manually run the Oracle9iAS Unified Messaging mail store configuration scripts with parameters:

• For UNIX:

  $ORACLE_HOME/oes/bin/install_mailstore.sh <connect_str> <sys_passwd>
  <system_passwd> <ctxsys_passwd> <SID> <host_name> <port_number>
  <INSTALLATION_NAME> <ORACLE_HOME> <es_mail_passwd> <umadmin_passwd> <oid_flag>
  
  

• For Windows:

  %ORACLE_HOME%\oes\bin\install_mailstore.bat <connect_str> <sys_passwd>
  <system_passwd> <ctxsys_passwd> <SID> <host_name> <port_number>
  <INSTALLATION_NAME> <ORACLE_HOME> <es_mail_passwd> <umadmin_passwd> <oid_flag>
  

  Note: The default INSTALLATION_NAME is UM_SYSTEM.

Configuring the Oracle9iAS Unified Messaging Middle Tier

• Configuring the middle tier does the following:

• Configures middletier with Oracle Internet Directory

• Configures middletier with mailstore

• Creates Oracle9iAS Unified Messaging server instances

To configure the Oracle9iAS Unified Messaging middle tier servers, perform the following steps:

1. Run the umconfig.sh script located on the application server:
   • For UNIX, enter the following command:

     $ORACLE_HOME/oes/bin/umconfig.sh
     
     

   • For Windows, enter the following command:

     %ORACLE_HOME%\oes\bin\umconfig.bat
     
     

   The Unified Messaging Configuration screen is displayed.

2. Select Middle Tier.

3. Click Next. The Middle Tier Configuration screen is displayed.

4. Enter the following information in the corresponding fields:

   Field	Description
   Database Hostname	The name of the machine on which the database is located
   SID	The system identifier of the database
   Port Number	The port number on which the listener is listening
   System Password	The system password of the database specified above

5. Click Next. The Configuration Tools screen is displayed and the middle tier configuration begins.

Once the middle tier configuration is complete, the End of Installation screen is displayed.

Log files for umconfig.sh are located in the following directory:

UNIX:

$ORACLE_HOME/oes/log/

Windows:

% ORACLE_HOME\oes\log\ 

Manually Configuring the Oracle9iAS Unified Messaging Middle Tier

Note: The manual steps described below are an alternative to running the middletier.sh script through the user interface.

Use the following command to run the Oracle9iAS Unified Messaging Middle Tier configuration scripts with parameters:

• For UNIX:

  $ORACLE_HOME/oes/bin/install_middletier.sh <connect_str> <system_passwd>
  <INSTALLATION_NAME> <ORACLE_HOME> <umadmin_passwd> <oid_flag>
  
  

• For Windows:

  %ORACLE_HOME%\oes\bin\install_middletier.bat <connect_str> <system_passwd>
  <INSTALLATION_NAME> <ORACLE_HOME> <umadmin_passwd> <oid_flag>
  

Configuring the Oracle9iAS Unified Messaging Calendar Store

Note: An Oracle9i database is required to install the Calendar store.

Configuring the Calendar does the following:

• Creates tablespaces for the Calendar schema

• Creates Calendar tables and indexes

• Loads Calendar related PL/SQL packages

• Loads Calendar related stored java procedures

• Configures Calendar store with Oracle Internet Directory

To configure the Oracle9iAS Unified Messaging Calendar store, perform the following steps:

1. Run the umconfig.sh script located on the application server:
   • For UNIX, enter the following command:

     $ORACLE_HOME/oes/bin/umconfig.sh
     
     

   • For Windows, enter the following command:

     %ORACLE_HOME%\oes\bin\umconfig.bat
     
     

   The Unified Messaging Configuration screen is displayed.

2. Select Calendar.

3. Click Next. The Calendar Configuration screen is displayed.

   Note: For a given deployment, there can be one or more mail stores, but only one Calendar store. Calendar and mail stores can be on the same or on different databases. Before a Calendar store is configured, you must configure that node as a mail store. However, you do not have to create users' mail accounts on that database.

4. Enter the following information in the corresponding fields:

   Field	Description
   Database Hostname	The name of the machine on which the database is located
   SID	The system identifier of the Calendar store
   Port Number	The port number on which the listener is listening
   System Password	The system password of the database specified above
   ES_MAIL Password	The ES_MAIL schema owner password. If an ES_MAIL password is not entered, it defaults to es

5. Click Next. The ES_CAL Password screen is displayed.

6. Enter the ES_CAL password and confirm it. If an ES_CAL password is not entered, the default is cal.

   Note: The Calendar store schema is owned by the ES_CAL database user.

7. Click Next. The Configuration Tools screen is displayed and the Calendar configuration begins.

Once the Calendar configuration is complete, the End of Installation screen is displayed.

The Log files for umconfig.sh are located in the following directory:

$ORACLE_HOME/oes/log/

Manually Configuring the Oracle9iAS Unified Messaging Calendar

Note: The manual steps described below are an alternative to running the cal_flow_install.sh through the user interface.

Use the following command to run the Oracle9iAS Unified Messaging Calendar configuration scripts with parameters:

• For UNIX:

  $ORACLE_HOME/oes/calserver/cal_flow_install.sh <Net9_Connect_String>
  <Sys_Passwd> <Flow_User> <Flow_User_Passwd> <App_User> <App_User_Passwd>
  <Es_Mail_Passwd> <Img_Prefix> <Def_Tblspace> <Index_Tblspace>
  <umadmin_passwd> <oid_flag>
  
  

• For Windows:

  %ORACLE_HOME%\oes\calserver\cal_flow_install.bat <Net9_Connect_String>
  <Sys_Passwd> <Flow_User> <Flow_User_Passwd> <App_User> <App_User_Passwd>
  <Es_Mail_Passwd> <Img_Prefix> <Def_Tblspace> <Index_Tblspace>
  <umadmin_passwd> <oid_flag>
  

  Note: If oid_flag is set to 0, the createdefaults.sh script is invoked to create the domain in Oracle Internet Directory.

Using the Administration Tools

This section describes the different administration tools used to administer the Oracle9iAS Unified Messaging system.

This section contains the following topics:

• Oracle Enterprise Manager

• Thin Client

Oracle Enterprise Manager

See Also: Oracle9i Application Server Administrator's Guide for more information about Oracle Enterprise Manager

Oracle Enterprise Manager is a Web-based tool that enables administrators to perform some of the management tasks for the Oracle9i database and Oracle9i Application Server. The Oracle Enterprise Manager can be used to administer Oracle9iAS Unified Messaging service processes. Through Oracle Enterprise Manager, administrators can perform the following tasks on Oracle9iAS Unified Messaging system:

• startup

• shutdown

• Reinitialize

• Modify default parameters

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

http://<machine name>:1810

Thin Client

See Also: Chapter 3, "Administration and Provisioning" for more information on domain and user provisioning, and Calendar and resource administration

Using the Oracle9iAS Unified Messaging Thin Client, administrators can perform domain and user provisioning tasks, and administer the Calendar and resource scheduler. Through the Oracle9iAS Unified Messaging Thin Client, administrators can do the following:

• Create and modify domain settings for users and distribution lists

• Create, delete, modify, and view e-mail, fax users, voice mail users, and distribution lists

• Add and delete members to and from distribution lists

• View all the distribution lists a specific user is on

• Create, delete, modify, and view server-side filters

• Create, delete, and modify lists

• Administer the Calendar and resource scheduler

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

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

Starting Up, Shutting Down, and Reinitializing Oracle9iAS Unified Messaging

This section explains how to start, stop, and reinitialize the Oracle9iAS Unified Messaging system.

This section contains the following topics:

• Verifying and Starting the Listener for the Mail Store and Calendar Store

• Verifying and Starting the Listener for the Middle Tier

• Starting the Oracle9iAS Unified Messaging System

• Stopping the Oracle9iAS Unified Messaging System

• Reinitializing the Oracle9iAS Unified Messaging System

• Creating a Public User

  See Also: Chapter 4, "Servers and Processes", for more information on how to start up, shut down, and reinitialize individual processes

Verifying and Starting the Listener for the Mail Store and Calendar Store

The Oracle Net Listener must be running on the mail store and Calendar store database so that the system can establish database connections from the Oracle9iAS Unified Messaging system and clients.

To verify that the listener is running, enter the following:

% lsnrctl status listener_es

If the computer returns a message that contains the line no listener, then the listener must be started.

To start the listener, enter the following:

% lsnrctl start listener_es

Verifying and Starting the Listener for the Middle Tier

Verify that the listener is running, by entering the following:

% lsnrctl status listener_es

If the computer returns a message that contains the line no listener, then the listener needs to be started.

To start the listener, perform the following steps:

1. Configure the listener with protocol addresses and other configuration parameters, using Oracle Net Configuration Assistant or Oracle Net Manager.

   See Also: Chapter 12, "Configuring and Administering the Listener," of the Oracle9i Net Services Administrator's Guide

2. Log in as superuser (root) and set file ownership and access permissions for the listener executable (tnslsnr) and its dependent shared libraries so that these files can be modified only by the superuser. The tnslsnr is located in the $ORACLE_HOME/bin directory.

3. Verify that the permissions of the individual directories found in the path names to these files, starting with the root directory, are modified in the same way.

4. Start the listener as root.

5. At the operating system prompt, enter tnslsnr with optional command line arguments.

   tnslsnr [listener_name] [-user user] [-group group]
   
   

   where:

   listener_name	Specifies the name of the listener, as listener_es. If omitted, the default name LISTENER is used.
   -user user	Specifies the user whose privileges the listener uses when superuser (root) privileges are not needed. After performing the privileged operations, the listener gives up root privileges irreversibly.
   -group group	Specifies the group whose privileges the listener uses when superuser (root) group privileges are not needed. After performing the privileged operations, the listener gives up root group privileges irreversibly.

Starting the Oracle9iAS Unified Messaging System

Starting an Oracle9iAS Unified Messaging service starts all the processes comprising that service type, such as IMAP4 and SMTP.

Using Oracle Enterprise Manager, perform the following procedure to start an Oracle9iAS Unified Messaging system:

1. Navigate to the Oracle9i Application Server home page

2. Select Oracle9iAS Unified Messaging.

3. Click Start.

Stopping the Oracle9iAS Unified Messaging System

Stopping an Oracle9iAS Unified Messaging system sends a request to the operating system to shut down all of the Oracle9iAS Unified Messaging processes. One reason an administrator would want to stop the Oracle9iAS Unified Messaging system is to perform maintenance on the system, such as upgrading the server hardware or software. It is not possible for the processes to be running while certain kinds of upgrades are performed.

Using Oracle Enterprise Manager, perform the following procedure to stop an Oracle9iAS Unified Messaging system:

1. Navigate to the Oracle9i Application Server home page.

2. Select Oracle9iAS Unified Messaging.

3. Click Stop.

Reinitializing the Oracle9iAS Unified Messaging System

Reinitializing an Oracle9iAS Unified Messaging process informs the operating system to reload its operational settings from the Oracle Internet Directory server. The process does not stop running, which means that users continue to receive uninterrupted service. Whenever a Oracle9iAS Unified Messaging process parameter is modified, it must be reinitialized to make the changes take effect.

Using Oracle Enterprise Manager, perform the following procedure to reinitialize an Oracle9iAS Unified Messaging process:

1. Navigate to the Oracle9i Application Server home page

2. Select Oracle9iAS Unified Messaging.

3. Click Reinitialize.

Creating a Public User

After configuring Oracle9iAS Unified Messaging, administrators must create a public user account through delegated administration service (DAS). This public user corresponds with the initial user that will be created through the Thin Client administration tool.

See Also: Oracle Internet Directory Administrator's Guide for more information on using DAS

Once the public user has been created, administrators can navigate to http://<machine name>:<port number>/um/admin/UMAdminLogin.uix, to create the initial domain and user.

See Also: Chapter 3, "Administration and Provisioning" for more information on creating the initial domain and user.