Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 2003Q4 Deployment Example Series: Evaluation Scenario 

Chapter 3
Configuring Java Enterprise System

This chapter describes how to configure and start the components that you use in this Java Enterprise System evaluation. You start the components one after the other, in a specific sequence, until the Java Enterprise System is functioning as a whole. You first start Application Server and Directory Server, because these components provide services that are required by other components.

The Java Enterprise System installation program created runnable instances of Directory Server, Application Server, Identity Server, and Portal Server. You start these instances and verify that they are running properly.

The installer does not create runnable instances of Messaging Server and Calendar Server. This chapter describes how to use the configuration wizards for these products to create instances and then start the instances.

This chapter contains the following sections:

About the Configuration Process

Running the Java Enterprise System installer accomplished the following:

This chapter describes how to start and use the default instances that the installer created. It also describes how to create and start instances of Messaging Server and Calendar Server.

Note

In a production system, you typically install the components only once. You may create additional instances as a system administration task when your enterprise’s scalability needs increase.

Verifying the Directory Server Default Instance

The services provided by Directory Server and Application Server support many of the other Java Enterprise System components. The evaluation begins by verifying that you can start and administer the default Directory Server and Application Server instances.

In this section you start the Directory Server default instance and then use Administration Server to verify that the default instance is configured correctly.

You learn the following:

Verifying the Directory Server Installation

Before starting the Directory Server default instance, verify the Directory Server installation.

    To Review the Installation Log File and Verify the Installation
  1. Navigate to the log file directory:

    2. cd /var/sadm/install/logs

  2. Use the ls command to list the contents of the directory:

    3. ls

    You see a list of log files for Java Enterprise System components.

  3. Open the install log for Directory Server. The file name includes a date stamp. It resembles Directory_Server_install.Bmmddxxxx.

    4. In the log file, you should see messages indicating that Sun ONE Directory Server, Sun ONE Directory Console Support, and Sun ONE Basic Libraries were installed, and that the overall installation completed successfully.

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. Navigate to the server root directory:

    2. cd /var/opt/mps/serverroot

  2. Run the start-admin command:

    3. ./start-admin

    Administration Server starts and displays a series of start-up messages that end with:

    startup:server started successfully

Starting the Directory Server Default Instance

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

    To Start the Directory Server Default Instance
  1. Navigate to the directory for the Directory Server instance you created with the installer. The instance directory name includes the name of the host computer. The following example uses the directory name for the Directory Server installed on host allinone:

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

    Tip

    Remember to substitute the host name that you are using.

  2. Run the start-slapd command:

    3. ./start-slapd

  3. Directory Server starts and displays the following message:

    4. node not a cluster member

    The message indicates that the computer on which you started Directory Server is not part of a Sun Cluster. The evaluation example does not use Sun Cluster, so this message is expected.

Using Sun ONE Server Console to Verify the Directory Server Instance

After starting Directory Server, start the Sun ONE Server Console. Server Console is the interface for Administration Server. You use it to administer Directory Server and other servers.

In this section you use the console to verify the default Directory Server instance and its contents.

    To Start and Use the Sun ONE Server Console
  1. Navigate to the serverroot directory:

    2. cd /var/opt/mps/serverroot

  2. Run the startconsole command:

    3. ./startconsole

    The Sun ONE Server Console Login dialog opens.

  3. Type your administrator user ID and password and click OK.

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

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

  4. Work with the nodes on the Servers and Applications tab.
    1. The top-level node represents the Administration Server domain. In Figure 3-1 this is the node labeled example.com. If necessary, expand the tree by double-clicking the top-level node.
    2. On the next level there are nodes representing the machines in the domain. In Figure 3-1, the example.com domain includes one machine, named allinone.example.com. If necessary, expand the tree by double-clicking the node that represents the machine on which you installed Java Enterprise System.
    3. On the next level is a node labeled Server Group. This node represents the Java Enterprise System servers running on the machine. In Figure 3-1, the Server Group node contains the Java Enterprise System servers that are running on allinone.example.com.
    4. On the next level are nodes representing the individual Java Enterprise System server instances currently running on the selected machine. In Figure 3-1, there are nodes for Sun ONE Administration Server, Sun ONE Directory Proxy Server, and Sun ONE Directory Server (allinone). You should see a similar display for your Administration Server domain.
    5. Double-click the Directory Server (allinone) icon in Server Group.

      6. The Sun ONE Directory Server window opens.

  5. In the Sun ONE Directory Server window:
    1. Click the Directory tab.

      2. The display refreshes and shows the contents of the directory server.

    2. Expand the dc=example,dc=com folder node.
    3. Click the People container.

      4. The window refreshes, and the contents of the People container are displayed in the right pane. Figure 3-2 shows the display for the Sun ONE Directory Server (allinone) instance. You should see a similar display for the host and domain names you are using.

      Verify that the People container contains entries for amAdmin, anonymous, authlessanonymous, and amService-srapGateway.

      Tip

      Remember to substitute the host and domain that you are using.

      Figure 3-2  Sun ONE Server Console’s Sun ONE Directory Server Window
      Screen capture; Sun ONE Directory Server window. People container is selected and the four users in People are displayed.

      These entries confirm that the Java Enterprise System installer populated the Sun ONE Directory Server with the sample data entries. (You requested the sample data entries on the installer’s Directory Server: Populate Data page. To review this, see To Supply Directory Server Information.)

  6. Exit the console.

