Chapter 6 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 6-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 should be performed before beginning Java Enterprise System installation. The left column lists the general order in which you should perform the tasks, the middle column describes the task action, and the right column contains useful information and the location of instructions.

Table 6-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/816-6876
2	Upgrade any existing component products that are incompatible with Java Enterprise System.	prodreg or pgkinfo command (for further information, refer to their man pages) "Identifying Component Upgrade Needs" Chapter 4, "Upgrading System Components"
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	The backup copy of the product registry is helpful in recovering from a failed installation.
6	Create the necessary system accounts.	For Directory Server or Administration Server to run as a non-root user, you must create the accounts before configuring. if Identity Server will be running as nobody or root, and will be running as part of a group such as nobody or system, those system accounts must already be set up.
7	If you are installing with Sun Cluster software, 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, 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 Identify 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 For additional information, see Chapter 2 of the Sun ONE Identity Server 6.1 Installation and Migration Guide, http://docs.sun.com/doc/816-6771-10.
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 is empty.	When you uninstall Web Server, the following directories are not removed during uninstallation and must be manually deleted: .../docs, .../https-admserv, .../https-instance_server
13	If you are installing Messaging Server:
	Stop sendmail before running the installer.	/etc/init.d/sendmail stop
	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 installing Calendar Server, verify that the second column in the /etc/hosts file contains the FQDN rather than a simple host name.	For example: 192.18.99.999 mycomputer.company.com loghost
15	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.

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 are asked if you want to install the full set of Java Enterprise System Products and Services.

Accept the default, Yes, by pressing Return.

The installer detects any of the component products in your distribution that are already on the system and shows the compatibility level for each component.

Review the list of products that are already installed and press Return to continue.

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.

If the installer detects shared components that are incompatible with the Java Enterprise System, it 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.

To exit the installer, type the ! character and press Return.

Type 1 and press Return to confirm that you are exiting the installer.

Perform any upgrades necessary for component products.

Follow the instructions in Chapter 4, "Upgrading System Components" for upgrading component products.

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 remove or upgrade shared components as needed.

Allow the installer to upgrade shared components during your active installation.



Note	After upgrading components, the machine must be rebooted for new versions to be recognized.

Repeat this procedure until the installer indicates that components meet Java Enterprise System dependency requirements.

Running the Installer in Text-Based Mode

To Start the Text-Based Installer

Obtain the Java Enterprise System distribution bundle by one of the following methods:

Download and unpack the software.

Insert the Java Enterprise System CD or DVD into the appropriate drive

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

Navigate to the correct directory:

If you downloaded the software, navigate to the directory where you downloaded it.

cd installer-directory

If you are using a CD, navigate to the correct directory for your installation, either to the Solaris_sparc or Solaris_x86 directory. For example:

cd /cdrom/Solaris_sparc

If you are using a DVD, navigate to the directory whose name matches your platform, either to the Solaris_sparc or Solaris_x86 directory.

Start the installer in text-based mode.

./installer -nodisplay

A full description of the installer options is contained in "Installer Command Line Options". You can also access this information by typing the following:

./installer -help

After the installer starts, it displays the Software License Agreement. Read the Software License Agreement—you must accept the agreement to continue.

Accept the Software License Agreement.

Type yes and press Return to accept the agreement.

To Select Languages for Installation

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

To Select Components

If there are any Java Enterprise System component products already installed on your machine, the installer displays a list of the detected component products. For example:

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.


Note	If the installer detects that all the products in your installation bundle are already installed, the installer closes. To reinstall, you need to uninstall components using the Java Enterprise System uninstaller and then restart the installer. Instructions for uninstalling are contained in Chapter 10, "Uninstalling Software".

You are asked if you want to install the full set of Java Enterprise System Products and Services.

If you select the default (Yes), the installer proceeds to Step below.

If you answer no, the installer displays a Product Selection Menu. For example:


Product Selection - Main Menu
-----------------------------
1. Sun ONE Web Server 6.1 (62.86 MB)
2. Sun ONE Instant Messaging Server 6.1 (19.21 MB)
3. Sun ONE Calendar Server 6.0 (37.05 MB)
4. Sun ONE Directory Proxy Server 5.2 (7.51 MB)
5. Sun ONE Application Server 7.0 Update 1 (113.57 MB)
6. Sun ONE Messaging Server 6.0 (147.05 MB)
7. Sun ONE Portal Server Secure Remote Access 6.2 (18.98 MB)
8. Sun ONE Administration Server 5.2 (12.17 MB)
9. Sun Cluster 3.1 (58.09 MB)
10. Sun ONE Identity Server 6.1 (61.39 MB
11. Sun ONE Message Queue 3.0.1 SP2 (5.24 MB)
12. Sun ONE Portal Server 6.2 (52.24 MB)
13. Sun ONE Directory Server 5.2 (44.70 MB)

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.

After each selection of subcomponents, the installer asks you to confirm or modify the subcomponents you want to install.

Confirm each selection of subcomponents.

After you confirm your final subcomponent selection, the installer displays product dependency information.

To Resolve Dependency Issues

The installer performs a dependency check of the selected component products. Depending on the results of this check, you might need to take action.

Determine which of the following findings apply to your components:

Compatible. If the components that you selected are compatible with each other and with the components detected on the machine, the installer accepts your selections and proceeds to the next question.

Incompatible. If the components that you selected are not compatible with each other and with the components detected on the machine, the installer cannot proceed. An error message describes the problem.

Exit the installer and either remove the incompatible component, or proceed to Step 2 or Step 3 for instructions on upgrading.

Remote component might work. If the selected components rely on a component that is not selected but for which a remote copy would be acceptable, you can proceed, but will receive a warning.

To upgrade a component product. If the installer detects a component that needs to be upgraded, perform the following steps:

Exit the installer.

Refer to "Upgrading System Components" for instructions on performing the necessary upgrades.

Run the installer again.

To upgrade a shared component. If the installer detects a shared component that needs to be upgraded, you can allow the installer to upgrade to the correct version (in the case of J2SE, you also have the option of installing a second J2SE SDK). For more information about upgrading shared components, see "Shared Component Upgrade Information".



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 Specify Installation Directories and Initiate the System Check

To Select a Configuration Type

You are asked to specify a configuration type, either custom (the default) or minimal:

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.

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 6-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). For example:

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.

[1] Installation Summary. Lists each component installed and the settings you specified. If you chose custom 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.

View the What to Do Next page.

The What to Do Next page provides an introduction to Java Enterprise System documentation, including links to component product documentation sets and a link to the product registry page. To access the What To Do Next page, use a browser to open the WhatsNext.html file located in your installation directory.

To Register Your Products With Sun

On the What to Do Next page, click the Register link in the Register Your Java Enterprise System Software section.

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.


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.