The following examples apply to installation on a single host in a single session:
An evaluation installation is generally considered a quick trial deployment. This example uses the graphical interface, custom installation, and the Configure Automatically During Installation type When you are presented with configuration pages, you accept defaults wherever possible.
This example installs all the Java ES components. Because Web Server is used as the web container, Application Server is not installed.
Check the installation sequence guidelines.
Check which guidelines apply to this example and make adjustments as needed. Refer to Table 2–1.
Check the installation prerequisites.
Check which tasks you might need to perform for this installation before starting. Refer to Table 1–1.
Start the Java ES graphical installer.
Choose the type of installation, select Custom.
The Java ES installer provides two types of installation:
Select and configures all products automatically with Web Server as the web container
Enables selection of Java ES components
Select the Configure Automatically During Installation type.
Messages indicate which Java ES components cannot be configured during installation.
At component selection, select Install All.
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Verify installation directories.
Accept configuration defaults when they are offered.
View the Installation Summary and Log.
Complete postinstallation configuration.
Chapter 5, Completing Postinstallation Configuration contains instructions for postinstallation configuration.
Start the Java ES components.
This example installs Application Server by itself.
Application Server requires a local copy of Message Queue. If you are using load balancing, a local copy of a web server is required.
Check the installation sequence guidelines.
Check which guidelines apply to this example and make adjustments as needed. Refer to Table 2–1.
Check the installation prerequisites.
Check which tasks you might need to perform for this installation before starting. Refer to Table 1–1.
Run the Java ES installer.
Choose the type of installation, select Custom.
Select the Configure Automatically During Installation or Configure Manually After Installation type.
For the Configure Automatically During Installation type, configuration pages are displayed for the local Java ES components that can be configured during installation.
For the Configure Manually After Installation type, configuration pages are not displayed.
At component selection, choose Application Server.
Resolve incompatibilities.
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Verify installation directories.
Run the installation.
View the Installation Summary and Log.
Complete postinstallation configuration.
Start Application Server which automatically starts Message Queue.
This example installs Directory Proxy Server with Directory Server on a single host.
Do not install Directory Proxy Server on the same system where Directory Server is installed, except for evaluation.
Check the installation sequence guidelines.
Check which guidelines apply to this example and make adjustments as needed. Refer to Table 2–1.
Check the installation prerequisites.
Check which tasks you might need to perform for this installation before starting. Refer to Table 1–1.
Run the Java ES installer.
Choose the type of installation, select Custom.
At component selection, select Directory Proxy Server.
If you are using a remote copy of Directory Server, deselect Directory Server and specify a remote copy during postinstallation configuration.
Resolve incompatibilities.
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Verify installation directories.
Run the installation.
View the Installation Summary and Log.
Complete postinstallation configuration.
Start the Directory Server first, then start the Directory Proxy Server.
This example installs Directory Server by itself.
Directory Server has no dependencies on other Java ES components.
If your deployment calls for Schema 2, you must configure Directory Server for Schema 2 before implementing any other Java ES components.
Check the installation sequence guidelines.
Check which guidelines apply to this example and make adjustments as needed. Refer to Table 2–1.
Check the installation prerequisites.
Check which tasks you might need to perform for this installation before starting. Refer to Table 1–1.
Run the Java ES installer.
Choose the type of installation, select Custom.
Select the Configure Automatically During Installation or Configure Manually After Installation type.
For the Configure Automatically During Installation type, configuration pages are displayed for the local Java ES components that can be configured during installation.
For the Configure Manually After Installation type, configuration pages are not displayed.
At component selection, select Directory Server.
Resolve incompatibilities.
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Verify installation directories.
Run the installation.
View the Installation Summary and Log.
Complete postinstallation configuration.
Start the Directory Server.
This example installs Message Queue by itself. Message Queue has no dependencies on other Java ES components.
Check the installation sequence guidelines.
Check which guidelines apply to this example and make adjustments as needed. Refer to Table 2–1.
Check the installation prerequisites.
Check which tasks you might need to perform for this installation before starting. Refer to Table 1–1.
Run the Java ES installer.
Choose the type of installation, select Custom.
Select the Configure Manually After Installation type.
At component selection, select Message Queue.
Resolve incompatibilities.
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Run the installation.
View the Installation Summary and Log.
Start Message Queue.
If your Java ES components use Java ES monitoring, you can install the Monitoring Console component in addition to the other Java ES components. However, Monitoring Console cannot run on the same host as any of the Java ES components. Monitoring Console must be installed in a separate installation session.
Check the installation sequence guidelines.
Check which guidelines apply to this example and make adjustments as needed. Refer to Table 2–1.
Check the installation prerequisites.
Check which tasks you might need to perform for this installation before starting. Refer to Table 1–1.
Run the Java ES installer.
Ensure that no other Java ES component products are installed on the same host as Monitoring Console.
Choose the type of installation, select Custom.
Select the Configure Automatically During Installation or Configure Manually After Installation type.
At component selection, choose Monitoring Console.
Resolve incompatibilities.
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Verify installation directories.
Run the installation.
View the Installation Summary and Log.
Complete postinstallation configuration.
After installing all the components that will use monitoring on other hosts, you will need to configure each of them for monitoring using instructions in Chapter 2, Enabling and Configuring the Monitoring Framework, in Sun Java Enterprise System 5 Monitoring Guide. This document also contains instructions for administering and using Java ES monitoring.
This example installs Service Registry by itself.
Service Registry requires a local copy of Application Server, HADB, and at least two of its subcomponents: Domain Administration Server and Command Line Administration Tool. Message Queue is also required.
Check the installation sequence guidelines.
Check which guidelines apply to this example and make adjustments as needed. Refer to Table 2–1.
Check the installation prerequisites.
Check which tasks you might need to perform for this installation before starting. Refer to Table 1–1.
Run the Java ES installer.
Choose the type of installation, select Custom.
Select the Configure Automatically During Installation or Configure Manually After Installation type.
At component selection, select Service Registry.
Application Server and its required subcomponents as well as HADB and Message Queue are automatically selected.
Resolve incompatibilities.
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Verify installation directories.
Run the installation.
View the Installation Summary and Log.
Complete postinstallation configuration.
Start Service Registry.
This example installs Web Server by itself. Web Server has no dependencies on other Java ES components.
Check the installation sequence guidelines.
Check which guidelines apply to this example and make adjustments as needed. Refer to Table 2–1.
Check the installation prerequisites.
Check which tasks you might need to perform for this installation before starting. Refer to Table 1–1.
Run the Java ES installer.
Choose the type of installation, select Custom.
Select the Configure Automatically During Installation or Configure Manually After Installation type.
At component selection, select Web Server.
Resolve incompatibilities.
The installer verifies software on your host and provides guidance if incompatibilities are identified.
Verify installation directories.
Run the installation.
View the Installation Summary and Log.
Complete postinstallation configuration.
Start Web Server