Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

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, a quick installation to see how things go. This example uses the graphical interface and the Configure Now option. When you are presented with configuration pages, you accept defaults wherever possible.

This example installs all the Java ES components except Sun Cluster software on a single host in a single installation session. Because Web Server is used as the web container, Application Server is not installed.

ProcedureTo Develop a Sequence for Java ES Evaluation

The following high-level tasks are required:

Steps
  1. Starting the Java ES graphical installer

  2. Checking the installation prerequisites

  3. At component selection, selecting Install All, then deselecting the Application Server and Sun Cluster components

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

  4. Verifying installation directories

  5. Selecting the Configure Now option

    Messages indicate which components cannot be configured during installation.

  6. Accepting configuration defaults when they are offered

    If you want to use non-default information, review the appropriate configuration tables in Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference.

  7. Viewing the Installation Summary and Log

  8. Completing post-install configuration

    Chapter 6, Configuring Components After Installation contains instructions for post-install configuration.

  9. Starting the components

    Verifying After Post-Installation Configuration contains the preferred Java ES startup sequence. Startup procedures follow the table.


    Note –

    If you are using a remote component to fulfill dependencies, the remote component must be installed and running before installing any components that depend on it.


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 Identity Management and Policy Core Services, Access Manager Administration Console, and Common Domain Services for Federation on another host by deselecting these subcomponents of Access Manager.


Note –

You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with Portal Server, Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging. Access Manager Realm (7.x) installation type can only be used if you are not installing any of these components.


ProcedureTo Develop a Sequence for Access Manager and Portal Server

The following high-level tasks are required:

Steps
  1. Running the Java ES installer

  2. At component selection, choosing Portal Server and Web Server

    Access Manager, Directory Server, and Directory Preparatory Tool are automatically selected. Because Administration Server supplies a graphical interface for Directory Server, you might also want to select Administration Server.

    • To use a remote copy of Directory Server, deselect Directory Serverand specific a remote copy when prompted.


      Note –

      The remote Directory Server must be running before installing any other components. For instructions on installing Directory Server, refer to Directory Server Only Example.


    • To use a remote copy of Access Manager, deselect Access Managerand specify a remote copy during postinstallation configuration.

  3. Resolving incompatibilities

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

  4. Selecting the Configure Now or Configure Later option

    • For the Configure Now option, configuration pages are displayed for those components that allow installation-time configuration. Do not accept defaults for components that are remote; use the remote information.

    • For the Configure Later option, configuration pages are not displayed.

  5. Running the installation

  6. Viewing the Installation Summary and Log

  7. Completing postinstallation configuration

  8. Starting components

  9. Accessing the default Access Manager login page

    http://webserver-host:port/amconsole

    The following table contains additional Access Manager information.

    Task 

    Relevant Information 

    Configuration information for the installer 

    Access Manager Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference

    Postinstallation configuration 

    Access Manager Postinstallation Configuration

    Starting and stopping 

    Starting and Stopping Access Manager

    Uninstalling 

    Access Manager Uninstallation Behavior

    Troubleshooting 

    Access Manager Troubleshooting Tips

    Upgrading 

    Sun Java Enterprise System 2005Q4 Upgrade Guide

    The following table contains additional Portal Server information.

    Task 

    Relevant Information 

    Configuration information for the installer 

    Portal Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference

    Postinstallation configuration 

    Portal Server and Portal Server Secure Remote Access Postinstallation Configuration

    Starting and stopping 

    Starting the Web Container to Access Portal Server Desktop

    Uninstalling 

    Portal Server Uninstallation Behavior

    Troubleshooting 

    Portal Server Troubleshooting Tips

    Upgrading 

    Sun Java Enterprise System 2005Q4 Upgrade Guide

Application Server Only Example

This example installs Application Server by itself.

Requirements

Application Server requires a local copy of Message Queue. If you are using load balancing, a local copy of a web server is required.


Note –

If you are using this component with Sun Cluster software, you must perform a precise series of tasks before installing any components. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.


ProcedureTo Develop a Sequence for Application Server

The following high-level tasks are required:

