This chapter contains the instructions for installing SunTM Internet Mail ServerTM 4.0 by using the graphical interface (GUI).
Topics in this chapter include:
|
|
Before installing SIMS 4.0 |
|
|
Installing SIMS 4.0 |
|
|
Installing SIMS optional features |
|
|
Installing the remote SIMS Administration console |
|
|
Installing the SIMS High Availability system |
|
|
After installing SIMS 4.0 |
If you are installing the SIMS High Availability system, refer to the Sun Cluster 2.2 documentation set to ensure that you have installed the necessary software and hardware required by the Sun Cluster.
You can revise the information you have provided during installation by using the SIMS Administration Console. See the Sun Internet Mail Server 4.0 Concepts Guide for information on the SIMS Administration Console and its capabilities.
Before installing SIMS 4.0, make sure that you have read the following chapters:
TABLE 7-1 Chapters Required before Installing SIMS 4.0
Chapter Number, Name
|
To Learn About...
|
|---|
|
1, Overview of SIMS 4.0
|
SIMS 4.0 changes, features
|
|
2, System Requirements
|
Platform, space, memory, client, SDS 3.1 requirements
|
|
3, Software and Configuration Requirements
|
SIMS and SIMS/HA software requirements, DNS configuration
|
|
4, Preparing to Install SIMS 4.0
|
NSDS, LDAP rollover, remote LDAP, clean system, patches
|
|
5, Planning to Configure SIMS 4.0
|
SIMS as a proxy, SP environment, and IMTA considerations
|
|
6, What SIMS 4.0 Installs
|
Lists of SIMS 4.0 packages and startup scripts
|
This section provides step-by-step instructions to install your Sun Internet Mail Server 4.0.
The installation steps are:
| |
1. |
Run the setup installation script. |
| |
2. |
Select the optional features. |
| |
3. |
Specify the LDAP server information. |
| |
4. |
Specify the server configuration information. |
| |
5. |
Start the Setup script. |
See "Installing SIMS Optional Features" on page 54 to install SIMS optional and add on features on your existing SIMS system.
See "Installing the SIMS High Availability System" on page 59 for instructions on installing the SIMS High Availability system.
See Appendix A, "Installing Netscape Directory Services for SIMS," for instructions to install NSDS with SIMS 4.0.
See Appendix B, "Installing Netscape Directory Services for SIMS High Availability," for instructions to install NSDS with the SIMS High Availability system 4.0.
Note - SIMS installation log files are located in /var/opt/SUNWmail/log/SIMS_installation_log.n after installation is complete, and are in /tmp while installation is in progress.
Running the Installation Script
| |
1. |
Log in as a non-root user. |
| |
2. |
Ensure that you have set the DISPLAY variable. |
| |
3. |
Insert the SIMS CD-ROM into the disk drive. |
| |
|
Make sure that your CD is mounted to the /cdrom directory. |
| |
4. |
Change to the SIMS product directory.
|
% cd /cdrom/sun_internet_mail_4_0
|
|
| |
5. |
Run the setup script from the software CD-ROM as non-root.
|
FIGURE 7-1 SIMS 4.0 Installation Top Page
Note - Running setup results in cleaning up the /tmp directory.
| |
6. |
Review the information pages and then click Install to install the SIMS 4.0 core and optional features. |
Note - See Chapter 1, "Overview of Sun Internet Mail Server 4.0," for a complete list features that comprise SIMS 4.0.
Selecting SIMS Optional Features
FIGURE 7-2 SIMS Optional Features
| |
7. |
Select the SIMS optional features that you wish to add to your SIMS server. |
| |
|
If you don't select any options, only the SIMS core components will be installed. |
Specifying the LDAP Server Configuration
| |
8. |
Click Apply to go to the Directory Services Information page. |
FIGURE 7-3 The Directory Information Page
| |
9. |
Enter the required information on the Directory Services Information page. |
Directory Services Server Name--The fully qualified domain name of the server on which the LDAP directory services are available; that is, either the Netscape Directory Services (NSDS) or the Sun Directory Services (SunDS).
Directory Services Server Port--The port number of which the LDAP server uses. For NSDS, this is the port number that you used during the NSDS installation.
Note - If you would like your SIMS server to use a remote LDAP server (instead of using the local LDAP server), you need to specify the fully qualified domain name (FQDN) and the port number of the remote LDAP server as the Directory Services Server Name and the Directory Services Server Port number here. Be sure that your LDAP server is configured and run before you click Apply here.
Note - If the local NSDS LDAP server, the remote NSDS, or the remote SunDS is not configured with the SIMS 4.0 schema, a warning displays at the top of the screen. Although you may choose to click Apply and continue the installation, you will need to manually perform certain configurations, as covered in "Preparing to Install SIMS with Remote LDAP" in Chapter 4, "Preparing to Install SIMS 4.0."
| |
10. |
Directory Services Type--The directory services of your choice: Netscape Directory Services or Sun Directory Services. The Netscape Directory Services is the preferred directory to use with SIMS 4.0. |
Specifying the Server Configuration
FIGURE 7-4 Configuration Page 1
| |
11. |
Enter the values in the first SIMS configuration page. |
| |
|
You may accept the default configuration values if they meet the requirements of your mail server. |
-
Mail Server Domain Name Suffix--The domain name of the mail server on which SIMS is being installed. For example, if this server resides in the stream domain at the site bridge, then specify stream.bridge.net in this field. This parameter has no default value. However, if installation can determine the domain name from resolv.conf, this value will be automatically supplied. This value can be the same as the Organization Top Level Domain Name field.
Note - SIMS 4.0 checks for a fully qualified domain name and will display error messages, depending on its finding. See Chapter 11, "Troubleshooting the Sun Internet Mail Server," for more information on configuring DNS setup.
-
Organization Top Level Domain Name Suffix--The highest level domain name used within your organization. For example, the top level domain name for an SP provider could be bridge.net. This value can be the same as the Mail Server Domain Name.
-
Postmaster User ID--The SolarisTM user listed in this field has permission to run all SIMS commands, programs, and start or stop daemons on the mail server. You will need this postmaster name to administer the mail server after installing SIMS. By default the installation assigns inetmail as the postmaster (the reserved user ID 72). Your input in this field should not exceed 64 characters. Although it is recommended that you use inetmail, you can change the default user name during the installation. You do not need to provide a password. However, the first time the postmaster logs into the mail server, the postmaster will be prompted for a new password before being able to execute any SIMS commands on the mail server.
-
Directory Administrator Name--The user name of the directory server administrator. The default name is Directory Manager for NSDS and admin for SunDS. After the installation is complete, the administrator can use the SIMS Administration Console to configure the directory server. Your input in this field should not exceed 64 characters. The name you provide in this field is logged in the directory configuration file so that the administrator always has access to the directory. This enables the administrator to solve problems associated with access control.
-
Directory Administrator Password--The password for the directory server administrator. The default password is secret for SunDS. For NSDS, you enter the password that you provided for the Directory Manger. Once the installation is complete, the Directory Administrator's password is needed to configure the directory server using the SIMS Administration Console. The password you provide in this field is logged in the directory configuration file. By default, this password is stored encrypted.
-
SIMS Administrator Name--The user name for the SIMS Administrator at the site who administers the SIMS server, including performing delegated management tasks. The SIMS Administrator is a real user in the directory and has been granted access to the entire LDAP directory through special Access Control Lists (ACLs).
-
SIMS Administrator Password--The password associated with the SIMS administrator. The default password is secret.
-
Domain Component Tree Root--The node name for the root of the Domain Component (DC) tree for which SIMS is installed. The default is internet. This will cause the DC tree to be rooted at the node o=internet. See the Sun Internet Mail Server 4.0 Concepts Guide for more information on the DC tree structure for SIMS 4.0.
-
Delegated Management Server--The fully qualified domain name (FQDN) of the Delegated Management server from which all requests from the hosted domains are accessed.
-
Firewall Location--Choose the button that best indicates the location of your mail server in relationship to your company's firewall machine. The firewall controls access between the Internet and your company's internal network.
-
No--Indicates that your mail server is on or outside the firewall, or if your company has no firewall.
-
Yes--Indicates that your mail server is behind a firewall. You will then be asked to specify the name of the smart host, which is the machine with more routing information and capabilities than your mail server.
| |
Smart Host--If you chose to put your mail server behind a firewall, you need to enter the fully qualified host name of the machine that has the routing information about your mail server. If your mail server cannot route mail to a recipient's address, it forwards the message to its smart host. |
| |
A smart host usually knows how to route messages through your company's firewall. Without routing information, the mail server cannot forward messages outside the firewall. It may only be able to communicate with machines in its own domain, specified domains, or with its peers. In small companies, the smart host may also serve as the firewall machine, providing a communication link between the company and the outside mail community. If neither the smart host nor the firewall machine can route a recipient's address, they return the message to the sender with a non delivery notice. |
-
VAR Mail Support-- Click on the button that best indicates your company's plans for this mail server. SIMS supports both /var/mail and Sun Message Store users. Sun Message Store that runs under the user id inetmail is more secure than
/var/mail that runs as root. Refer to the Sun Internet Mail Server 4.0 Administrator's Guide for migration instructions.
Note - /var/mail/ is only supported for the default domain and not for the hosted domains.
| |
12. |
Click Apply to go to the second page of the configuration pages. |
| |
|
Your input in the form fields is saved to a file and the next configuration page displays. |
FIGURE 7-5 Configuration Page 2
| |
|
Your input in this form is optional. |
-
Organization Long Name--Enter your full company name.
Note - This should not be the same as Organization Name shown in Step 13 above.
-
Postal Address--Enter the street address of the individual who administers this mail server.
-
City Name--Enter the city name in which your mail server resides. Your input in this field should not exceed 128 characters.
-
State/Province--Enter the state name in which your mail server resides. Your input in this field should not exceed 128 characters.
-
Telephone Number--Enter the telephone number of the individual administering this mail server.
-
Fax Number--Enter the fax number of the individual who administers this mail server.
| |
14. |
Click Apply to go to the Configuration Summary page. |
| |
|
This page shows how you specified the configuration of your SIMS system. |
Running the Setup Installation
After selecting SIMS optional components and specifying configurations for both core and optional components, you are now ready to begin installing SIMS 4.0.
| |
15. |
Click Start Install in the Configuration Summary page, if the information you provided in all the forms is accurate. |
If the command tool is not invoked automatically, verify that your DISPLAY variable is set correctly. You will then need to restart the software. If the command tool is not available, an error message will be displayed. Check the patch to the command tool or your operating system setup.
| |
16. |
Enter the root password at the password prompt. |
| |
17. |
Enter the SIMS Postmaster's password. |
You may not see the screen to enter your password during your installation session. This screen will only appear if the user inetmail does not exist on your system.
Look for any warnings or error messages that may display as the installation proceeds.
| |
18. |
Press Enter to exit the command tool window when prompted. |
| |
|
The Installation Summary page displays. |
| |
19. |
Select Exit from the browser File menu to quit out of the GUI installation interface. |
| |
|
You have now successfully installed SIMS 4.0. |
| |
20. |
If you have installed any patches during the installation, reboot your system now. Otherwise, go directly to Step 18.
|
| |
21. |
If you choose to reboot your system later, start the mail server.
|
# /etc/init.d/im.server start
|
|
See "After Installing SIMS 4.0" on page 68 for a roadmap of post installation configurations and tasks.
The following are SIMS 4.0 optional features that you may choose to add to your SIMS core server. Additionally, you can install these features as standalone components on servers where SIMS is not installed.
|
|
Sun Web Access |
|
|
Message Transfer Agent SDK |
|
|
SIMS 4.0 Documentation Set |
|
|
Remote Administration Console |
See Chapter 5, "SIMS Architecture," in the Sun Internet Mail Server 4.0 Concepts Guide for overviews of each components of SIMS.
To install SIMS optional features:
FIGURE 7-6 SIMS Optional and Add On Features
| |
2. |
Select the SIMS optional feature that you wish to add to your SIMS server or install as an standalone component. |
| |
3. |
Click Apply to go to the Directory Services Information page. |
| |
5. |
Click Apply to go to the Configuration Page 1. |
FIGURE 7-7 Configuration Page 1 Screen for SIMS Optional Features
| |
6. |
Specify the server configuration on which the optional or standalone component will be installed. |
-
Mail Server Domain Name Suffix--The domain name of the mail server on which the optional feature or standalone component is being installed. For example, if this server resides in the stream domain at the site bridge, then specify stream.bridge.net in this field. This parameter has no default value. However, if installation can determine the domain name from resolv.conf, this value will be automatically supplied. This value can be the same as the Organization Top Level Domain Name field.
-
Organization Top Level Domain Name Suffix--The highest level domain name used within your organization. For example, the top level domain name for an SP provider could be bridge.net. This value can be the same as the Mail Server Domain Name.
-
Postmaster User ID--The SolarisTM user listed in this field has permission to run all SIMS commands, programs, and start or stop daemons on the mail server. You will need this postmaster name to administer the mail server after installing SIMS. By default, the installation assigns inetmail as the postmaster (the reserved user ID 72). Your input in this field should not exceed 64 characters. Although it is recommended that you use inetmail, you can change the default user name during the installation. You do not need to provide a password. However, the first time the postmaster logs into the mail server, the postmaster will be prompted for a new password before being able to execute any SIMS commands on the mail server.
-
Domain Component Tree Root--The node name for the root of the Domain Component (DC) tree for the server on which SIMS optional features or standalone components are being installed. The default is internet. This will cause the DC tree to be rooted at the node o=internet. See the Sun Internet Mail Server Concepts Guide for more information on the DC tree structure for SIMS 4.0.
| |
7. |
Click Apply to go to the Configuration Summary page. |
You can administer the SIMS product from either Microsoft Windows 95,
Windows NT 4.0, or SolarisTM systems.
Note - It is recommended that you do not run the SIMS Administration console on a dual boot machine running both Windows 95 and Windows NT. The console will experience a NullPointerException error, which will cause problems loading the main page.
 |
