Sun and OracleChannel SunHow to BuyLog InEnglish

Sun Java Communications Suite 5 Installation Guide
  Search only this book
Search Help
View this book in:
Contained Within
Find More Documentation
Featured Support Resources
 Download this book in PDF (1689 KB)

Chapter 3 Installing Communications Suite With the Graphical Interface

This chapter provides instructions for using the interactive graphical interface to install the Communications Suite software.

This chapter includes the following sections:

Before Installing

Before beginning the tasks in the chapter, you should have developed an installation sequence and ensured that any general installation requirements and prerequisites are met.

Verifying Prerequisites and Requirements

Refer to Verifying General Installation Prerequisites for specific information on prerequisites for this release of Communications Suite.

You can find system requirements for Communications Suite listed in the Sun Java Communications Suite 5 Release Notes. For Java ES, see Platform Requirements and Issues in Sun Java Enterprise System 5 Release Notes for UNIX.

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.

  • For Configure Now: On the Access Manager: Administration (1 of 7) page, select Legacy (version 6.x style). On the Access Manager: Web Container for running Access Manager (4 of 7) page. set the Console Deployment URI to amconsole (the default value).

  • 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

(Optional) Setting Your Local Display for a Remote Host

If you are logging in to a remote host, make sure your DISPLAY environment variable is properly set to the local display. If the DISPLAY variable is not set properly, the installer runs in text-based mode.

  • Example for C Shell (host name myhost):


    setenv DISPLAY myhost:0.0

  • Example for Korn Shell (host name myhost):


    DISPLAY=myhost:0.0

You might need to grant display authorization to run the installer on your local display. For example, you can use the following command to grant display authority from myhost to the root user on serverhost:


myhost\> xauth extract - myhost:0.0 | rsh -l root serverhost xauth merge -

For full instructions on granting such authorization safely, refer to the “Manipulating Access to the Server” chapter in the Solaris X Window System Developer's Guide.

Getting the Software

  • For Download. Navigate to the directory where you downloaded the Communications Suite installation bundle and expand the bundle. For example:

    unzip compressed-file.zip

    You will see a Copyright file, a README directory and the operating system directory, such as Solaris_sparc. In the operating system directory, you will see the Product directory, the release_info file, and the installer script.

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


    cd /tmp

    You will run the installer command using the fully qualified path to the installer. For example:


    mountpoint/os_arch/installer

    In this example, mountpoint is where you mounted the CD and os_arch matches your platform, such as Solaris_sparc.

  • For DVD. Navigate to the DVD directory whose name matches your platform.

Running the Installer in Graphical Mode

A full description of the options for the installer command 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 graphical installer:

    ./installer

    The Welcome page is displayed.

    Note –

    If you click Cancel at any time, the installer exits after you have confirmed that you want to terminate the installation session.

  3. Click Next to continue.

    The Software License Agreement page is displayed.

  4. If you accept all the terms of the License, click Yes, Accept License.

    If you do not accept all the terms of the License, select Decline. This ends the installation session.

ProcedureTo Select Components and Languages

After you have accepted the terms of the license, the installer surveys the software on your host and presents you either with a page for upgrading certain components detected on the host, or the Component Selection page.

Note –