Verifying the Application Server Default Instance

In this section you start the Application Server default instance and then use Application Server’s administrative console to verify that the default instance is configured correctly.

You learn the following:

Starting the Application Server Administration Server

    To Start the Application Server Administration Server Process
  1. Navigate to the directory for the Application Server Administration Server. This directory name includes the default application server domain, domain1. (Do not confuse this domain name with the Administration Server domain name.) The following example shows the directory name:

    2. cd /var/opt/SUNWappserver7/domains/domain1/admin-server/bin

  2. Run the startserv command:

    3. ./startserv

    The Application Server administration console starts up, displaying a sequence of startup messages that ends with:

    startup: server started successfully

Starting the Default Application Server Instance

This section shows you how to open the Application Server administration console and start the Application Server instance. To open the Application Server administration console:

  1. Using a web browser, open this URL:

    2. http://allinone.example.com:4848

    This opens the Prompt dialog.

    Tip

    Remember to substitute the host and domain that you are using.

  2. In the Prompt dialog, type your Application Server administrator user ID and password. Click OK.

    3. The main administration console window opens. It displays information about the server, including the available Application Server domains and instances. Figure 3-3 shows the console window for the example.com domain. It shows a Application Server domain named domain1 that contains an instance named server1. Domain1 and server1 were created by the Java Enterprise System installer.

    Figure 3-3  Sun ONE Application Server Console Window
    Screen capture; left pane displays contents of domain1. App Server Instances node is expanded, showing server1 sub-node.

  3. In the console window, start the server1 instance.
    1. In the App Server Instances pane, click server1.

      2. The console displays a message: Apply Changes Required

      This tells you that configuration information that you specified with the Java Enterprise System installer has not yet been applied to the server1 instance.

    2. Click the Apply Changes button.

      3. The console displays a message: Changes applied to instance.

    3. Click Restart.

      4. The server1 instance is started and the window displays a message: Instance Started.

The default Application Server instance is now running.

Using Application Server Online Documentation

This section shows you where to find the Application Server online documentation.

  1. In your web browser, type the URL http://allinone.example.com:81/.

    2. This opens the Application Server Getting Started documentation page.

    Tip

    Remember to substitute the host and domain that you are using.

  2. Familiarize yourself with Application Server online documentation by clicking the links on this page.

Verifying the Identity Server Default Instance

The Java Enterprise System installer configured a default instance of Identity Server that runs in the web container provided by Application Server. When you start the Application Server default instance, you also start the Identity Server default instance. (You specified this behavior in the installer’s Identity Server: Sun ONE Application Server page. To review, see Figure 2-7.)

In this section you use the Identity Server administration tool to verify that Identity Server is running.

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://allinone.example.com:81/amconsole

    Notice that you specified the URI amconsole on the installer’s Identity Server: Web Container for Running the Sun ONE Identity Services page.)

    The Login dialog opens.

    Tip

    Remember to substitute the host and domain that you are using.

  2. In the login dialog, type the Administration User ID (the default value is amadmin) and password. (You defined this ID and password on the installer’s Identity Server: Sun ONE Application Server page. To review, see Figure 2-7.) Click OK.

    3. The Sun ONE Identity Server administration console opens in the browser. Figure 3-4 shows the administration console displaying information about the example organization. Notice that the organization name is displayed and highlighted in the left panel, just below the word “Search.”

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

  3. Review the information displayed on the console.
    1. Notice that the Identity Management tab is selected by default.
    2. Both panes display the organization name in their title bars. In Figure 3-4, both panes display the name example.

      3. This confirms that Identity Server is running and configured for the example organization.

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

    5. The Logout page opens.

