Oracle Email Administrator's Guide Release 9.0.3 Part Number B10033-01 |
|
| View PDF |
This chapter discusses the administration tools and explains how to configure, start up, shut down, and reinitialize the Oracle Email system.
This chapter contains the following topics:
This section describes pre-configuration procedures that must be done prior to confuguring Oracle Email.
This section contains the following topics:
To verify that the Java and Oracle Text Options were installed and configured on the mail store database, run the following sql query as sysdba
:
SQL> select comp_id, version, status from dba_registry;
Verify that the infrastructure and application servers are running:
ps -ef | grep http
To start the infrastructure and application servers:
% opmnctl startall
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.
To register the mail store database with the Oracle Internet Directory infrastructure, the following procedures must be performed using the Oracle Net Configuration Assistant (NETCA) and the Database Configuration Assistant (DBCA):
Perform the following steps to run Oracle Net Configuration Assistant (NETCA):
$ORACLE_HOME/bin/netca
Perform the following steps to run the Oracle Database Configuration Assistant (DBCA):
$ORACLE_HOME/bin/dbca
acmeadmin
.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
The Oracle Email configuration wizard creates tablespaces and schema for 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 refer to the $ORACLE_HOME/oes/install/sql/tblspc.sql
script.
ESTERSTORE
that is reserved for tertiary storage of old messages. To enable tertiary storage, pre-create tablespace ESTERSTORE
on a different disk prior to installation. After which, create an instance of the housekeeping server with the TertiaryStore
parameter enabled, and parameter Tertiary Store Age Threshold
to the desired age value in terms of number of days (the default is 30). The housekeeping server instance automatically moves messages periodically.
Note:: If you pre-create tablespaces, the Oracle Email configuration wizard log shows some errors indicating tablespace creation failed. These errors can be ignored. |
See Also:
Chapter 4, "Servers and Processes", for more information on tertiary storage and how to configure server proceses |
This section describes how to configure the Oracle Email mail store, and middle tier servers.
This section contains the following topics:
Configuring the mail store database does the following:
To configure the Oracle Email mail store, perform the following steps on the middle tier server:
umconfig.sh
script located on the application server:
$ORACLE_HOME/oes/bin/umconfig.sh
%ORACLE_HOME%\oes\bin\umconfig.bat
The Unified Messaging Configuration screen appears.
ES_Mai
l password screen is displayed.
ES_MAIL
password and confirm it. If an ES_MAIL
password is not entered, the default is es
.
UMADMIN
password screen is displayed.
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.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:
Note: The manual steps described below are an alternative to running the |
Enter the following command to manually run the Oracle Email mail store configuration scripts with parameters:
cd $ORACLE_HOME/oes/bin install_mailstore.sh <connect_str> true <system_passwd> <ctxsys_passwd> <SID> <host_name> <port_number> UM_SYSTEM <ORACLE_HOME> <es_mail_passwd> <umadmin_passwd> <oid_flag> <domain_name>
cd %ORACLE_HOME%\oes\bin install_mailstore.sh <connect_str> true <system_passwd> <ctxsys_passwd> <SID> <host_name> <port_number> UM_SYSTEM <ORACLE_HOME> <es_mail_passwd> <umadmin_passwd> <oid_flag> <domain_name>
Where:
umbackend.tar
File
Note: If the mail store database was not installed from Oracle Collaboration Suite, the |
Perform the following steps to install the umbackend.tar
file:
umbackend.tar
file from $ORACLE_HOME/oes
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 for the database platform must be transferred from the application server to the mail store database as the database owner.umbackend.tar
file:
tar xvf umbackend.tar
cd backend/Disk1 ./runInstaller
install_infra.sql
FileAdministrators must run <mailstore_database_oracle_home/
on the mailstore database machine after installing the
oes/install/sql/install_infra.sqlumbackend.tar
file.
Configuring the middle tier does the following:
To configure the Oracle Email middle tier servers, perform the following steps:
umconfig.sh
script located on the application server:
$ORACLE_HOME/oes/bin/umconfig.sh
%ORACLE_HOME%\oes\bin\umconfig.bat
The Unified Messaging Configuration screen is displayed.
UMADMIN
password screen is displayed.
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.Once the middle tier configuration is complete, the End of Installation screen is displayed.
Log files for umconfig.sh
and umconfig.bat
are located in the following directories:
Note: The manual steps described below are an alternative to running the |
Use the following command to run the Oracle Email Middle Tier configuration scripts with parameters:
cd $ORACLE_HOME/oes/bin install_middletier.sh true true UM_SYSTEM <ORACLE_HOME> <umadmin_passwd> <oid_flag> <global_db_name> <domain_name>
cd $ORACLE_HOME/oes/bin install_middletier.sh true true UM_SYSTEM <ORACLE_HOME> <umadmin_passwd> <oid_flag> <global_db_name> <domain_name>
Where:
This section describes the different administration tools used to administer the Oracle Email system.
This section contains the following topics:
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 Oracle Email service processes. Through Oracle Enterprise Manager, administrators can perform the following tasks on Oracle Email system:
To perform administration tasks for Oracle Email through Oracle Enterprise Manager, administrators must navigate to the following URL:
http://<machine name>:1810
See Also::
Chapter 3, "Administration and Provisioning" for more information on domain and user provisioning |
Using the Oracle Email Thin Client, administrators can perform domain and user provisioning tasks. Through the Oracle Email Thin Client, administrators can do the following:
To perform administration tasks for Oracle Email through the Thin Client, administrators must navigate to the following URL:
http://<machine name>:<port>/um/traffic_cop
This section explains how to start, stop, and reinitialize the Oracle Email system.
This section contains the following topics:
See Also::
Chapter 4, "Servers and Processes", for more information on how to start up, shut down, and reinitialize individual processes |
The Oracle Net Listener must be running on the mail store database so that the system can establish database connections from the Oracle Email system and clients.
To verify that the listener is running, enter the following:
% lsnrctl status listener_es
From command prompt, enter the following command:
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
From command prompt, enter the following command:
lsnrctl start listener_es
From the Services Console:
To verify that the listener is running, enter the following:
% lsnrctl status listener_es
From command prompt, enter the following command:
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:
From command prompt, enter the following command:
lsnrctl start listener_es
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.tnslsnr
with optional command line arguments.
tnslsnr [listener_name] [-user user] [-group group]
where:
Starting an Oracle Email 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 Oracle Email system:
Stopping an Oracle Email system sends a request to the operating system to shut down all of the Oracle Email processes. One reason an administrator would want to stop the Oracle Email 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 Oracle Email system:
Reinitializing an Oracle Email 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 Oracle Email 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 Oracle Email process:
After configuring Oracle Email, 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.
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. |