To Select Components and Languages (Sun Java Enterprise System 5 Installation Guide for UNIX)

Sun Java Enterprise System 5 Installation Guide for UNIX

To Select Components and Languages

The installer checks your host for previously installed versions of Java ES product components. Some product components can be upgraded by the installer (Application Server, Message Queue, Java DB, and HADB). For example:

The following components can be upgraded by the Java ES installer. 
Others will appear disabled, "* *", in the Choose Software Components Main Menu.

High Availability Session Store 4.4 - Upgradable, Compatible
Message Queue 3.7 UR1 - Upgradable, Incompatible

   <Press ENTER to continue>

If any other incompatible components are identified, you will need to remove or upgrade them manually. Instructions for upgrading outside the Java ES installer are contained in Sun Java Enterprise System 5 Upgrade Guide for UNIX. When incompatibility issues are resolved, installation can proceed.

Note –

HP-UX does not support Sun Cluster components, Directory Preparation Tool, HADB, or third-party web containers. Linux does not support Sun Cluster components, and only supports the BEA WebLogic third-party container for Configure Now installation.

Choose Software Components - Main Menu
---------------------------------------
Note: "*  *" indicates that the selection is disabled

[ ] 1.  Directory Preparation Tool 6.4
[ ] 2.  Web Server 7.0
[ ] 3.  Sun Cluster Geographic Edition 3.1 2006Q4
[ ] 4.  Web Proxy Server 4.0.4
[ ] 5.  Directory Server Enterprise Edition 6.0
[ ] 6.  High Availability Session Store 4.4
[ ] 7.  Access Manager 7.1
[ ] 8.  Sun Cluster 3.1 8/05
[ ] 9.  Message Queue 3.7 UR1
[ ] 10. Application Server Enterprise Edition 8.2
[ ] 11. Service Registry 3.1
[ ] 12. Portal Server Secure Remote Access 7.1
[ ] 13. Monitoring Console 1.0
[ ] 14. Portal Server 7.1
[ ] 15. Java DB 10.1
[ ] 16. Sun Cluster Agents 3.1
[ ] 17. All Shared Components
   Enter a comma separated list of products to install, or press R to refresh
   the list [] {"<" goes back, "!" exits}:

Type a comma-separated list of the numbers associated with the components you want to install, and press Return.

The installer presents a list called Choose Software Components — Confirm Choices which shows the components you selected.

If the chosen components are correct, press Return.

The installer queries you about installing subcomponents for those components you chose. For example:

Component Selection -  "Directory Server Enterprise Edition 6.0"
---------------------------------------------------------------------------------------
*[X] 1. Directory Server Core Server
*[X] 2. Directory Service Control Center
*[X] 3. Directory Server Enterprise Edition 6 Command-Line Utilities
*[X] 4. Directory Proxy Server 6 Core Server

Enter a comma-separated list of componets to install 
(or D to install all) [D] {"<" goes back, "!" exits}

Not all product components have subcomponents. In this case, the single product component is displayed, but no response is required from you. In cases where subcomponents are displayed, you must respond to the query.

Complete your subcomponent selections.

After you have confirmed all your subcomponent selections, the installer queries you about installing multilingual packages.

To install multilingual packages for all selected components, select (1) Yes and press Return.

By default, multilingual packages for the components you selected are installed. If you select (2) No, only English packages are installed. In this case, you will be queried to confirm this choice and warned that you will not be able to install localization packages later.

Resolve product component dependency errors.

If there is a problem with component dependencies, the installer displays a Product Dependency Check error or warning, depending on the problem. Typical problems might include:
- A local dependency has not been met
  
  In this situation, return to Choose Software Components and select the appropriate product component to satisfy the local dependency.
- A remote dependency will be met later during postinstallation configuration
  
  If you do not intend to specify a remote installation, return to Choose Software Components and select the appropriate product component to satisfy the dependency locally.
- Previous versions of product components are already installed on the local host
  
  If incompatible versions of product components are detected, you will need to exit the installer and upgrade or remove the incompatible versions.

Resolve shared component dependency errors.

If any incompatible versions of shared components are found on the host, you are asked if you want to upgrade them. Review the Shared Components Upgrade Required list and determine if it is safe for the installer to automatically upgrade these shared components.

Caution –
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 Java ES versions of the shared components. For information about upgrading, see the Sun Java Enterprise System 5 Upgrade Guide for UNIX.
- Type 1 (the default) or press Return to have the installer upgrade the shared components.
- Type 2 to cancel the installation session so that you can upgrade the shared components manually.
If you type 2, you must remove or upgrade the shared components on the Shared Components Upgrade Required list before you can continue with installation.

On Solaris OS, indicate if the installer should upgrade the J2SE SDK.

On Solaris OS, if an incompatible system-wide version of the J2SE SDK is detected, the J2SE Software Development Kit Upgrade Required page is displayed. You are presented with choices about what to do: (1) automatically upgrade the SDK version, or (2) manually upgrade the SDK version. Read the page and decide whether to upgrade automatically or manually. The default value is Automatically.

If a higher version of the JDK is encountered, with one or more JDK packages missing (for example, the 64–bit JVM), the installer treats this version as incompatible. In the case, choosing either option (1) or (2) results in the JDK being downgraded to the version of the JDK required by Java ES.