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