Verifying the Portal Server Default Instance

When you installed Java Enterprise System, you chose to have the installer create a default instance of Portal Server. (You made this choice in the installer’s Portal Server: Web Container page. To review this, see Figure 2-10.)

The default Portal Server instance runs in the web container provided by Application Server. When you start the Application Server default instance, you also start the Portal Server default instance.

In this section you open the sample portal desktop to verify that Portal Server is running.

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

    2. http://allinone.example.com:81/portal/

    The Sun ONE Portal Server sample Desktop opens. Figure 3-5 shows the sample desktop.

    Tip

    Remember to substitute the host and domain that you are using.

    Figure 3-5  Sun ONE Portal Server Sample Portal Desktop
    Screen capture; shows sample desktop's Login and Sample JSP channels.

  2. Explore the sample portal Desktop by clicking links and tabs.

    3. The sample portal desktop consists of sample Portal Server desktop containers, such as the Sample JSP Channel. Each desktop container holds and displays content provided by a channel. For more information on the sample portal used in the evaluation deployment example, see the Sun ONE Portal Server 6.2 Desktop Customization Guide.

Proceed to Configuring a Messaging Server Instance.

Note

If you are configuring a multiple-machine deployment of Java Enterprise System you must create an Administration Server instance at this stage of the configuration process, before you create Messaging Server and Calendar Server instances.This procedure is described in the deployment examples that cover multiple-machine deployments.

For single-machine deployments, like this example, you do not need to create the Administration Server instance. The procedure is omitted from this deployment example.

Configuring a Messaging Server Instance

After you start Directory Server and Application Server and verify Identity Server and Portal Server, you create instances of Messaging Server and Calendar Server and start these components.

This section describes how to create and start a Messaging Server instance. You learn the following:

Running the Directory Server Preparation Tool

Before configuring Messaging Server and Calendar Server instances you use the Sun ONE Directory Server Preparation Tool to apply one of the Sun ONE LDAP schemas and other configuration to your Directory Server instance. This configuration step prepares Directory Server to interoperate with Messaging Server and Calendar Server.

