Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for AIX-Based Systems Part Number B12204-02 |
|
|
View PDF |
This chapter discusses and explains how to install the Oracle Voicemail & Fax system.
This chapter contains the following topics:
Running the Oracle Voicemail & Fax Configuration Assistant on the Middle Tier
Adding an Additional Information Storage Database to Oracle Collaboration Suite
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:
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.
Restart the CT Media or NetMerge server and bring it up to level 5 before installation.
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 each 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
Intel NetMerge Converged Communication Server or CT Media Server
S.410 SDK V1.0 for CT Media
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:
|
This section contains these topics:
You may do a manual install of the Oracle 9iAS Core which is described below or you have the option of doing a silent installation of the Oracle 9iAS Core. For more information, see "Silent Installation of Oracle9iAS Core" .
To install the Oracle9iAS core:
Insert the Oracle Voicemail & Fax CD into the CD-ROM drive.
Run install.bat
located in the \install\win32
directory to display the Welcome screen of the Oracle Universal Installer.
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 Name field.
Enter the path to the Oracle home in the Path field.
You can also click Browse to locate the Oracle home path.
Click Next to display the Oracle Internet Directory screen.
Enter a user name and a password. The default user name is cn=orcladmin
.
Click Next to display the Create Instance Name screen.
Enter a name for the Oracle9iAS instance in the Instance Name field.
Enter the ias_admin password for the current host in the ias_admin Password field.
Click Next to display the Summary screen.
Click Install to display the End of Installation screen.
Click Exit to display the Exit screen.
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.
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 Container
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
.
To install the Oracle Voicemail & Fax code:
Upon completion of the system restart, the Mailstore Selection screen displays.
Select an information store from the Mailstore Selection list.
If you select an information store other than <none> from the Mailstore Selection list, you will be asked to provide a UM password. The default is welcome
.
Otherwise the Password for DB User 'um' field is inactive.
Click Next to display the Summary screen.
Click Install to display the End of Installation screen.
Click Exit.
Proceed to "Oracle Voicemail & Fax Information Store Database Accounts" to complete a recommended step.
When you install Oracle Voicemail & Fax, the UM user account is automatically created. Voice mail processes use the UM account to access the information store, and the account contains the schema objects used in the delivery of message-waiting-indicator (MWI) requests. The following roles and privileges are granted to the account: CONNECT, RESOURCE, DBA, EXECUTE ON DBMS_AQ, EXECUTE ON DBMS_AQADM,
and JAVAUSERPRIV.
The default password provided during installation is welcome
.
The JAVAUSERPRIV
privilege is not required for the processes to run. Therefore, Oracle recommends removing this privilege after installation to make your system more secure.
Note: You will need to perform the following procedure for each information store. |
To revoke the JAVAUSERPRIV
privilege:
Log in as SYSTEM
.
Execute the commands:
REVOKE JAVAUSERPRIV FROM UM;
CALL DBMS_JAVA.revoke_permission('PUBLIC', 'java.net.SocketPermission', '*', 'read,write')
;
Proceed to "Running the Oracle Voicemail & Fax Configuration Assistant on the Middle Tier" to continue the installation.
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
Configures Enterprise Manager to administer Oracle Voicemail & Fax processes
Loads the UM
schema into the information storage database
Run uminfra_install.sh
on each middle tier system, located in the $ORACLE_HOME/um/uminfra
directory to display the Mailstore Selection screen of the configuration assistant.
Select an information store from the Mailstore Selection list.
If you select an information store other than <none> from the Mailstore Selection 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 newSYSTEM 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. |
Click Next and select the Oracle Voicemail & Fax Telephony Server that you want to be managed by this middle tier.
Click Next to display the End of Installation screen.
Click Exit.
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.
You can do a silent installation of the Oracle9iAS core.
To do a silent installation:
Edit the %CD_HOME%\Disk1\install\win32\ias_core_top.rsp
file. Comments in the file provide instructions on the required values.
Run the following command:
full_path
\
setup.exe -silent -response
full_path
\ias_core_top.rsp
Go to the ORACLE_HOME
\um\scripts
directory and run the findmailstores.bat
file.
Reboot the system. The second part of the installation automatically begins. See "Installing the Oracle Voicemail & Fax Code" .
To add additional telephony servers:
Follow the procedures outlined in "Installing Oracle Voicemail & Fax Telephony Server".
Execute $ORACLE_HOME/um/uminfra/uminfra_install.sh
on each middle tier.
Select None for the information store.
Select the voice mail server you want to be managed by this Oracle Enterprise Manager Daemon server.
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:
To set up the new information storage database for Oracle Voicemail & Fax:
Execute $ORACLE_HOME/um/uminfra/uminfra_install.sh
on each middle tier.
Select the new information storage database and supply the necessary passwords.
Select None for the voice mail server.
On each telephony server the sc_vsto.cfg
file must be updated with the new information storage information.
Example 7-1 shows the sc_vsto.cfg
file before it is updated.
Example 7-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 7-2 shows an updated sc_vsto.cfg
file.
Example 7-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