Sun Java Enterprise System 5 Installation FAQs for UNIX

Running the Installer

This section contains questions about running the Java ES installer.

Q20: How do I run the Java ES installer?

Answer: To run the Java ES installer, you must be superuser on a host. You can install Java ES interactively using the graphical or text-based interface, or silently by means of a reusable script called a state file. The Java ES product documentation contains syntax and examples for using the installation commands in Appendix B, Installation Commands, in Sun Java Enterprise System 5 Installation Guide for UNIX.

Graphical mode This interactive mode provides a wizard that leads you through the process of installing Java ES software on a graphical workstation. Instructions for using the graphical installer are contained in Chapter 3, Installing With the Graphical Interface, in Sun Java Enterprise System 5 Installation Guide for UNIX. The installer tutorial provides a walkthrough of the graphical installer. See Sun Java Enterprise System 5 Installer Tutorial for UNIX.

To run the graphical installer, type the following at the command line: ./installer
Text-based mode This interactive mode provides the same functionality as graphical mode, but you are prompted for responses on a line-by-line basis in a terminal window. Instructions for using the text-based installer are contained in Chapter 4, Installing With the Text-Based Interface, in Sun Java Enterprise System 5 Installation Guide for UNIX.

To run the text-based installer, type the following at the command line: ./installer -nodisplay
Silent mode Silent mode is a non-interactive method used for installing Java ES software on multiple hosts that share similar configurations. To create the installation script, you first perform an interactive session during which your responses to the installer are captured as a set of name-value pairs in a state file. You edit the state file for host specifics, then use the state file as input to run the installer on other hosts. This process allows you to propagate one configuration across multiple hosts in your enterprise. Instructions for using silent mode are contained in Chapter 5, Installing in Silent Mode, in Sun Java Enterprise System 5 Installation Guide for UNIX, including Appendix C, Example State File, in Sun Java Enterprise System 5 Installation Guide for UNIX.

At the end of a successful interactive installation session, you are given an option of registering your installation with Sun by using the Java ES Reporter utility. For a description of Java ES Reporter, refer to How Java ES Reporter Works in Sun Java Enterprise System 5 Installation Guide for UNIX.

Tip –

To practice using the installer, type the following command which runs the graphical installer without installing software: ./installer -no

Q21: Can the installer upgrade components that are already on my host?

Answer: Yes and no, depending on the type of component you want to upgrade.

Product components In general, product components cannot be upgraded by the installer. If the installer detects incompatible versions of product components on the host, you must remove or upgrade these components before installation can proceed.

Note –
If the installer finds upgradable versions of Application Server, HADB, Java DB, or Message Queue on the host, it marks them as upgradable in the Choose Software Components page and will upgrade them if you select them. Upgradable versions can mean earlier versions of Java ES or Solaris-bundled versions of Application Server and Message Queue.
Shared components Shared components are automatically upgraded whenever the Java ES installer installs or upgrades a product component. In addition, for certain upgrades or Solaris 10 zones scenarios, you can manually install or upgrade all shared components to Java ES 5 by selecting the All Shared Components item on the Choose Software Components page. These scenarios are described in the Sun Java Enterprise System 5 Upgrade Guide for UNIX. For a general understanding of zones in relation to Java ES, see Appendix A, Java ES and Solaris 10 Zones, in Sun Java Enterprise System 5 Installation Planning Guide.

Q22: What is the difference between the Configure Now and Configure Later configuration types?

Answer: The installer gives you the option of performing initial configuration for many of the Java ES components during installation.

Configure Now This configuration type prompts you to enter the initial configuration values during the installation session. Configure Now can be selected for only some components. If you select components for Configure Now that cannot be configured during installation, the installer indicates that it will not configure them. You will configure them after installation.
- Components that can be configured during installation include Access Manager, Application Server, Directory Server, HADB, Portal Server, Portal Server Secure Remote Access, Web Server, and Web Proxy Server.
- Components that cannot be configured during installation include Directory Proxy Server, Java DB, Monitoring Console, Service Registry, and Sun Cluster software .
Configure Later This configuration type instructs the installer to copy component software packages to the host. You might be asked to enter a few values that are necessary for copying the packages. The installer proceeds without doing further configuration, and no runnable instances are created. You create runnable instances after installation by supplying configuration values when prompted by component configuration wizards or in configuration files. You can select Configure Later for all components.

The configuration type that you selected (Configure Now or Configure Later) applies to an entire installation session.

Regardless of whether you perform the initial configuration in the installer (Configure Now) or manually after installation, there is usually some additional postinstallation configuration required. See Q28: What postinstallation configuration is required?

Q23: How can I reproduce the same installation on another host?

Answer: You can propagate one configuration across multiple hosts in your enterprise by using silent mode of the Java ES installer. For instructions, see Chapter 5, Installing in Silent Mode, in Sun Java Enterprise System 5 Installation Guide for UNIX.

Q24: Does the installer check dependencies on remote components?

Answer: In general, the installer checks dependencies and versions on the local host only. However, one situation exists where the installer interacts with a remote host: if you select the Configure Now configuration type and are using a remote component (such as Directory Server or Access Manager) to satisfy a dependency. In this case, the installer tries to connect with the remote component during the installation session. If the remote component is not available, installation stops, and you receive an error message. To avoid this situation, install, configure, and start any remote components before starting an installation session.

In a Configure Later installation, the installer runs as though the remote component is available and does no checking. Installation succeeds, and you can proceed to postinstallation configuration. However, if the remote component is not available, you receive errors when you try to run any component that depends on that remote component.

Tip –

To indicate to the installer that you will be using a remote component, select all the components that you will install locally and then deselect any dependency that will be fulfilled by a remote component. When you attempt to proceed, the installer prompts you to fulfill any requirements for the component that you deselected. At this point, you indicate to the installer that you are using a remote component to fulfill a dependency.

Q25: How do I use a third-party web container?

Answer: On Solaris OS, Access Manager and Portal Server can use the third-party web containers BEA WebLogic Server or IBM WebSphere Application Server. On Linux, both are supported for Configure Later, but only BEA WebLogic is supported for Configure Now. HP-UX does not support third-party web containers.

To indicate a third-party web container to the installer, select all of your components, then deselect Sun Java Application Server or Sun Java Web Server. When you click Next, the installer displays the Web Container Selection page telling you that a web container is needed. Select Use Third-Party Web Container.

Tip –

Tip Install, configure, and start any third-party web container in your deployment before installing Java ES. For installation, configuration, and startup instructions, refer to the BEA or IBM product documentation.

Q26: How do I get patches that the installer indicates are missing?

Answer: When the installer performs a system check, the installer might identify missing patches. In most cases, the installer cannot proceed until you install the patches. On Solaris OS, patch clusters offer all the needed Java ES patches. See Q8: What are the system requirements for installation?

In some situations, you need to cancel the installation, but in others you can leave the installer running while you apply the patch. The Sun Java Enterprise System Installation Guide contains an example procedure for installing a patch.

For a Kernel Patch Any patch which is kernel-related will not be able to be applied with the installer running. For such patches, such as patches on libc, do the following:

Exit the installer.
In a browser, go to the patch site for your operating system and find the patch you need:
- Sun OS: http://sunsolve.sun.com
- Linux: http://www.redhat.com
- HP-UX: http://www.itrc.hp.com
Download the patch to the local host.
Bring the host to single user mode.
Apply the patch.
Reboot the host.
Restart the installer.

For a Non-Kernel Patch For required patches that are not kernel-related, do the following:

Leave the installer running and open a separate terminal window.
In a browser, go to the patch site for your operating system and find the patch you need:
- Sun OS: http://sunsolve.sun.com
- Linux: http://www.redhat.com
- HP-UX: http://www.itrc.hp.com
Download the patch to the local host.
In the new terminal window, apply the patch.
Tell the installer to recheck the host and continue with installation.

Q27: How do I know if my Java ES installation succeeded?

Answer: After the installer indicates that installation is complete, you can view directories or the product registry, or perform some component exercises to verify that the software packages have been successfully copied to your host. See Verifying After Installation in Sun Java Enterprise System 5 Installation Guide for UNIX.