Previous Contents Index Next |
Sun Java Enterprise System 2004Q2 Installation Guide

> ## Chapter 4
> Installing Software Using the Graphical Interface

> This chapter provides instructions for using the installer’s interactive graphical interface to install the Java Enterprise System software. Before starting the tasks in this chapter, you should have already completed the tasks in Chapter 2, "Preparing for Installation".

> This chapter includes the following sections:

> - Preinstallation Checklist
> - Identifying Component Upgrade Needs
> - Running the Installer in Graphical Mode
> - Adding Components
> - Next Steps

> For an introduction to the Java Enterprise System installer, read How Does the Java Enterprise System Installer Work?

> ##

> Preinstallation Checklist

> The following table lists the tasks that you should perform before beginning installation. The left column lists the order in which you should perform the tasks, the middle column describes the action, and the right column contains other useful information and the location of instructions.

> Table 4-1 Preinstallation Tasks

> Order | Task | Instructions and Helpful Information
> --- | --- | ---
> 1 | Verify that system requirements are met. | Java Enterprise System Release Notes, http://docs.sun.com/doc/817-5503
> 2 | Upgrade any existing component products that are incompatible with Java Enterprise System 2004Q2. | prodreg, pkginfo, or rpm command (for further information, refer to their man pages) Identifying Component Upgrade Needs Chapter 8, "Upgrading from Java Enterprise System 2003Q4" Chapter 9, "Upgrading Components from Versions Predating Java Enterprise System"
> 3 | Plan how to install product components. | Chapter 2, "Preparing for Installation"
> 4 | Gather configuration information for component products. | Chapter 3, "Gathering Installation and Configuration Information" Appendix A, "Worksheets for Gathering Information"
> 5 | Make a copy of the product registry file, /var/sadm/install/productregistry on Solaris, /var/opt/sun/install/productregistry on Linux. | The backup copy of the product registry is helpful in recovering from a failed installation.
> 6 | Create the necessary system accounts. | For Directory Server, Directory Proxy Server, or Administration Server to run as a non-root user, you must create the accounts before configuring.
> 7 | If you are installing with Sun Cluster software (available on Solaris only), plan your installation sequence. | High Availability Using Sun Cluster Software
> 8 | If you are installing components that depend on servers or services that are already installed, ensure that the existing servers and services are running and accessible. | For example, If you are installing Portal Server, Secure Remote Access subcomponents, the Portal Server, Secure Remote Access core must be running and accessible.
> 9 | If you are installing Application Server or Directory Server on Solaris, verify that Perl is installed. | Perl packages (SUNWpl5*) can be found on the Solaris 8 and Solaris 9 media. Use pkgadd to add the packages.
> 10 | If you are installing Identity Server or Messaging Server, verify that the domain name of the machine on which the Identity Server is going to be installed is set. | To set the domain name, do one of the following: If the file /etc/resolv.conf exists, enter the domain name in the domain configuration entry. Example: domain madisonparc.com If the file /etc/resolv.conf does not exist, enter the following command: # domainname domain_name
> 11 | If you are installing Web Server, verify that UID 80 and GID 80 are not already allocated for Web Server use. | If 80 is already allocated to Web Server, errors will occur and Web Server installation will fail.
> 12 | If this is a reinstallation, verify that the Web Server directory does not exist. | The default installation directory for Web Server is /opt/SUNWwbsvr on Solaris and is /opt/sun/webserver on Linux.
> 13 | If you are installing Calendar Server or Messaging Server, verify that the second column in the /etc/hosts file contains the fully-qualified domain name (FQDN) rather than a simple host name. | For example: 192.18.99.999 mycomputer.company.com loghost
> 14 | If you are upgrading the J2SE software, verify that you have stopped other products that depend on the J2SE component you are upgrading. | Refer to J2SE Platform Upgrade Information for more J2SE information.
> 15 | If Directory Proxy Server is to use a preinstalled configuration Directory Server, ensure that the configuration Directory Server is running during the installation of Directory Proxy Server. If you are installing Directory Proxy Server and configuration Directory Server at the same time, it is not necessary to perform this preinstallation task. |

> ##

> Identifying Component Upgrade Needs

> For software that has been installed using a package-based installation, you can use the installer to perform a pre-installation check of the Java Enterprise System-related software packages that are already on your system. The benefit of doing this is that you can identify any component incompatibilities in advance and take care of them before installation. This allows your installation session to run more efficiently.

> ##### To Use the Graphical Installer for Identifying Component Upgrade Needs

> 1. Provide access to your local display.
> - The Java Enterprise System installer may need access to your local display. If you are logging in to a remote machine, or using the su command to become superuser on a local machine, use the xhost command on the local machine to allow access to your local display. For example, use the following command to grant access to all users:

> xhost +

