Sun ONE logo      Previous      Contents      Index      Next     

Sun ONE Application Server 7 Getting Started Guide

Chapter 2
Evaluation Installation of Sun ONE Application Server

If you have already installed the product, proceed to Chapter 3, "Setting Up Your Environment".

If you are using the Solaris 9 Operating Environment and the application server has been installed as part of the Solaris 9 installation, ensure that you follow the Solaris post-installation steps in "Configuring After Solaris 9 Installation" to configure your application server environment.

If you are installing the product for the first time, this chapter leads you through the installation of the evaluation product using the interactive methods of installing the product. If you either have the non-evaluation distribution or would like to use the silent installation methods, refer to the Sun ONE Application Server 7 Installation Guide for detailed installation steps.

Sun ONE Application Server 7 allows different types of installation according to user role, as well as different methods of installation, such as command-line, GUI and silent modes. This chapter describes each type of installation and gives instructions for installing as an evaluator in GUI mode. When you are ready to install the product for development or operational use, refer to the Installation Guide for complete details.

The following topics are described in this chapter:

About Installation

Before you run the setup program as described in Sun ONE Application Server 7 Installation Guide, you should review the types and methods of installation described in this chapter. You’ll select a type of installation based on your role as a user, then select the method of installation that most suits your installation environment.

Types of Distribution

Sun ONE Application Server is available in both evaluation and non-evaluation distributions. The evaluation distribution's installation experience is streamlined to require a minimum of user input.

The non-evaluation distribution enables you to install the product for the purpose of development or operational deployment, and to select specific components that to installed. This guide leads you through the evaluation installation experience.

The evaluation installation experience automatically installs the following components:

Installation Methods

Using the evaluation distribution, you can install the application server using any of three methods:

Although this guide focuses on the graphical interface installation method, you can easily use the command-line, interactive-based installation method as well.

For more information on the silent installation method, consult the Installation Guide.

Installing for Evaluation

This section includes the following topics:

You can opt to download the basic Evaluation version of the Sun ONE Application Server or a version that also includes Sun ONE Studio 4.0.

Preparing to Install

Your system should meet the system requirements described in the following table.

Operating System

Architecture

Minimum Memory

Recommended Memory

Minimum Disk Space

Recommended Disk Space

Sun Solaris 8 for SPARC, Sun Solaris 9 for SPARC

32 and 64 bit

128 MB without Sun ONE Studio

512 MB with Sun ONE Studio

512 MB

250 MB free

500 MB free

Microsoft Windows

  • 2000 Advanced Server, SP2+
  • 2000 Server, SP2+ or above
  • 2000 Professional, SP 2 or above
  • Windows XP Professional

Intel 32 bit

128 MB without Sun ONE Studio

256 MB with Sun ONE Studio

256 MB without Sun ONE Studio

512 MB with Sun ONE Studio

250 MB free

500 MB free

Solaris: Required Patches

The following Solaris patches must be installed for Solaris 8 systems:

109326-06 or higher

108827-26 or higher

110934 for packaged-based installation only

These patches can be retrieved from the patch finder page located at the following URL:

http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

It is recommended that Solaris 8 users should have the “Sun recommended patch cluster” installed. The cluster includes the three required patches listed above. This patch is available at: http://sunsolve.sun.com/ under “Recommended and Security Patches.”

Once you have satisfied the system requirements, you are ready to install the application server.

Running the Setup Program

The following steps enable you to install Sun ONE Application Server 7 using graphical-interface mode. If you choose to use command-line installation instead, the steps involved in that method are identical. In place of GUI-based installation screens, text-based screens are shown during a console-based installation.

The following steps apply to all platforms:

Note

You must have administrative privileges on your Windows machine to install Sun ONE Application Server 7. You cannot install more than one Sun ONE Application Server on a single Windows machine.

  1. Expand or unzip the installation bundle to a temporary directory.
  2. If you are not in the directory already, change to the directory where you expanded the files.

    3. Note

    UNIX: If you are installing Sun ONE Application Server remotely, you must enable the display configuration on the machine where you are installing the product.

  3. Type the following at the command prompt:

    4. #./setup

    To run command-line installation, type

    #./setup -console

    On Windows, you can also navigate using Windows Explorer to the directory where you expanded the files and double-click the setup file.

    The installation interface appears.

  4. Read the Welcome screen and click Next.
  5. Read the License Agreement, select the radio button to agree to the terms of the license, and click Next.

    6. You must accept the license agreement to continue with the installation.

  6. Enter the path to your installation directory or click the ellipsis (...) to browse for a directory.

    7. If the directory does not already exist, the Create New Directory? dialog box appears. Click Create Directory. You can also click Choose New to select an existing directory.

  7. On the Server Configuration Information dialog box, enter the following:
    • Admin User: Name of the user who administers the server (for example, admin).
    • Admin User’s Password: Password to access the administration server. Minimum number of characters is 8. Re-enter the password in the text box below to confirm your choice.
    • Admin Server Port: Port number to access the administration server.

      A default port number appears (for example 4848, if that port is not in use on your machine). Change the default number if necessary. The installation program will check port numbers for validity and availability when you click Next.

    • HTTP Server Port: Port number to access the default server instance.

      A default port number appears (for example 1024, if that port is not in use on your machine). Change the default number if necessary. The installation program will check port numbers for validity and availability when you click Next.

      Note

      The installation program automatically detects ports in use and suggests currently unused ports for the default settings. By default, if you are running as root on UNIX or are on Windows, the initial default ports are 80 and 4848 for the HTTP server and administrative server respectively. If you are running as non-root on UNIX, the HTTP server port defaults to 1024. If any of these initial default ports are being actively used on your system, the installation program will suggest alternative port numbers.

  8. The Checking Disk Space dialog box appears.
  9. Click Install Now to complete the installation.

    10. An Installation Progress indicator bar appears.

    As installation ends, the Installation Complete screen appears. Users should review this screen and click Finish to exit the installer.

Proceed to Chapter 3, "Setting Up Your Environment."

For troubleshooting tips, see the Installation Guide.

Uninstalling Sun ONE Application Server

When you uninstall Sun ONE Application Server for Evaluation, all components are automatically selected for uninstallation. You cannot select individual components to uninstall.

The uninstallation program detects any running processes and stops them before continuing with the uninstall process.

Perform the following steps on both UNIX and Windows platforms:

  1. Change to your machine’s Sun ONE Application Server installation directory.
  2. Type one of the following commands at the command prompt:
    • GUI mode:

      ./uninstall

    • Command-line mode:

      ./uninstall -console

  3. Read the Welcome screen and click Next or hit Enter to continue with the uninstall process.
  4. On the Ready to Uninstall screen, a list of uninstallable components appears. Review the components and click Next or hit Enter to proceed.

    5. You cannot select individual components to uninstall using the Evaluation version of Sun ONE Application Server.

  5. Click Uninstall Now or hit Enter.

    6. The uninstallation progress meter appears.

  6. The Uninstall Summary screen appears.

    7. Review the details and click Exit or hit Enter to quit the uninstallation program.

  7. Change to your installation directory and manually remove any leftover files and directories.

Configuring After Solaris 9 Installation

The Sun ONE Application Server 7 installation that is installed as part of a Solaris 9 installation contains only the necessary libraries, executables and other files required to support the application server. No application server configuration exists upon installation. To create an initial configuration, you must use the application server’s asadmin command line interface (CLI). The create-domain subcommand of the asadmin CLI enables you to create an administrative domain in a location of your choice. Each administrative domain consists of an administrative server and application server instance configurations. When you create an initial administrative domain, you specify the administrative user name, password and port number associated with the administrative server of the domain.

Once you’ve created an administrative domain, you can create one or more application server instances within the domain. Each application server instance houses an HTTP server, the J2EE[tm] web and EJB containers and other application server facilities.

Administrative domains and application server instances are explained further in the next section of this guide.

Create an Administrative Domain

By default, the create-domain subcommand creates the new administrative domain configuration under /var/appserver/domains/. If you are logged in as a user that does not have write permissions to this area, you must specify a suitable location when creating the administrative domain. You specify the location in which to create the domain configuration using the --path option on the create-domain subcommand.

