test

Sun Java Enterprise System 2005Q1 Deployment Example Series: Evaluation Scenario

Configuring Messaging Server

In this section you learn the following:

ProcedureTo Create and Configure a Messaging Server Instance

This procedure runs the Messaging Server configuration wizard to create and configure a Messaging Server instance. For a summary of the input values, see Messaging Server Configuration Wizard Details.

Steps

  1. Change directory to the Messaging Server directory:


    cd /opt/SUNWmsgsr/sbin

  2. Run the command that starts the configuration wizard:


    ./configure

    The configuration wizard’s Welcome page is displayed.

  3. Click Next.

    The Fully Qualified Host Name page is displayed.

  4. Confirm that the default value specifies your evaluation_host.

    Click Next. The Select Directory to Store Configuration and Data Files page is displayed.

  5. Click Next to accept the default value of /var/opt/SUNWmsgsr.

    The Create New Directory? dialog box is displayed.

  6. Click Create Directory.

    Tip –

    If you previously installed and uninstalled Java ES, a different dialog box appears, stating that /var/opt/SUNWmsgsr is not empty. Click Accept Anyway to overwrite the existing instance directory.

    The Select Components to Configure page is displayed.

  7. Click Next to accept the default values (Message Transfer Agent, Message Store, and Messenger Express are selected).

    The Messaging Server User and Group page is displayed.

  8. Do the following:

    • In the Enter Username text field, confirm that the default value is mailsrv.

    • In the Enter Group text field, confirm that the default value is mail.

    Click Next. The Configuration Directory Server Panel page is displayed.

    Figure 6–5 Configuration Directory Server Page

    Screen capture; shows the new LDAP entries described in step 3.

  9. Do the following:

    • In the Config Server LdapURL text field, confirm that the default value is ldap://evaluation_host :389.

    • In the Bind text field, confirm that the default value is cn=Directory Manager. There must be a space between Directory and Manager.

    • In the Password text field, type password.

      Tip –

      Supplying these values specifies your default Directory Server instance and administrator account.

    Click Next. The User/Group Directory Server Panel page is displayed.

  10. Confirm the following default values:

    • In the User/Group Server LdapURL text field, confirm that the default value is ldap://evaluation_host:389.

    • In the Bind text field, confirm that the default value is cn=Directory Manager. There must be a space between Directory and Manager.

    • In the Password text field, confirm that the default value is password.

    Click Next. The Postmaster Email Address page is displayed.

    Figure 6–6 Postmaster Email Address Page

    Screen capture; text fields display the values described in step 8.

  11. Do the following:

    • In the Enter Email Address text field, type admin@examplecorp.com .

    Click Next. The Password For All Admin Accounts page is displayed.

    Figure 6–7 Password for All Admin Accounts Page

    Screen capture; text field displays the email address described in step 10.

  12. Type the following values to establish an administrative password for Messaging Server:

    • In the Enter Password text field, type password.

    • In the Re-enter Password to Verify text field, type password .

    Click Next. The Default Email Domain page is displayed.

    Figure 6–8 Default Email Domain Page

    Screen capture; text fields display the values specified in step 11.

  13. Do the following:

    • In the Enter Email Domain text field, type examplecorp.com.

    Click Next. The Organization DN for the Default Email Domain page is displayed.

    Figure 6–9 Organization DN for the Default Email Domain Page

    Screen capture; Enter Email Domain text field displays evaluation_domain, as described in text.

  14. Confirm that the default Organization DN is o=examplecorp.com,o=examplecorp.

    Tip –

    The Messaging Server configuration wizard will create a new branch in your LDAP tree, with the name you supply in the Enter Organization DN text field. You add your Java ES users in this branch.

    Click Next. The Ready to Configure page is displayed.

  15. Review the information. Click Configure Now.

    The Ports in Use dialog box is displayed.

    Tip –

    You specify the ports for your Messaging Server instance later in this procedure.

  16. Click OK.

    The configuration process continues. When the configuration process is complete, the Sequence Completed page is displayed.

  17. Click Next.

    The Installation Summary page is displayed.

  18. Review the installation summary, and then click Close.

  19. Change directory to the Messaging Server directory: 


    cd /opt/SUNWmsgsr/sbin

  20. Run the command that specifies the ports for communicating with Messaging Server:


    ./configutil -o service.http.port -v 88
./configutil -o service.http.sslport -v 448

  21. Run the command that starts Messaging Server:


    ./start-msg

    The startup process displays a series of startup messages. The startup process might take a few moments. When startup is complete, the following message is displayed:


    starting job-controller server

    You have created and started a Messaging Server instance.

ProcedureTo Verify that Messaging Server Configuration Modified the Directory Tree

This procedure describes how to use the Sun Java System Server Console to verify that the Messaging Server added the o=examplecorp.com,o=examplecorp organization to the directory tree.

Steps

  1. Return to the Server Console’s Directory Server Window.

  2. In the View menu, choose Refresh.

    The directory tree display is refreshed.

    Figure 6–10 Schema 2 Directory Tree Modified by Messaging Server Configuration

    Screen capture; directory server window shows the LDAP entries described in step 3.

  3. Review the modified directory tree.

    Confirm that there is a new node for examplecorp.com. Your display should resemble Figure 6–10. The examplecorp.com node represents the LDAP organization created by the Messaging Server configuration tool. The full LDAP DN for the organization is o=examplecorp.com,o=examplecorp.

    Tip –

    Your new LDAP organization supports single sign-on and proxy authentication. When you create LDAP entries for Java ES users, you add them to this LDAP organization.

  4. Click the examplecorp.com node.

    The right pane displays the contents of the organization.

  5. Confirm that the organization has the iplanet-am-managed-people-container object class. Do the following:

    1. In the right pane, right-click the People container, and then choose Edit with Generic Editor from the menu.

      The generic editor is displayed.

      Figure 6–11 Generic Editor

      Screen capture; generic editor's Object Class text field displays iplanet-am-managed-people-container.

    2. In the generic editor, confirm that the object class text field contains iplanet-am-managed-people-container.

      This verifies that you have successfully configured your directory tree for Java Enterprise System messaging services.

    3. Click OK to close the generic editor.

  6. Exit the console.

ProcedureTo Verify Your Messaging Server Instance

This procedure shows you how to log in to your Messaging Server instance, using the administrator account and the default web interface.

Steps

  1. In your web browser, open this URL:


    http://evaluation_host:88

    The Messenger Express login page is displayed.

  2. Type these values:

    • User ID: admin

    • Password: password

    Click Log in. The Messenger Express main window is displayed. You see a display similar to Figure 6–12. This confirms that your Messaging Server instance is configured and running.

    Figure 6–12 Messenger Express Main Window

    Screen capture; Messenger Express main window's initial display. There are no received messages.

  3. Click Logout, in the upper right corner of the Messenger Express main window.

    This verifies that you successfully configured and started your Messaging Server instance.