> - If you are logging in to a remote machine, 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 (machine name myhost):

> setenv DISPLAY myhost:0.0

> - Example for Korn Shell (machine name myhost):

> DISPLAY=myhost:0.0

> 2. Start the installer using the -no option to indicate that this is not an active installation:

> ./installer -no

> 3. Proceed through the installer pages to the Component Selection page.
> 4. Click View Component Statuses at the top of the page.

> The View Component Statuses report lists the installed component products, specifying the level of Java Enterprise System compatibility for each component.

> 5. If the View Component Statuses report indicates that the machine has older versions of component products installed, exit the installer and upgrade the reported components. Otherwise, close the View Component Statuses report and proceed to Step 6.

> To upgrade components from Java Enterprise System 2003Q4 versions, refer to Chapter 8, "Upgrading from Java Enterprise System 2003Q4". To upgrade components from earlier versions, refer to Chapter 9, "Upgrading Components from Versions Predating Java Enterprise System".

> 6. Click Select All to select all component products. Then, click Next to continue.

> If the machine contains shared components that are incompatible with Java Enterprise System, the Shared Components Upgrades Required page is displayed.

> 7. For each shared component, review the Installed Version against the Required Version to determine what upgrading needs to be done.
> 8. Exit the installer. Then, determine whether the newer Java Enterprise System versions of shared components are compatible with other installed applications on the host.

> Caution | Do not upgrade shared components without checking the dependencies that exist on the host. Functional problems might occur for applications installed on the host that use the shared components. You should verify that existing applications are compatible with the required versions of the shared components.

> After you have verified that it is safe to upgrade shared components on the host, do one of the following:

> - Upgrade shared components as needed.
> - Allow the installer to upgrade shared components during your active installation.

> Repeat the preceding steps until the installer indicates that components meet Java Enterprise System requirements.

> ##

> Running the Installer in Graphical Mode

> This section contains the following procedures:

> - To Start the Graphical Installer
> - To Select Languages for Installation
> - To Select Component Products
> - To Allow the Installer to Check Your Selections
> - To Upgrade Shared Components
> - To Specify Installation Directories and Initiate the System Check
> - To Specify a Configuration Type
> - To Specify the Common Server Settings
> - To Configure the Individual Component Products
> - To Confirm Installation Readiness
> - To Register Products and Begin Installing Software
> - To Cancel Installation
> - To Complete the Installation Session

> If you have problems during uninstallation, refer to Chapter 11, "Troubleshooting".

> ##### To Start the Graphical Installer

> 1. Provide access to your local display.
> - The Java Enterprise System installer may need access to your local display. If you are logging in to a remote machine, or using the su command to become superuser on a local machine, use the xhost command on the local machine to allow access to your local display. For example, use the following command to grant access to all users:

> xhost +

> - If you are logging in to a remote machine, 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 (machine name myhost):

> setenv DISPLAY myhost:0.0

> - Example for Korn Shell (machine name myhost):

> DISPLAY=myhost:0.0

> 2. If you are not logged in as root, become superuser.
> 3. Start the graphical installation interface:
> - If you downloaded the software, navigate to the directory where you downloaded it.

> cd installer-directory

> Enter the command to start the installer:

> ./installer

> - If you are using a DVD, navigate to the directory whose name matches your platform, either to the Solaris_sparc, Solaris_x86 or Linux_x86 directory. Then, enter the command to start the installer:

> ./installer

> - If you are using CDs, navigate to a directory 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:

> mount-point/os-arch/installer

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

> You can use the optional -no parameter to run the installer without installing any software. This is useful to familiarize yourself with the installer and for creating state files for a subsequent silent install.

> A full description of the installer options is contained in Installer Command-line Options.

> 4. The installer starts and the Welcome page is displayed.

> ##### To Select Languages for Installation

> The languages you choose will be installed for all the components you select. Each language causes additional packages to be installed, which adds to the disk space required for installation. English is always installed.

> Note | If the language of the host system locale is not English, the language on the host system is selected by default.

> 1. On the Language Support page, select the languages in which you want to install the Java Enterprise System components.
> 2. Click Next to continue.

> ##### To Select Component Products

> The Component Selection page displays a list of component products, organized in groups of related services.

> 1. To install all selectable components, click Select All. Then, click Next and skip to To Allow the Installer to Check Your Selections
> 2. To install specific component products, individually select the component products you want to install. As you make each selection, the installer automatically selects any components that the component you selected depends on.

> Tip | If you are planning to satisfy dependencies by referring to components installed on other machines, scan the entire list of component products after you have made your selections. You can then make sure any components the installer automatically selected are deselected.

> After you have finished selecting components, click Next to continue.

> Next to each component product is a number that represents the disk space it requires. At the top of the page, the Estimated number changes as you select and deselect component products, providing an approximate total of the disk space required for all your selected component products.

