8 Installing and Configuring Oracle Voicemail & Fax

This chapter discusses and explains how to install the Oracle Voicemail & Fax system.

This chapter contains the following topics:

• Preinstallation Checklist

• Installation Requirements

• Installing Oracle Voicemail & Fax Telephony Server

• Running the Oracle Voicemail & Fax Configuration Assistant on the Middle Tier

• Adding an Oracle Voicemail & Fax Telephony Server

• Adding an Additional Information Storage Database to Oracle Collaboration Suite

Preinstallation Checklist

This section describes preinstallation tasks that must be performed prior to installing Oracle Voicemail & Fax.

Perform the following tasks prior to installing Oracle Voicemail & Fax:

1. Modify the Windows Service named CT Media or Intel NetMerge CC Server so that it runs under the context of the user performing the installation. The user performing the installation should be in the CTMUsers group.

2. Restart the CT Media or NetMerge server and bring it up to level 5 before installation.

Installation Requirements

Installation of Oracle Voicemail & Fax consists of two tasks:

• Installing the Oracle Voicemail & Fax Telephony Server on a Windows 2000 system

• Running the Oracle Voicemail & Fax Configuration Assistant on the middle tier

Prior to installing Oracle Voicemail & Fax you must have the following:

• Oracle Collaboration Suite with Oracle Email: Installed, configured, and running on a system other than that where Oracle Voicemail & Fax is installed

• Windows 2000 Resource Kit

• CT Media Server or Intel NetMerge Converged Communication Server

• S.410 SDK V1.0 for CT Media 2.1

Installing Oracle Voicemail & Fax Telephony Server

Installing the Oracle Voicemail & Fax Telephony Server is a two part process. The first part of the process installs the Oracle9iAS core and the second part installs the Oracle Voicemail & Fax code.

Notes: Both parts of the telephony server installation must be performed using a user name that belongs to the CTMUser User Group and Administrators Group. The running user name of the CT Media or NetMerge servers must be the same as the user name running the installation. To change the running user name, select Start > Settings > Control Panel > Adminstrative Tools > Services. Right click the service. Choose Properties. Click the Log On tab and change the Log on as option.

This section contains these topics:

• Installing the Oracle9iAS Core

• Installing the Oracle Voicemail & Fax Code

Installing the Oracle9iAS Core

To install the Oracle9iAS core:

1. Insert the Oracle Voicemail & Fax Release 2 (9.0.4.1.0) for Microsoft Windows 2000 (32-bit) CD-ROM.

2. Run install.bat located in the \install\win32 directory to display the Welcome screen of the Oracle Universal Installer.

3. Click Next to display the File Locations screen. In the Destination section, enter the name of an Oracle home (or select an existing Oracle home from the drop-down list) in the Name field.

4. Enter the path to the Oracle home in the Path field.

   You can also click Browse to locate the Oracle home path.

5. Click Next to display the Oracle Internet Directory screen.

6. Enter a user name and a password. The default user name is cn=orcladmin.

7. Click Next to display the Create Instance Name screen.

8. Enter a name for the Oracle9iAS instance in the Instance Name field.

9. Enter the ias_admin password for the current host in the ias_admin Password field.

10. Click Next to display the Summary screen.

11. Click Install to display the End of Installation screen.

12. Click Exit to display the Exit screen.

13. Select Yes, restart the system now and click OK to restart the system.

    After the system restarts, the second part of the installation automatically begins.

Installing the Oracle Voicemail & Fax Code

This part of the installation does the following:

• All of the Oracle Voicemail & Fax files are copied to the telephony server

• Prompts are added to the CTMedia Container

• The sc_vsto.cfg file is created to configure Oracle Voicemail & Fax Conatiner

• The rmid, rmiregistry, and UMProcessMgrService processes are installed

• The Oracle Voicemail & Fax Media Services Profile is loaded into the CT Media Server. Changes are made to SCR_AppProfile, SCR_ASIMap, and SCR_RoutingRules.

1. Upon completion of the system restart, the Mailstore Selection screen displays.

2. Select an information store from the Mailstore Selection drop-down list.

3. If you select an information store other than <none> from the Mailstore Selection drop-down list, you will be asked to provide a UM password. The default is welcome.

   Otherwise the Password for DB User 'um' field is inactive.

4. Click Next to display the Summary screen.

5. Click Install to display the End of Installation screen.

6. Click Exit.

   Proceed to the next section to continue the installation.

Running the Oracle Voicemail & Fax Configuration Assistant on the Middle Tier

Note: If you are only adding an additional telephony server to an existing installation of Oracle Collaboration Suite, proceed to "Adding an Oracle Voicemail & Fax Telephony Server".

The Oracle Voicemail & Fax configuration assistant performs the following tasks:

• Loads Oracle Voicemail & Fax middle tier process entries into Oracle Internet Directory

• Loads all Oracle Voicemail & Fax entries into targets.xml, consoleConfig.xml for integration with EMD

• Loads the UM schema into the information storage database

1. Run uminfra_install.bat on the middle tier system, located in the %ORACLE_HOME%\um\uminfra directory to display the Mailstore Selection screen of the configuration assistant.

2. Select an information store from the Mailstore Selection drop-down list.

   If you select an information store other than <none> from the Mailstore Selection drop-down list, you will be asked to provide SYSTEM, ES_MAIL, and UM passwords. The default values are as follows:

   • SYSTEM: manager

   • ES_MAIL: es

   • UM: welcome

   
   

   Note: If you created a new SYSTEM password during the creation of the information storage database, and new ES_MAIL and UM passwords during the Oracle Email installation, you must use these new passwords.

   
   