Monitoring Console cannot be run on any host where its monitored components are located. Because the installer does not prevent you from installing them together, it is important that you always run a separate installation session to install Monitoring Console on a host separate from the Communications Suite components. For instructions in installing Monitoring Console, see the Sun Java Enterprise System 5 Installation Guide for UNIX.

  1. If needed, run an upgrade session using the installer.

    The installer surveys the host for incompatible versions of Application Server, Message Queue, and HADB. If any of these components are found, the Choose to Upgrade or Install page is displayed, allowing you to upgrade these components.

    • If you do not plan to install any of these components in your session, you can accept the default which is Install New Software, then proceed with installation.

    • If you will be installing any of these components, choose Upgrade Existing Software. An upgrade session starts, displaying the upgradable components. Shared components are usually included. When you have completed the upgrade session, you can then start a new installation. For additional information, refer to How Upgrading Works.

    Note –

    Application Server, Message Queue, and HADB are the only product components that can be upgraded by the installer. If any other incompatible product components are found, you will receive a message telling you that you must exit the installer and upgrade or remove these components before the installer can proceed.

  2. Select the software you want to install.

    • If your installer window is too small to view all the text, you might need to resize the window manually by dragging the corner.

    • To see information about the individual product components, hold the cursor over the item. A description of that item is displayed in the text box at the bottom of the page.

    • To see information on the compatibility status of a product component, click the ellipsis (...) in the Details column, if available.

    • Product components that are already installed are disabled (grayed out). If they can be upgraded by the installer, their Status is Upgradable.

    • Click the Help button to view the online help for the page.

    • On Solaris 10. If you are running the installer in a non-global zone, any components that cannot be installed into a non-global zone will be disabled.

    Note –

    There are some specific issues to be aware of when installing or upgrading in Solaris 10 zones. For guidelines, refer to Solaris 10 Zones.

    On the Component Selection page, you can select components for installation as follows:

    • All components. To select all product components and their required shared components, choose Select All.

    • Some components. To select some product components, individually select the product components. As you make each selection, the installer automatically selects any product components that the component you selected depends on.

    • Subcomponents. To select subcomponents, expand the subcomponent list by clicking the expansion turner to the left of the component. As you make each selection, the installer automatically selects any product subcomponents that the component you selected depends on.

    • Shared components. To upgrade all shared components to the current release, select Shared Components.

    • Language packages. To install language packages, click Install multilingual packages for all selected components. (The default value is unselected.) Each additional component you select causes additional multilingual packages to be installed, adding to the disk space required for installation.

  3. If applicable, select a web container.

    • If you are not sure which product component to use for your web container, you can select both Application Server and Web Server, then choose Configure Now when prompted for configuration type. You will be offered a choice of web container on a configuration page later in the installation session.

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

  4. If applicable, select a third-party web container.

    To use a third-party web container, do the following:

    1. Do not select Application Server or Web Server at the Component Selection page.

      When you click Next, the Web Container Selection page is displayed.

    2. Choose Use Third-Party Web Container.

    3. Click OK.

  5. If applicable, specify any remote dependencies.

    To satisfy dependencies by using product components installed on other hosts, do the following:

    1. After you made you product component selections, expand and scan the entire list of components.

      Examine the selected components to see what the installer has automatically selected that you might not be aware of.

    2. Deselect any product component that you are planning to access on a remote host.

      For example, a previously-installed and configured Directory Serveris commonly accessed remotely. When you click Next, the Dependency Warning screen is displayed.

    3. Choose Use a Version Installed on a Remote Host.

    4. Click OK.

ProcedureTo Resolve Dependency and Compatibility Issues

The installer performs a dependency check of the selected product components and their associated shared components. If there is a problem, the installer might display one or more messages informing you of the problem and directing you to take action.

  1. Resolve product component dependency issues.

    The installer can only upgrade Application Server, Message Queue, or HADB. If incompatible versions of other product components are detected, you will need to upgrade or remove those components, then restart installation. For full instructions on upgrading Communications Suite components, see the Sun Java Communications Suite 5 Release Notes. For Java ES components, refer to Sun Java Enterprise System 2006Q3 Upgrade Guide.

  2. Click Next.

  3. Repeat steps 1 and 2 until you are allowed to proceed.

  4. On Solaris OS, resolve J2SE SDK incompatibility.

    If an incompatible system-wide version of the J2SE SDK is detected on Solaris OS, the J2SE SDK Upgrade Required page is displayed. You are presented with choices about what to do to upgrade this software. Read the page and decide whether to upgrade automatically or manually. The default value is Automatically.

  5. Resolve shared component incompatibilities.

    After the product component issues have been resolved, the installer performs a compatibility check of any shared components already installed. If incompatible versions of shared components are detected, the Shared Components Upgrade Required page is displayed.

    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.

    1. Click Cancel to prevent the installer from upgrading.

      If you select Cancel, you must remove the incompatible shared components manually or the installer will not be able to continue past this point in the installation.

    2. Click Next to have the installer upgrade the incompatible shared components during this installation session.

      The Installation Directories page is displayed.

ProcedureTo Specify Installation Directories and Initiate the System Check

A default installation directory is displayed for each selected product component.

  1. Examine the default installation directories.

    To see a complete list of all the default directories and ports, refer to Chapter 2, Default Installation Directories and Ports, in Sun Java Enterprise System 5 Installation Reference for UNIX.

    • Verify that the directories are correct for your deployment.

    • If the default directories are not acceptable, browse for alternate paths and change as needed.

  2. Click Next to initiate the system check.

    The installer checks 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 result.

    Message Displayed 

    Your Action 

    System ready for installation

    Click Next to continue. 

    System ready for installation

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

    Click Next to continue, 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

    Click View Report for information on the problems that the installer found. If any patches are missing, the patch numbers appear in this report. If you can fix the reported problems without stopping the installer, do so and then click Check Again to recheck the system. 

    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.

    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.

  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. When the system check is complete and you are satisfied with the state of the system, click Next.

