Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 2004Q2 Deployment Example Series: Evaluation Scenario 

Chapter 3
Configuring and Verifying the Evaluation Deployment

This chapter describes how to configure, start, and verify the components that you installed on your evaluation_host. This chapter contains the following sections:

About the Configuration Process

The installation procedure described in Chapter 2 accomplishes the following:

Before you can use your evaluation deployment, you must start the components and configure the components not configured by the installer. You perform the procedures in the following order:

  1. Start and verify Directory Server. You start Directory Server first because all the other components use directory services.
  2. Start Web Server. Starting Web Server starts the components that run in the Web Server web container, which are Identity Server and Portal Server. Identity Server must be running before you start the components that depend on Identity Server’s authentication services.
  3. Verify that Identity Server is running. Identity Server must be running because the other components use Identity Server’s authentication services.
  4. Verify that Portal Server is running.
  5. Configure Directory Server for Schema 2.
  6. Create, configure, and start an instance of Messaging Server.
  7. Create, configure, and start an instance of Calendar Server.

After you complete these procedures, you can use Java Enterprise System portal, messaging, and calendar services.

Note

Throughout this document you see commands that contain the variables evaluation_host and evaluation_domain. When you execute the commands you must substitute the host name and domain name that you are using. These variables are defined as follows:

  • evaluation_host: The fully-qualified name of the system on which you are installing Java Enterprise System components. For example, if you are installing on a system named evaluation.example.com, your evaluation_host is evaluation.example.com. You use evaluation_host to configure communication between components. For example, you configure components to connect to Directory Server at evaluation_host:389. You also use evaluation_host in the URLs for web-based interfaces to Identity Server, Messaging Server, Calendar Server, and Portal Server.
  • evaluation_domain: The name of the DNS domain for the system on which you are installing components. For example, if you are installing on a system named evaluation.example.com, your evaluation_domain is example.com. You use evaluation_domain as your default mail domain. It is also the default name for the LDAP domain the installer creates in your Directory Server.

Starting and Verifying the Directory Server Default Instance

Directory Server provides directory services that support login and authentication for the portal, messaging, and calendar services. You begin verifying your evaluation deployment by verifying that you can start and administer the default Directory Server instance.

In this section you learn the following:

Starting Administration Server

Before starting the Directory Server default instance, start Administration Server. Administration Server is the administration tool for Directory Server.

    To Start Administration Server
  1. Change directory to the server root directory:

    2. cd /var/opt/mps/serverroot

  2. Run the command to start Administration Server:

    3. ./start-admin

    Administration Server starts and displays a series of start-up messages. The startup process might take a few moments. When startup is complete, the following message is displayed:

    startup:server started successfully

Starting the Directory Server Default Instance

After you start Administration Server, start the default Directory Server instance.

    To Start the Directory Server Default Instance
  1. Change directory to the directory for the default Directory Server instance. The directory name is includes the unqualified name of the host system.

    2. cd /var/opt/mps/serverroot/slapd-unqualified_evaluation_host

  2. Run the command to start Directory Server:

    3. ./start-slapd

    Directory Server starts without a message.

Using Server Console to Verify the Directory Server Instance

