Oracle eMail Server Installation Guide Release 5.2 for Sun SPARC Solaris 2.6 Part Number A88649-01 |
|
This chapter describes tasks that must be done after you have installed or upgraded eMail Server.
This chapter contains this topic:
The tasks described in this section are as follows:
The listener must be running so that the system can establish database connections from the eMail Server and clients. The listener may already be running if you have not stopped it since preinstallation.
To verify that the listener is running, enter the following:
% lsnrctl status
If the computer returns a message that contains the line no listener
, then the listener needs to be started. Otherwise, the listener is up and running and you may proceed to Task 2.
To start the listener, enter the following:
% lsnrctl start
There are several processes that run in the background to perform specific eMail Server functions.
Warning: Do not run any eMail Server 5.2 administration tools against previous eMail Server versions. |
See Also:
Table A-1, "eMail Server Processes and Descriptions" in Appendix A for a list of processes and their descriptions |
To start the Guardian process, enter the following:
% ofcguard start [connect=connect_string
]
The connect_string
is required if accessing a remote node. To verify the startup of the Guardian process, locate the guardian01.log
file in the$ORACLE_HOME/office/log/
SID
and enter the following:
% tail -f hostname
guardian01.log
% oomgr
Enter your user name, password, connect string, and qualified domain name at the appropriate prompts.
Since you have only one domain level, all you need to enter is your username and password. You initially must use the connect_string
and qualified_domain
, however, if you are trying to connect to another database.
To start processes, enter the following:
IOFCMGR> startup all; Started successfully.
IOFCMGR> disp process;
The following is sample output:
To exit IOFCMGR
, enter the following:
IOFCMGR> exit
Perform the following steps to check server process logs:
Access the $ORACLE_HOME/office/log/
SID
directory.
Check the following log files for error messages.
Fully qualified domains are within any company or organization. The domain is usually in the form of company/organization_name.extension
. Oracle.com and whitehouse.gov are two examples of fully qualified domains. At this point, your installation of eMail Server has only one ldomain level (the top level), which you chose using the installation wizard. To insert the next level of your domain, perform the following steps:
% oomgr
IOFCMGR>
.
IOFCMGR>whoami
Login: ADMIN Node: ESNODE: Domain: COM
IOFCMGR>insert domain qualifiedname=
qualified name.extension
confignode=
node_name
description="your company/organization name";
Inserted successfully
An example of qualified_name.extension
is oracle.com. The description
is optional in the above command line. To create a subdomain belowqualified_name.extension
, log out of OOMGR and repeat Steps 1 through 3, connecting into the qualified_name.extension
domain.
IOFCMGR>connect admin/
password
/
service_name
/
qulified name.extension
Connected.
Create a test user and alias to send a test message, and ensure that the mail is delivered as expected.
IOFCMGR>whoami
Login: ADMIN Node: ESNODE: Domain:company/organization_name.extension
IOFCMGR>insert person username=username
password=password
uanode=node
; Inserted successfully. IOFCMGR>exit
The gateway configuration file unx.cfg, is created during the installation. Register the gateway with Sendmail, the standard UNIX mail transfer agent that handles all messages traveling to and from the Internet. To register the gateway with Sendmail, specify gateway information in the sendmail.cf
file so that Sendmail knows how to forward messages coming in from the Internet. Set up aliases to redirect incoming mail to the gateway.
Perform the following steps from root
.
sendmail.cf
file, usually located in either /etc/
or /etc/mail/
, by adding the following information about the SMTP/MIME mailer to the end of the file:
Mofcmail, [tab] P=$ORACLE_HOME
/bin/ofcuto, F=rlSsDCFMPpmn, S=10, R=20,
[tab]A=ofcuto -$ORACLE_HOME
$ORACLE_SID
-fconfig_file
-
$g $a $b $f $x ( $u )
sendmail.cf
file, add the following entries to ruleset Parse1 before the line "# short circuit local delivery so forwarded email works
":
## Oracle eMail Server: Hook to Oracle eMail Server mailer ## R$+.ofcmail<@$=w.>[tab][tab]$#ofcmail$:$1[tab][tab]Oracle eMail Server passoff R$+.OFCMAIL<@$=w.>[tab][tab]$#ofcmail$:$1[tab][tab]Oracle eMail Server passoff
Add the following entries to ruleset Parse1 before the line "# handle locally delivered names
":
## Oracle eMail Server: Hook to Oracle eMail Server mailer ## R$+.ofcmail[tab][tab]$#ofcmail$:$1[tab][tab]Oracle eMail Server passoff R$+.OFCMAIL[tab][tab]$#ofcmail$:$1[tab][tab]Oracle eMail Server passoff##
sendmail.cf
file, add the user name of the owner of the Oracle eMail Server $ORACLE_HOME
directory. Trusted users such as root
, daemon
, and uucp
generally begin with a "T":
T root daemon uucp Oracle_eMail_Server_owner
sendmail.cf
file and the rc.local
file, restart Sendmail as the root user.
# ps -ef|grep sendmail
/etc/mail
directory as follows:
# cd /etc/mail
sendmail.cf
file, you can direct all mail into the eMail Server. This is done by changing the following Mlocal
mailer definition and replacing it with the Mofcmail
mailer definition. Use a text editor to perform the following steps:
Mlocal
mailer definition.
Mlocal,[tab]P=$ORACLE_HOME
/bin/ofcuto, F=rlSsDCFMPpmn, S=10, R=20,[tab]A=ofcuto-$ORACLE_HOME
-fconfig_file
-$g $a $b $f $x ($u
aliases
file located in the /etc/mail
directory, and insert the following line at the end of the file:
username: username.ofcmail@system_name
.domain_name.extension
username.ofcmail is the minimum amount of information required. system_name, domain_name.extension
are optional.
aliases
database by entering the following:
# newaliases
process_id
number from the sendmail.pid
file located in the /etc/mail
directory. Enter the command
# kill -9 process_id
# /usr/lib/sendmail -bd -q30m
You must export private aliases and distribution lists from the eMail Server directory to an LDAP directory. To replicate data from the eMail Server directory to an LDAP directory, you must run a migration script to create data files that you can import into the LDAP directory.
Use the following procedure to replicate the private aliases, distribution lists, and public data from the eMail Server directory to an LDAP directory:
MigrateIOData.sh
scripts that generate the following two data files in the $ORACLE_HOME/office/log
directory:
% cd $ORACLE_HOME/office/admin/rsql % ldapadd -hhostname
-p 389 -f add_ldap_attr.dat % ldapadd -hhostname
-p 389 -f add_ldap_obj.dat
Replace hostname
with the name of the machine on which Oracle Internet Directory is running.
If you are using a third-party LDAP directory, you must define the eMail Server database schema specified in the add_ldap_attr.dat
and add_ldap_obj.dat
files before importing the data into the directory.
replog.log
and private_aliases_and_dls.log
files to the /tmp
directory of the LDAP server.
Note:
You can copy the files to a directory other than the / |
replog.log
file for erroneous data, by running the following command on the LDAP server as the LDAP directory database owner:
% $ORACLE_HOME/ldap/bin/bulkload.sh -connect service_name
-check -generate
/tmp/replog.log
Replace service_name
with the LDAP directory database service name in the tnsnames.ora
file.
$ORACLE_HOME/ldap/log
directory show no errors. Bulk load the data on the LDAP server as follows:
% bulkload.sh -connect service_name
-load -generate
/tmp/replog.log
Replace service_name
with the LDAP directory database service name in the tnsnames.ora
file.
At this point, all directory objects except private aliases and distribution lists are loaded into the directory.
% acl.pl replog.log
% acl.pl replog.log netscape
The command creates a file called replog.log.acl
. The generated Access Control List, ACL, will be for Oracle Internet Directory or Netscape.
Perform the following steps to set up the ESPrefs.
espref
directory located in $ORACLE_HOME/office/admin
to the host where the web server is running. The espref
directory contains the following directories:
espref.jar
file located in the $ORACLE_HOME/office/lib
directory into the espref/beans
directory on the target host.
espref.jar
file:
% cd espref/beans % jar xvf espref.jar
espref/config
directory. The configuration files are text files, where each entry is separated by a space.
The esDomains.cfg
file lists the following domain information:
All entries in the file must be formatted in the following way:
domain host SID port
acme.com mail.acme.com mail 1521
The esConnectStrings.cfg
file contains the following connect information for all the nodes in the system:
All entries in the file must be formatted as follows:
connectstring host SID port
imapmail mail.acme.com mail 1521
It can also have the following format:
connnectstring = database connect info as used in the tnsnames.ora
format
imapmail (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
(Host=mail.acme.com)(Port=1521)))(CONNECT_DATA=(SERVICE_NAME=mail)))
The esPrefs.cfg
file contains an array of key/value pairs the administrator sets to enable subscribers to set the auto-reply and auto-forward templates. This must be set to either Yes or No, depending on the administrator's preference.
The values must be formatted as follows:
AutoReplySet Yes/No
AutoForwardSet Yes/No
To configure the ESPrefs server, set the path of the configuration directory.
espref
directory.
Copy the espref
directory from the build environment to$ORACLE_HOME/Apache/Apache/htdocs/espref
Unjar the espref.jar
file located in the$ORACLE_HOME/Apache/Apache/htdocs/espref/beans
directory:
% cd $ORACLE_HOME/Apache/Apache/htdocs/espref/beans % jar xvf espref.jar
Refer to Task 7: Configure eMail Server Preferences (ESPrefs) to configure ESprefs.
Open $ORACLE_HOME/Apache/Jserv/etc/jserv.properties
using a text editor, and add the following two lines to the end of the file:
wrapper.bin.parameters=-DFILE_LOCATION=$ORACLE_HOME
/Apache/Apache/htdocs
/espref/config/ wrapper.classpath=$ORACLE_HOME
/Apache/Apache/htdocs/espref
% cd $ORACLE_HOME/Apache/Apache/bin % ./apachectl stop % ./apachectl start
http://hostname
:port
/espref/jsp/esLogin.jsp
You should see the logon page.
The Thin Client is an application that gives you access to e-mail functions, directory, and message searching capability from a single web page. You can customize the Thin Client to support your working style. With the Thin Client, you can compose new messages, organize existing messages and message folders, search for messages, create address book aliases and distribution lists, change your password, check mail quotas, change time zones, create mail rules and filters, and customize the look of the Thin Client.
esclient
directory as follows:
Copy the esclient
directory from the build environment to$ORACLE_HOME/Apache/Apache/htdocs/esclient
Untar the esclient.tar
file located in the $ESCLIENT_HOME
directory:
% cd $ESCLIENT_HOME % tar xvf esclient.tar
Open $ORACLE_HOME/Apache/Jserv/etc/jserv.properties
and use a text editor to verify that the following lines are contained in the file:
wrapper.bin.parameters=-DES_PROPERTIES=$ESCLIENT_HOME/es.properties wrapper.classpath=$ESCLIENT_HOME/lib/j2ee.jar wrapper.classpath=$ESCLIENT_HOME/lib/jgl.zip wrapper.classpath=$ESCLIENT_HOME/lib/classes111.zip wrapper.classpath=$ESCLIENT_HOME/lib/ldap.jar wrapper.classpath=$ESCLIENT_HOME/lib/providerutil.jar wrapper.classpath=$ESCLIENT_HOME/lib/es.jar
Use a text editor to verify or insert the following lines into the zone.properties
file, also located in the /$ORACLE_HOME/Apache/Jserv/etc
directory:
repositories=$ESCLIENT_HOME/servlets
*.dat
files found in $ESCLIENT_HOME/doc
to OiD, as follows:
% ldapadd -hhost
-D 'cn=orcladmin' -wpassword
> -f*.dat
Load DIT file using the following command:
ldapadd -hhost
-D 'cn=orcladmin' -wpassword
-f oracle.ldif
es.properties
file located in the directory using the text editor. Instructions on how to configure this file are located within the es.properties
file.
http://hostname
:port
/esclient/templates/login.jsp
You should see the logon page.
There are four log files to monitor to ensure that your first message is successfully sent and delivered.
syslog
This log file is located in the /var/log
directory and is written to by the Sendmail daemon.
ofcuto.log
This log file is located in the $ORACLE_HOME/office/log/
SID
directory and is written to by the ofcuto
process that the Sendmail mailer launches.
system_name
_ofcutosrv.log
This log file is located in the $ORACLE_HOME/office/log/
SID
directory and is written to by the ofcutosrv
process that uploads the mail into eMail Server.
system_name
_postman.log
This log file is located in the $ORACLE_HOME/office/log/
SID
directory and is written to by the postman
process which evaluates the e-mail from the submission queue.
The list is in the order by which e-mail is passed to eMail Server. Use the % tail -f
command to view these files in real time.
Use the following command to send your first test e-mail (you must be logged in as root
).
# /usr/lib/sendmail -v address
Where address
is the name of your test user. Since an alias has been set up, you do not need the rest of the address in order to send e-mail.
# /usr/lib/sendmail -v user1 user1...aliased to user1.ofcmail first test message. . user1.ofcmail...Connecting to ofcmail... user1.ofcmail...Sent
The message entered by the administrator is "first test message."
By following the log files you should see the message flow through to the destination account inside eMail Server.
The next step is to log in to the account using the IMAP client chosen during the installation to confirm that the message was sent.
Depending upon how you utilize Oracle eMail Server (such as number of users and number of messages), you may find that the default settings in the SPS (scalable protocol server) files are too low. Monitor the IMAP4 log file, node_name
_imap01.log
, located in the $ORACLE_HOME/office/log/
SID
directory while the system is in use, to determine whether or not the protocol servers are adequately configured.
Perform the following steps to import the statistics file:
% $ORACLE_HOME
/office/admin/pckg/apply-stats.sh
% ORACLE_HOME/office/admin/pckg/em-stats.dmp
The Oracle Enterprise Manager (OEM) Capacity Monitoring Pack allows an administrator to monitor e-mail traffic on the server from a Windows NT platform.
emschart.jar
from the Solaris installation to the NT machine where OEM is installed. The location of this file in the Solaris installation is$ORACLE_HOME/office/admin/emschart.jar
.
jar
command to extract the contents of the emschart.jar
.
c:\> jar -xvf emschart.jar
setup.exe
command which is located in the emschart/Disk1/install/win32
directory, and follow the prompts through the installation.
A status dialog box will tell you when a node is discovered. Discovered nodes will appear on the Navigator Tree.
See Also:
Troubleshooting OEM E-mail Capacity Monitoring Pack in Chapter 5 if you fail to discover nodes |
Use the Discover Node function for nodes that have an Intelligent Agent. If you add services to these nodes, you must restart the agent on the nodes before discovering the new services.
|
Copyright © 1996-2001 Oracle Corporation. All Rights Reserved. |
|