3
Postinstallation

This chapter describes tasks that must be done after you have installed or upgraded eMail Server.

This chapter contains this topic:

Postinstallation Tasks

Postinstallation Tasks

The tasks described in this section are as follows:

Task 1: Verify the Network Listener

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

Note:
If you installed a new Member node, use the tnsping command to check the configuration and verify that the DCN is up and running.

Task 2: Start eMail Server Processes

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

Note:
The Guardian process is the parent of all eMail Server processes. If it is not running, the next task will fail.

Enter the following to start the OOMGR.

% 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.

Note:
The default username is admin and the password is welcome.

See Also:
The Oracle eMail Server Administration Guide for more information on OOMGR
Perform the following steps to start eMail Server processes and verify that they are running.

To start processes, enter the following:
```
IOFCMGR> startup all;
Started successfully.
```

To display process status, enter the following:

IOFCMGR> disp process;

The following is sample output:

Server Name

Instance

Last Wakeup

Process Id

DBSession Id

Postman

1

06 Dec 14:24

3771

652

Collector

1

06 Dec 05:51

3772

654

Monitor

1

06 Dec 11:13

3774

653

Statistics

1

06 Dec 14:07

3777

655

IOLISTENER

1

3778

657

Replicator

1

06 Dec 14:24

3780

656

POP3SRV

1

3783

658

IMAP4SRV

1

3785

660

SMTP.COM

1

06 Dec 14:23

3787

662

SMTP_IN.COM

1

06 Dec 14:26

3790

666

To exit IOFCMGR, enter the following:

IOFCMGR> exit

Check the eMail Server process logs. The logs contain entries for all typical operation and errors. Check the logs to ensure that the Guardian and all other registered server processes are error-free.

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.

Process Log File Name

Guardian

local_guardian01.log

Postman

node_name_postman01.log

Collector

node_name_collector01.log

Monitor

node_name_mon.log

Statistics

node_name_stt.log

Replicator

node_name_repl01.log

POP3

node_name_pop301.log

IMAP4

node_name_imap01.log

Listener

node_name_lsnr01.log

Process	Log File Name
Guardian	`local_guardian01.log`
Postman	`node_name``_postman01.log`
Collector	`node_name``_collector01.log`
Monitor	`node_name``_mon.log`
Statistics	`node_name``_stt.log`
Replicator	`node_name``_repl01.log`
POP3	`node_name``_pop301.log`
IMAP4	`node_name`_imap01.log
Listener	`node_name`_lsnr01.log

See Also:
If you find error codes or messages, see "Error Codes and Messages" in the Oracle eMail Server Administration Guide for descriptions and corrective actions

Task 3: Insert a Qualified Domain Name

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:

Use the OOMGR command line to insert the next level of domain. Enter the following:
```
% oomgr
```
to start IOFCMGR>.
To display login, node, and domain information, enter the following:
```
IOFCMGR>whoami
Login: ADMIN Node: ESNODE: Domain: COM
```
Note:
The domain returned by the computer must match the domain you created during the configuration in order to continue.
To further qualify the domain, enter the following:
```
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 below
qualified_name.extension, log out of OOMGR and repeat Steps 1 through 3, connecting into the qualified_name.extension domain.
Connect the OOMGR session to your new domain.
```
IOFCMGR>connect admin/password/service_name/qulified name.extension
Connected.
```

Task 4: Create a Test User

See Also:
Oracle eMail Server Administration Guide for more information regarding inserting an account

Create a test user and alias to send a test message, and ensure that the mail is delivered as expected.

Verify that you are connected to the fully qualified domain as follows:

IOFCMGR>whoami
Login: ADMIN Node: ESNODE: Domain: company/organization_name.extension

Insert your test user as follows:

IOFCMGR>insert person username=username password=password uanode=node;
Inserted successfully.
IOFCMGR>exit

Note:
Username and password can be anything you choose.

Task 5: Configure SMTP Gateway and Create Aliases

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.

Note:
You can use any version of Sendmail supplied with your operating system or supplied on the eMail Server CD for Windows NT. If you do not have Sendmail, you can download it from ftp.sendmail.org. For documentation on Sendmail, go to http://www.sendmail.org.

Note:
The Sendmail file can require configuration steps in addition to those provided here, depending on how many gateways you are using and the complexity of your system. See the documentation for the version of Sendmail for more information.

Note:
Oracle Support Services can only provide information on the basic Sendmail configuration required to receive messages. For more complex configurations, contact the distributor of your Sendmail program.

Perform the following steps from root.

Use a text editor to modify the 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 -f config_file - 

$g $a $b $f $x ( $u )

Entry Description

Mofcmail

This directs Sendmail to run the eMail Server mailer. The mailer delivers the message to the Gateway process, which inserts the message in the Internet Messaging database. You can specify a different mailer name. See the Sendmail documentation for more information about mailers.

$ORACLE_HOME

Enter the full path for the $ORACLE_HOME directory.

$ORACLE_SID

The system identifier (SID) that you registered in the listener.ora file during installation.

config_file

Enter the name of the gateway configuration file. The default filename is unx.cfg.

[tab]

Press the Tab key where indicated instead of the space bar.

Entry	Description
`Mofcmail`	This directs Sendmail to run the eMail Server mailer. The mailer delivers the message to the Gateway process, which inserts the message in the Internet Messaging database. You can specify a different mailer name. See the Sendmail documentation for more information about mailers.
`$ORACLE_HOME`	Enter the full path for the `$ORACLE_HOME` directory.
`$ORACLE_SID`	The system identifier (SID) that you registered in the `listener.ora` file during installation.
`config_file`	Enter the name of the gateway configuration file. The default filename is `unx.cfg`.
`[tab]`	Press the Tab key where indicated instead of the space bar.

In the machine-dependent section of the 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##

Note:
You may use both lines but then you need to have both upper and lower case aliases.

In the list of trusted users in the 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
```
After modifying the sendmail.cf file and the rc.local file, restart Sendmail as the root user.
To locate the Process ID of the existing Sendmail, enter the following command:
```
# ps -ef|grep sendmail
```
To pass e-mail to the eMail Server, it is necessary to create a unix alias. Change to the /etc/mail directory as follows:
```
# cd /etc/mail
```