> Component products that are already installed are disabled (and thus grayed out). To see a report about these components, click View Component Statuses at the top of the page.

> ##### To Allow the Installer to Check Your Selections

> When you click Next on the Component Selection page, the installer performs a dependency check of the selected component products. If there is a problem with dependencies, the installer displays a Product Dependency Checks error window or warning window, depending on the problem:

> - If a local dependency cannot be met, the installer displays an error window. For example, if Messaging Server was selected but Administration Server was not, the installer displays an error window because Messaging Server requires Administration Server to be installed on the same machine.

> In this situation, click Close to dismiss the error window, and then select the appropriate component to satisfy the local dependency.

> - If a remote dependency must be met later during component configuration, the installer displays a warning window. For example, if Identity Server was selected but Directory Server was not, the installer displays a warning window as a reminder that you will need to specify a remote installation of Directory Server when you configure Identity Server.

> In this situation, click Continue if you intend to specify a remote installation during configuration. Otherwise, click Cancel and select the appropriate component to satisfy the dependency locally.

> - If previous versions of component products are already installed, the installer displays a warning window.

> In this situation, you should click Cancel, exit the installer, and upgrade the reported components.

> To upgrade components from Java Enterprise System 2003Q4 versions, refer to Chapter 8, "Upgrading from Java Enterprise System 2003Q4". To upgrade components from earlier versions, refer to Chapter 9, "Upgrading Components from Versions Predating Java Enterprise System".

> ##### To Upgrade Shared Components

> When you click Next on the Component Selection page, the installer performs a dependency check of the selected component products. After this check, the installer performs a compatibility check of any shared components already installed.

> 1. If an incompatible system-wide version of the J2SE Software Development Kit is detected, the J2SE(TM) Software Development Kit Upgrade Required page is displayed.

> Note | The installer performs this check only on the Solaris platform because the Linux platform does not have a specfic, system-wide installation of the J2SE Software Development Kit.

> For information about the upgrade options, see J2SE Platform Upgrade Information. Select an option and click Next.

> 2. If incompatible versions of any other shared components are detected, the Shared Components Upgrade Required page is displayed.

> Caution | Do not upgrade shared components without checking the dependencies that exist on the host. Functional problems might occur for applications installed on the host that use the shared components. You should verify that existing applications are compatible with the required versions of the shared components.

> To have the installer upgrade the shared components listed on the Shared Components Upgrades Required page, click Next.

> ##### To Specify Installation Directories and Initiate the System Check

> The Installation Directories page displays the default directories for the component products you have selected.

> 1. Examine the default installation directories and verify that they are correct for your deployment before accepting them.
> 2. If the directory defaults are not acceptable, browse for alternative paths and change as needed.
> 3. Click Next to initiate the system check.

> The installer checks the following system requirements, based on the directories you provided:

> - Available disk space
> - Installed memory
> - Operating system patches
> - Operating system resources

> The left column of the following table lists the possible results of the system check. The right column specifies what you should do for each type of result.

> Table 4-2 System Check Results

> Message Displayed | Your Action
> --- | ---
> System ready for installation | Click Next to specify a configuration type.
> System ready for installation Includes a warning that memory is not at the recommended level. | Click Next to proceed with the installation, but add memory when you are done. If you do not add memory, performance might be seriously affected.
> System not ready for installation | Click View Report for information on the problems that the installer found. Problems can include insufficient memory, missing required operating system patches, and so on. If you need to stop the installer to resolve a problem, click Cancel. Fix the problem and then restart the installer. If you can fix the reported problems without stopping the installer, do so and then click Check Again to recheck the system. Click Next to proceed when the system check displays the following message: System ready for installation

> 4. When the system check is complete and you are satisfied with the state of the system, click Next.

> ##### To Specify a Configuration Type

> If you have chosen components that can be configured at installation time, the Configuration Type page is displayed.

> Note | The following component products cannot be configured at installation time: Calendar Server, Communications Express, Instant Messaging, Messaging Server, Sun Cluster and Sun Remote Services Net Connect.

> 1. Decide which configuration type you want:
> - Configure Now. Allows you to configure component products that permit configuration at installation time.

> Your tasks include specifying the common server settings, then specifying the configuration information for the components products you selected.

> - Configure Later. The installer proceeds without doing further configuration. Skip to To Confirm Installation Readiness.
> 2. Select a configuration type and click Next.

> ##### To Specify the Common Server Settings

> If you chose a configuration type and component set that require configuration during installation, the configuration pages are displayed. Descriptions of the information on each configuration page of the installer are contained in Chapter 3, "Gathering Installation and Configuration Information", organized according to component.

