Chapter 5 Installing Software Using the Text-Based Interface

This chapter provides instructions for installing the Java Enterprise System components using the interactive text-based interface.

How to Use Text-Based Mode

The text-based installer mode does not display graphical screens, but instead prompts you for information using a series of questions. The following table describes the responses you make to the Java Enterprise System installer prompts.

Table 5-1 Responding to Installer Prompts
Action	Input
To accept default values as indicated in square brackets ([ ])	Press Return.
To select items from a list	Type the numbers for the items in a comma-separated sequence and then press Return. Spaces are not allowed. For example, to select item 2 in a list, type 2 and then press Return. To select items 1, 3, and 4, type 1,3,4 and then press Return.
To deselect items from a list	Type the numbers for the items in a comma-separated sequence, entering the minus character (-) before each number. No spaces are allowed. Press Return when you are done. For example, to deselect item 2 from the list, type -2 and then press Return. To deselect items 1, 3, and 4, type -1,-3,-4 and then press Return.
To provide a value to a text field For example, when prompted to supply a user name or port number.	Type the value and then press Return.
To provide a password	Type the password and then press Return. The password does not appear on the terminal window.
To return to the previous page	Type the left bracket (<) character and then press Return.
To exit the session	Type the exclamation mark character (!) and then press Return.

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 5-2 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 component incompatibilities in advance and take care of them before installation. This allows your installation session to run more efficiently.

To Use the Text-Based Installer for Identifying Upgrade Needs

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

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

./installer -nodisplay -no

Proceed through the installer pages until you have specified what languages you want supported.

After you choose language support, the installer inspects your system for previously installed component products.

If the installer discovers any previously installed component products, it reports information about the components under the title Component Products Detected on This Host.

In this case, review the information in the report. If it indicates that your system has older versions of component products installed, exit the installer and upgrade the reported components. Otherwise, use the Component Selection menus to choose the components you want to install. Then, proceed to Step 5.

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

If the installer does not discover any previously installed component products, it asks whether you want to install the full set of Java Enterprise System products and services under the title Installation Type. Press Return to accept the Yes default.

The installer performs a dependency check of the component products and provides explanation on any issues. Review product dependency issues and press Return to continue.

The installer inspects your system for shared components that are incompatible with the Java Enterprise System. If it discovers any incompatible shared components, the installer displays an explanation of the shared components that will be upgraded during installation.

Review the shared component issues and decide whether you are going to allow the installer to upgrade these shared components during installation or whether you need to upgrade them manually.



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.

Exit the installer by typing the ! character and then pressing Return.

Perform any upgrades necessary for shared components.

Determine whether the newer version is compatible with other installed applications on the host. After you have verified that it is safe to upgrade shared components on the host, do either of the following:

Manually 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 Text-Based Mode

To Start the Text-Based Installer

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

Start the text-based 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 -nodisplay

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 -nodisplay

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 -nodisplay

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.

After the installer starts, it displays the Welcome information.

To Select Languages for Installation

You are asked to select additional language packages for installation. English is always installed.

To Select Components

After you select languages for installation, the installer checks your system for previously installed versions of component products.

If the installer finds no previously installed versions of component products, it prompts you to install the full set of Java Enterprise System Products and Services:

Installation Type
-----------------

Do you want to install the full set of Sun Java(TM) Enterprise System
Products and Services? (yes/no) [Yes] {"<" goes back, "!" exits}

If you select the default (Yes), the installer proceeds to the next section. Skip to To Upgrade Shared Components.

If you select No, the installer displayed the Component Selection Main Menu.

If the installer detects any previously installed component products, it displays a list of the detected component products under the title Component Products Detected on This Host. Then, the installer displays the Component Selection Main Menu.

These component products will not be available for product selection, but might require upgrading if the versions do not meet Java Enterprise System requirements or dependency requirements of other component products.

The Component Selection Main Menu lists the component products you can install:

Component Selection - Main Menu
-------------------------------
Note: "* *" indicates that the selection is disabled

