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
- © 2010, Oracle Corporation and/or its affiliates