Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

Running the Installer in Text-Based Mode

If you have problems during installation, refer to the troubleshooting information in Chapter 9, Troubleshooting.

ProcedureTo Begin Installation

  1. If you are not logged in as root, become superuser.

  2. Start the text-based installation interface:

    Note –

    A full description of options for the installer command can be found in Appendix B, Installation Commands.

    • For CDs. Navigate to a directory that is not on the CD so that you can switch CDs during the installation session. For example:

      cd /tmp

      Enter the command to start the installer using the fully qualified path to the installer:

      /installer -nodisplay

      In this command, mount-point is where you mounted the CD and os-arch matches your platform: Solaris_sparc , Solaris_x86 or Linux_x86.

    • For a DVD. Navigate to the DVD directory whose name matches your platform, then enter the command to start the installer:

      ./installer -nodisplay

    • For a Download. Navigate to the directory where you downloaded the software, then enter the command to start the installer:

      ./installer -nodisplay

      Welcome information is displayed.

  3. Press Enter to go to the Software License Agreement.

  4. Press Enter to display the Software License Agreement.

    Continue pressing Enter to read to the end of the Agreement.

  5. If you accept all the terms of the License, type yes and press Enter. The Language Support page is displayed.

    If you do not accept all the terms of the License, select the default no by pressing Enter. This will end the installation process.

ProcedureTo Select Languages and Components

The installer first checks your system for previously installed versions of components and displays a list of the detected components, if any are found, under the title Component Products Detected on This Host.

Note –

Detected components will not be available for selection, but might require upgrading if the versions do not meet Java ES requirements or dependency requirements of other components.

  1. Specify the additional language packages you want to install by entering a comma-separated list of the numbers associated with the languages, and press Return.

    English is always installed.

  2. Specify which components to install by typing a comma-separated list of numbers associated with the components you want to install, and press Return.

    If the installer finds no previously installed versions of components, the installer displays the Component Selection Main Menu which looks similar to the following.

    Component Selection - Main Menu
    Note: "*  *" indicates that the selection is disabled
    [ ] 1. Sun Java(TM) System Calendar Server 6 
    [ ] 2. Sun Java(TM) System Directory Preparation Tool
    [ ] 3. Sun Java(TM) System Web Server 6.1 SP5
    [ ] 4. Sun Java(TM) System Messaging Server 6
    [ ] 5. Sun Java (TM) System Web Proxy Server 4.0
    [ ] 6. Sun Java(TM) System Administration Server 5
    [ ] 7. High Availability Session Store (HADB)
    [ ] 8. Sun Cluster 3.1U4
    [ ] 9. Sun Java(TM) System Access Manager 7 
    [ ] 10. Sun Java(TM) System Communications Express 6
    [ ] 11. Sun Java(TM) System Message Queue 3 Enterprise Edition
    [ ] 12. Sun Java(TM) System Application Server Enterprise Edition 8.1
    [ ] 13. Sun Java(TM) System Directory Proxy Server 5
    [ ] 14. Sun Java(TM) System Portal Server Secure Remote Access
    [ ] 15. Sun Java(TM) System Instant Messaging 7
    [ ] 16. Sun Java(TM) System Portal Server 6
    [ ] 17. Sun Cluster Agents for Sun Java(TM) System
    [ ] 18. Sun Java(TM) System Directory Server 5
    [ ] 19. Sun Java (TM) System Delegated Administrator
    [ ] 20. Service Registry 3.0
       Enter a comma separated list of products to install  [] {"<" goes
        back, "!" exits}:
  3. Continue through the installer prompts to select the subcomponents for each product you selected, if applicable.

    Note –

    Not all components have subcomponents. These products will be displayed without interaction.

    After you finish selecting components and their subcomponents, the installer performs a dependency check. If there is a problem with dependencies, the installer displays a Product Dependency Check error or warning, depending on the problem. Typical problems might include:

    • A local dependency has not been met

      In this situation, return to Component Selection and select the appropriate component to satisfy the local dependency.

    • A remote dependency will be met later during postinstallation configuration

      If you do not intend to specify a remote installation, return to Component Selection and select the appropriate component to satisfy the dependency locally.

    • Previous versions of components are already installed on the local host

      In this situation, upgrade or remove the reported components and ask the installer to check again. To upgrade components from earlier Java ES versions, refer to Sun Java Enterprise System 2005Q4 Upgrade Guide.

  4. If any incompatible versions of components are found, you will be asked to remove them from the host. Answer yes and press Return to have the installer remove them or select the default no by pressing Return to remove the components manually.

    Note –

    If you select the default no, you must remove the component before continuing with the installation.

ProcedureTo Resolve Dependency and Compatibility Issues