After you start Directory Server, start Server Console and verify the LDAP directory configuration.

    To Verify the LDAP Directory Configuration
  1. Change directory to the serverroot directory:

    2. cd /var/opt/mps/serverroot

  2. Run the command to start Server Console:

    3. ./startconsole &

    The Sun Java System Server Console Login dialog box is displayed.

  3. Type your administrator ID (admin) and password (password) and click OK.

    4. The Server Console is displayed, displaying information about the servers and applications in your Administration Server domain. Figure 3-1 shows information for the example.com domain. You see similar information for your domain.

    Figure 3-1  Server Console’s Servers and Applications Tab
    Screen capture; displays the nodes described in step 4.

  4. Expand the nodes on the Servers and Applications tab and locate the node that represents the default Directory Server instance.
    1. The top-level node represents your default Administration Server domain. In Figure 3-1 this is the node labeled example.com. In your console window, it will be labeled with your evaluation_domain.
    2. On the next level, the nodes represent the systems in your Administration Server domain. In Figure 3-1, the example.com domain includes one system, named evaluation.example.com. In your console window, it will be labeled with your evaluation_host.
    3. On the next level is a node labeled Server Group. This node groups the component instances that are running on your evaluation_host. In Figure 3-1, the Server Group node groups the component instances that are running on evaluation.example.com.
    4. On the next level, the nodes represent the individual component instances in your Server Group. One of these nodes represents the default Directory Server instance. In Figure 3-1, this is the node labeled Directory Server (evaluation.example.com). In your console window it will be labeled Directory Server (evaluation_host).

      5. Double-click the node that represents your default Directory Server instance. The Sun Java System Directory Server window is displayed.

  5. Click the Directory tab.

    6. The LDAP directory tree is displayed.

    Figure 3-2  Default LDAP Directory Tree
    Screen capture; Directory Server window. People container is selected and the three users described in text are displayed.

  6. Verify the default LDAP domain set up by the installer.

    7. Your default LDAP domain has the same name as your evaluation_domain. The default LDAP domain node is labeled with the individual domain components. For example, if your evaluation_domain is example.com, the default LDAP domain node is labeled dc=example,dc=com. Figure 3-2 shows the default LDAP domain node for example.com. You see a similar display for your LDAP domain.

  7. Locate the sample LDAP directory entries set up by the installer.
    1. Expand the default LDAP domain node.
    2. Click the People container.

      3. The right pane displays the contents of the People container. Figure 3-2 shows the People container for the default Directory Server instance on evaluation.example.com. You see a similar display for the Directory Server instance on your evaluation_host.

  8. Verify that the People container contains entries for amAdmin, anonymous, and authlessanonymous.

    9. These entries confirm that the Java Enterprise System installer populated the LDAP directory with the sample data you requested during installation.

  9. Leave the Server Console running.

Starting the Web Server Default Instance

After you start Directory Server, you start the Web Server default instance. Starting Web Server also starts Identity Server and Portal Server.

    To Start the Web Server Default Instance
  1. Change directory to the Web Server default instance directory. The directory name includes the fully qualified name of the system on which you installed Web Server.

    2. cd /opt/SUNWwbsvr/https-evaluation_host

  2. Run the command to start Web Server:

    3. ./start

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

    startup: server started successfully

Verifying the Identity Server Default Instance

Starting the Web Server default instance starts the two components that run in Web Server’s web container, Identity Server and Portal Server.

In this section, you learn the following:

    To Log In to Identity Server Administration Console and Verify Identity Server
  1. In a web browser, open the following URL:

    2. http://evaluation_host/amconsole/index.html

    The Login page is displayed.

  2. Type your administration user ID (amadmin) and password (password). Click Log in.

    3. The console displays information about the default Identity Server domain.

  3. To confirm that your Identity Server is configured correctly, check the Identity Server domain name. It should match the first domain component in your evaluation_domain. For example, if your domain is example.com, the console displays example.

    4. In Figure 3-3 the console displays information about the example domain. The domain name is displayed in the left panel, just below the Identity Management tab.

    Figure 3-3  Identity Server Administration Console
    Screen capture; shows values described in step 3.

  4. Log out of the Identity Server console. Click Logout in the upper right corner of the page.

Verifying the Portal Server Default Instance

The installation procedure in Chapter 2 creates a sample portal desktop. In this section you open the sample portal desktop to verify that Portal Server is running.

    To View the Sample Portal Desktop and Verify the Default Portal Server Instance
  1. In your web browser, open the following URL:

    2. http://evaluation_host/portal/dt

    The Portal Server sample desktop is displayed. Figure 3-4 shows the sample desktop. Opening the sample desktop verifies that your default Portal Server instance is running.

    Figure 3-4  Sample Portal Desktop
    Screen capture; shows sample desktop's Login and Sample JSP channels.

Configuring Directory Server for LDAP Schema 2