This procedure provides instructions on how to run the Directory Server Preparation Tool (a Perl script named comm_dssetup.pl) and configure your LDAP Directory Server to work with your Messaging Server, Calendar Server, and the User Management Utility (commadmin).

    To Run the Directory Server Preparation Tool
  1. Navigate to the preparation tool directory:

    2. cd /opt/SUNWmsgsr/lib

  2. Run the command that starts the preparation tool:

    3. perl comm_dssetup.pl

  3. The preparation tool displays a series of messages and then prompts you, Do you want to continue?

    4. Type Y and press Enter to continue.

    Note

    When you respond to the prompts, be sure to supply the values that you supplied when you ran the Java Enterprise System installer. You want the preparation tool to operate on the Sun ONE Directory Server instance that you created with the installer.

    For more information on these values, see Table 3-1.

  4. The preparation tool prompts you, Enter the full path to the directory where the Sun ONE Directory server was installed.

    5. Accept the default value (/var/opt/mps/serverroot) and press Enter to continue.

  5. The preparation tool displays a numbered list of directory server instances and prompts you, Which instance do you want? [1]

    6. You must choose the instance you created with the Java Enterprise System installer. The name of this instance ends with the name of the machine on which you installed Java Enterprise System. For the evaluation deployment example there is normally only one instance on the machine.

    Confirm that the default value for this prompt (1) specifies the correct instance, and press Enter to accept the default and continue. If there is more than one instance, type in the number of correct instance you want and press Enter to continue.

  6. The preparation tool prompts you, Please enter the directory manager DN [cn=Directory Manager]:

    7. Verify that the default value is cn=Directory Manager and press Enter to continue.

  7. The preparation tool prompts you for the Directory Manager password. Type “password” and press Enter to continue.

    8. Note

    You must use the Directory Manager password you set up on the Java Enterprise System installer’s Directory Server: Administration page. For more information, see To Supply Administration Server Information.

  8. The preparation tool prompts you, Will this directory server be used for users/groups? [Yes]

    9. Press Enter to accept the default value of Yes and continue.

  9. The preparation tool prompts you, Please enter the Users/Groups base suffix [o=usergroup].

    10. You must type in the values that identify your domain. For example, the domain name used in this document is example.com and you type dc=example,dc=com.

    Note

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

  10. The preparation tool displays a list of Sun ONE LDAP schemas and prompts you, Please enter the Schema Type (1, 1.5, 2).

    11. Type 2, and press Enter to continue.

  11. The preparation tool prompts you, Do you want to update the schema files? [Yes]

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

  12. The preparation tool prompts you, Do you want to configure new indexes? [Yes]

    13. Press Enter to accept the default value (Yes) and continue.

  13. 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) and continue.

    The preparation tool displays a series of informational messages, beginning with “generating files.”

  14. 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) and continue.

  15. The preparation tool executes the generated scripts to configure the Sun ONE Directory Server instance.

    16. The scripts display a series of informational messages that ends with “Successful Completion.”

    Table 3-1  Directory Server Preparation Tool Input Values

    Item

    Description

    Directory server root

    Specifies the location of the installation root of the Directory Server on the Directory Server machine. In this deployment, the server root is /var/opt/mps/serverroot.

    Directory server instance

    If multiple instances of Directory Server reside on the machine, choose the one to be configured with Messaging Server. In this deployment, there is only one instance.

    Directory Manager (DN)

    The Directory Manager DN (cn=Directory Manager) is the administrator who is responsible for the user and group data in the Organization Tree. Be sure that the Directory Manager DN you specify in this script is the same DN that you set up in your Directory Server installation as well as your Messaging Server installation. This deployment uses cn=Directory Manager.

    Will this directory server be used for users/groups?

    For this deployment, answer Yes. You then answer questions on selecting a DC Tree base suffix and a User and Group base suffix for your Organization Tree.

    Users/Groups base suffix

    The User and Group base suffix is the top entry in the Organization Tree which holds the namespace for user and group entries. Be sure that the User and Group base suffix you select is the same as what you specified during your Directory Server installation and in your Messaging Server installation.

    If you installed Identity Server, be sure the suffix specified in Identity Server installation is the same as what you specify for this question. If you do not use the same suffix, Messaging Server does not recognize your Identity Server installation.

    In this deployment, use dc=example,dc=com.

    Schema type

    Because this deployment is using Sun ONE LDAP v.2, choose option 2.

    Update schema files?

    For this deployment, answer Yes. New elements are added to your schema.

    Configure new indexes?

    For this deployment, answer Yes. New indexes are used to create caches to improve efficiency of directory searches.

Verifying Directory Server Configuration

This procedure describes how to use the Sun ONE Server Console to verify the configuration performed by the Directory Server Preparation Tool. In Running the Directory Server Preparation Tool, you ran the Directory Server Preparation Tool and configured Directory Server for use as a shared user directory for all of the Java Enterprise System components.

    To Verify that Directory Server is Configured as a Shared User Directory
  1. Navigate to the serverroot directory:

    2. cd /var/opt/mps/serverroot

  2. Run the startconsole command:

    3. ./startconsole

    The Sun ONE Server Console Login dialog opens.

  3. In the Sun ONE Server Console Login dialog, type your administrator ID and password, and then click OK.

    4. The Sun ONE Server Console opens.

    Figure 3-6  Sun ONE Server Console
    Screen capture; shows the values described in step 4.

  4. Expand the nodes on the Servers and Applications tab until the Directory Server node is visible. Figure 3-6 shows the display for the example.com domain. The nodes have been expanded to display the Directory Server (allinone) node. You should see a similar display for the Administration Server domain and host name you are using.

    5. Double-click the Directory Server node. The Sun ONE Directory Server window opens.

    Figure 3-7  Sun ONE Directory Server Window
    Screen capture; shows the action described in step 5c. Menu is open and Edit with Generic Editor is selected.

  5. In the Sun ONE Directory Server window:
    1. Click the Directory tab.
    2. Expand the nodes and review the new two-level, shared, directory structure. Compare Figure 3-7 with Figure 3-2. Notice the new node for the example.com organization. You should see a similar node for the organization name you are using.

      3. Click the organization name folder node. The display is refreshed. The right pane displays the contents of the organization name folder.

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

      4. The Generic Editor opens.

      Figure 3-8  Generic Editor
      Screen capture; shows Object Class iplanet-am-managed-people-container.

  6. In the Generic Editor, verify that the object class is iplanet-am-managed-people-container. This verifies that you have successfully configured Directory Server with Sun ONE LDAP Schema, version 2. Click OK to close the editor.
  7. Exit the console.

Creating a Messaging Server Instance

This procedure shows you how to run the Sun ONE Messaging Server Configuration Wizard to create and start an instance of Messaging Server.

    To Run the Messaging Server Configuration Wizard
  1. Navigate to the Sun ONE Messaging Server directory:

    2. cd /opt/SUNWmsgsr/sbin

  2. Run the configure command:

    3. ./configure

    The configuration wizard’s welcome page opens.

  3. In the Welcome page, click Next.

    4. The configuration wizard’s Software License Agreement page opens.

  4. In the Software License Agreement page, click Accept.

    5. The Select Directory to Store Configuration and Data Files page opens.

  5. In the Select Directory to Store Configuration and Data Files page, accept the default value of /var/opt/SUNWmsgsr. Click Next.

    6. The Create new directory? message opens, as shown in Figure 3-9.

    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.

    Figure 3-9  Create New Directory Message
    Screen capture; shows Create new directory message over the Select Directory page.

  6. In the Create new directory? message, click Create Directory.

    7. The Select Components to Configure page opens.

  7. In the Select Components to Configure page, verify that Message Transfer Agent, Message Store, and Messenger Express are selected as default values.
    • 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.
    • Messenger Express. Handles the HTTP protocol retrieval of messages from the Message Store. If you are only configuring Messenger Express, you must also select the Message Store and the MTA.

      • Click Next to accept the default values and continue. The Sun ONE Messaging Server User and Group page opens.

  8. In the Sun ONE Messaging Server User and Group page, confirm the following default values:
    • Enter Unix username: mailserv
    • Enter Unix group: mail

      • Click Next to accept the default values. The Configuration Directory Server Panel page opens.

  9. In the Configuration Directory Server Panel page confirm the following default values:
    • Config Server LdapURL: ldap://allinone.example.com:389
    • Bind as: cn=Directory Manager

      • Enter the following value:

    • Password: password

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

      Note

      The password you supply must match the Directory Manager password you established for Directory Server on the Directory Server Administration page. This allows Messaging Server to access Sun ONE Directory Server. (See To Supply Directory Server Information.)

  10. In the User/Group Directory Server Panel page confirm the following default values:
    • User/Group Server LdapURL: ldap://allinone.example.com:389
    • Bind as: cn=Directory Manager
    • Password: password

      • Click Next to accept the default values. The Postmaster Email Address page opens.

      Note

      The password you supply must match the Directory Manager password you established for Directory Server on the Directory Server Administration page.

  11. In the Postmaster Email Address page enter the following values:
    • Enter email address: scott@example.com

      • Click Next.The Password for all admin accounts page opens.

      Tip

      Remember to substitute the domain that you are using.

  12. In the Password for all Admin Accounts page, enter the following values to establish an administrative password for Messaging Server:
    • Enter password: password is recommended.
    • Re-enter password to verify: password

      • Click Next. The Default Email Domain page opens.

  13. In the Default Email Domain page, confirm the following default value:
    • Enter Email Domain: example.com

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

  14. In the Organization DN for the Default Email Domain page, confirm the following default value:
    • Enter Organization DN: o=example.com, dc=example.com

      • Click Next. The Ready to Configure page opens.

      Tip

      Remember to substitute the host and domain that you are using.

  15. In the Ready to Configure page, review the information. Click Configure Now.

    16. You might receive the Ports in Use message shown in Figure 3-10.

    Figure 3-10  Ports In Use Message
    Screen capture; shows the Ports in Use message.

  16. If you receive the Ports in Use message:
    1. Click OK.
    2. Open a terminal window. Do not stop the configuration wizard.
    3. In the terminal window, use the grep command to locate the sendmail process:

      4. ps -ef | grep sendmail

    4. Use the pkill command to terminate the sendmail process:

      5. pkill sendmail

    5. Return to the Ready to Configure page.
  17. When the configuration process is complete, the Installation Summary page opens.

    18. Figure 3-11  Installation Summary Page
    Screen capture; shows the installation summary page.

  18. In the Installation Summary page, view the details, and then click Close.
  19. Perform the following commands to set the listening ports for the Messaging Server’s WebMail web interface.
    1. cd /opt/SUNWmsgsr/sbin
    2. ./configutil -o service.http.port -v 88
    3. ./configutil -o service.http.sslport -v 448
  20. Stop and restart the Messaging Server processes to enable the configuration changes you just made.
    1. cd /opt/SUNWmsgsr/sbin
    2. ./stop-msg
    3. ./start-msg

Configuring a Calendar Server Instance

This procedure shows you how to run the Sun ONE Calendar Server Configuration Wizard to create and start an instance of Calendar Server. To run the configuration wizard:

  1. Navigate to the Calendar Server directory:

    2. cd /opt/SUNWics5/cal/sbin

  2. Run the csconfigurator command:

    3. ./csconfigurator.sh

    Tip

    The Calendar Server configuration program configures your site’s specific requirements and creates a new ics.conf configuration file. For more information on configuring Calendar Server, refer to the Sun ONE Calendar Server Installation Guide for Solaris Operating Systems (http://docs.sun.com/doc/816-6707-10).

    The configuration wizard’s Welcome page opens.

  3. In the Welcome page, click Next to continue.

    4. The Administration, User Preferences and Authentication page opens.

  4. In the Administration, User Preferences and Authentication page, enter the following values:
    • LDAP Server Host Name: allinone.example.com
    • LDAP Server Port: 389
    • Directory Manager DN: cn=Directory Manager
    • Directory Manager Password: password
    • Base DN: o=example.com,dc=example,dc=com

      • Confirm the following default values:

    • Administrator User ID: calmaster
    • Administrator Password: password

      • Click Next. A Question dialog opens.

      Tip

      Remember to substitute the host and domain that you are using.

      Note

      The Directory Manager password you supply must match the Directory Manager password you established for Directory Server on the Directory Server Administration page. This allows Calendar Server to access Directory Server. (See To Supply Directory Server Information.)

      Figure 3-12  Question Dialog
      Screen capture; shows the Question dialog above the Administration, User Preferences and Authentication page.

  5. In the Question Dialog, click Create it to create the calmaster user.

    6. The Email and Email Alarms page opens.

  6. In the Email and Email Alarms page, enter the following values:
    • Email alarms: Enabled
    • Administrator Email Address: scott@example.com
    • SMTP Host Name: allinone.example.com

      • Click Next. The Problem connecting to SMTP Host dialog may appear, as shown in Figure 3-13.

      Figure 3-13  The Problem Connection to SMTP Host Dialog
      Screen capture; shows the Problem connection to SMTP host message above the Email and Email Alarms page.

  7. In the Problem connecting to SMTP Host dialog, click Accept, and then click Next to continue. For the purposes of this deployment, you use this host as the SMTP server.

    8. The Runtime configuration page opens.

  8. In the Runtime Configuration page enter the following values:
    • Service Port: 89
    • Maximum Sessions: 5000
    • Maximum Threads: 20
    • Number of server processes: 1
    • Runtime User ID: icsuser
    • Runtime Group ID: icsgroup
    • Calendar Server Startup: select both Start after successful configuration and Start on System Startup

      • Click Next. The Create New User ID dialog opens.

      Figure 3-14  Create New User ID Dialog
      Screen capture; shows the Create new User ID message above the Runtime configuration page.

  9. In the Create New User ID dialog, click Create User ID.
  10. In the Runtime configuration page, click Next.

    11. The Select Directory to store configuration and data files page opens.

  11. In the Select Directory to Store Configuration and Data Files page, accept the default values. Click Next to continue.

    12. The Ready to Configure page opens.

  12. In the Ready to Configure page, click Configure Now.

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

    Note

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

  13. In the Configuration Summary page, review the details, and then click Close.

You have verified, configured, and started all of the servers you use in this deployment example. You can proceed to Chapter 4, "Provisioning a Java Enterprise System User."



Previous      Contents      Index      Next     

Copyright 2004 Sun Microsystems, Inc. All rights reserved.