Alternative SMTP delivery: If your intention is to not have any unix accounts on your server, then, by editing the 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:

Note:
The Mofcmail mailer definition will redirect all message stores, including those destined for OS users (such as root). This option gives the administrator the lowest level of control over incoming message stores.

Comment out all three lines of the Mlocal mailer definition.

Add the following new line just below the three lines you have just commented out:

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

Kill and restart Sendmail (see Step 11, below).

Use the text editor to edit the aliases file located in the /etc/mail directory, and insert the following line at the end of the file:

Note:
This option gives the administrator the highest level of control over incoming message stores. For an installation with many users, however, this option may be inappropriate as the administrator must create an alias for each user.

username: username.ofcmail@system_name.domain_name.extension

username.ofcmail is the minimum amount of information required. system_name, domain_name.extension are optional.

Note:
The names in the message store are appended with .ofcmail. This extension needs to be stripped or added as messages enter or leave the message store. This is done by rewrite rules in the alias file or simply by passing all messages through the local mailer in the sendmail.cf file. This option offers another level control to the administrator between the two previously mentioned options. Refer to Sendmail documentation at www.sendmail.org for more information.

Add the new alias to the aliases database by entering the following:
```
# newaliases
```
To terminate the Sendmail process, use the text editor to retrieve the process_id number from the sendmail.pid file located in the /etc/mail directory. Enter the command
```
# kill -9 process_id
```

To restart Sendmail, enter the following:

# /usr/lib/sendmail -bd -q30m

Note:
You can also use the # ps -aef|grep sendmail command to retrieve the process_id information. Once you have the process_id, you can use kill -HUP process_id to terminate and restart Sendmail.

Task 6: Migrate Directory Data to an LDAP Directory

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.

Note:
The private aliases and distribution lists that were stored in the eMail Server directory can be migrated to a standard-based LDIF representation of this data. However, to store these in the directory, use the thin client.

Note:
eMail Server Version 5.2 has a PL/SQL package which has been written that will migrate the data to an LDIF file. Make sure that the database parameter UTL_FILE_DIR has been specified in the initSID.ora file. The script that starts the migration is still MigrateIOData.sh

Note:
You must run the migration script to use the client's address book search feature.

Use the following procedure to replicate the private aliases, distribution lists, and public data from the eMail Server directory to an LDAP directory:

Manually invoke the MigrateIOData.sh scripts that generate the following two data files in the $ORACLE_HOME/office/log directory:
- replog.log contains all data except private aliases and distribution lists
- private_aliases_and_dls.log contains only private aliases and distribution lists
If you are using Oracle Internet Directory for the LDAP directory, configure the initial context and add the initial directory tree before importing the data.

See Also:
Oracle Internet Directory Administrator's Guide, "Managing Entries" and "Managing Schema" for more information
Start the LDAP server.

See Also:
Oracle Internet Directory Administrator's Guide, "Preliminary Tasks" for more information
Insert the eMail Server database schema (not the data) into the Oracle Internet Directory database. As the owner of the eMail Server database account, enter the following:
```
% cd $ORACLE_HOME/office/admin/rsql
% ldapadd -h hostname -p 389 -f add_ldap_attr.dat
% ldapadd -h hostname -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.

See Also:
The documentation for the third-party LDAP directory for instructions on how to do this
Copy the 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 /tmp directory; the /tmp directory is used in this step and subsequent steps as an example.
Check the eMail Server directory entries in 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
```
Note:
ORACLE_HOME is located where the LDAP server is installed.

Replace service_name with the LDAP directory database service name in the tnsnames.ora file.
If the bulkload check is successful, the files in the $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
```
Note:
The bulkload.sh script is located in the
$ORACLE_HOME/ldap/bin directory on the LDAP server.

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.
To load the private aliases and distribution lists into the directory, begin by running one of the following commands on the eMail Server:
- For Oracle Internet Directory:
```
% acl.pl replog.log
```
- For a Netscape LDAP directory:
```
% acl.pl replog.log netscape
```
  Note: The acl.pl script only supports Netscape as a third party vendor.
The command creates a file called replog.log.acl. The generated Access Control List, ACL, will be for Oracle Internet Directory or Netscape.

Task 7: Configure eMail Server Preferences (ESPrefs)

Perform the following steps to set up the ESPrefs.

Copy the espref directory located in $ORACLE_HOME/office/admin to the host where the web server is running. The espref directory contains the following directories:
- config
- media
- beans
- jsp
Copy the espref.jar file located in the $ORACLE_HOME/office/lib directory into the espref/beans directory on the target host.

Expand the espref.jar file:

   % cd espref/beans
   % jar xvf espref.jar

Edit the following configuration files located in the espref/config directory. The configuration files are text files, where each entry is separated by a space.

esDomains.cfg

The esDomains.cfg file lists the following domain information:

domain = domain name
host = name of the DCN node
SID = SID of the database
port = port number on which the SQLNET listener is running.

All entries in the file must be formatted in the following way:

domain  host  SID  port

Example

acme.com  mail.acme.com  mail 1521

Note:
Only one entry per domain is needed.

esConnectStrings.cfg

The esConnectStrings.cfg file contains the following connect information for all the nodes in the system:

connectstring = database connect string
host = host name of the database
SID = SID of the database
port = port number on which the SQLNET listener is running.

All entries in the file must be formatted as follows:

connectstring  host  SID  port

Example

imapmail  mail.acme.com  mail 1521

It can also have the following format:

connnectstring = database connect info as used in the tnsnames.ora 
format

Note:
This must be one string.

Example

imapmail (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)

(Host=mail.acme.com)(Port=1521)))(CONNECT_DATA=(SERVICE_NAME=mail)))

esPrefs.cfg

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

Task 8: Set Up the ESPrefs Server

To configure the ESPrefs server, set the path of the configuration directory.

iAS Server Setting

Set up the 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.
Set up the iAS configuration file.

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
```

Restart iAS.

% cd $ORACLE_HOME/Apache/Apache/bin
% ./apachectl stop
% ./apachectl start

Test to see that ESPrefs works. Open a browser and enter the following URL:
```
http://hostname:port/espref/jsp/esLogin.jsp
```
You should see the logon page.

Task 9: Configure eMail Server Thin Client

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.

Note:
The Thin Client must be installed on a different
$ORACLE_HOME than that of the database and eMail Server. In the following steps, $ESCLIENT_HOME refers to the full path of the directory where esclient resides.