> Before beginning this phase of the installation, verify that you have gathered the configuration information needed for the component products you selected.Worksheets for collecting your configuration data can be found in Appendix A, "Worksheets for Gathering Information".

> For a Configure Now configuration, the Common Server Settings page is displayed.

> 1. Accept the defaults or use the information you have gathered in the component product worksheets. Common server settings values are described in Table 3-2.

> Values that you enter here appear as default values on the component product configuration pages.

> Tip | Write down any non-default information you enter here as well as passwords. You might need this information for subsequent tasks. The worksheets in Appendix A, "Worksheets for Gathering Information" can help you keep track of this information.

> 2. Click Next to proceed to the component products configuration pages.

> ##### To Configure the Individual Component Products

> After you have specified the Common Server Settings, the installer presents one or more configuration pages for the component products you selected.

> Some of the fields in a component product page display default values from the Common Server Settings page. These values can be edited. For example, the following sample screen shows the initial Directory Server configuration page. The fields whose default values are set by the Common Server Settings page are Administrator User ID and Administrator Password. These fields are marked with the note “* Shared default value.”

> 1. As the individual configuration pages are displayed, you are asked to specify information for the settings.

> 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 in /var/sadm/install/logs on Solaris and in /var/opt/sun/install/logs on Linux.

> The following table provides cross-references to specific pages in Chapter 3, "Gathering Installation and Configuration Information," where you can find detailed information on the configuration settings.

> Table 4-3 Location of Component Product Field Descriptions

> Component | Location of Configuration Information
> --- | ---
> Administration Server | Administration Server Configuration
> Application Server | Application Server Configuration
> Calendar Server | Calendar Server Configuration
> Directory Server | Directory Server Configuration
> Directory Proxy Server | Directory Proxy Server Configuration
> Identity Server | Identity Server Configuration
> Identity Server SDK | Identity Server SDK Configuration
> Instant Messaging | Instant Messaging Configuration
> Message Queue | Message Queue Configuration
> Messaging Server | Messaging Server Configuration
> Portal Server | Portal Server Configuration
> Portal Server, Secure Remote Access | Portal Server, Secure Remote Access Configuration
> Web Server | Web Server Configuration

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

> When you click Next on the final configuration page of the final component product, installation configuration is done. The installer is now ready to install the software packages.

> ##### To Confirm Installation Readiness

> Before transferring the software to your system, the installer displays a summary page, showing the component products that you selected on the Component Selection page. Shared components are not explicitly listed, but they will be installed if they are needed.

> 1. Review the components listed on the Ready to Install page.

> Note | When the installer displays this page, a Shared Components Upgrade Install window is displayed telling you that the shared components are being installed. Wait until the shared components are installed before proceeding.

> 2. Make necessary changes on the Component Selection page.
> 1. To return to the Component Selection page, click the Back button and continue to click Back on successive pages until the Component Selection page is again displayed.
> 2. Click Next to move forward through the installer again. You do not need to enter previously-entered values.
> 3. Click Next when you are satisfied with the Ready to Install list.

> ##### To Register Products and Begin Installing Software

> The Product Registration page provides the option of registering your products while software is being installed.

> 1. If you do not want to fill in and submit the registration forms while installation is running, deselect the default option “Open registration window during installation.”
> 2. Click Install to begin installing the component packages. 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.

> Note | Depending on the size and complexities of your installation, the installation process can be somewhat lengthy.

> ##### To Cancel Installation

> You can cancel installation by clicking Cancel. This starts the uninstaller and removes software that has already been installed.

> ##### To 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. This information is saved in files located in /var/sadm/install/logs on Solaris and in /var/opt/sun/install/logs on Linux so that you can refer to it after you exit the installer.
> - Installation Summary. Lists each component installed and the settings you specified. If you chose Configure Now configuration, this summary includes all the configuration values.
> - Installation log. Displays the installer’s log messages for component products.
> 2. Click Close to exit the installer.

> Your installer session is done. Component products that were installed will need to be started after you have completed the post-installation tasks.

> 3. Proceed to Next Steps for instructions on how to complete the Java Enterprise System installation.

> ##

> 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. The Component Selection page disables choices that represent the installed components.

> For example, suppose you have installed Identity Server and its dependencies during this installation. Later, you decide to install Portal Server. The existing instance of Identity Server will be used to meet Portal Server’s dependency, and you will not be asked to reinstall Identity Server.

> ##

> Next Steps

> At the end of this chapter you should have completed the installer portion of your Java Enterprise System installation. Proceed to Postinstallation Configuration and Startup for final instructions on configuring the component products for your environment.

> Note | Although you might have done extensive configuration during your installation, most component products require some additional configuration. Read the postinstallation configuration requirements carefully before proceeding to any other tasks.

> If you want to make an installation image available to other administrators in your enterprise, refer to Setup Instructions for Network Installation.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.