Sun Java Enterprise System 5 Installation Guide for Microsoft Windows

Chapter 2 Example Installation Sequences

This chapter provides sequencing guidelines for some common Sun Java Enterprise System (Java ES) installations.

This chapter contains the following sections:

How to Use This Chapter

The example installation sequences in this chapter provide high-level guidelines for some common Java ES installations. These procedures provide the sequential steps required to implement particular deployment scenarios.

The single-session examples describe typical steps for installing one or a number of Java ES components on a single host in a single installation session. An evaluation example is included. The remaining examples describe situations where multiple installation sessions are performed on multiple hosts, for a variety of solutions. The sequences in this chapter are based on the relationships among the Java ES 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. Warning messages identify the problem and tell you what you need to do. These message also tell you about incompatible versions of some or all of the components that are already installed on the local host. You can also use the Java ES installer to identify already installed components.

Tip –

Remove or upgrade any incompatible versions of Java ES components before starting the installer.

Table 2–1 Installation Sequence Guidelines


Installation Guideline Topic	Description
Monitoring	Monitoring Console cannot be run on the same host as Java ES components that it monitors. Therefore, Monitoring Console should be installed on another host in a separate installation session.
Installation-time configuration	The following components can be installed in a Configure Automatically During installation, but configuration cannot be performed during installation: Monitoring Console and Service Registry.
Remote component	If you are using a remote Java ES component to fulfill dependencies, the remote Java ES component must be installed and running before installing any Java ES components that depend on the remote component.

Access Manager modes	You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with Portal Server. Access Manager Realm (7.x) installation type can only be used if you are not installing Portal Server.

Single-Session Installation Examples

The following examples apply to installation on a single host in a single session:

Evaluation Example

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.

To Develop a Sequence for Java ES 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.

Start the Java ES graphical installer.

Choose the type of installation, select Custom.

The Java ES installer provides two types of installation:

Default

Select and configures all products automatically with Web Server as the web container

Custom

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.

Application Server Only Example

This example installs Application Server by itself.

To Install Application Server: Example Sequence

Before You Begin

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.

Directory Proxy Server Example

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

Note –

Do not install Directory Proxy Server on the same system where Directory Server is installed, except for evaluation.

To Install Directory Proxy Server: Example Sequence

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.

Directory Server-Only Example

This example installs Directory Server by itself.

To Install Directory Server: Example Sequence

Before You Begin

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.

Message Queue-Only Example

This example installs Message Queue by itself. Message Queue has no dependencies on other Java ES components.

To Install Message Queue: Example Sequence

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.

Monitoring Console-Only Example

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.

To Install Monitoring Console: Example Sequence

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.

Service Registry-Only Example

This example installs Service Registry by itself.

To Install Service Registry: Example Sequence

Before You Begin

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.

Web Server-Only Example

This example installs Web Server by itself. Web Server has no dependencies on other Java ES components.

To Install Web Server: Example Sequence

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

Access Manager SDK With Container Configuration Example

This example installs Access Manager SDK, using a copy of Access Manager that is already installed on a remote host.

To Configure Host A: Example Sequence

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.

Accept licence agreement and select the destination folder for installation.

Choose the type of installation, select Custom.

Select the Configure Automatically During Installation or Configure Manually After Installation type.

For post installation configuration information, see Chapter 5, Completing Postinstallation Configuration.

At component selection, choose Access Manager, Directory Server, and web container.

Resolve incompatibilities.

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

Type administrator user name and password.

Run the installation.

View the Installation Summary and Log.

Verify that the Directory Server and web container are installed and running.

Access the default Access Manager login page.

http://webserver-host:port/amserver

To Configure Host B: Example Sequence

Before You Begin

Access Manager core services must be installed and running on a remote host (Host A).
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 core services.

The Java ES installer does not allow you to configure the web container when you are installing only the Access Manager SDK.

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.

Accept licence agreement and select the destination folder for installation.

Choose the type of installation, select Custom.

Select the Configure Manually After Installation type.

At component selection, choose Access Manager SDK.

Resolve incompatibilities.

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

Type administrator user name and password.

Run the installation.

View the Installation Summary and Log.

Configure and start web container administration server.

For more information about configuring web container, see Chapter 5, Completing Postinstallation Configuration.

Edit the AccessManager-base\setup\AMConfigurator.properties file.

Modify the following parameters in the AMConfigurator.properties file:
- Set DEPLOY_LEVEL to 4.
- Set SERVER_HOST and SERVER_PORT to the host and port of the full server which will be used by Access Manager SDK.
- Set DS_HOST, DS_DIRMGRPASSWD, and ROOT_SUFFIX to the hostname, directory manager password, and root suffix of the Host A Directory Server.
- Set ADMINPASSWD and AMLDAPUSERPASSWD to the amadmin and amldapuser passwords used on Host A.
- Set AM_ENC_PWD 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: Accessmanager-base/config/AMConfig.properties
- Set WEB_CONTAINER to the corresponding value for the web container being used.
- Set BASEDIR to the install directory used during the Configure Manually After Installation of Access Manager SDK.
- Set AM_REALM 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 WS6 (Sun Java System Web Server), then you should modify the settings that are prefixed by WS61 (WS61_INSTANCE , WS61_HOME, WS61_PROTOCOL and so on.

As administrator, use the edited AMConfigurator.propertiesfile to deploy Access Manager.

AccessManager-base\setup\amconfig.bat

Identity Management Example

In this example, identity management is implemented by installing Access Manager and Directory Server, with Directory Server on a remote host.

To Install Host A: Example Sequence

Before You Begin

Access Manager requires Directory Server, but not necessarily a local copy.
Access Manager requires a web container, which in this example is Web Server.
Remote Directory Server must be running before installing any other Java ES components.

Installing and starting Directory Server

See Directory Server-Only Example.

To Install Host B: Example Sequence

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.

Accept licence agreement and select the destination folder for installation.

Choose the type of installation, select Custom.

Select the Configure Manually After Installation type.

At component selection, choose Access Manager and Web Server.

Directory Server is automatically selected and installed.

Resolve incompatibilities.

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

Type administrator user name and password.

Run the installation.

View the Installation Summary and Log.

Edit the AccessManager-base\setup\AMConfigurator.properties file.

Set DS_HOST, DS_DIRMGRPASSWD, and ROOT_SUFFIX to the host name, directory manager password , and root suffix of the Host A Directory Server.

Configure Web container and start the administration server.

For more information about configuring web container, see Chapter 5, Completing Postinstallation Configuration.

Access the default Access Manager login page.
http://webserver-host:port/amserver

Web and Application Services Example

HADB, which is 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 host.

On a partitioned operating system, a preferred solution is to install two host servers with at least one HADB process running on each.

To Install Web and Application Services: : Example Sequence

The general tasks include:

Installing the Java ES components
Starting the servers
Configuring load balancing

The following example shows how to install all Java ES components on a node. On subsequent nodes, install the Java ES components required by your deployment. A minimum of two installation sessions are required.

Before You Begin

Application Server requires a local copy of HADB 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.
Load Balancing Plug-in subcomponent of Application Server requires a Web Server. This example uses the Sun Java System web container.

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 type.

Message Queue requires no configuration.

At component selection, choose Application Server.

Message Queue, HADB, and all the subcomponents of Application Server except the Application Server Node Agent and Load Balancing Plug-in are automatically selected.

Expand the Application Server component and select Load Balancing Plug-in.

Note –
You must install the Web Server and Load Balancing Plug-in using the same access permissions.

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 the Java ES components.

Complete load balancing configuration.

Refer to the Chapter 5, Configuring HTTP Load Balancing, in Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.