Sun Java Communications Suite 5 Installation Guide

Running the Installer in Text-Based Mode

A full description of options for the installer command and its options is contained in Appendix F, Installation Commands.

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

ProcedureTo Begin Installation

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

  2. Start the text-based installer:

    ./installer —nodisplay

    Welcome information is displayed.

  3. Press Return to display the Software License Agreement.

    Continue pressing Return to read the entire Agreement.

  4. To accept the terms of the License Agreement, type yes and press Return.

    If you do not accept all the terms of the License, select the default no by pressing Return. This ends the installation session.

ProcedureTo Select Components and Languages

The installer checks your host for previously installed versions of product components. If any are found, a list of the detected components is displayed, under the title Component Products on This Host.

Later in the installation session, you might be instructed to upgrade or remove those components before continuing. When these issues are resolved, installation can proceed.

The installer displays the Component Selection Main Menu. For example:

Choose Software Components - Main Menu
Note: "*  *" indicates that the selection is disabled

[ ] 1.  Sun Java(TM) System Calendar Server 6 2006Q4
[ ] 2.  Sun Java(TM) System Directory Preparation Tool
[ ] 3.  Sun Java(TM) System Web Server 7.0 2006Q4
[ ] 4.  Sun Cluster Geographic Edition 3.1 2006Q4
[ ] 5.  Sun Java (TM) System Web Proxy Server 4.0.4 2006Q4
[ ] 6.  Sun Java(TM) System Messaging Server 6 2006Q4
[ ] 7.  Sun Java(TM) System Directory Server Enterprise Edition 6.0 2006Q4
[ ] 8.  Sun Java (TM) System High Availability Session Store 4.4 2006Q4
[ ] 9.  Sun Cluster 3.1U4
[ ] 10. Sun Java(TM) System Access Manager 7.1 2006Q4
[ ] 11. Sun Java(TM) System Communications Express 6 2006Q4
[ ] 12. Communication Services Delegated Administrator 2006Q4
[ ] 13. Sun Java(TM) System Message Queue 3.7 UR1
[ ] 14. Sun Java(TM) System Application Server Enterprise Edition 8.2 2006Q4
[ ] 15. Service Registry 3 2006Q4
[ ] 16. Sun Java(TM) System Instant Messaging 7 2006Q4
[ ] 17. Sun Cluster Agents 3.1 2006Q4
[ ] 18. All Shared Components
   Enter a comma separated list of products to install, or press R to refresh
   the list [] {"<" goes back, "!" exits}:
  1. Type a comma-separated list of the numbers associated with the components you want to install, and press Return.

    The installer presents a list called Choose Software Components — Confirm Choices which shows the components you selected.

  2. If the chosen components are correct, press Return.

    The installer queries you about installing subcomponents for those components you chose. For example:

    Component Selection - Selected Product "Sun Java (TM) System Directory Server Enterprise Edition 6.0 2006Q4"
    *[X] 1. Java Enter5prise System Directory Server 6 Core Server
    *[X] 1. Java Enter5prise System Directory Service Control Center
    *[X] 1. Java Enter5prise System Directory Server Enterprise Edition 6 Command-Line Utilities
    *[X] 1. Java Enter5prise System Directory Proxy Server 6 Core Server
    Enter a comma-separated list of componets to install (or D to install all) [D] {"<" goes back, "!" exits}

    Not all product components have subcomponents. In this case, these components are displayed, but no response is required from you.

  3. Make your subcomponent selections.

    After you have confirmed all your subcomponent selections, the installer queries you about installing multilingual packages.

  4. To install multilingual packages for all selected components, type Y and press Return.

    Default is N, which means only English packages are installed. If you type Y, multilingual packages are installed for all languages for all the components you selected.

  5. Resolve product component dependency errors.

    If there is a problem with component 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 product 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 product component to satisfy the dependency locally.

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

      If incompatible versions of product components are detected, you will need to exit the installer and upgrade or remove the incompatible versions.

  6. Resolve shared component dependency errors.

    If any incompatible versions of shared components are found on the host, you are asked if you want to upgrade them. Review the Shared Components Upgrade Required list and determine if it is safe for the installer to automatically upgrade these shared components.

    Caution – Caution –

    Do not upgrade shared components without checking the dependencies that exist on the host for non-Communications Suite applications. First verify that these existing applications are compatible with the required versions of the shared components. For information about upgrading Communications Suite product components, see the Sun Java Communications Suite 5 Upgrade Guide, and for Java ES products see the Sun Java Enterprise System 2006Q3 Upgrade Guide.

    • Type 1 (the default) or press Return to have the installer upgrade the shared components.

    • Type 2 to cancel the installation session so that you can upgrade the shared components manually.

    If you type 2, you must remove or upgrade the shared components on the Shared Components Upgrade Required list before you can continue with installation.

  7. On Solaris OS, indicate if the installer should upgrade the J2SE SDK.

    If an incompatible system-wide version of the J2SE SDK is detected, you are asked if you want the installer to upgrade or if you want to upgrade manually. 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.