To install on Windows 95 or Windows NT 4.0
|
| |
1. |
Insert the SIMS 4.0 CD-ROM into the CD-ROM drive. |
The CD-ROM Autoplay starts, displaying two options: View README and Install. If the Autoplay screen does not appear after a few seconds, then continue with step 3 below.
| |
2. |
Click the Install button. |
| |
3. |
Click the Start button. |
| |
5. |
Run the setup script.
|
<cdrom_drive_letter>:\win35\setup.exe
|
|
Running the setup script begins the installation program.
| |
To install on SolarisTM systems
|
| |
|
This starts the SIMS GUI Installation setup script as a non-root user. |
FIGURE 7-8 SIMS Optional Features Screen
| |
3. |
Select the Remote Administration Console feature. |
FIGURE 7-9 Remote Administration Console Configuration Summary Page
Installing the SIMS High Availability system must be done as a new installation followed by migrating users to the High Availability system. An existing SIMS installation cannot be simply upgraded to an HA installation.
SIMS High Availability installation is controlled by the SIMS installation script. If you are installing SIMS on an HA cluster, the SIMS installation script provides the HA installation.
Your SIMS software will be installed in the directory /opt. The HA software, however, will be installed in directory <ha-dir>/opt, where <ha-dir> is defined by you during the installation.
This section contains the instructions for installing the SIMS High Availability by using the graphical user interface (GUI). First you will be installing the SIMS High Availability on the machine where HA will be primarily used. Next, you will install HA on the machine where HA will be used as a backup to the primary machine.
See Chapter 12, "SIMS Asymmetric High Availability System," for information on the SIMS High Availability system configuration and fail over information.
See the Sun Cluster documentation set for information on commands that are used in this section and for information on packages installed by Sun Cluster.
Note - SIMS High Availability installation must be fresh and cannot be upgraded.
| |
To prepare before installing SIMS/HA
|
| |
|
Before installing the SIMS High Availability system, make sure that you have completed the following steps: |
| |
2. |
Install the Sun Cluster 2.2 software. |
| |
3. |
Install Veritas File System (VxFS) 3.3.2 (or later release). |
| |
5. |
Set up a logical host name for your HA machine. |
| |
|
Use the Sun Cluster documentation set to set up this host name. The disk group or groups that belong to this logical host name must contain sufficient space to store the SIMS product, configuration files, message store, message queues, and directory. |
| |
6. |
Remove any existing SIMS software as root to allow fresh installation of SIMS/HA. |
| |
|
See for instructions on how to remove the SIMS/HA system. |
| |
7. |
Ensure that the following shared volumes names were not used: |
| |
|
/opt/SUNWmail
/opt/SUNWconn
/var/opt/SUNWmail
/var/opt/SUNWconn
/etc/opt/SUNWmail
/etc/opt/SUNWconn |
| |
8. |
Ensure that multiple shared volumes for shared files were not used. |
| |
|
The SIMS High Availability installs all shared files on only one shared volume. For example, you cannot have /opt/SUNWmail on one volume and /opt/SUNWconn on another volume. |
| |
To install the SIMS High Availability system
|
Installing the SIMS High Availability involves installing the software first on the machine where SIMS/HA will be primarily used. The next step is to install SIMS/HA on the machine that will be used as a backup for the SIMS/HA system. The steps are as follow:
| |
1. |
Login as root.
|
$su
Password: <Enter your root password>
|
|
Note - Use your system administration console screen to monitor the steps for installing SIMS on both primary and secondary machines.
| |
2. |
Change the directory to where your Sun Cluster software resides. |
| |
3. |
Check if you are already on the master machine where HA will be primary used.
|
| |
|
If this command returns a logical host name, you are already on the master machine and can skip to step 5. But if you are not on the master machine, it returns nothing. |
Caution - If the logical host name returned above is not known to DNS, SIMS/HA will not install. Additionally, the logical host name must NOT be a DNS alias.
| |
4. |
Switch over to the primary HA machine.
|
# ./haswitch <local-machine> <ha-logical-hostname>
|
|
| |
|
Where,
local-machine is the logical host name for the machine on which the SIMS High Availability will be primarily used, for example, ha-primary, and
ha-logical-hostname is the logical host name assigned to the HA machine, for example
active-ha. |
| |
|
This starts the SIMS GUI Installation setup script as a non-root user. |
| |
6. |
Click Install next to install the SIMS core and optional features. |
FIGURE 7-10 SIMS High Availability System
| |
9. |
Select the logical host name of the machine on which you install SIMS. |
FIGURE 7-11 SIMS/HA Logical Host Name
| |
10. |
Specify the shared file system where the SIMS 4.0 HA software will reside. |
FIGURE 7-12 SIMS/HA Shared File System
During installation, SIMS checks to ensure that the shared file system has sufficient disk space.
Note - Record the name of the shared disk that you are selecting. Use the same name during SIMS/HA installation on the secondary machine.
| |
|
This displays the summary page and runs the setup script. |
You are now done with installing the SIM High Availability on the primary machine. Next, you will be installing the SIMS High Availability on the secondary machine.
| |
12. |
Switch over to the secondary HA machine.
|
# ./haswitch <local-machine> <ha-logical-hostname>
|
|
| |
|
Where,
local-machine is the host name of the machine on which SIMS/HA will be used as the secondary machine, for example, ha-secondary, and
ha-logical-hostname is the logical name assigned to the HA machine, for example
active-ha. This is the same host name that you selected in step 9 above. |
| |
13. |
Install SIMS/HA on the secondary machine from the command-line.
|
% ./setup_tty.secondary -f <shared-file-system>
|
|
| |
|
Where shared-file-system is the shared disk that you selected in step 10 above. As in the example shown in FIGURE 7-12, you may have selected /active-ha/disk1 as the shared disk on which HA and SIMS files were stored. |
| |
14. |
If you have installed patches, you need to stop the node before rebooting. |
| |
|
If you did not install any patches, skip to the next step following next.
|
# /opt/SUNWcluster/bin/scadmin stopnode
|
|
| |
15. |
Reboot the machine on which you have installed the patches. |
| |
|
If you did not install any patches, skip to the next step. |
| |
16. |
Start up the SIMS services under the HA framework.
|
# /opt/SUNWhadf/bin/hareg -y Sun_Internet_Mail
|
|
You are now done with installing the SIMS High Availability on both primary and secondary machines.
FIGURE 7-13 illustrates the SIMS High Availability system after it is fully installed on both the primary and secondary machines.
Note - SIMS supports failure detection and consequent fail over at the hardware and operating system level. Failure at the SIMS service level, such as message access becoming unavailable while the rest of the system remains functional, are not detected and do not cause automatic fail over.
FIGURE 7-13 SIMS/HA System
If you choose to reboot your SIMS/HA system after installing the software, restart your Sun Cluster software by going to steps 17 and 18 below. Otherwise, see "Starting SIMS Administration Console for High Availability Systems" on page 77 in Chapter 9, "Post Installation Tasks," for instructions on invoking the SIMS Administration Console.
| |
17. |
Restart Sun Cluster on the primary SIMS/HA machine
|
# /opt/SUNWcluster/bin/scadmin startcluster
<local-machine> <cluster-name>
|
. |
| |
|
local-machine is the name of the primary SIMS High Availability machine, and |
| |
|
cluster-name is the name of your Sun Cluster. |
| |
18. |
Restart Sun Cluster on the secondary machine.
|
# /opt/SUNWcluster/bin/scadmin startnode <cluster-name>
|
|
See "After Installing SIMS 4.0" on page 68 for a roadmap of post-installation configurations and tasks.
Note - After you have installed the SIMS High Availability, you need to configure the Netscape browser property files by setting the default security level to low. See "Netscape Browser Configuration" on page 70 in Chapter 9, "Post Installation Tasks," for instructions on configuring the Netscape browser.
Removing the SIMS High Availability System
| |
|
SIMS installs files on the shared file disk as well as on the local disks for the primary and secondary SIMS/HA machines as shown in FIGURE 7-13 above. To completely remove SIMS/HA software, you need to delete files from all three locations. |
| |
|
To accomplish this, use the uninstall command that is available from both SUNWmail and SUNWimha directories. |
| |
|
The first time uninstall is used, it is available on both /opt/SUNWmail/sbin and /opt/SUNWimha/sbin directories. However, once it is removed from the shared disk, the uninstall command for the secondary machine is available on the other local disk only in the /opt/SUNWimha/sbin directory. |
| |
|
The following steps completely remove the SIMS High Availability from the shared disk and the two local disks. |
| |
1. |
Check to see if you are already on the master machine.
|
| |
|
If this command returns a logical host name, you are already on the master machine and can skip to Step 3. If you are not on the master machine, it returns nothing.` |
| |
2. |
Switch over to the secondary HA machine.
|
# ./haswitch <local-machine> <ha-logical-hostname>
|
|
| |
|
Where,
local-machine is the machine on which SIMS/HA will be used secondary, for example, ha-secondary, and
ha-logical-hostname is the logical name assigned to the HA machine, for example,
active-ha. |
| |
3. |
Uninstall on the secondary machine from the following location.
|
# /opt/SUNWmail/sbin/uninstall -d sims
or
# /opt/SUNWimha/sbin/uninstall -d sims
|
|
| |
|
This removes all files from both the SUNWmail on the shared disk and SUNWimha on the local disk of the secondary machine. See FIGURE 7-13. |
| |
4. |
Switch over to the primary HA machine.
|
# ./haswitch <local-machine> <ha-logical-hostname>
|
|
| |
|
Where,
local-machine is the logical name for the machine on which SIMS/HA will be primary used, for example, ha-primary, and
ha-logical-hostname is the logical host name assigned to the HA machine, for example
active-ha. |
| |
5. |
Uninstall on the primary machine from the following location.
|
# /opt/SUNWimha/sbin/uninstall -d sims
|
|
This removes all files from SUNWimha on the local disk of the primary machine.
After you have completed installing or upgrading to SIMS 4.0, be sure that you read the following chapters:
Note - After you have installed SIMS, be sure to configure the Netscape browser property files by setting the default security level to low. See "Netscape Browser Configuration" on page 70 in Chapter 8, "Post Installation Configurations," to configure the Netscape browser.
TABLE 7-2 Chapters Required after Installing SIMS 4.0
Chapter Number, Name
|
To Learn About...
|
|---|
|
8, Post Installation Configurations
|
Netscape browsers and SIMS as a proxy configurations
|
|
9, Post Installation Tasks
|
Starting and testing your SIMS server. Starting SIMS Administration and Delegated Management consoles, Web Access, directories. You may go directly to this chapter
|
|
11, Troubleshooting SIMS Server
|
DNS setup configuration, log files, removing sendmail, rebooting after re-installing
|
|
App A, Installing NSDS for SIMS
|
Instructions to install NSDS 4.1 and configure it for SIMS 4.0
|
|
App B, Installing NSDS for SIMS/HA
|
Instructions to install NSDS 4.1 and configure it for SIMS/HA 4.0
|
|
Sun Internet Mail Server 4.0 Web Access Guide
|
Set up, configure, and administer the Sun Web Access.
|
Copyright © 1999 Sun Microsystems, Inc. All Rights Reserved.