Messaging Server (Sun Java Enterprise System 2005Q4 Installation Planning Guide)

Sun Java Enterprise System 2005Q4 Installation Planning Guide

Messaging Server

Examine your deployment architecture for computer systems with instances of Messaging Server.

Messaging Server provides mail collection, storage, and delivery services. Messaging Server's services can be accessed through Communications Express, Portal Server, and third-party email clients.

Messaging Server has a solution-level dependency on a source of user and group data. The user and group data contains account names and passwords that are used to verify access to messaging services. The user and group data also identifies user's mail servers and other information needed to deliver mail. This information is typically in an LDAP directory managed by Directory ServerTherefore, it is logical to install and configureAccess Manager after Directory Server.

If your solution uses single sign-on, Messaging Server is a consumer of Access Manager services. In single sign-on solutions, Messaging Server must be installed and configured after both Directory Server and Access Manager are installed and configured.

In order to use Messaging Server with an LDAP directory managed by Directory Server, the Directory Preparation Tool must be run on the computer that is running the Directory Server instance. Therefore, the Directory Preparation Tool is covered as part of Messaging Server installation.

Installing and configuring Messaging Server modifies the LDAP directory tree, as described in Developing Your User Management Specifications. This modification adds a branch to the tree that represents the email domain managed by the Messaging Server instance. Information about users in the email domain is added to this email domain branch. If your solution uses single-sign on, all of the other components in the solution, such as Calendar Server, should also store their user data in the email domain branch. Therefore, it is logical to install and configure Messaging Server before installing any other components that might use the email domain branch.

Basic Installation Procedures for Messaging Server

Determine which redundancy strategy, if any, your solution is using for messaging services.
- If your solution uses load-balancing.
- If your solution uses clustered messaging services, the Sun Cluster software must be installed, configured, and verified before Messaging Server.
Use the Java ES installer to install Messaging Server on all computers systems specified in your deployment architecture. The installer does not configure instances of Messaging Server.
Run the Directory Preparation Tool on the computer that is running Directory Server.
Run the Messaging Server configuration wizard.
1. When you configure Messaging Server you must specify the Directory Server instance where information about Messaging Server users is stored.
2. When you configure Messaging Server you supply the name of the LDAP directory branch that will represent the email domain managed by the Messaging Server instance. The Messaging Server configuration wizard adds this branch to the tree.
Start and verify all instances of Messaging Server.
If your solution includes single sign-on, configure Messaging Server for single sign-on, restart Messaging Server, and verify functioning of single sign-on.
If your solution includes Sun Cluster software, install, configure, start, and verify the Sun Cluster Agent for Messaging Server.
If your solution uses load balancing for the Administration Server instances, verify that the load balancer is working properly.

Choosing Configuration Values for Messaging Server

For each Messaging Server instance in your solution, you must input values that configure the instance to interoperate with the other components in the solution. For example, if your solution uses Access Manager single sign-on, the Messaging Server instances must be configured to interoperate with Access Manager. Use Table 3–9 to help you choose configuration values.

Table 3–9 Key Configuration Values for Messaging Server Instances


Input Field	Choosing a Value for Your Solution
Enter FQHN	The fully qualified domain name for the computer on which you are configuring Messaging Server.
Select Components to Configure	Select the components that your solution specifies for this computer. This information is available in the deployment architecture. For more information, see Analyzing a Deployment Architecture.
Enter Username and Enter Group	You specify the username and group under which the Messaging Server instance will run.
Config Server LDAP URL, Bind As, Password.	You specify the Directory Server instance that your solution uses for configuration data, and the directory manager account and password. The Messaging Server configuration wizard writes configuration data about the Messaging Server instance to this directory.
User/Group Server LDAP URL, Bind As, Password.	You specify the Directory Server instance that your solution uses for user and group data, and the directory manager account and password. The Messaging Server configuration wizard adds the mail domain branch to this Directory Server's directory tree. The Messaging Server looks up user and group data in this directory.
Password for All Admin Accounts	You establish the password used for all of the Messaging Server instance's administrator accounts.
Default Email Domain	You establish the email domain for which the Messaging Server instance provides mail services.
Enter Org DN	You establish the LDAP directory tree branch that will store data about users in the default email domain. The DN for the directory tree branch can be specified as o=, ou=, or dc=,dc= If your solution uses a single user entry to authenticate and authorize multiple services, you must configure the other components to use the LDAP branch you specify in this field for user and group data.

Adding Installation Procedures for Messaging Server to Your Installation Plan

To add installation and configuration instructions for Messaging Server, do the following:

If theMessaging Server instances are load balanced, the first instruction in your installation plan is confirming that the load balancer is functioning before anyJava ES software is installed.
If your solution uses Sun Cluster software, Messaging Server has a local dependency on Sun Cluster software. Do the following:
1. Each computer that runs an instance of Messaging Server must a Sun Cluster node. The Sun Cluster software must be installed, configured, and verified before Messaging Server is installed.
2. In your plan, list all of the computers that run clustered Messaging Server instances.
3. For each computer, add the instructions for installing Sun Cluster software. For the Sun Cluster software installation instructions, see Sun Cluster Software. For an example installation plan that shows how to run the installer multiple times on a computer to set up clustered components, see Table 3–4.
Next, in your plan, list all of the computers with Messaging Server instances.

Tip –
If your solution uses clustered Messaging Server instances, this is the second time the installer runs on the computers designated for Messaging Server.
1. In your plan, for each computer, add an instruction to run the Java ES installer and select Messaging Server.
2. If the computers that run Access Managerare already listed in your plan (for example, if Directory Server is installed on the same computer) add an instruction to select Access Manager. You can install Access Manager at the same time as Directory Server, even if you use the configure now option, but your plan must put the instructions for configuring, starting, and verifying the Directory Server instances before the instructions for configuring or starting any instance Access Manager.
Underneath each Messaging Server instance, list the key values for configuring the instance. Use to help you select configuration values.
Directory Preparation Tool-need table of configuration values.
For each computer, add an instruction to start and verify the Messaging Server instance.
If the Messaging Serverinstances are load balanced, add an instruction to verify operation of the load balancer.
If the Messaging Server instances are clustered, add an instruction to complete the cluster configuration by installing the Sun ClusterAgents for Messaging Server and verifying their operation. You can find the instructions for the Sun Cluster Agent in Sun Cluster Software.