To create an administrative domain, follow these steps:

  1. If you are not using the root user ID, you will need to either request that the systems administrator create an administrative domain on your behalf or request that your user ID be added to a UNIX group that is able to create administrative domains. See the following note for details if you do not have root user access.

    2. Note

    User Permissions on UNIX Platforms: In order for a non-root user to create and delete administrative domains, the user ID must be added to a UNIX group that has write permissions to the domain configuration file. In this case, the following steps must be taken by the systems administrator.

    Create a UNIX group that will be the group which is applied to the installation-wide domain configuration files. For example, a UNIX group named asadmin.

      1. Set the installation-wide domain config files located under /etc/appserver to be owned by the newly created UNIX group. The files are named domains.bin and domains.lck. For example, after changing the group assigned to these files:

        2. -rw-r--r-- 1 root asadmin 0 Sep 18 14:34 domains.bin

        -rw-r--r-- 1 root asadmin 0 Sep 18 14:34 domains.lck

      2. Enable write access to these files by the newly created UNIX group. In this example, the resulting permissions would look like the following:

        3. -rw-rw-r-- 1 root asadmin 0 Sep 18 14:34 domains.bin

        -rw-rw-r-- 1 root asadmin 0 Sep 18 14:34 domains.lck

      3. Add the user ID to the UNIX group.

    Alternatively, if a systems administrator does not want to provide non-root users with write access to the installation-wide configuration files, the administrator can use the root user ID to create an administrative domain on behalf of a user. During creation of a new administrative domain, administrators can specify the --sysuser and --path options to identify the UNIX user ID that will own the domain's directories and files and the location under which the administrative domain will be created.

    Once an administrative domain is created under your user ID, you may execute asadmin subcommands to create new application server instances and perform a wide variety of administrative operations against the application server instances without the user ID belonging to the UNIX group that has write privileges for the administrative domain configuration file. Membership in the UNIX group is required only to create and delete administrative domains.

  2. Ensure that the /usr/sbin directory is included in your path.
  3. From the command line, execute the following command to create a new administrative domain, domain1:

    4. asadmin create-domain --path domain_config_dir --adminport 4848 --adminuser admin --adminpassword password domain1

    where domain_config_dir specifies the location under which the administrative domain configuration will be created.

    The --adminport, --adminuser and --adminpassword options specify the initial settings of the new administrative server defined for the domain.

    If the root user is executing the create-domain subcommand to create an administrative domain on your behalf, the --sysuser option should be used to specify the system user ID under which the administrative domain files and directories will be created. For example:

    asadmin create-domain --sysuser ckamps --path domain_config_dir --adminport 4848 --adminuser admin --adminpassword password domain1

    Upon execution of the create-domain subcommand, you should see the following message:

    Created Domain domain1 successfully

    If the name domain1 has already been used, execute the create-domain subcommand again with another domain name. You can use periods and other characters in your domain names. You could use your login user name as a qualifier to help ensure that your domain name is unique. For example: ckamps.domain1.

    When you execute the create-domain subcommand and the following error message is encountered, the message is an indication that your user ID does not have permissions to access the domain configuration files:

    Cannot create domain : domain1 problem locking store /etc/appserver/domains.lck (Permission denied)

    See the steps above for either adding your user ID to the appropriate UNIX group or requesting that your systems administrator create the administrative domain on your behalf.

  4. Execute the list-domains subcommand to display a list of all of the domains configured for the application server installation. (Execution of this read-only command does not require your user ID to be part of the UNIX group that has write privileges to the domain configuration files).

    5. asadmin list-domains domain1 [domain_config_dir/domain1]

    where the value of domain_config_dir represents either the default location for newly created administrative domains or the value specified on the --path option of the create-domain subcommand.

Create an Application Server Instance

Once either the systems administrator has created an administrative domain on your behalf or you created the administrative domain, your next step is to create an application server instance under the newly created administrative domain. Creation of an application server under your own administrative domain does not require that your user ID be part of the UNIX group that has write privileges to the domain configuration files.

To create an application server instance, execute the create-instance subcommand to create the application server instance:

asadmin create-instance --domain domain1 --instanceport 80 server1

where domain1 is the domain name specified during domain creation, 80 is the HTTP server port number of the application server instance, and server1 is the name of the instance. Specify appropriate values for these options depending on your specific environment. Since port numbers less than 1024 are not accessible to non-root users, you will need to specify a port number greater than 1024 if you are logged in as a non-root user.

As long as you have only a single administrative domain defined on your system, you do not need to specify the target domain name when creating an instance.

For more information on how to prepare your application server environment after installation of the application server as part of a Solaris 9 installation, consult the Sun ONE Application Server Administrator's Guide.



Previous      Contents      Index      Next     

Copyright 2003 Sun Microsystems, Inc. All rights reserved.