After the installer performs a dependency check for components, it performs a compatibility check of any shared components already installed. If incompatible versions of shared components are detected, the installer displays a Shared Component Upgrades Required report indicating what shared components are not compatible.

  1. Resolve any component dependency issues and click Next.

    The installer then performs a compatibility check of any shared components that are already installed. If incompatible shared components are found, the installer lists them.

  2. Review the list of incompatible shared components and determine if it is safe for the installer to automatically upgrade the shared components listed.

    On Solaris OS. If an incompatible system-wide version of the J2SE SDK is detected, the J2SE SDK Upgrade Required page is displayed. The installer performs this check only on the Solaris platform because the Linux platform does not have a specific, system-wide installation of the J2SE SDK.

    Caution – Caution –

    Do not upgrade shared components without checking the dependencies that exist on the host for non-Java ES applications. First verify that these existing applications are compatible with the required versions of the shared components.

    For information about upgrades, see the Sun Java Enterprise System 2005Q4 Upgrade Guide.

  3. Press Return to allow the installer to automatically upgrade the shared components listed.

    This upgrade does not happen until you reach the Ready to Install page.

ProcedureTo Specify Installation Directories and Initiate the System Check

A default installation directory will be displayed for each selected component.

  1. Accept the default installation location, or replace the default for your deployment.

  2. Repeat this step for every component selected for installation.

    After the installation directory of the final, selected component is chosen, the installer will automatically perform a system check. The installer checks for disk space, memory, operating system patches and operating system resources.

  3. If operating system patches are found to be missing, apply patches according to the following procedure.

    Note –

    To install any missing operating system patches, do the following:

    1. Go to the Sunsolve site:

    2. Click Patch Portal.

    3. Enter the patch number in the PatchFinder text box, and click Find Patch.

    4. Download the zip file for the patch.

    5. Expand the zip file. For example: unzip

    6. A directory is created for the patch files.

    7. Apply the patch. For example: patchadd 117885-44

    8. Back in the Java ES installer, click Check Again. All system requirements are rechecked.

ProcedureTo Select a Configuration Type


    Specify a configuration type from the following options:

    • Configure Now. Allows you to configure components that permit configuration at installation time.

      Your Configure Now tasks include specifying the common server settings, and the configuration information for the components selected.

      Note –

      Some components cannot be configured during a Configure Now installation. If you are warned that you will need to configure these components after installation, click Next to proceed and see Chapter 6, Configuring Components After Installation.

    • Configure Later. You enter only the minimum values that are necessary for installing the packages.

      The installer proceeds without doing further configuration. If you choose this option, skip to Running the Installer in Text-Based Mode.

ProcedureTo Specify Configuration Data

For a Configure Now installation, you are asked to provide configuration information for the components that allow installation-time configuration. Defaults are displayed, except for passwords (which must be a minimum of 8 characters).

Tip –

Your configuration values are gathered by the installer as you proceed through the configuration panels. After installation is done, you can access this information in the Installation Summary:

Solaris OS: /var/sadm/install/logs

Linux: /var/opt/sun/install/logs

  1. Specify common server settings.

    Either accept the defaults, or use alternate data to answer the installer questions regarding these global fields. Refer to Common Server Settings in Sun Java Enterprise System 2005Q4 Installation Reference.

  2. Specify component settings.

    Either accept the defaults or use the information you gathered in the component worksheets to answer the installer questions regarding each component. For information on the configuration values on each page, refer to:

    Note –

    You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with Portal Server, Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging. Access Manager Realm (7.x) installation type can only be used if you are not installing any of these components.

    • For Configure Now—You will be prompted with the following: Install type [Legacy]. Select Legacy (version 6.x style) which is the default. When you are asked for the web container for running Access Manager, set the Console Deployment URI to amconsole.

    • For Configure Later—As root, run the amconfig script to configure Access Manager after installation. To select the Legacy (6.x) installation type, set the following parameters in your configuration script input file, amsamplesilent:

      • AM_REALM=disabled

      • CONSOLE_DEPLOY_URI=/amconsole

  3. A list of your selected components and subcomponents is displayed. Review this list carefully. If you need to make changes, type < and press Return until you reach the question that requires a change.

    Although shared components are not explicitly listed, they have already been verified and will be installed if they are needed.

ProcedureTo Install the Software

  1. To start the installation, press Return to accept the default [1].

    The installation process starts and a progress indicator bar informs you of the state of the installation. For example:

    Java Enterprise System

    Note –

    Depending on the size and complexities of your installation, the installation process can be lengthy.

    When the installation has successfully completed, the Installation Complete message is displayed.

  2. Examine the postinstallation files

    Files are located in /var/sadm/install/logs on Solaris OS and in /var/opt/sun/install/logs on Linux.

    • [1] Installation Summary. Lists each component installed and the settings you specified. If you chose Configure Now configuration, this summary includes all the configuration values.

    • [2] Installation log. Displays the installer’s log messages for components.

    • A separate log file contains information about the installation of shared components.

    To see a full listing of the Java ES logs, refer to Examine Installation Log Files.

  3. Exit the installer.

    Your installer session is done. Components that were installed will need to be started after you have completed all postinstallation tasks. Proceed to Next Steps