This procedure walks you through configuring the Messaging Server initial runtime configuration.
Ensure in your setup that DNS is properly configured and that it is clearly specified how to route to hosts that are not on the local subnet.
The /etc/defaultrouter should contain the IP address of the gateway system. This address must be on a local subnet.
The /etc/resolv.conf exists and contains the proper entries for reachable DNS servers and domain suffixes.
In /etc/nsswitch.conf, the hosts: and ipnodes: line has the files, dns and nis keywords added. The keyword files must precede dns and nis. So if the lines look like this:
hosts: nis dns files ipnodes: nis dns files
They should be changed to this:
hosts: files nis dns ipnodes: files nis dns
Make sure that the FQDN is the first host name in the /etc/hosts file.
If your Internet host table in your /etc/hosts file looks like this:
123.456.78.910 budgie.west.sesta.com 123.456.78.910 budgie loghost mailhost
Change it so that there is only one line for the IP address of the host. Be sure the first host name is a fully qualified domain name. For example:
123.456.78.910 budgie.west.sesta.com budgie loghost mailhost
You can verify that the lines are read correctly by running the following commands:
# getent hosts ip_address # getent ipnodes ip_address
If the lines are read correctly, you should see the IP address followed by the FQDN and then the other values. For example:
# getent hosts 220.127.116.11 18.104.22.168 budgie.west.sesta.com budgie loghost mailhost
On Solaris OS 10 U3 and earlier platforms, you not only have to add the Fully Qualified Domain Name (FQDN) to the /etc/hosts file, but also to the/etc/inet/ipnodes file. Otherwise, you will get an error indicating that your host name is not a Fully Qualified Domain Name. From Solaris OS 10U4 onwards, the contents of the /etc/inet/ipnodes and /etc/hosts files have been merged together into just the/etc/hosts file. Applying kernel patch 120011-14 on any Solaris 10 system will also perform the merge, and subsequent removal of the/etc/inet/ipnodes file.
Invoke the Messaging Server initial runtime configuration with the following command:
You might need to use the xhost(1) command if you are configuring Messaging Server on a remote system.
The table below describes optional flags you can set with the configure program:
Invokes a command-line configuration program.
Invokes a GUI user interface program.
Uses a silent installation file. Must be used with -nodisplay and -noconsole flags. See To Perform a Silent Installation.
Once you run the configure command, the configuration program will start:
The first panel in the configure program is a copyright page. Select Next to continue or Cancel to exit. If you didn’t configure the administration server (Messaging Server 2005Q4 or earlier only) you will be warned, select okay to continue.
Enter the Fully Qualified Host Name (FQHN).
This is the machine on which Messaging Server will operate. When you installed the server using the Java Enterprise System installer, you probably specified the physical host name. However, if you are installing a cluster environment, you will want to use the logical hostname. Here is the chance to change what you originally specified.
Select directory to store configuration and data files.
Select the directory where you want to store the Messaging Server configuration and data files. Specify a pathname that is not under the msg-svr-base. Symbolic links will be created under msg-svr-base to the configuration and data directory. For more information on these symbolic links, see 1.11 Post-Installation Directory Layout.
Make sure you have large enough disk space set aside for these files.
You will see a small window indicating that components are being loaded.
This may take a few minutes.
Select Components to Configure.
Select the Messaging components that you want to configure.
Message Transfer Agent: Handles routing, delivering user mail, and handling SMTP authentication. The MTA provides support for hosted domains, domain aliases, and server-side filters.
Message Store: Provides the foundation for unified messaging services through its universal Message Store. Access to the message store is available through multiple protocols (HTTP, POP, IMAP). If you are only configuring a Message Store, you must also select the MTA.
Webmail Server: Handles the HTTP protocol retrieval of messages from the Message Store. This component is also used by Communication Express to provide web-based access.
Messaging Multiplexor: Acts as a proxy to multiple messaging server machines within an organization. Users connect to the Multiplexor server, which redirects each connection to the appropriate mail server. This component is not enabled by default. If you do check the MMP as well as the Message Store, they will be enabled on the same system; a warning message will appear for you to change your port numbers after configuration. For instructions on doing so, see 1.12 Post-Installation Port Numbers.
To configure the MMP, see Chapter 7, Configuring and Administering Multiplexor Services.
Check any components you want to configure, and uncheck those components you do not wish to configure.
Enter the system user name and the group that will own the configured files.
For information on setting up system users and groups, see 1.1 Creating UNIX System Users and Groups.
Configuration Directory Server Panel
Enter your Configuration Directory LDAP URL, Administrator and Password. This is taken from the Administration Server configuration. Note that this is for Messaging Server 6 2005Q4 and earlier, later versions do not store configuration data in Directory Server and do not use the Administration Server.)
Gather the Configuration Server LDAP URL from your Directory Server installation. See the Directory Server Installation worksheet from Table D–1.
The Directory Manager has overall administrator privileges on the Directory Server and all Sun Java System servers that make use of the Directory Server (for example, the Messaging Server). It also has full administration access to all entries in the Directory Server. The default and recommended Distinguished Name (DN) is cn=Directory Manager and is set during Directory Server configuration.
If you select something other than the default, you will have a mismatch between the Administration Server and the configuration Directory Server. This will require manual post-configuration steps. So modify this entry only if you really know what you are doing.
User/Group Directory Server Panel
Enter your Users and Groups Directory LDAP URL, Administrator and Password.
Gather the User/Group Server LDAP URL information from the host and post number information from your Directory Server installation. See the Directory Server Installation worksheet from Table D–1.
The Directory Manager has overall administrator privileges on the Directory Server and all Sun Java System servers that make use of the Directory Server (for example, the Messaging Server) and has full administration access to all entries in the Directory Server. The default and recommended Distinguished Name (DN) is cn=Directory Manager and is set during Directory Server configuration.
If you are installing against a replicated Directory Server instance, you must specify the credentials of the replica, not the master directory.
Postmaster Email Address
Enter a Postmaster Email Address.
Select an address that your Administrator will actively monitor. For example, email@example.com for a postmaster on the siroe domain. This address cannot begin with “Postmaster.”
The user of the email address is not automatically created. Therefore, you will need create it later by using a provisioning tool.
Password for administrator accounts
Enter an initial password that will be used for service administrator, server, user/group administrator, end user administrator privileges as well as PAB administrator and SSL passwords.
After the initial runtime configuration, you might change this password for individual administrator accounts. For more information, see 4.1 To Modify Your Passwords.
Default Email Domain
Enter a Default Email Domain.
This email domain is the default that is used if no other domain is specified. For example, if siroe.com is the default email domain, then the domain to which messages addressed to user IDs without a domain will be sent.
If you are using the Delegated Administrator CLI, the command-line interface for provisioning users and groups with Sun LDAP Schema 2, you will want to specify the same default domain during its configuration. For more information, see the Sun Java System Delegated Administrator 6.4 Administration Guide.
Enter an Organization DN under which users and groups will be created. The default is the email domain prepended to the user/group suffix.
For example, if your user/group suffix is o=usergroup, and your email domain is siroe.com, then the default is o=siroe.com, o=usergroup (where o=usergroup is your user/group Directory suffix which was specified in 1.1 Creating UNIX System Users and Groups.
If you choose the same user/group Directory suffix as your Organization DN, you may have migration problems if you decide to create a hosted domain. If you want to set up a hosted domain during initial runtime configuration, then specify a DN one level below the User/Group suffix.
Ready to Configure
The configuration program will check for enough disk space on your machine and then outline the components it is ready to configure.
To configure the Messaging components, select Configure Now. To change any of your configuration variables, select Back. Or to exit from the configuration program, select Cancel.
Starting Task Sequence, Sequence Completed, and Installation Summary Panels
You can read the installation status by selecting Details on the final Installation Summary page. To exit the program, select Close.
A log file is created in msg-svr-base/install/configure_YYYYMMDDHHMMSS.log, where YYYYMMDDHHMMSS identifies the 4-digit year, month, date, hour, minute, and second of the configuration.
An initial runtime configuration is now set up for your Messaging Server. To change any configuration parameter, refer to other parts of this document for instructions on doing so.
To start Messaging Server, use the following command: