Chapter 2 Example Installation Sequences
This chapter provides high-level sequencing guidelines for some common Sun JavaTM Enterprise System (Java ES) installations. These are not literal procedures, but instead provide the sequential steps required to implement particular deployment scenarios.
This chapter contains the following sections:
How to Use This Chapter
The single-session examples describe typical steps for installing one or a number of Java ES product components on a single host in a single installation session. All other examples in this chapter describe situations where multiple installation sessions are performed on multiple hosts, for a variety of solutions. For the most part, the sequences in this chapter are based on the relationships among the product components as shown in Sun Java Enterprise System 5 Installation Planning Guide.
At component selection, the Java ES installer identifies incompatible versions of components as well as unmet requirements. You receive warning messages that identify the problem and tell you what you need to do. Many of these messages tell you about requirements that are not yet met. Other messages tell you that incompatible versions of some or all of the components you are trying to install are already on the local host. You can use the Java ES installer to identify components that are already on your local host. For instructions, refer to When Incompatible Components Are Installed.
Tip –
Installation goes most smoothly if any incompatible versions of Java ES components are identified and removed or upgraded before starting the installer.
The following table describes some common situations that might influence the sequence in which you should install the components, or the order in which tasks should be performed on multiple hosts or in multiple installation sessions. The left column lists the situation, and the right column explains how to handle the situation.
Table 2–1 Installation Sequence Guidelines|
Situation |
Description |
|---|---|
|
Monitoring is included. |
Monitoring Console cannot be run on the same host as the Java ES product components that it monitors. Therefore, Monitoring Console should be installed on another host. |
|
Installation-time configuration is not possible for all components. |
The following components can be installed in a Configure Now installation, but configuration cannot be done during installation: Sun Cluster components, Monitoring Console, and Service Registry. During installation, you will receive a message telling you to configure after installation. |
|
Upgrading components is required. |
You might receive messages asking you to remove or upgrade product components that are already on the host. On Solaris OS, some bundled components (Application Server, Message Queue, and HADB), can be upgraded during installation. For all other components, refer to the upgrading procedures in the Sun Java Enterprise System 5 Upgrade Guide for UNIX |
|
Solaris 10 zones are used. |
In a Solaris 10 zones environment, shared components must be installed separately in the global zone before installing into a local zone. Message Queue can only be installed in the global zone, after which it is propagated to all non-global zones. Refer to Solaris 10 Zones Examples for further guidelines. |
|
Sun Cluster software is included. (Solaris OS only) |
If Sun Cluster software is part of your deployment, you must perform a precise series of tasks before installing any Java ES product components. Java ES components that can be configured for Sun Cluster are Application Server, Directory Server, HADB, Message Queue, and Web Server. Refer to Sun Cluster Software Example to see Sun Cluster guidelines. |
|
Remote components are used. |
If you are using a remote product component to fulfill dependencies, the remote product component must be installed and running before installing any Java ES product components that depend on it. |
|
Third-party components are used. |
If you are using a third-party product as your web container, the third-party product must be installed and running before installing any Java ES product component that depends on it. Note: HP-UX does not support third-party web containers. For Configure Now, Linux only supports the BEA WebLogic third-party container. |
|
Access Manager modes |
When you are installing Access Manager with Portal Server, you can select either Realm (7.x) mode or Legacy (6.x) mode for Access Manager (ignoring the installer message that says Legacy mode is required for Portal Server). However, Portal Server supports Realm mode only if Access Manager is configured with Directory Server, with AM SDK configured for the data store. |
Single-Session Installation Examples
The following examples apply to installing on a single host in a single session:
Evaluation Example
An evaluation installation is generally considered a trial deployment, that is, a quick installation to see how things go. This example uses the graphical interface and the Configure Now type When you are presented with configuration pages, you accept defaults wherever possible.
This example installs all the Java ES product components (except Sun Cluster software and Monitoring Console) on a single host in a single installation session. Because Web Server is used as the web container, Application Server is not installed.
To Develop a Sequence for Java ES Evaluation
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Starting the Java ES graphical installer
Use either the graphical or text-based installer.
-
At component selection, choosing Select All, then deselecting the Application Server, Sun Cluster software, and Monitoring Console product components
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Verifying installation directories
-
Selecting the Configure Now type
Messages indicate which product components cannot be configured during installation.
-
Accepting configuration defaults when they are offered
If you want to use non-default information, review the appropriate configuration tables in Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Installation Reference for UNIX.
-
Viewing the Installation Summary and Log
-
Completing postinstallation configuration
Chapter 6, Completing Postinstallation Configuration contains instructions for postinstallation configuration.
-
Starting the product components
Verifying After Postinstallation Configuration contains the preferred Java ES startup sequence. Startup procedures follow the table.
Access Manager and Portal Server Example
This example installs Portal Server with Access Manager on a single host, using Web Server as the web container. Portal Server and Access Manager should use the same type of web container.
You can use Access Manager Core Services, Access Manager Administration Console, and Common Domain Services for Federation on another host by deselecting these subcomponents of Access Manager.
When you are installing Access Manager with Portal Server, you can select either Realm (7.x) mode or Legacy (6.x) mode for Access Manager (ignoring the installer message that says Legacy mode is required for Portal Server). However, Portal Server supports Realm mode only if Access Manager is configured with Directory Server, with AM SDK configured for the data store.
To Develop a Sequence for Access Manager and Portal
Server
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
-
At component selection, choosing Portal Server and Web Server
Access Manager, Directory Server, Directory Preparation Tool, Java DB, and Service Registry are automatically selected.
-
To use a remote copy of Directory Server, deselect Directory Server and specify a remote copy when prompted.
Note –The remote Directory Server must be running before installing any other product components. For instructions on installing Directory Server, refer to Directory Server Only Example.
-
To use a remote copy of Access Manager, deselect Access Manager and specify a remote copy during postinstallation configuration.
-
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Selecting the Configure Now or Configure Later type
-
For the Configure Now type configuration pages are displayed for those product components that allow installation-time configuration. Do not accept defaults for product components that are remote; use the remote information.
-
For the Configure Later type, configuration pages are not displayed.
-
-
Running the installation
-
Viewing the Installation Summary and Log
-
Completing postinstallation configuration
-
Starting product components
-
Starting and Stopping Web Server (Access Manager and Portal Server start automatically with Web Server.
-
Accessing the default Access Manager login page
For Legacy mode: http://webserver-host:port/amconsole
For Realm mode: http://webserver-host:port/amserver
The following table contains additional Access Manager information.
Task
Relevant Information
Configuration information for the installer
Postinstallation configuration
Starting and stopping
Uninstalling
Troubleshooting
Upgrading
The following table contains additional Portal Server information.
Task
Relevant Information
Configuration information for the installer
Postinstallation configuration
Portal Server and Portal Server Secure Remote Access Postinstallation Configuration
Starting and stopping
Accessing the Portal Server Desktop by Starting the Web Container
Uninstalling
Troubleshooting
Upgrading
Application Server Only Example
This example provides guidelines for installing Application Server on a single host.
Requirements
Application Server requires a local copy of HADB, Java DB, and Message Queue. If you are using load balancing, a local copy of a web server is required.
To Develop a Sequence for Application Server
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
-
At component selection, choosing Application Server
Message Queue, HADB, and Java DB are automatically selected. The Load Balancing Plugin and the Application Server Node Agent are not selected.
(Optional) If you are going to implement load balancing, expand Application Server and select the Load Balancing Plugin subcomponent. Select Web Server if you want to install Web Server in the same session. If you want to use Web Server 6.0 or Apache Web Server, Web Server 6.0 or Apache Web Server must already be installed.
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Verifying installation directories
-
Selecting the Configure Now or Configure Later type
-
For the Configure Now type, configuration pages are displayed for the local product components that can be configured during installation.
Gather your Application Server configuration information from the tables in Application Server Configuration Information in Sun Java Enterprise System 5 Installation Reference for UNIX.
-
For the Configure Later type, configuration pages are not displayed.
-
-
Running the installation
-
Viewing the Installation Summary and Log
-
Completing postinstallation configuration
-
Starting Application Server (automatically starts Message Queue)
The following table contains additional Application Server information.
Task
Relevant Information
Configuration information for the installer
Postinstallation configuration
To Configure Application Server After a Configure Later Installation
Starting and stopping
Uninstalling
Troubleshooting
Upgrading
Directory Proxy Server Only Example
This example provides guidelines for installing Directory Proxy Server on a single host.
To Develop a Sequence for Directory Proxy Server
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
-
At component selection, selecting Directory Proxy Server
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Verifying installation directories
-
Selecting the Configure Now or Configure Later option
-
Running the installation
-
Viewing the Installation Summary and Log
-
Creating an instance of Directory Proxy Server
-
Starting Directory Proxy Server
Starting and Stopping Directory Proxy Server
The following table contains additional Directory Proxy Server information.
Task
Relevant Information
Starting and stopping
Uninstalling
Upgrading
Directory Server Only Example
With Directory Server Enterprise Edition, you can install Directory Server Core, Directory Proxy Server, and the tools for administering your directory service remotely. Directory Server provides LDAP and DSML directory services, managing client access to your directory database. Directory Proxy Server offers proxy LDAP service with configurable load balancing and routing. Directory Proxy Server also enables data distribution for high scalability, and virtual directory access to both LDAP and relational databases. Remote administration tools include the web based Directory Service Control Center, and command line remote configuration tools.
In production deployments, you typically deploy each Directory Server Enterprise Edition component on a different host. Before deploying Directory Server Enterprise Edition software in production, read the Sun Java System Directory Server Enterprise Edition 6.0 Deployment Planning Guide.
This example provides guidelines for installing Directory Server on a single host.
Requirements and Sequence Issues
Directory Server has no dependencies on other Java ES product components.
-
If you are using this product component with Sun Cluster software, you must perform a precise series of tasks before installing any product components. Refer to Sun Cluster Software Example
-
Directory Server must be running before installing other product components that depend on Directory Server.
-
If your deployment calls for Schema 2, you must configure Directory Server for Schema 2 before implementing any other product components.
To Develop a Sequence for Directory Server
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Planning your schema
For guidelines, refer to LDAP Schema and LDAP Directory Tree Structure in Sun Java Enterprise System 5 Installation Planning Guide.
-
Running the Java ES installer
-
At component selection, selecting Directory Server
Directory Preparation Tool is automatically selected.
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Verifying installation directories
-
Selecting the Configure Now or Configure Later type
-
For the Configure Now type, configuration pages are displayed for the local product components that can be configured during installation.
Gather your configuration information from the tables in Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Installation Reference for UNIX.
-
For the Configure Later type, configuration pages are not displayed.
-
-
Running the installation
-
Viewing the Installation Summary and Log
-
Starting Directory Server
Starting and Stopping Directory Server
The following table contains additional Directory Server information.
Task
Relevant Information
Configuration information for the installer
Starting and stopping
Uninstalling
Troubleshooting
Upgrading
Message Queue Only Example
Note –
On Solaris 10, Message Queue can only be installed in the global zone, after which it is propagated to all non-global zones.
This example provides guidelines for installing Message Queue on a single host.
Requirements
Message Queue has no dependencies on other Java ES product components.
To Develop a Sequence for Message Queue
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
-
At component selection, selecting Message Queue
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Selecting the Configure Later type
Message Queue cannot be configured during installation
-
Running the installation
-
Viewing the Installation Summary and Log
-
Starting Message Queue
Starting and Stopping Message Queue
The following table contains additional Message Queue information.
Task
Relevant Information
Postinstallation configuration
Starting and stopping
Uninstalling
Troubleshooting
Upgrading
Monitoring Console Only Example
If your product components will use Java ES monitoring, you need to install the Monitoring Console component on another host where no other product components are installed. Monitoring Console cannot run on the same host as any of the Java ES components.
To Develop a Sequence for Monitoring Console
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
Be sure that no other Java ES component products are installed on the same host as Monitoring Console.
-
At component selection, choosing Monitoring Console
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Selecting the Configure Later type
Monitoring Console cannot be configured during installation.
-
Running the installation
-
Viewing the Installation Summary and Log
-
Completing postinstallation configuration
After installing all the components that will use monitoring, configure for monitoring using instructions in the Sun Java Enterprise System 5 Monitoring Guide. This document also contains instructions for administering and using Java ES monitoring.
The following table contains additional Monitoring Console information.
Task
Relevant Information
Postinstallation configuration
Starting and stopping
Uninstalling
Troubleshooting
Upgrading
Portal Server Secure Remote Access Example
This example describes installation of only Portal Server Secure Remote Access with Access Manager on a single host, using Web Server as the web container.
Requirements
Portal Server Secure Remote Access requires a local copy of Access Manager or Access Manager SDK. Portal Server Secure Remote Access Core requires a local copy of Portal Server except in case of Gateway, where Portal Server Secure Remote Access does not require a local copy of Portal Server and can be installed on a separate host. Portal Server Secure Remote Access must be installed in the same location as Portal Server. Directory Server is required by Portal Server, but not necessarily a local copy. Access Manager requires a local web container, which in this example is Web Server.
To Develop a Sequence for Portal Server Secure Remote Access
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
-
At component selection, choosing Portal Server Secure Remote Access, Portal Server, and Web Server
Portal Server, Access Manager and Directory Server are automatically selected, as well as Java DB and Service Registry.
-
To use a remote copy of Directory Server, deselect Directory Server and specify a remote copy when prompted.
-
To use a remote copy of Access Manager, deselect Access Manager and specify a remote copy during postinstallation configuration.
-
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Selecting the Configure Now or Configure Later type
-
For the Configure Now type, configuration pages are displayed for those product components that allow installation time configuration.
Do not accept defaults for product components that are remote; use the remote information.
You will need to gather your configuration information from the tables in Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Installation Reference for UNIX.
-
For the Configure Later type, configuration pages are not displayed.
-
-
Running the installation
-
Viewing the Installation Summary and Log
-
Completing any postinstallation configuration
For Configure Now:
-
Configuring Access Manager After a Configure Now Installation
-
Portal Server and Portal Server Secure Remote Access Postinstallation Configuration
For Configure Later:
-
-
Starting the product components
-
Starting and Stopping Web Server (Access Manager and Portal Server start automatically.)
-
Accessing the default Access Manager login page
http://webserver-host:port/amserver
-
Accessing the portal
http://webserver-host:port/portal/dt
-
Enabling Portal Server Secure Remote Access in the Portal Server Deployment page
This allows Portal Server Secure Remote Access subcomponents to be started.
-
Accessing the Portal Gateway
https://gateway-server:port/
The following table contains additional Portal Server Secure Remote Access information.
Task
Relevant Information
Configuration information for the installer
Starting and stopping
Uninstalling
Troubleshooting
Upgrading
Service Registry Only Example
This example provides guidelines for installing Service Registry on a single host.
Requirements
Service Registry requires a local copy of Application Server and at least two Application Server subcomponents: Domain Administration Server and Command Line Administration Tool. Message Queue, HADB, and Java DB are also required.
Note –
For installation on Solaris 10, Service Registry should be installed in a separate non-global zone. For more information, refer to Solaris 10 Zones Examples.
To Develop a Sequence for Service Registry
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
-
At component selection, selecting Service Registry
Application Server and its required subcomponents as well as HADB, Java DB, and Message Queue are automatically selected.
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Verifying installation directories
-
Selecting the Configure Now or Configure Later type
Service Registry cannot be configured during installation.
-
For the Configure Now type, the Application Server and HADB configuration pages are displayed by the installer.
Gather your configuration information from the tables in Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Installation Reference for UNIX
-
For the Configure Later type, configuration pages are not displayed.
-
-
Running the installation
-
Viewing the Installation Summary and Log
-
Completing postinstallation configuration, in this order
Postinstallation configuration of Application Server and HADB are necessary only if those services are to be used separately or if Configure Later was chosen for Application Server.
-
Starting Service Registry
Refer to the Service Registry 3.1 Administration Guide for instructions.
The following table contains additional information for installing Service Registry.
Task
Relevant Information
Postinstallation configuration
Uninstalling
Troubleshooting
Web Server Only Example
This example provides guidelines for installing Web Server on a single host.
Requirements
Web Server has no dependencies on other product components.
To Develop a Sequence for Web Server
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
-
At component selection, selecting Web Server
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Verifying installation directories
-
Selecting the Configure Now or Configure Later type
-
For the Configure Now type, the Web Server configuration pages are displayed by the installer.
You are asked to select the Web Server configuration type, either Admin or Agent. Admin is the default.
Gather your configuration information from the tables in Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Installation Reference for UNIX
-
For the Configure Later type, configuration pages are not displayed.
-
-
Running the installation
-
Viewing the Installation Summary and Log
-
Completing any postinstallation configuration
-
Starting Web Server
Starting and Stopping Web Server
The following table contains additional information for installing Web Server.
Task
Relevant Information
Postinstallation configuration
Starting and stopping
Uninstalling
Troubleshooting
Upgrading
Solaris 10 Zones Examples
This section contains a brief description of Solaris 10 zones support for the current release of Java ES. Installation sequence examples are included. The following topics are addressed in this section:
Overview of Solaris Zones
The Solaris 10 zones feature (also known as Solaris containers) provides a means of creating virtualized operating system environments within an instance of Solaris OS. This allows one or more processes to run in isolation from other activities on the host. For example, a process running in a zone will only be able to send signals to other processes in the same zone, regardless of user ID and other credential information.
Every Solaris 10 host contains a single global zone. The global zone is both the default zone for the host and the zone used for system-wide administrative control. All processes run in the global zone if no non-global zones are created by the global administrator. Some Java ES product components, such as Sun Cluster software, can only be installed in the global zone. A non-global zone can be thought of as a box. One or more applications can run in this box without interacting with the rest of the host. Each non-global zone has what appears to be its own instance of an installed Solaris 10 operating system with configuration and other information unique to that non-global zone. When a package is installed in the global zone, it is, by default, propagated to all non-global zones. In other words, the package is installed in the non-global zones as well as in the global zone. This propagation provides non-global visibility and availability to packages that are installed in the global zone. This propagation behavior can optionally be suppressed when the package is added, thus restricting the package to the global zone only. The default configuration for a non-global zone is to share portions of the global zone's file system. Two types of non-global zones are supported: whole root zone and sparse root zone.
A whole root zone contains a read/write copy of the file system that exists in the global zone. When a whole root zone is created, all packages that are installed in the global zone are made available to the whole root zone. A package database is created and all packages are copied onto the whole root zone, creating a dedicated and independent copy of all files.
A sparse root zone contains a read/write copy of only a portion of the file system that exists in the global zone, while other file systems are mounted read-only from the global zone as loopback virtual file systems, for example, /usr. The global administrator selects which file systems to share with a sparse root zone at the time the sparse root zone is created.
Note –
For Java ES, it is assumed that for sparse root zones the /opt file system is not inherited from the global zone and is, therefore, writable.
For your zones deployment to succeed, it is crucial that you plan the tasks and sequence of those tasks very carefully. Java ES components can potentially be installed in any type of zone in an almost unlimited set of combinations, and in almost any order. In some cases, the order in which Java ES product components are installed, and the order in which non-global zones are created, can be very important. For a full description of planning for implementing Java ES in a Solaris zones environment, refer to the Appendix A, Java ES and Solaris 10 Zones, in Sun Java Enterprise System 5 Installation Planning Guide.
Zones Support for This Release of Java ES
The following list describes the level of zones support for this release of Java ES:
-
Both whole root zones and sparse root zones are supported.
-
Java ES can be installed in the global zone when non-global zones already exist.
-
Non-global zones can be created after Java ES is installed in the global zone.
-
All shared components in a zone must be from the same release of Java ES.
-
Whole root and sparse root deployments of Java ES should not be mixed on a single computer.
-
The Java ES installer can install Java ES components in sparse root zones with the following exceptions:
-
Sun Cluster software, Sun Cluster Geographic Edition, and Sun Cluster Agents can only be installed in the global zone.
-
Message Queue can only be installed or upgraded in the global zone, or in a whole root zone.
-
Shared components can only be installed or upgraded in the global zone, or in a whole root zone.
-
Before Application Server can be installed into the sparse root zone, any version of Application Server that is bundled with the operating system must be manually removed from the global zone.
-
-
The Java ES installer controls propagation of the packages it installs in the global zone:
-
Shared components are always propagated.
-
Message Queue and Java DB are always propagated.
-
All other product components are never propagated.
-
-
If you have a previous version of Java ES installed in a whole root zone, you should not install Java ES in the global zone.
Special Situation: Installing Shared Components in a Whole Root Zone
Installation of shared components in a whole root zone can be blocked if specific versions of Sun Java Web Console are already installed in the zone. This, in turn, can block installation of product components in the whole root zone.
Note –
This situation is addressed in Bug 6451030 in the Sun Java Enterprise System 5 Release Notes for UNIX.
Some earlier versions of the Sun Java Web Console packages contain an incorrect attribute setting that prevents Sun Java Web Console from being upgraded in whole root zones. The Sun Java Web Console packages that contain the incorrect attribute setting were shipped with Solaris 10, Solaris 10 Update 1 (1/06), Solaris 10 Update 2 (6/06), and Java ES 4 (2005Q4). The packages are correct in Solaris 10 Update 3 (11/06) and Java ES 5. To determine if your host contains the defective packages, run the following command in the global zone:
pkgparam -v SUNWmcon SUNW_PKG_ALLZONES
If you receive the following response, your host contains the defective packages:
SUNW_PKG_ALLZONES='true'
If you want to install Java ES 5 in a whole root zone, you will first need to upgrade the Sun Java Web Console packages in the global zone. You have the following options:
-
Option 1: Run the Java ES installer in the global zone and install only All Shared Components. This will upgrade the Sun Java Web Console packages and fix the zones attribute. This will also install all the other Java ES 5 shared components into the global zone and propagate them into all non-global zones. This might not be acceptable for your situation and is not recommended if you have a previous version of Java ES installed in a whole root zone.
-
Option 2: Upgrade only the Sun Java Web Console packages in the global zone. To do this, log into the global zone and navigate to the Java ES 5 installation directory for Solaris. As root, do the following:cd Product/sunwebconsole ./setup The setup script will upgrade Sun Java Web Console to version 3.0.2, which contains the repaired zones attributes.
Note –The Product/sunwebconsole directory is only found in the full Java ES 5 installer, and is not available in Java ES suite installers. If you are using a suite installer, you must download and unzip the full Java ES 5 installer to access this directory.
After you apply one of these options, you can install Java ES 5 components in a whole root zone.
Solaris 10 Whole Root Zones Example
This example provides guidelines for installing Java ES software in a Solaris 10 whole root zone.
To Develop a Sequence for Solaris 10 Whole Root Zones
The following high-level tasks are required:
-
Verifying that Solaris 10 is installed on your host
The global zone is automatically created.
-
Verifying that all your whole root zones are in the running state
A zone is in the running state when it has been configured, installed, and booted. For information on whole root zones, refer to Chapter 18, Planning and Configuring Non-Global Zones (Tasks), in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Starting the Java ES installer in the desired whole root zone
-
At component selection, choosing the components you want
If a component cannot be installed in a whole root zone, then it will be unavailable for component selection.
-
Viewing the Installation Summary and Log
-
Completing postinstallation configuration as needed
Chapter 6, Completing Postinstallation Configuration provides postinstallation configuration instructions.
-
Starting product components
Chapter 7, Verifying Installed Product Components provides procedures for starting and stopping the Java ES product components.
-
Repeating this process in additional whole root zones as needed
Solaris 10 Sparse Root Zones Example
This example provides guidelines for installing Java ES software in a Solaris 10 sparse root zone.
To Develop a Sequence for Solaris 10 Sparse Root Zones
-
Verifying that Solaris 10 is installed on your host
The global zone is automatically created.
-
Verifying that all your sparse root zones are in the running state
A zone is in the running state when it has been configured, installed, and booted. For information on sparse root zones, refer to Chapter 18, Planning and Configuring Non-Global Zones (Tasks), in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Starting the Java ES installer in the global zone, and selecting only shared components
Select only All Shared Components at component selection; no other components should be selected. When shared component installation is complete, the shared component are in the global zone and are also propagated to all non-global zones.
Note –For shared components that use multilingual packages, the Java ES multilingual packages must be present in the global zone.
-
If Message Queue or Application Server are being used, upgrading Message Queue in the global zone
Message Queue is often installed during Solaris 10 installation and does not support installation into a sparse root zone. Therefore, Message Queue must be installed in the global zone, after which it is propagated to all non-global zones.
-
If Application Server is being used, removing the bundled Application Server from the global zone
If Application Server is being used in the deployment, the Application Server that is bundled in Solaris 10 must be removed from the global zone. In the global zone on the host, list the Application Server packages as follows:
pkginfo -i | grep -i "application server"
If Application Server packages are present, remove them from the global zone. Because these packages are automatically removed from all the non-global zones, you will need go to each sparse root zone and reinstall Application Server.
-
Starting the Java ES installer in the desired sparse root zone
-
At component selection, choosing the components you want
If a component cannot be installed in a sparse root zone, then it will be unavailable for component selection.
-
Viewing the Installation Summary and Log
-
Completing postinstallation configuration as needed
Chapter 6, Completing Postinstallation Configuration provides postinstallation configuration instructions.
-
Starting product components
Chapter 7, Verifying Installed Product Components provides procedures for starting and stopping the Java ES product components.
-
Repeating this process in additional sparse root zones as needed
Sun Cluster Software Example
Product components that can be configured to run in a cluster instead of on a single server include Application Server, Directory Server, HADB, Message Queue, and Web Server. Communications Suite components that can be configured to run in a cluster include Calendar Server, Instant Messaging, and Messaging Server.
Note –
HP-UX and Linux do not support Sun Cluster components.
This example provides guidelines for installing Messaging Server in a Sun Cluster framework.
Before you install or configure Sun Cluster software, ensure that the combination of hardware and software that you choose for your cluster is currently a supported Sun Cluster configuration. For guidelines on implementing Sun Cluster software within a Java ES environment, refer to Chapter 2, Installing and Configuring Sun Cluster Software, in Sun Cluster Software Installation Guide for Solaris OS and Sun Cluster 3.1 8/05 With Sun Java Enterprise System 5 Special Instructions.
Requirements and Sequencing Issues
Messaging Server requires Directory Server, but not necessarily a local copy. You will need the Sun Cluster Core component as well as the Sun Cluster Agents for Directory Server and Messaging Server. If a remote Directory Server is used, then the Sun Cluster Agent for Directory Server is not required.
Installing, configuring, and starting the product components in the correct order is crucial for a successful Sun Cluster implementation.
-
Installing the Java ES Sun Cluster product component
-
Configuring the Sun Cluster framework
-
Installing and configuring Messaging Server using instructions in the Sun Java Communications Suite 5 Installation Guide
-
Installing additional Java ES product components that are required
-
Configuring the Sun Cluster data services using the agents for the relevant Java ES product components
At least three installation sessions are performed on each node in the cluster, one using the Communications Services installer and two using the Java ES installer. For instructions on using the Communications Services installer, refer to Sun Java Communications Suite 5 Installation Guide.
Phase I. Installing and Configuring the Sun Cluster Framework
The following tasks must be performed on all nodes in the cluster.
To Develop a Sequence for the Sun Cluster Framework
-
Verifying that the hardware is connected correctly for the cluster
-
Sun Cluster 3.0–3.1 Hardware Collection for Solaris OS (SPARC Platform Edition) http://docs.sun.com/coll/1024.1
-
Sun Cluster 3.0–3.1 Hardware Collection for Solaris OS (x86 Platform Edition) http://docs.sun.com/coll/1142.1
-
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
On Solaris 10, Sun Cluster software can only be installed in the global zone.
-
At component selection, choosing only the Sun Cluster product component
Tip –During a Configure Now installation, you are prompted whether to enable support for remote Sun Cluster configuration. If you select Yes, postinstallation configuration for Sun Cluster software will be easier.
-
Selecting the Configure Later type
-
If needed, manually installing the Sun Cluster support for additional features: RSMAPI (SUNWscrif), SCI-PCI adapters (SUNWsci), RSMRDT drivers (SUNWscrdt)
Refer to the Sun Cluster Software Installation Guide for Solaris OS for further information.
-
Following the instructions to configure the Sun Cluster Framework for each host in the cluster
Follow instructions in Chapter 2, Installing and Configuring Sun Cluster Software, in Sun Cluster Software Installation Guide for Solaris OS. When the Sun Cluster documentation refers to a Sun Cluster CD-ROM, substitute the name of the equivalent Java ES CD-ROM.
For documentation on creating resource groups and configuring data services, refer to the Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Phase II. Installing and Configuring Product Components and Agents
The following tasks must be performed on all nodes in the cluster.
To Develop a Sequence for Configuring Product Components
and Agents
-
Installing and configuring non-Java ES products
For instructions on installing and configuring Messaging Server, refer to Sun Java Communications Suite 5 Installation Guide, including the appropriate Sun Cluster Agents.
-
Running the Java ES installer
-
In the Java ES installer, selecting needed Java ES components that were not installed with Messaging Server
-
Resolving incompatibilities
The installer verifies software on your node and provides guidance if incompatibilities are identified.
-
Verifying installation directories
-
Selecting the Configure Now or Configure Later type
Sun Cluster Agents cannot be configured during installation.
-
Configuring all the selected product components except Sun Cluster Agents
-
Starting all the product components except Sun Cluster Agents, in this order:
-
Starting Messaging Server
For instructions on starting Messaging Server, refer to Starting and Stopping Messaging Server in Sun Java Communications Suite 5 Installation Guide.
-
Configuring the data services for the product components you have installed and configured
Sun Cluster Data Services Configuration
The following table contains additional Sun Cluster information.
Task
Relevant Information
Postinstallation configuration information
Starting and stopping
Uninstalling
Sun Cluster Software and Sun Cluster Geographic Edition Uninstallation Behavior
Troubleshooting
Upgrading
Access Manager SDK With Container Configuration Example
This example provides guidelines for installing Access Manager SDK, using a copy of Access Manager that is already installed on a remote host.
Note –
To use this sequence example, also refer to known issue 6293225 in the Sun Java Enterprise System 5 Release Notes for UNIX.
Requirements
Before you install Access Manager SDK, the Access Manager Services Core must be installed and running on a remote host. The web container information and Directory Server configuration information that you provide in this installation example must match the web container and Directory Server configuration information that you provided during installation of Access Manager Services Core.
Note –
When the installer asks for information about the remote web container and Directory Server, default values are displayed based on the local host. Do not accept the default values; use them only as examples of format. Instead, you must supply the correct information for the remote host.
The Java ES installer does not allow you to configure the web container when you are installing only the Access Manager SDK.
To Develop a Sequence for Host A
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Installing and starting Access Manager core services
To Develop a Sequence for Host B
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer to install a web container
The web container must be configured and started.
-
Running the Java ES installer to install Access Manager SDK
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Selecting the Configure Later type
-
Running the installation
-
Viewing the Installation Summary and Log
-
Verifying that your web container is installed and running
-
Editing the amsamplesilent file in the AccessManager-base directory
Solaris OS: /opt/SUNWam/bin
Linux and HP-UX: /opt/sun/identity/bin
-
Copy the amsamplesilent file to am.sdk_install.
-
Edit the am.sdk_install file by modifying the following parameters:
-
SERVER_NAME
-
SERVER_HOST
-
SERVER_PORT
-
ADMIN_PORT
-
DS_HOST
-
DS_DIRMGRPASSWD
-
ROOT_SUFFIX
-
ADMINPASSWD
-
AMLDAPUSERPASSWD
-
COOKIE_DOMAIN
-
AM_ENC_PWD
-
NEW_OWNER
-
NEW_GROUP
-
PAM_SERVICE_NAME
-
WEB_CONTAINER
-
-
Modify only the following parameters in the am.sdk_install file:
-
DEPLOY_LEVEL should be set to 4.
-
SERVER_HOST and SERVER_PORT should be set to the host and port of the full server which will be used by Access Manager SDK.
-
DS_HOST, DS_DIRMGRPASSWD, and ROOT_SUFFIX should be set to the hostname, directory manager password, and root suffix of the Host A Directory Server.
-
ADMINPASSWD and AMLDAPUSERPASSWD should be set to the amadmin and amldapuser passwords used on Host A.
-
AM_ENC_PWD should be set to the password encryption key used on Host A. For the Access Manager SDK, use the same encryption key for AM_ENC_PWD as the encryption key specified during the remote installation of Access Manager on Host B. Use the following command to obtain this value on Solaris OS: grep pwd /etc/opt/SUNWam/config/AMConfig.properties. On Linux and HP-UX, use grep pwd /etc/opt/sun/identity/config/AMConfig.properties
-
WEB_CONTAINER should be set to the corresponding value for the web container being used.
-
BASEDIR should be set to the install directory used during the Configure Later installation of Access Manager SDK.
-
AM_REALM should be set to Enabled if realm mode is used on Host A, and Disabled if legacy mode is used on Host A.
-
Find the settings corresponding to the web container that will be used for the SDK and modify these settings with the details of the web container. For example, if WEB_CONTAINER is set to WS (Sun Java System Web Server), then you should modify the settings which are prefixed by WS_ (WS_INSTANCE , WS_HOME, WS_PROTOCOL and so on.)
-
-
-
As root, deploying Access Manager using the edited am.sdk_install file:
-
Restarting your web container
Identity Management Example
In this example, identity management is implemented by installing Access Manager and Directory Server, with Directory Server on a remote host.
Requirements
Access Manager requires Directory Server, but not necessarily a local copy. Access Manager requires a web container, which in this example is Web Server. The remote Directory Server must be running before installing any other product components.
To Develop a Sequence for Host A
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Installing and starting Directory Server
To Develop a Sequence for Host B
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
-
At component selection, choosing Access Manager and Web Server
Directory Server and the Directory Preparation Tool are automatically selected.
-
Deselect Directory Server and specify a remote copy when prompted.
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Selecting the Configure Now or Configure Later type
-
For the Configure Now type, configuration pages are displayed for those product components that allow installation-time configuration.
Do not accept defaults for product components that are remote; use the remote information. You will need to gather your configuration information from the tables in Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Installation Reference for UNIX.
-
For the Configure Later type, configuration pages are not displayed.
-
-
Running the installation
-
Viewing the Installation Summary and Log
-
Completing any postinstallation configuration
For Configure Now:
Configuring Access Manager After a Configure Now Installation
For Configure Later:
-
Starting the product components
Starting and Stopping Web Server (Access Manager starts automatically.)
-
Accessing the default Access Manager login page for Realm Mode
http://webserver-host:port/amserver
-
Establishing an initial user and setting up single sign-on
Portal Server Using a Remote Access Manager Example
This example provides guidelines for installing Portal Server and its required product components on one host, using a copy of Access Manager that is already installed with Directory Server on another host. Access Manager and Portal Server must use the same type of web container on a host.
Requirements
Portal Server requires Access Manager. Access Manager requires a local or remote copy of Directory Server and a local web container. You can run Portal Server on a separate host from Access Manager, in which case Portal Server requires a local copy of the Access Manager SDK and a local web container. When you install Portal Server and the Access Manager SDK, you need to deselect the unneeded subcomponents of Access Manager. (The installer automatically selects all Access Manager subcomponents when you select Portal Server.)
To Develop a Sequence for Host A
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Verifying that Access Manager and Directory Server are installed and running
To Develop a Sequence for Host B
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Running the Java ES installer
-
At component selection, selecting Portal Server
Access Manager SDK, Access Manager Core Services, Administration Console, and Federation Management are automatically selected as well as Directory Server Core Server, the Directory Preparation Tool, Java DB, and Service Registry. The web container is not selected. The Web Container Selection page prompts you to select a web container.
-
Deselecting Directory Server and all subcomponents of Access Manager except Access Manager SDK
Dependency messages guide you to do the following:
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Selecting the Configure Now type
The configuration pages are displayed.
-
In the Access Manager: Specify Configuration Information page, supplying the following values for the remote Access Manager:
Note –Passwords must be different for amAdmin and amladpuser.
-
Administrator (amAdmin) Password (retyped)
-
LDAP user (amldapuser) Password (retyped)
-
Password Encryption Key (must match the encryption key entered for Host A)
-
-
In the Access Manager: Directory Server Information page, specifying the information for the Directory Server on Host A.
-
Directory Server Information
-
Directory Manager Password
-
Suffix
-
-
In the Access Manager: Web container for running Sun Java System Access Manager Services, specifying the information about the remote Access Manager on Host A
Host name should be the fully qualified name on Host A.
-
In the Portal Server: webcontainer page, specifying the web container (and any configuration parameters) that Portal Server is running within
-
Running the installation
-
Viewing the Installation Summary and Log
-
Completing any required postinstallation configuration:
Portal Server and Portal Server Secure Remote Access Postinstallation Configuration
Web and Application Services Example
HADB (used for high availability session storage) works with Application Server to provide failover capabilities that include session persistence.
This example provides guidelines for implementing a two-node HADB cluster with load balancing. However, a preferred solution is to install HADB on four hosts with nothing else installed on them. The domain administration server (DAS) with a copy of HADB for administration and a load balancer and Web Server would be installed on a separate machine.
On a partitioned operating system, a preferred solution is that two servers be installed (either host or zone) with at least one HADB instance running on each.
Requirements and Sequence Issues
Application Server requires a local copy of HADB, Java DB, and Message Queue. Application Server and HADB must be on the same host so you can use the integrated management tools provided by Application Server. The Load Balancing Plugin subcomponent of Application Server requires a web server.
The general tasks include:
-
Installing the Java ES product components
-
Starting the servers
-
Configuring HADB
-
Configuring load balancing
You can use the following guidelines to install all product components on a node or zone. On subsequent nodes, install the product components required by your deployment. A minimum of two installation sessions are required.
To Develop a Sequence for Web and Application Services
The following high-level tasks are required:
-
Checking the installation sequence guidelines
Check to see what sequence guidelines apply. Refer to Table 2–1.
-
Checking the installation prerequisites
Check to see what installation prerequisites apply. Refer to Table 1–3.
-
Verifying that the hardware is connected correctly for your cluster
-
Running the Java ES installer
-
At component selection, choosing Application Server
Message Queue, HADB, Java DB, and all the subcomponents of Application Server except the Application Server Node Agent and Load Balancing Plugin are automatically selected.
-
Expanding the Application Server product component and selecting Load Balancing Plugin.
Note –You must install Web Server and Load Balancing Plug-in using the same file system access permissions.
-
Resolving incompatibilities
The installer verifies software on your host and provides guidance if incompatibilities are identified.
-
Selecting the Configure Now type
Message Queue requires no configuration.
The configuration pages are displayed for product components that can be configured during installation. Gather your configuration information from the table in HADB Configuration Information in Sun Java Enterprise System 5 Installation Reference for UNIX.
-
Running the installation
-
Viewing the Installation Summary and Log
-
Starting the product components:
-
Starting and Stopping Application Server (Message Queue automatically starts.)
-
-
Completing HADB postinstallation configuration
Refer to Configuring HADB After a Configure Later Installation.
-
Completing load balancing configuration
Non-Root Examples
Although the Java ES installer is designed to run as root, you might want to install some components as non-root. This is not a trivial process, but some deployments require it. To install either Access Manager or Portal Server as a non-root user on either Solaris OS or Linux, refer to the following instructions:
-
Access Manager. To install Access Manager as a non-root user, follow the instructions contained in Chapter 9, Configuring Access Manager to Run as a Non-root User, in Sun Java System Access Manager 7.1 Postinstallation Guide.
-
Portal Server. To install Portal Server as a non-root user, follow the instructions contained in Sun Java System Portal Server 7.1 Configuration Guide.
Note –
HP-UX does not support non-root.
For additional non-root information in this document, see Configuring Product Components With Non-root Identifiers
- © 2010, Oracle Corporation and/or its affiliates