The installation procedure in Chapter 2 creates an LDAP directory with a default LDAP schema. Before you configure Messaging Server and Calendar Server instances, you must apply Schema 2 to your LDAP directory tree.

Schema 2 adds LDAP attributes that support shared user entries. When you create user entries in a Schema 2 directory tree, the user entries can authenticate through Identity Server and log in to any service provided by a Java ES component.

In this section you learn the following:

Applying LDAP Schema 2 to Your Directory Tree

This procedure runs the Directory Server Preparation Tool (a Perl script named comm_dssetup.pl) and applies Schema 2 to your LDAP directory tree.

Note

The script displays a series of prompts. You answer most of the prompts by pressing Enter to accept the default value. The default values identify your default Directory Server instance.

    To Apply Schema 2 to Your Directory Tree
  1. Change directory to the preparation tool directory:

    2. cd /opt/SUNWmsgsr/lib

  2. Run the command that starts the preparation tool:

    3. perl comm_dssetup.pl

    The preparation tool displays a series of messages and then prompts you: Do You Want To Continue? [Y].

  3. Press Enter to accept the default value.

    4. The preparation tool prompts you: Enter the Full Path to the Directory Where The Sun ONE Directory Server was Installed.

  4. Press Enter to accept the default value (/var/opt/mps/serverroot).

    5. The preparation tool displays a numbered list of directory server instances and prompts you: Which Instance Do You Want? [1].

  5. Choose the default Directory Server instance created by the Java Enterprise System installer. For the evaluation deployment there is normally only one instance on your evaluation_host.
    • If the default value for this prompt (1) specifies the correct instance (the instance name ends with your evaluation_host), press Enter to accept the default value.
    • If there is more than one Directory Server instance, type in the number that specifies the default Directory Server instance and press Enter.

      • The preparation tool prompts you: Please Enter The Directory Manager DN [cn=Directory Manager].

  6. Press Enter to accept the default value (cn=Directory Manager).

    7. The preparation tool prompts you for the Directory Manager password.

  7. Type password and press Enter.

    8. The preparation tool prompts you: Will This Directory Server Be Used For Users/Groups? [Yes].

  8. Press Enter to accept the default value.

    9. The preparation tool prompts you: Please Enter The Users/Groups Base Suffix [o=usergroup].

  9. Type the domain components that identify your evaluation_domain. For example, if your evaluation_domain is example.com, you type dc=example,dc=com.

    10. Note

    If your evaluation_domain name includes a subdomain, you must specify each domain component of the name separately. For example, if your evaluation_domain is my.example.com, type dc=my,dc=example,dc=com.

    The preparation tool displays a list of Sun ONE LDAP schemas and prompts you: Please Enter The Schema Type (1, 1.5, 2) [2].

  10. Confirm that the default value is 2. Press Enter.

    11. The preparation tool prompts you: Do You Want To Update The Schema Files? [Yes].

  11. Press Enter to accept the default value (Yes).

    12. The preparation tool prompts you: Do You Want To Configure New Indexes? [Yes].

  12. Press Enter to accept the default value (Yes).

    13. The preparation tool prompts you: Do You Want To Reindex The New Indexes Now? [yes].

  13. Press Enter to accept the default value (yes).

    14. The preparation tool displays a summary of the values that you entered and prompts you: Do You Want To Continue? [Y].

  14. Review the values you entered. Press Enter to accept the default value (y).

    15. The preparation tool displays a series of informational messages, beginning with “generating files.” This may take a few moments.

    The preparation tool generates script files and then prompts you: Ready to execute the script now. Do you want to continue? [Y].

  15. Press Enter to accept the default value (Y).

    16. The preparation tool executes the generated scripts to configure the Directory Server instance. This may take a few moments.

    The scripts display a long series of informational messages that ends with the following:

    Successful Completion

You have configured your directory tree for Schema 2.

Verifying the Directory Tree