[ ] 1. Sun Java(TM) System Calendar Server 6 2004Q2 (42.66 MB)
[ ] 2. Sun Java(TM) System Web Server 6 2004Q1 Update 1 Service Pack 2
(63.51 MB)
[ ] 3. Sun Java(TM) System Messaging Server 6 2004Q2 (122.87 MB)
[ ] 4. Sun Remote Services Net Connect (27.62 MB)
[ ] 5. Sun Java(TM) System Administration Server 5 2004Q2 (12.98 MB)
[ ] 6. Sun Java(TM) System Identity Server 2004Q2 (27.17 MB)
[ ] 7. Sun Cluster 3.1 4/04 (58.93 MB)
[ ] 8. Sun Java(TM) System Communications Express (16.88 MB)
[ ] 9. Sun Java(TM) System Message Queue 3.5 SP 1 (8.40 MB)
[ ] 10. Sun Java(TM) System Instant Messaging 6 2004Q2 (9.89 MB)
[ ] 11. Sun Java(TM) System Application Server 7.0 Update 3 (80.92 MB)
[ ] 12. Sun Java(TM) System Directory Proxy Server 5 2004Q2 (9.44 MB)
[ ] 13. Sun Java(TM) System Portal Server Secure Remote Access 2004Q2
(14.82 MB)
[ ] 14. Sun Java(TM) System Portal Server 2004Q2 (76.90 MB)
[ ] 15. Sun Cluster Agents for Sun Java(TM) System (7.41 MB)
[ ] 16. Sun Java(TM) System Directory Server 5 2004Q2 (45.28 MB)

Enter a comma separated list of products to install [] {"<" goes
back, "!" exits}:

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

The installer asks you to confirm or modify the products you want to install.

Confirm your product selection.

The installer asks you to select which subcomponents, if any, to install for each component product you have selected.

Continue through the installer prompts to select which subcomponents to install.

To Allow the Installer to Check Your Selections

After you finish selecting component products and their subcomponents, the installer performs a dependency check of the selected component products. If there is a problem with dependencies, the installer displays a Product Dependency Check error or warning, depending on the problem:

If a local dependency cannot be met, the installer displays an error. 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, return to the Component Selection Main Menu and 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, continue with installation if you intend to specify a remote installation during configuration. Otherwise, return to the Component Selection Main Menu and select the appropriate component to satisfy the dependency locally.

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

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

To Upgrade Shared Components

After the installer performs a dependency check of the component products you have chosen to install, it performs a compatibility check of any shared components already installed.

If an incompatible system-wide version of the J2SE Software Development Kit is detected, the installer asks whether you want to upgrade the existing J2SE SDK or to install a second J2SE SDK for use by Java Enterprise System.



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 these upgrade options, see J2SE Platform Upgrade Information. Select an option and press Return.

If incompatible versions of any other shared components are detected, the displays a report similar to the following.

Shared Component Upgrades Required
-----------------------------------

The shared components listed below are currently installed. They will be
upgraded for compatibility with the products you chose to install.

Component Package
--------------------
NSS SUNWtls
3.3.6:PATCHES:114045-02,115924-02 (installed)
3.3.10:PATCHES:114045-10,115924-08 (required)
ICU SUNWicu
1.0:PATCHES:116103-03 (installed)
1.0:PATCHES:116103-04 (required)
NSSX SUNWtlsx
3.3.6:PATCHES:114045-02,115924-02 (installed)
3.3.10:PATCHES:114045-10,115924-08 (required)
ICUX SUNWicux
1.0:PATCHES:116103-03 (installed)
1.0:PATCHES:116103-04 (required)

Enter 1 to continue and 2 to exit [1] {"<" goes back, "!" exits}:



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 listed shared components, continue with the installation.

To Specify Installation Directories and Initiate the System Check

To Select a Configuration Type

You are asked to specify a configuration type, either Configure Now (the default) or Configure Later:

To Specify Configuration Data

If you have selected component products or a configuration type that require configuration during installation, you are asked to provide the configuration information for the common server settings and the component product settings.

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

Specify common server settings.

Either accept the defaults, or use the information you have gathered in the common server settings worksheet to answer the installer questions. Refer to Common Server Settings for information on these fields.

Specify component product settings.

Either accept the defaults or use the information you have gathered in the component product worksheets to answer the installer questions.

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 5-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

To Confirm Installation Readiness

Your component product selection is displayed (shared components are not explicitly listed, but they will also be installed if they are needed).

Review this list carefully. If you need to make changes, press < until you reach the question that requires a change.

To Install the Software

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
|-1%--------------25%-----------------50%--



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.

Examine the post-installation files, located in /var/sadm/install/logs on Solaris 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 component products.

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

Exit the installer.

Adding Components

To install additional component products, you can run the installer again. The installer detects the newly installed components and uses them to satisfy the dependencies of other components. Choices that represent the installed components are disabled.

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 instructions on further configuring the component products for your environment.

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


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.