ProcedureTo Specify a Configuration Type and Common Settings

If some of the product components you have chosen can be configured during installation, the Configuration Type page is displayed. You have the following configuration choices:

  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 enter 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. Choose how your administrator user ID and password should be entered.

    If you selected more than one product component that uses administrator user ID and password, the Password Choice Panel is displayed.

    Note –

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

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

    • Use a single administrator account and password. (default) If you accept the default, you will enter the administrator user ID and password once, and the these fields will not be displayed again on the configuration pages.

    • Use different administrator account for each product. If you select this option, you will be asked to enter administrator user ID and password on the configuration pages for each of the selected components.

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

    Either accept the defaults, or use alternate data to answer the installer questions regarding these global fields. Values that you enter here appear as default values on subsequent product component configuration pages. Refer to online help or to Common Settings in Sun Java Enterprise System 5 Installation Reference for UNIX for information on these fields.

  4. Click Next to proceed.

    For a Configure Now installation, the configuration pages for each product component that can be configured during installation are displayed one by one.

    Tip –

    Configuration values are gathered by the installer as you proceed through the installation. After installation is completed, you can access this information in the Installation Summary in the following locations:

    Solaris OS: /var/sadm/install/logs

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

ProcedureTo Specify Configuration Data

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

Some of the fields in a configuration pages display default values from the Common Server Settings page. These values can be edited.

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.

  • 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

  1. As the individual configuration pages are displayed, specify the information for the settings.

    Defaults are displayed for configuration values, except for passwords.

  2. Click Next to proceed to the next product component configuration page.

  3. When you click Next on the final configuration page, installation-time configuration is done.

    The Ready to Install page is displayed.

ProcedureTo Install the Software

Before transferring the software to your host, the installer displays the components that you selected. Although shared components are not explicitly listed, they have already been verified and will be installed if they are needed.

  1. Review the components listed and make any necessary changes.

    1. To return to the Component Selection page, click the Back button.

      Continue to click Back on successive pages until the Component Selection page is again displayed. Make whatever changes are needed.

    2. Click Next to move forward through the installer again.

      You do not need to re-enter previously-entered values. Dependencies are rechecked. The system check is also repeated.

  2. Click Next when you are satisfied with the Ready to Install list.

    The Product Registration page is displayed.

  3. Accept the default “Open registration window during installation” to register your products while software is being installed.

    If not, deselect this option.

  4. Click Install to begin installing the component packages.

    Note –

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

    During installation, the following occurs:

    • A progress bar displays the overall percentage complete.

    • The names of packages are displayed as they are installed.

    • If you accepted the product registration option, a browser window that enables you to register is displayed.

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

    Note –

    If you click Cancel at the Progress page, the installer exits after you have confirmed that you want to terminate the installer session.

    If you click Stop while the installation is in progress, the installer rolls back any component packages that have already been installed and presents the Summary page. You are asked to confirm whether you want to terminate the installer session.

ProcedureTo Complete the Installation Session

When installation is complete, the Installation Complete page is displayed. Any issues from the installation, such as insufficient memory, are noted on this page. In addition, you are provided with access to the installation summary and logs.

  1. Click View Summary or View Install Log to examine information about the installation.

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

    • Installation Log. Displays the installer’s log messages for components.

    You can access this information at any time in the following locations

    Solaris OS: /var/sadm/install/logs

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

    For more information on the installer logs, refer to Examining Installation Log Files.

  2. To access the postinstallation instructions, click the box to automatically display the Installation Guide.

    Although you might have done extensive configuration during your installation, most product components require some additional configuration.

  3. Click Close to exit the installer.

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

Adding Components

To install additional components, you can run the installer again. The installer detects the newly-installed components and uses them to satisfy the dependencies of other components. Installed product components are disabled at the Component Selection page.

Note –

When adding product components to a host where a Communications Suite installation has already been done, be sure to use the correct paths and passwords if the new product component will use a product component that is already installed and configured. If you do not remember what these are, refer to the Installation Summary for the original installation before adding any product components to the host.

Next Steps

After you have completed the installer portion of your Communications Suite installation, proceed as follows: