How the Java ES Installer Works

Sun Java Enterprise System (Java ES) integrates a number of Sun server-side products into a system that provides the server software needed to support distributed enterprise applications. In this document, these products are referred to as the Java ES product components. A single installer is provided for installing the Java ES product components and shared components in various combinations. Because of the complex interrelationships of these components, installation requires much more preinstallation and postinstallation effort than is required to install a single Java ES component.

Portal Server on Windows can only be used as an evaluation platform or a developer platform. It can not be used as a deployment platform. Do not use Java ES installer for Windows to install Portal Server 7.1. Use the Zipinstaller to install Portal Server. The ReadMe file provided with the installer has information on how to install Portal Server. Acess the Installer from http://www.sun.com/download/products.xml?id=465e130d

The Zipinstaller provides you a pre-configured image of Sun Java System Portal Server 7.1 Update 1. You can get a working copy of Portal Server simply by unzipping the contents of this file.

Java ES Components Used in This Release

ThisJava ES software release includes the following selectable Java ES components. The abbreviated names used in this guide follow the name and version.

• Access Manager 7.1

• Application Server 8.2 Enterprise Edition (Application Server)  

• Directory Proxy Server 6.0

• Directory Server Enterprise Edition 6.0 (Directory Server)

• High Availability Session Store 4.4 (HADB)

• Message Queue 3.7 UR1

• Monitoring Console 1.0

• JavaDB 10.2

• Portal Server 7.1

• Portal Server Secure Remote Access 7.1

• Service Registry 3.1

• Web Proxy Server 4.0.4

• Web Server 7.0

To see the full list of services and subcomponents as displayed in the Java ES installer, refer to Appendix A, Java ES Components for This Release. This appendix also lists the shared components that are provided with this release.

Installer Modes

The Java ES Windows installer uses the Microsoft Windows Installer (MSI) framework to install Java ES system on your host. You can install the Java ES software interactively or by means of a reusable script.

• Graphical Mode (Interactive). Provides an interactive graphical wizard that leads you through the tasks of installing the Java ES software on a graphical workstation.

• Silent Mode. Provides the option to run the installer on multiple hosts, each time using a generated response file to specify an input to the installer. For silent mode installation, first run the installer through a wizard while you save your responses as a set of name-value pairs in a response file. For detailed information about the silent mode installation, refer to Chapter 4, Installing in Silent Mode.

Language Selection

The Java ES installer enables you to install multilingual packages for Java ES. The following languages are available:

• English

• French

• German

• Japanese

• Korean

• Spanish

• Simplified Chinese

• Traditional Chinese

By default, the installer automatically installs Java ES in English language.

Setup Types

The Java ES installer enables you to select one of the following setup types:

• Default. Selecting the Default setup type installs and configures all the Java ES components.

• Custom. Selecting the Custom setup type allows you to select the Java ES components you want to install.

Configuration Types and Parameter Settings

Many Java ES components require some degree of installation-time configurationdepening on which Java ES components you select and which installation type you choose.

The following configuration types are available in the installer:

• Configure Automatically During Installation: Use this option to evaluate the components on a single host. During installation, you configure components that permit installation-time configuration.

  In this mode, the default values for the administrator user ID and Password are displayed but these default settings can be modified during postinstallation. All other configuration parameters such as port numbers are predetermined defaults presented at the end of installation. These default values are used for configuring the components.

  ---

  Note –

  The administrator user ID and password should not contain any special characters, and the password should be eight or more characters long.

  ---

• Configure Manually After Installation: With this option during installation, you can provide only the minimum values that are necessary for placing the software components in their directories. Configuration is performed after installation.

  When you select this option, the administrator settings dialog box is not displayed. Only the files are copied during installation. You mustmanually edit the properties file with the correct values. For more information about how to edit the properties file, refer to Chapter 5, Completing Postinstallation Configuration.

  If a component is dependent on other components, ensure that you configure the dependent components first.

Depending on which configuration option you select, you might be required to provide the administrator ID and password during installation. For example, most of the components require you to specify an administrator user ID and password. By setting these common values, you are setting default values for all component administrator user IDs and passwords.

During Multi-Session installation of Java ES Components, the configuration mode, Configure Automatically during Install or Configure Manually After Installation, selected in first session install is taken as default in next successive sessions without prompting for configuration selection mode screen.

Dependency Check

Many Java ES components depend on the presence of other components to provide their core functions. The installer does extensive cross checking of Java ES components to verify that the components you select during installation will function properly together. For this reason, the installer might prompt you to include certain Java ES components as you make your component selections.

The Java ES installer uses the following rules for handling dependencies among the Java ES components:

• Selecting a Java ES Component. When you select a Java ES component for installation, in most cases the installer automatically selects all its subcomponents.

  The installer also selects the components and subcomponents upon which the selected component depends. For example, if you select Application Server, the installer automatically selects Message Queue.

• Deselecting a Java ES Component. If you deselect a Java ES component, in most cases the installer automatically deselects all its subcomponents.

  If you deselect a component that is required locally or remotely for another selected component, the installer displays various warnings when you attempt to proceed.

• Selecting a Subcomponent. If you select a subcomponent, the installer automatically selects the Java ES component to which the subcomponent belongs, but not the other subcomponents.

  If the selected subcomponent depends on other components or subcomponents, the others are automatically selected.

• Deselecting a Subcomponent. If you deselect a subcomponent, the installer deselects only that subcomponent and not the other subcomponents.

  If you deselect a subcomponent that is required locally or remotely for another selected component, the installer displays various warnings when you attempt to proceed.

Upgrading

A Java ES component is upgraded by performing a fresh installation of the component by using the Java ES installer. Perform a fresh installation by first removing the previous version's packages and installing Release 5 in the same path. Alternatively, you can install Release 5 in a parallel path, leaving the previous version intact.

In either case must reconfigure the component by migrating the previous version's configuration data to the new installation, performing a new configuration, or doing a combination of both. For some Java ES components an utility is provided for reconfiguring or migrating configuration data for the component.

Java ES 5 Windows installer does not support in-place upgrade of previous versions of the components. Instead, the installer supports coexistence with Java ES 4. After installing Java ES 5, you need to follow the upgrade procedure described in the Sun Java Enterprise System 5 Upgrade Guide for Microsoft Windows to upgrade Java ES components. Upgrade scenarios for individual components are described in the respective upgrade guides.

When Java ES 5 installation is attempted, the installer first detects the presence of Java ES 4 on the system. On successful detection, the installer checks for pre-existing Java ES 4 shared components in the Windows SYSTEM directory, because these components cause incompatibility issues with Java ES 5. If any of the shared components are being used by Java ES 4 services, you are prompted to stop the running Java ES 4 services.

In addition, the installer automatically renames the Java ES 4 shared components. The renaming information is stored in the installer log file. If you need to start any of the Java ES 4 services, you should restore the names of shared components manually.

Java ES 4 and Java ES 5 servers cannot be started simultaneously.

Installation Logs

During the course of installation or uninstallation, log records are generated for the operations that occur. These records are saved into a single file located at %Temp%\SUNJavaES.log.

Uninstalling

The configuration for all the products are removed before they are uninstalled. The scripts used to remove the configuration are a part of the uninstallation program. You can uninstall the Java ES system by choosing Start>Settings>Control Panel>Add/Remove Programsor by running the uninstall program in Silent mode.