This chapter provides instructions for using the interactive graphical interface to install the Sun JavaTM Enterprise System (Java ES) software.
This chapter includes the following sections:
Before beginning the procedure in this chapter, you should have developed an installation sequence, surveyed your system for incompatibilities, and fulfilled any necessary prerequisites. Refer to Installation Prerequisites for more specific information.
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: On the Access Manager: Administration (1 of 6) page, select Legacy (version 6.x style). On the Access Manager: Web Container for running Access Manager (4 of 6) 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:
If you have problems during installation, refer to the troubleshooting information in Chapter 9, Troubleshooting.
(Optional) Provide access to your local display.
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):
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.
If you are not logged in as root, become superuser.
Start the graphical installation interface.
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:
Enter the command to start the installer using the fully qualified path to the installer:
In this command, mountpoint is where you mounted the CD and os-arch matches your platform, such as Solaris_sparc, Solaris_x86 or Linux_x86.
For a DVD. Navigate to the DVD directory whose name matches your platform, and enter the command to start the installer:
For a Download. Navigate to the directory where you downloaded the software, and enter the command to start the installer:
The Welcome page is displayed.
If you click Cancel at any time, the installer exits after you have confirmed that you do want to terminate the installer session.
Click Next to continue.
The Software License Agreement page is displayed.
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 will end the installation process.
The Language Support page is displayed.
If your installer window is too small to view all the text, you might need to resize the window manually by dragging the corner.
The packages for the languages you choose will be installed for all the components you select. Each selection causes additional packages to be installed, adding to the disk space required for installation. English is always installed.
The following points about component selection and the Component Selection page will help you make selections.
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.
On Solaris OS. If an incompatible version of Application Server or Message Queue is detected, you can choose to upgrade the bundled version during installation. If the installer determines that there is a risk to data or if applications have been deployed, you will be asked if you want to continue. If you answer no, you will need to exit the installer, remove the incompatible versions of Application Server or Message Queue and restart the installation process.
This upgrade performed by the installer does not handle any data migration.
If an incompatible component that cannot be upgraded by the installer is detected, you need to remove or manually upgrade the component. For upgrade instructions, refer to the Sun Java Enterprise System 2005Q4 Upgrade Guide. After resolving the problem, click Refresh List to redisplay the Component Selection panel.
On the Language Support page, select the languages in which you want to install the Java ES components.
Click Next to continue.
The Component Selection page is displayed.
The Component Selection page displays a list of components, organized in groups of related services.
To see information about the individual components, hold the cursor over the item. A description of that item is displayed in the text box at the bottom of the page. Components that are already installed are disabled (grayed out).
To see information on the compatibility status of a component, click the ellipsis (...) in the Details column, if available.
Select the components you want to install.
To select all components, choose Select All and click Next.
To select some components, individually select the components. As you make each selection, the installer automatically selects any components that the component you selected depends on.
If applicable, select a web container.
If you are not sure which component to use for your web container, you can select both Application Server and Web Server, then choose the Configure Now option. You will be offered a choice of web container on a subsequent configuration page.
Access Manager and Portal Server need to use the same type of web container.
If applicable, select a third-party web container.
If you are going to use a third-party web container, do the following:
If applicable, specify any remote dependencies.
If you are going to satisfy dependencies by using components installed on other hosts, do the following:
After you have made your component selections, expand and scan the entire list of components to see what the installer has automatically selected.
Deselect any component that you are going to access on a remote host, such as Directory Server. When you click Next, the Dependency Warning screen is displayed.
Choose to use a version installed on a remote host.
The installer performs a dependency check of the selected 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.
Resolve component dependency issues and click Next. Repeat this process until you are allowed to proceed.
The installer then performs a compatibility check of any shared components already installed. If any incompatible versions of components are found, you will be asked to remove them from the host.
Click Yes to have the installer remove the incompatible shared components or click No to remove the components manually.
If you select No, you must remove the component before continuing with the installation.
After the offending component has been removed, 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.
Review the incompatible components list and determine if it is safe for the installer to automatically upgrade the shared components listed.
Click Next to allow the installer to automatically upgrade the shared components listed.
This upgrade does not happen until you reach the Ready to Install page.
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.
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.
The Installation Directories page is displayed.
The Installation Directories page displays the default installation directories for the components you have selected. For example:
Examine the default installation directories.
To see a list of all the default directories and ports, refer to Chapter 3, Default Installation Directories and Ports, in Sun Java Enterprise System 2005Q4 Installation Reference.
Verify that the directories are correct for your deployment.
If the default directories are not acceptable, browse for alternative paths and change as needed.
Click Next to initiate the system check.
The installer checks for disk space, memory, operating system patches and operating system resources based on the installation directories provided. 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.
System ready for installation
Click Next to continue.
System ready for installation Includes a warning that memory is not at the recommended level.
Click Next to continue, but add memory when installation is complete. 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. 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.
Go to the Sunsolve site: http://sunsolve.sun.com
Click Patch Portal.
Enter the patch number in the PatchFinder text box, and click Find Patch.
Download the zip file for the patch.
Expand the zip file. For example: unzip 112785-44.zip
A directory is created for the patch files.
Apply the patch. For example: patchadd 117885-44
Back in the Java ES installer, click Check Again. All system requirements are rechecked.
When the system check is complete and you are satisfied with the state of the system, click Next.
If some of the components you have chosen can be configured during installation, the Configuration Type page is displayed. You have the following configuration choices:
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.
Some components cannot be configured during installation. If any of these components were selected, you are warned that you will need to configure these 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 option, skip to Running the Installer in Graphical Mode.
Specify a configuration type.
For a Configure Now installation, you are asked to provide global configuration information. Defaults are displayed, except for passwords (passwords must be a minimum of 8 characters).
Specify common server settings.
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:
Solaris OS: /var/sadm/install/logs
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 the following component configuration pages. Refer to Common Server Settings in Sun Java Enterprise System 2005Q4 Installation Reference for information on these fields. The following sample screen shows the Common Server Settings configuration page.
Click Next to proceed.
The components configuration pages for each component that can be configured during installation are displayed one by one.
For a Configure Now installation, the installer presents one or more configuration pages for the selected components that can be configured during installation. The following information can help in your selection:
For information on the configuration values on each page, click the online help button at the bottom of each page.
For information on the configuration values for each configuration page, refer to Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference.
For configuration worksheets, refer to Chapter 2, Configuration Worksheets, in Sun Java Enterprise System 2005Q4 Installation Reference.
Some of the fields in a component configuration page display default values from the Common Server Settings page. These values can be edited. For example, the fields in the Directory Server sample screen that contain default values set by the Common Server Settings page are Administrator User ID and Administrator Password. These fields are marked with the note “ Shared default value.”
The following example screen shows the initial Directory Server configuration page.
Although Sun Cluster software itself cannot be configured during installation, you are offered the option of enabling remote support to simplify postinstallation configuration. The default is Yes.
As the individual configuration pages are displayed, specify the information for the settings.
Click Next to proceed to the next component configuration page.
When you click Next on the final configuration page, installation-time configuration is done.
The Ready to Install page is displayed.
Before transferring the software to your system, the installer lists 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.
Review the components listed and make any necessary changes.
Click Next when you are satisfied with the Ready to Install list.
The Product Registration page is displayed.
Accept the default “Open registration window during installation” if you want to register your products while software is being installed.
If not, deselect the default option.
If you click Cancel at the Progress page, the installer exits after you have confirmed that you do want to terminate the installer session.
If you click Stop while the installation is in progress, the installer rolls back any components that have already been installed and presents the Summary page. You are asked to confirm whether you want to terminate the installer session.
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, the installation process can be lengthy.
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.
Click View Summary or View Install Log to examine information about the installation.
This information is available in the following locations after you exit the installer:
On Solaris OS: /var/sadm/install/logs
On Linux: /var/opt/sun/install/logs
To see a full listing of the Java ES logs, refer to Examine Installation Log Files.
To access the postinstallation instructions, click the box to automatically display the Installation Guide for UNIX.
Click Close to exit the installer.
Your installation session is done. Components that were installed will need to be started after you have completed all postinstallation tasks.
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 components are disabled at the Component Selection page.
For example, suppose you have installed Access Manager and its required components during this installation. Later, you decide to install Portal Server. The existing instance of Access Manager will be used to meet the Portal Server dependency on Access Manager. You will not be asked to reinstall Access Manager.
After you have completed the installer portion of your Java ES installation, proceed as follows:
Verifying After Installation provides instructions for verifying that this phase of installation was successful.
Chapter 6, Configuring Components After Installation provides final instructions on postinstallation configuration. Although you might have done extensive configuration during your installation, most components require some additional configuration.