3. Click Next and select the server where Oracle Voicemail & Fax is installed to be associated with the middle tier.

4. Click Next to display the End of Installation screen.

5. Click Exit.

6. Restart the Oracle Voicemail & Fax Windows 2000 telephony server upon completion of the configuration assistant.

See Also: Oracle Voicemail & Fax Administrator's Guide for further configuration information

This concludes the installation of Oracle Voicemail & Fax. The last two sections of this chapter apply only if you are adding an additional voice mail server or information store.

Adding an Oracle Voicemail & Fax Telephony Server

To add additional telephony servers:

1. Follow the procedures outlined in "Installing Oracle Voicemail & Fax Telephony Server".

2. Execute %ORACLE_HOME%\um\uminfra\uminfra_install.bat on the middle tier.

3. Select None for the information store.

4. Select the voice mail server you want to be managed by this Oracle Enterprise Manager Daemon server.

Adding an Additional Information Storage Database to Oracle Collaboration Suite

Any time an additional information storage database is added to the Oracle Collaboration Suite system, you must rerun the Oracle Voicemail & Fax configuration assistant and update the sc_vsto.cfg file.

Rerunning the Oracle Voicemail & Fax configuration assistant does the following:

• Creates the UM schema on the information storage database

• Creates the Advanced Queue Message Waiting Indicator process

To set up the new information storage database for Oracle Voicemail & Fax:

1. Execute %ORACLE_HOME%\um\uminfra\uminfra_install.bat on the middle tier.

2. Select the new information storage database and supply the necessary passwords.

3. Select None for the voice mail server.

4. On each telephony server the sc_vsto.cfg file must be updated with the new information storage information.

   Example 8-1 shows the sc_vsto.cfg file before it is updated.

   Example 8-1 sc_vsto.cfg File

   {
    Container_ORCL_VPIM: {
       Container_DLGC_DLLName: "orclcont.dll"
       Container_DLGC_Initialize: "StorageInitialize"
       Container_DLGC_Shutdown: "StorageShutdown"
       Container_DLGC_Parameters: {
         Container_ORCL_ESNode:"v2store.v2store"
         Container_ORCL_DBSet: (
             {
                 Container_ORCL_DBName: "v2store.v2store"
                 Container_ORCL_PoolMax: 10
                 Container_ORCL_PoolMin: 1
                 Container_ORCL_DBUserid: "um"
                 Container_ORCL_DBPassword:
   "0495022e8cbe976b4e9156aeff710fdbe6dfeac30dff5ddd81"
                 Container_ORCL_DBConnect: 
   "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=thintest.us.oracle.com)
   (PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=v2store.v2store)))"
             }
         )
         }
    }
   
      Container_DLGC_FileStrategy: {
         Container_DLGC_DLLName: "std_sto.dll"
         Container_DLGC_Initialize: "StorageInitialize"
         Container_DLGC_Shutdown: "StorageShutdown"
         Container_DLGC_Parameters: {      }
      }
   }
   
   

   Example 8-2 shows an updated sc_vsto.cfg file.

   Example 8-2 Updated sc_vsto.cfg File

   {
    Container_ORCL_VPIM: {
       Container_DLGC_DLLName: "orclcont.dll"
       Container_DLGC_Initialize: "StorageInitialize"
       Container_DLGC_Shutdown: "StorageShutdown"
       Container_DLGC_Parameters: {
         Container_ORCL_ESNode:"v2store.v2store"
         Container_ORCL_DBSet: (
             {
                 Container_ORCL_DBName: "v2store.v2store"
                 Container_ORCL_PoolMax: 10
                 Container_ORCL_PoolMin: 1
                 Container_ORCL_DBUserid: "um"
                 Container_ORCL_DBPassword:
   "0495022e8cbe976b4e9156aeff710fdbe6dfeac30dff5ddd81"
                 Container_ORCL_DBConnect: 
   "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=database_host_name)
   (PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=v2store.v2store)))"
             }
             {
                 Container_ORCL_DBName: "2nd_information_storage_database_name"
                 Container_ORCL_PoolMax: 10
                 Container_ORCL_PoolMin: 1
                 Container_ORCL_DBUserid: "um"
                 Container_ORCL_DBPassword:
   "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
                 Container_ORCL_DBConnect: 
   "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=2nd_database_host_name)
   (PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=2nd_information_storage_database_
   name)))"
             }
         )
         }
    }
   
      Container_DLGC_FileStrategy: {
         Container_DLGC_DLLName: "std_sto.dll"
         Container_DLGC_Initialize: "StorageInitialize"
         Container_DLGC_Shutdown: "StorageShutdown"
         Container_DLGC_Parameters: {      }
      }
   }
   
   

   In the preceding example, the parameters are defined as follows:

   • ORCL_DBName: The global database name, which can be retrieved from Oracle Internet Directory

   • PoolMax, PoolMin: The values depend on the system. The default values are 10 and 1

   • DBUserid: Always um

   • DBPassword: An encrypted string of the um user password. Obtain this password by executing the following program:

     %ORACLE_HOME%\um\scripts\encrypt.exe um_password
     
     

     The program will output an encrypted string, which the user can copy and paste into the file.

   • DBConnect: The connect string of the new database, which can be retrieved from LDAP