This procedure describes how to use the Server Console to verify the configuration performed by the Directory Server Preparation Tool.

    To Verify that Directory Server is Configured With Schema 2
  1. Return to the Server Console’s Directory Server Window.
  2. In the View menu, choose Refresh.

    3. The directory tree display is refreshed.

    Figure 3-5  Schema 2 Directory Tree
    Screen capture; shows the new LDAP entries described in step 3.

  3. Review the new directory structure.

    4. Compare Figure 3-5 and Figure 3-2. Notice the new LDAP entities in the dc=example,dc=com branch. You see similar changes in your directory tree.

This verifies that Schema 2 is applied to the directory tree.

Configuring Messaging Server

In this section you learn the following:

Configuring a Messaging Server Instance

This procedure runs the Messaging Server configuration wizard to create and configure a Messaging Server instance.

    To Create and Configure a Messaging Server Instance
  1. Change directory to the Messaging Server directory:

    2. cd /opt/SUNWmsgsr/sbin

  2. Run the command that starts the configuration wizard:

    3. ./configure

    The configuration wizard’s Welcome page is displayed.

  3. Click Next.

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

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

    5. The Create New Directory? dialog box is displayed.

  5. Click Create Directory.

    6. Note

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

    The Select Components to Configure page is displayed.

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

    7. The Messaging Server User and Group page is displayed.

  7. Do the following:
    • In the Enter Unix Username text field, confirm that the default value is mailsrv.
    • In the Enter Unix Group text field, confirm that the default value is mail.

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

      Figure 3-6  Configuration Directory Server Page
      Screen capture; text fields display the values described in step 8.

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

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

  9. 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 3-7  Postmaster Email Address Page
      Screen capture; text field displays the email address described in step 10.

  10. Do the following:
    • In the Enter Email Address text field, type test.user@evaluation_domain

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

      Figure 3-8  Password for All Admin Accounts Page
      Screen capture; text fields display the values specified in step 11.

  11. 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 3-9  Default Email Domain Page
      Screen capture; Enter Email Domain text field displays evaluation_domain, as described in text.

  12. Do the following:
    • In the Enter Email Domain text field, confirm that the default value is evaluation_domain.

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

  13. Do the following:
    • In the Enter Organization DN text field, confirm that the default value is o=evaluation_domain,dc=domain_componnent1, dc=domain_component2. If your domain contains more than two domain components, you must specify all of them. For example, if your domain is my.example.com, you must type dc=my,dc=example,dc=com.

      • Note

      This configuration wizard will create a new organization in your LDAP tree, with the name you supply in the Enter Organization DN text field. You will add your Java ES users to your new LDAP organization.

      Click Next. The Ready to Configure page is displayed.

  14. Review the information. Click Configure Now.
  15. When the configuration process is complete, the Installation Summary page is displayed.
  16. Review the summary, and then click Close.
  17. Change directory to the Messaging Server directory:

    18. cd /opt/SUNWmsgsr/sbin

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

    19. ./configutil -o service.http.port -v 88

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

  19. Run the command that starts Messaging Server:

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

Verifying the Directory Tree

This procedure describes how to use the Sun Java System Server Console to verify that the Messaging Server configuration tool performed additional directory tree configuration.

    To Verify that Messaging Server Configuration Modified the Directory Tree
  1. Return to the Server Console’s Directory Server Window.
  2. In the View menu, choose Refresh.

    3. The directory tree display is refreshed.

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

    4. Confirm that there is a new node for an LDAP organization. In Figure 3-5 the default LDAP domain node (dc=example,dc=com) has a sub node labeled example.com. The example.com node represents the LDAP organization that was created by the Messaging Server configuration tool. The full LDAP name for the new organization is o=example.com,dc=example,dc=com. In your directory tree, you see a similar node for your new organization.

    Note

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

  4. Click the node for you new LDAP organization.

    5. The right pane displays the contents of the organization.

  5. Confirm that the organization has the iplanet-am-managed-people-container object class.
    1. In the right pane, right-click the People container, and then choose Edit with Generic Editor from the menu.

      2. The generic editor is displayed.

      Figure 3-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 Schema 2 directory tree for Java Enterprise System messaging services.
    3. Click OK to close the generic editor.
  6. Exit the console.