Steps
  1. Running the Java ES installer

  2. At component selection, choosing Application Server

    Message Queue is 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 desired. If you want to use Apache web server, Apache web server must already be installed. Web Server will also be installed. At the Application Server installation page, choose between Web Server and Apache. Supply the path to the web server.

  3. Resolving incompatibilities

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

  4. Verifying installation directories

  5. Selecting the Configure Now or Configure Later option

    1. For the Configure Now option, configuration pages are displayed for the local 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 2005Q4 Installation Reference.

    2. For the Configure Later option, configuration pages are not displayed.

  6. Running the installation

  7. Viewing the Installation Summary and Log

  8. Completing post-install configuration

  9. Starting Application Server (automatically starts Message Queue)

    The following table contains additional Application Server information.

    Task 

    Relevant Information 

    Configuration information for the installer 

    Application Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference

    Postinstallation configuration 

    To Configure Application Server After a Configure Later Installation

    Starting and stopping 

    Starting and Stopping Application Server

    Uninstalling 

    Application Server Uninstallation Behavior

    Troubleshooting 

    Application Server Troubleshooting Tips

    Upgrading 

    Sun Java Enterprise System 2005Q4 Upgrade Guide

Directory Server Only Example

This example installs Directory Server by itself.

Requirements and Sequence Issues

Directory Server has no dependencies on other Java ES components. However, because Administration Server provides a graphical interface for Directory Server, you might also want to select Administration Server.


Note –

If you are using replication for encryption for Directory Server, you should select Administration Server at component selection.


ProcedureTo Develop a Sequence for Directory Server

The following high-level tasks are required:

Steps
  1. Running the Java ES installer

  2. At component selection, selecting Directory Server and (optionally) Administration Server

    The Directory Preparation Tool is automatically selected.

  3. Resolving incompatibilities

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

  4. Verifying installation directories

  5. Selecting the Configure Now or Configure Later option

    1. For the Configure Now option, configuration pages are displayed for the local components that can be configured during installation.

      Gather your configuration information from the tables in Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference.

    2. For the Configure Later option, configuration pages are not displayed.

  6. Running the installation

  7. Viewing the Installation Summary and Log

  8. Completing post-install configuration

  9. Starting the components in this order:

    1. Starting and Stopping Directory Server

    2. (Optional) Starting and Stopping Administration Server and the Server Console

      The following table contains additional Directory Server information.

      Task 

      Relevant Information 

      Configuration information for the installer 

      Directory Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference

      Postinstallation configuration 

      Directory Server Postinstallation Configuration

      Starting and stopping 

      Starting and Stopping Directory Server

      Uninstalling 

      Directory Server Uninstallation Behavior

      Troubleshooting 

      Directory Server Troubleshooting Tips

      Upgrading 

      Sun Java Enterprise System 2005Q4 Upgrade Guide

Directory Proxy Server Example

This example installs Directory Proxy Server with Directory Server on a single host.

Requirements

Directory Proxy Server requires Directory Server, but not necessarily a local copy. In addition, Directory Proxy Server requires a local copy of Administration Server.

ProcedureTo Develop a Sequence for Directory Proxy Server

The following high-level tasks are required:

Steps
  1. Running the Java ES installer

  2. At component selection, selecting Directory Proxy Server

    Directory Server, Directory Preparation Tool, and Administration Server are automatically selected.

    (Optional) If you are using 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 components. For instructions on installing Directory Server, refer to Directory Server Only Example.


  3. Resolving incompatibilities

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

  4. Verifying installation directories

  5. Selecting the Configure Now or Configure Later option

    1. For the Configure Now option, configuration pages are displayed for the local components that can be configured during installation.

      Do not accept defaults for components that are remote; use the remote information.

      Gather your configuration information from the tables in Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference

    2. For the Configure Later option, configuration pages are not displayed.

  6. Running the installation

  7. Viewing the Installation Summary and Log

  8. Completing post-install configuration

  9. Starting the components in this order:

    1. Starting and Stopping Directory Server

    2. Starting and Stopping Administration Server and the Server Console

    3. Starting and Stopping Directory Proxy Server

      The following table contains additional Directory Proxy Server information.

      Task 

      Relevant Information 

      Configuration information for the installer 

      Directory Proxy Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference

      Postinstallation configuration 

      Directory Proxy Server Postinstallation Configuration

      Starting and stopping 

      Starting and Stopping Directory Proxy Server

      Uninstalling 

      Directory Proxy Server Uninstallation Behavior

      Troubleshooting 

      Directory Proxy Server Troubleshooting Tips

      Upgrading 

      Sun Java Enterprise System 2005Q4 Upgrade Guide