Set up the 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
```

Set up the iAS configuration file as follows:

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

Configure Oracle Internet Directory (OiD) by loading *.dat files found in $ESCLIENT_HOME/doc to OiD, as follows:

% ldapadd -h host -D 'cn=orcladmin' -w password> -f *.dat

See Also:
Oracle Internet Directory Administrator's Guide for more information about loading the preferences schema manually using the OiD administrator's console.
The orclMailApplicationPreferences.readme file contains a list of required attributes.

Load DIT file using the following command:

ldapadd -h host -D 'cn=orcladmin' -w password -f oracle.ldif

Note:
One LDAP entry is required for each user. See the entry.readme file located in the $ESCLIENT_HOME/doc directory for more information.

Configure the 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.
Test to see that the Thin Client works. Open a browser and enter the following url:
```
http://hostname:port/esclient/templates/login.jsp
```
You should see the logon page.

Task 10: Send a Test E-mail

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.

Example

# /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.

Task 11: Configure Protocol Servers

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.

See Also:
Oracle eMail Server Administration Guide, Chapter 10, for information and instructions regarding configuration of the SPS files.

Task 12: Load Shipped Statistics File for the Cost Based Optimization (Optional)

Perform the following steps to import the statistics file:

Run the following script:

% $ORACLE_HOME/office/admin/pckg/apply-stats.sh

Enter the user's database password.

Enter the path of the statistics dumpfile:

% ORACLE_HOME/office/admin/pckg/em-stats.dmp

Task 13: Configure OEM E-mail Capacity Monitoring Pack (Optional)

Note:
To use the Monitoring Pack, Oracle Enterprise Manager (OEM) and the associated Diagnostic Pack are required. Please contact Oracle Sales for more information.

The Oracle Enterprise Manager (OEM) Capacity Monitoring Pack allows an administrator to monitor e-mail traffic on the server from a Windows NT platform.

Note:
You must be using a TCP/IP network protocol.

On the NT side, install OEM, including the Diagnostic Pack.

See Also:
Oracle Enterprise Manager Installation for more information
Copy the file 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.
On the NT machine, open a DOS prompt window. In this window, use the jar command to extract the contents of the emschart.jar.
```
c:\> jar -xvf emschart.jar
```
Once the contents are extracted, there will be a new directory named emschart. To install the E-mail Capacity Monitoring Pack, run the setup.exe command which is located in the emschart/Disk1/install/win32 directory, and follow the prompts through the installation.

Note:
The jar command is released with the Java Development Kit from Sun. If the NT machine already has a version of the JDK installed, the jar command will be in the JDK bin directory.
Discover a node with Oracle database server and applications installed.
1. On the NT machine, choose Navigator from the OEM menu bar.
2. Open the folder called Nodes and enter the name of the node you want to discover in the text window of the Discover Nodes dialog box. Click OK to continue.
  
  Note:
  To discover multiple nodes at one time, enter each node you want to discover on a new line with the text window.
  
  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
The Navigator provides access to the Discovery/Refresh Wizard, which simplifies identifying network services and populating the Navigator tree. These services, such as databases and listeners, can be administered with OEM components. If you cannot discover a node (because an Agent is not running on the node), the Discovery/Refresh Wizard allows you to manually enter the information about services on nodes.

Note:
Access to OEM services, such as jobs and events, will not be available if a node is manually configured.
1. To discover new services, select Discover Node from the Console Navigator menu to start the Discovery Wizard.
  
  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.
2. To refresh existing services, select Refresh Node from the Console Navigator menu to start the Refresh Wizard.
  
  Note:
  Databases on the machine where Oracle Management Server is running are discovered automatically.

`Server Name`	`Instance`	`Last Wakeup`	`Process Id`	`DBSession Id`
`Postman`	`1`	`06 Dec 14:24`	`3771`	`652`
`Collector`	`1`	`06 Dec 05:51`	`3772`	`654`
`Monitor`	`1`	`06 Dec 11:13`	`3774`	`653`
`Statistics`	`1`	`06 Dec 14:07`	`3777`	`655`
IOLISTENER	1		3778	657
`Replicator`	1	`06 Dec 14:24`	3780	656
POP3SRV	1		3783	658
IMAP4SRV	1		3785	660
SMTP.COM	1	`06 Dec 14:23`	3787	662
`SMTP_IN.COM`	`1`	`06 Dec 14:26`	`3790`	`666`

3 Postinstallation

Postinstallation Tasks

Task 1: Verify the Network Listener

Task 2: Start eMail Server Processes

Task 3: Insert a Qualified Domain Name

Task 4: Create a Test User

Task 5: Configure SMTP Gateway and Create Aliases

Task 6: Migrate Directory Data to an LDAP Directory

Task 7: Configure eMail Server Preferences (ESPrefs)

esDomains.cfg

Example

esConnectStrings.cfg

Example

Example

esPrefs.cfg

Task 8: Set Up the ESPrefs Server

iAS Server Setting

Task 9: Configure eMail Server Thin Client

Task 10: Send a Test E-mail

Example

Task 11: Configure Protocol Servers

Task 12: Load Shipped Statistics File for the Cost Based Optimization (Optional)

Task 13: Configure OEM E-mail Capacity Monitoring Pack (Optional)

3
Postinstallation