ProcedureTo Specify Installation Directories and Initiate the System Check

  1. Accept the default installation locations for the selected product components, or replace the default locations and press Return.

    A default installation directory is displayed for each selected product component. For example, on Solaris:

    Installation Directories
    Enter the name of the target installation directory for each product:
    Directory Server [/opt/SUNWdsee]  {"<" goes back, "!" exits}
    Directory Preparation Tool [/opt/SUNWcomds]  {"<" goes back, "!" exits}
    Web Server [/opt/SUNWwbsvr7]  {"<" goes back, "!" exits}
    Web Server Instance [/var/opt/SUNWwbsvr7]  {"<" goes back, "!" exits}
  2. Review any issues discovered by the system check.

    After the installation directories are chosen, the installer automatically initiates a check for disk space, memory, swap space, operating system patches, and operating system resources based on the components you selected. The left column of the following table lists the possible results of the system check. The right column specifies what action you should take for each situation

    Message Displayed 

    Your Action 

    System ready for installation

    Proceed with installation. 

    System ready for installation

    Includes a warning that memory or swap space is not at the recommended level. 

    Proceed with installation, but add memory or swap space when installation is complete. If you do not add memory or swap space, performance might be seriously affected. 

    System not ready for installation

    If any patches are missing, the patch numbers are displayed. If you can fix the reported problems without stopping the installer, do so and then click Proceed with installation. 

    For some issues, such as low memory, you can proceed with installation, but for others, such as missing patches, you must resolve the issue before the installer can proceed.

    Solaris 10. If the installer is running in a non-global zone, you will receive a message telling you that memory information is not available.

  3. Install any missing operating system patches.

    You will need to install missing patches before you can proceed with installation. For guidelines, refer to To Install a Patch.

  4. After the system is ready for installation, press Return to continue.

    You are queried about what type of configuration you want for the installation and asked to provide global settings.

ProcedureTo Specify a Configuration Type and Common Server Settings

  1. Specify a configuration type from the following options:

    • Configure Now (the default). Allows you to configure product components that permit configuration at installation time. Your Configure Now tasks include specifying the common server settings, and entering the configuration information for the product components selected.

      Note –

      Some product components cannot be configured during installation. If any of these product components were selected, you receive a message saying that you will need to configure these product components after installation.

    • Configure Later. You provide only the minimum values that are necessary for installing the packages. The installer proceeds without doing further configuration. If you chose the Configure Later type, skip to To Install the Software.

  2. For a Configure Now installation, specify common server settings.

    The installer presents you with a list of common server settings and their defaults for the components your selected. For example:

    Specify Common Server Settings
    Enter Host Name [myComputer]  {"<" goes back, "!" exits}
    Enter DNS Domain Name []  {"<" goes back, "!" exits}
    Enter IP Address []  {"<" goes back, "!" exits}
    Enter Server admin User ID  [Admin]  {"<" goes back, "!" exits}
    Enter Admin User's Password (Password cannot be less than 8 characters) []  {"<" goes back, "!" exits}
    Confirm Admin User's Password  []  {"<" goes back, "!" exits}
    Enter System User [root] {"<" goes back, "!" exits}
    Enter system Group [root] {"<" goes back, "!" exits}

    Either accept the defaults, or use alternate data for these global parameters. For information on the parameters, refer to the Common Settings in Sun Java Enterprise System 5 Installation Reference for UNIX.

    Note –

    When passwords are typed, they must be at least 8 characters long. The following special characters cannot be used:

    ; & ( ) ! | < > ' “ $ ^ \ # / , @ %

ProcedureTo Specify Component Configuration Data

For a Configure Now installation, the installer presents one or more configuration queries for the selected product components that can be configured during installation. The following information can help in your selection:

Tip –

After installation is complete, you can access your configuration information in the Installation Summary here:

Solaris OS: /var/sadm/install/logs

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

  1. Specify configuration settings for product components.

    Either accept the defaults or use the information you gathered in the product component worksheets to answer the installer queries regarding each product component.

    A typical configuration query looks similar to the following:

    Web Server: Specify instance Settings
    Server Name []  {"<" goes back, "!" exits}
    Enter HTTP Port [80]  {"<" goes back, "!" exits}
    Enter Runtime UNIX User ID [webservd]  {"<" goes back, "!" exits}
    Enter Document Root Directory [/var/opt/SUNWwbsvr7/docs] {"<" goes back, "!" exits}

    Note –

    You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with 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 product components.

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

    • 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

    Note –

    To use Web Server as the web container, the Web Server Configuration Type mode must be set to Admin Server, not Agent, when you are queried on the Web Server Configuration Type Data page. Default value is Admin Server.

  2. Review the list of your selected product components and subcomponents.

    After configuration values are set, the installer displays a Ready to Install list of the components and subcomponents that you have selected. For example:

    Ready to Install
    The following components will be installed.
    Product: Sun Java Communications Suite 5
    Uninstall Location: /var/sadm/prod/SUNWcomm-entsys5
    Space Required: 199.10 M
    Sun Java (TM) System Web Server 7.0 2006Q4
    Sun Java (TM) System Web Server 7.0 CLI
    Sun Java (TM) System Web Server 7.0 Core
    Sun Java (TM) System Directory Preparation Tool
    Sun Java (TM) System Directory Server Enterprise Edition 6.0 2006Q4
    Sun Java (TM) System Directory Server 6 Core Server
    Sun Java (TM) System Directory Service Control Center
    Sun Java (TM) System Directory Server Enterprise Edition 6 Command-Line Utilities
    Sun Java (TM) System Directory Proxy Server 6 Core Server

    If you need to make changes, type < and press Return until you reach the prior query that requires a change. Although shared components are not explicitly listed, they have already been verified and will be installed if they are needed by the selected product components.

ProcedureTo Install the Software

When you are satisfied with the Ready to Install list, you can start the installation.

Note –

For Linux, do not use the rpm command while the installer is running. If you do, the installer might hang.

  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, this process can be lengthy.

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

  2. Examine the Installation Summary and Installation logs.

    When installation is complete, any issues from the installation, such as insufficient memory, are displayed on the screen. The following files also contain useful information

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

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

    After installation, these files can be found here:

    Solaris OS: /var/sadm/install/logs

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

    To see a full listing of the installer logs, refer to Examining Installation Log Files.

  3. Exit the installer.

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