Instant Messaging Only Example

This example installs Instant Messaging by itself. It is not uncommon for Instant Messaging to be installed in a separate installation session after other components have been installed and configured.


Note –

If you are using single sign-on or Access Manager managed policies, Access Manager is required. For guidelines, refer to Instant Messaging and Access Manager Example


Sequence Issues

ProcedureTo Develop a Sequence for Instant Messaging

The following high-level tasks are required:

Steps
  1. Running the Java ES installer

  2. At component selection, choosing Instant Messaging

  3. Resolving incompatibilities

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

  4. Verifying installation directories

  5. Selecting the Configure Later option

    Instant Messaging cannot be configured during installation.

  6. Running the installation

  7. Viewing the Installation Summary and Log

  8. Completing post-install configuration

    Configuring Instant Messaging After a Configure Later Installation

  9. Starting Instant Messaging (after starting any other components that Instant Messaging might depend on)

    Starting and Stopping Instant Messaging Server and Multiplexor

    The following table contains additional Instant Messaging information.

    Task 

    Relevant Information 

    Postinstallation configuration 

    Configuring Instant Messaging After a Configure Later Installation

    Starting and stopping 

    Starting and Stopping Instant Messaging Server and Multiplexor

    Uninstalling 

    Instant Messaging Uninstallation Behavior

    Troubleshooting 

    Instant Messaging Troubleshooting Tips

    Upgrading 

    Sun Java Enterprise System 2005Q4 Upgrade Guide

    Deployment scenarios 

    Sun Java System Communications Deployment Planning Guide

Message Queue Only Example

This example installs Message Queue by itself.

Requirements

Message Queue has no dependencies on other Java ES components.


Note –

If you are using this component with Sun Cluster software, you must perform a precise series of tasks before installing any components. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.


ProcedureTo Develop a Sequence for Message Queue

The following high-level tasks are required:

Steps
  1. Running the Java ES installer

  2. At component selection, selecting Message Queue

  3. Resolving incompatibilities

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

    • Solaris OS:

      If a previous copy of Message Queue, Platform Edition is detected on the host, the installer will automatically update the installation with Message Queue, Enterprise Edition.

      If a previous copy of Message Queue, Enterprise Edition is detected on the host, you must exit the installer and follow the instructions for upgrading to Message Queue, Enterprise Edition in the Sun Java Enterprise System 2005Q4 Upgrade Guide.

    • Linux:

      If a previous copy of Message Queue, (Platform or Enterprise Editions) is detected on the host, you must exit the installer and follow the instructions for upgrading and migrating to Message Queue, Enterprise Edition in the Sun Java Enterprise System 2005Q4 Upgrade Guide.

  4. Selecting the Configure Later option.

    Message Queue cannot be configured during installation

  5. Running the installation

  6. Viewing the Installation Summary and Log

  7. Starting Message Queue

    Starting Message Queue

    The following table contains additional Message Queue information.

    Task 

    Relevant Information 

    Postinstallation configuration 

    Message Queue Postinstallation Configuration

    Starting and stopping 

    Starting Message Queue

    Uninstalling 

    Message Queue Uninstallation Behavior

    Troubleshooting 

    Message Queue Troubleshooting Tips

    Upgrading 

    Sun Java Enterprise System 2005Q4 Upgrade Guide

Portal Server Secure Remote Access Example

This example installs Portal Server Secure Remote Access with Access Manager on a single host, with 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 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.


Note –

You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with Portal Server, Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging. Access Manager Realm (7.x) installation type can only be used if you are not installing any of these components.


ProcedureTo Develop a Sequence for Portal Server Secure Remote Access

The following high-level tasks are required:

Steps
  1. Running the Java ES installer

  2. At component selection, choosing Portal Server Secure Remote Access and Web Server

    Portal Server, Access Manager, Directory Server, and Directory Preparation Tool, and 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 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.


      Note –

      The remote Access Manager must be running before installing any other components. For instructions on installing Access Manager, refer to Identity Management Example.


  3. Resolving incompatibilities

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

  4. Selecting the Configure Now or Configure Later option

    1. For the Configure Now option, configuration pages are displayed for those components that allow installation time configuration. Do not accept defaults for components that are remote; use the remote information.

      You will need to gather your configuration information from the tables in Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference.

    2. For the Configure Later option, configuration pages are not displayed.

  5. Running the installation

  6. Viewing the Installation Summary and Log

  7. Completing any post-install configuration

    For Configure Now:

    For Configure Later:

  8. Starting the components

  9. Accessing the default Access Manager login page


    http://webserver-host:port/amserver
  10. Accessing the portal


    http://webserver-host:port/portal/dt
  11. Accessing the Portal Gateway


    http://gateway-server:port/

    The following table contains additional Portal Server Secure Remote Access information.

    Task 

    Relevant Information 

    Configuration information for the installer 

    Portal Server Secure Remote Access Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference

    Starting and stopping 

    Starting and Stopping Portal Server Secure Remote Access

    Uninstalling 

    Portal Server Secure Remote Access Uninstallation Behavior

    Troubleshooting 

    Portal Server Secure Remote Access Troubleshooting Tips

    Upgrading 

    Sun Java Enterprise System 2005Q4 Upgrade Guide

Service Registry Only Example

This example installs Service Registry by itself.

Requirements

Service Registry requires a local copy of Application Server and at least two of its subcomponents: Domain Administration Server and Command Line Administration Tool. Message Queue is also required.

ProcedureTo Develop a Sequence for Service Registry

The following high-level tasks are required:

Steps
  1. Running the Java ES installer

  2. At component selection, selecting Service Registry

    Application Server and its required subcomponents as well as Message Queue are automatically selected.

  3. Resolving incompatibilities

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

  4. Verifying installation directories

  5. Selecting the Configure Now or Configure Later option

    1. For the Configure Now option, the Application Server configuration pages are displayed by the installer.

      Gather your configuration information from the tables in Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference

    2. For the Configure Later option, configuration pages are not displayed.

      Service Registry cannot be configured during installation.

  6. Running the installation

  7. Viewing the Installation Summary and Log

  8. Completing post-install configuration, in this order

    1. Application Server Postinstallation Configuration

    2. Service Registry Postinstallation Configuration

  9. StartingApplication Server and Service Registry

    The following table contains additional information for installing Service Registry.

    Task 

    Relevant Information 

    Postinstallation configuration 

    Service Registry Postinstallation Configuration

    Uninstalling 

    Service Registry Uninstallation Behavior

    Troubleshooting 

    Service Registry Troubleshooting Tips

Web Server Only Example

This example installs Web Server by itself.

Requirements

Web Server has no dependencies on other components.


Note –

If you are using this component with Sun Cluster software, you must perform a precise series of tasks before installing any components. Refer to Sun Cluster Software Example to see Sun Cluster guidelines.


ProcedureTo Develop a Sequence for Web Server

The following high-level tasks are required:

Steps
  1. Running the Java ES installer

  2. At component selection, selecting Web Server

  3. Resolving incompatibilities

    The installer verifies software on your host and provides guidance if incompatibilities are identified.

  4. Verifying installation directories

  5. Selecting the Configure Now or Configure Later option

    1. For the Configure Now option, the Web Server configuration pages are displayed by the installer.

      Gather your configuration information from the tables in Chapter 1, Configuration Information, in Sun Java Enterprise System 2005Q4 Installation Reference

    2. For the Configure Later option, configuration pages are not displayed.

  6. Running the installation

  7. Viewing the Installation Summary and Log

  8. Completing any post-install configuration

    Web Server Postinstallation Configuration

  9. Starting Web Server

    Starting and Stopping Web Server

    The following table contains additional information for installing Web Server.

    Task 

    Relevant Information 

    Postinstallation configuration 

    Web Server Postinstallation Configuration

    Starting and stopping 

    Starting and Stopping Web Server

    Uninstalling 

    Web Server Uninstallation Behavior

    Troubleshooting 

    Web Server Troubleshooting Tips

    Upgrading 

    Sun Java Enterprise System 2005Q4 Upgrade Guide