Configuring a Calendar Server Instance

In this section you learn the following:

    To Create and Configure a Calendar Server Instance
  1. Change directory to the Calendar Server directory:

    2. cd /opt/SUNWics5/cal/sbin

  2. Run the command that starts the configuration wizard:

    3. ./csconfigurator.sh

    The configuration wizard’s Welcome page is displayed.

  3. Click Next to continue.

    4. The Administration, User Preferences and Authentication page is displayed.

    Figure 3-12  Administration, User Preferences and Authentication Page
    Screen capture; text fields show values specified in step 4.

  4. Do the following:
    • In the LDAP Server Host Name text field, confirm that the default value is evaluation_host.
    • In the LDAP Server Port text field, confirm that the default value is 389.
    • In the Directory Manager DN text field, type cn=Directory Manager.You must put a space between Directory and Manager.
    • In the Directory Manager Password text field, type password.
    • In the Base DN text field, type the DN for your LDAP organization. For example, if your LDAP organization is example.com, you type o=example.com,dc=example,dc=com.

      • Note

      The default name for your LDAP organization is based on your evaluation_domain. The form for the organization name is: o=evaluation_domain,dc=domain_component1,dc=domain_component2.

      If your evaluation_domain includes a subdomain, you must specify each domain component of the name separately. For example, if your evaluation_domain is my.example.com, type o=my.example.com,dc=my,dc=example,dc=com.

    • In the Administrator User ID text field, confirm that the default value is calmaster.
    • In the Administrator Password text field, type password.

      • Click Next. The wizard verifies the connection to the default Directory Server instance. A Question dialog box is displayed.

  5. Click Create It to create the calmaster user.

    6. The Email and Email Alarms page is displayed.

    Figure 3-13  Email and Email Alarms Page
    Screen capture; displays the values described in step 6.

  6. Do the following:
    • In Email Alarms, confirm that the default selection is Enabled.
    • In the Administrator Email Address text field, type test.user@evaluation_domain.
    • In the SMTP Host Name text field, confirm that the default value is evaluation_host.

      • Click Next. The Problem Connecting to SMTP Host dialog box might be displayed.

  7. In the Problem Connecting to SMTP Host dialog box, click Accept, and then click Next to continue.

    8. The Runtime Configuration page is displayed.

    Figure 3-14  Runtime Configuration Page
    Screen capture; fields display the values described in step 8.

  8. Do the following:
    • In the Service Port text field, type 89.
    • In the Maximum Sessions text field, confirm that the default value is 5000.
    • In the Maximum Threads text field, confirm that the default value is 20.
    • In the Number of Server Processes text field, confirm that the default value is 1.
    • In the Runtime User ID text field, confirm that the default value is icsuser.
    • In the Runtime Group ID text field, confirm that the default value is icsgroup.
    • Confirm that Start After Successful Configuration is selected.
    • Confirm that Start on System Startup is selected.

      • Click Next. The Create New User ID dialog box is displayed.

  9. Click Create User ID.

    10. The Directories to Store Configuration and Data Files page is displayed.

  10. In the Directories to Store Configuration and Data Files page, click Next to accept the default values.

    11. The Create New Directory? dialog box is displayed.

    Note

    If you previously installed and uninstalled Java Enterprise System, a different message will appear, stating that /var/opt/SUNWmsgsr is not empty. Click to overwrite the existing directory. Do this for each directory.

  11. In the Create New Directory? dialog box, click Create Directory. Do this for each new directory.

    12. The Ready to Configure page is displayed.

  12. Click Configure Now.

    13. When configuration is complete, the Configuration Summary page is displayed.

  13. Review the details and click Close.

    14. Note

    In the Runtime Configuration page, you selected the Start after successful configuration option. Calendar Server now starts automatically.

You have verified, configured, and started all of the servers in the evaluation deployment.



Previous      Contents      Index      Next     

Part No: 817-5417-10.   Copyright 2004 Sun Microsystems, Inc. All rights reserved.