|
| |
| Sun Java Enterprise System Installation Guide for Microsoft Windows | |
Chapter 2
Developing Your Installation SequenceThis chapter provides information and guidelines for developing an installation sequence based on your Sun Java Enterprise System deployment plan. If you have not yet developed a deployment plan, refer to Java Enterprise System Deployment Planning Guide (http://docs.sun.com/app/docs/doc/819-2326).
This chapter contains the following sections:
What Does My Deployment Call for?This section discusses how to interpret your deployment planning documents in relation to the Sun Java Enterprise System installation tasks you need to perform. There are two deployment planning documents that form the basis of your installation plan: the deployment architecture and the implementation specification.
Reviewing Your Deployment Architecture
A deployment architecture is a high-level mapping of a logical architecture to a physical computing environment. The physical environment includes the computing nodes in an intranet or internet environment, the network links between them, and other physical devices needed to support the software.
The following figure shows a typical deployment architecture.
Figure 2-1 Example of a Deployment Architecture
What Are My Key Installation Issues?Each deployment revolves around a different set of issues and components. By examining your implementation specification, you can identify the main issues that will determine the tasks required to perform the installation.
The following table presents some typical deployment situations that might affect your installation sequence.
Table 2-1 Installation Issues to Consider
Situation
Guidelines or Instructions
Directory replication
Guidelines for setting up Directory Server replication are contained in the Sun Java Enterprise System User Management Guide (http://docs.sun.com/app/docs/doc/817-5761).
Separation of Portal Server and Access Manager
Portal Server and Access Manager can be installed on separate machines.
Schema 1
For a Schema 1 deployment, you cannot use Access Manager.
Single user entry
Guidelines for setting up a single user entry, possibly for single sign-on, can be found in the Sun Java Enterprise System User Management Guide (http://docs.sun.com/app/docs/doc/817-5761). Access Manager is required to set up single sign-on for Schema 2.
How Do Component Interdependencies Affect My Installation?To determine the best sequence for installing the Sun Java Enterprise System, it is important to understand how the components depend on each other. From an installation point of view, the Sun Java Enterprise System components are layered with the bottom layer generally providing a base for the layers above.
The preceding figure does not necessarily indicate which components require the presence of other components in the host. For example, if your deployment does not require a web container, then the second layer in the figure would not be a factor in your installation planning.
The following table shows the dependencies among the Sun Java Enterprise System components (it does not show dependencies on shared components, such as J2SE). Using this table, you can list or diagram the chain of dependencies for your installation. The left column lists the components, the middle column lists what is required for each component, and the right column indicates whether or not the required components must be installed on the local machine.
Table 2-2 Cross-component Dependencies
Component
Required Component(s)
Must Be Local?
Access Manager
Directory Server
No
Web container, either of the two:
Yes
Access Manager SDK
Access Manager
No
Administration Server
Directory Server
No
Application Server
Message Queue
Yes
Web Server (required for load balancing)
Yes
Calendar Server
Directory Server
No
For Schema 2:
Access Manager or
Access Manager SDK
No
YesA web container. See Access Manager.
No
Communications Express
Directory Server
No
Administration Server
Yes
Access Manager or
Access Manager SDKNo
YesWeb container, either of the two:
Yes
Calendar Server, if using calendar service
No
Messaging Server with Administration Server, if using messaging service
Yes
Delegated Administrator
Any web container and Access Manager
Yes
Directory Proxy Sever
Directory Server
No
Administration Server
Yes
Directory Server
None
Not applicable
Directory Preparation Script
Directory Server
Yes
HADB
None
Not applicable
Instant Messaging
Directory Server
No
For single sign-on or Access Manager managed policies:
Access Manager
or
Access Manager SDK
No (Instant Messaging Core)
Yes (Instant Messaging Resources)
A web container. See Access Manager.
No
Message Queue
None
Not applicable
Messaging Server
Directory Server
No
Administration Server
Yes
For Schema 2:
Access Manager or
Access Manager SDK
No
YesA web container. See Access Manager.
No
Portal Server
Access Manager or
Access Manager SDKNo
YesA web container. See Access Manager.
Yes
Portal Server Secure Remote Access
Portal Server
No
Access Manager or
Access Manager SDKNo
YesA web container. See Access Manager.
Yes
Service Registry
Application Server
Yes
Web Proxy Server
None
Not applicable
Web Server
None
Not applicable
Component dependencies affect the installation in a number of ways. For example:
- Web Container. Several products such as Access Manager, Portal Server, Communication Express, and Delegated Administrator require a web container. The web container can be either an Application Server or Web Server.
- Remote Dependencies. A number of component dependencies can be satisfied by using a remote copy of a required component. The remote component must be installed and running before installing any component that depends on it. This requires multiple installation sessions.
- Schema 1. Calendar Server and Messaging Server can use either Schema 1 or Schema 2. If you are using Calendar Server or Messaging Server with Schema 1, Access Manager cannot be used.
- Schema 2. If you are using Calendar Server or Messaging Server with Schema 2, you must select Access Manager or Access Manager SDK.
- Single sign-on. Access Manager is required if you are implementing single sign-on or Access Manager managed policies in a Schema 2 environment. Delegated Administrator is automatically installed with Access Manager.
- Access Manager SDK. Access Manager SDK is only required if you are using Access Manager. When installed separately, Access Manager SDK requires a remote copy of Access Manager.
During installation, if you fail to select a component that fulfills a requirement, a message informs you that the requirement has not been met. The installation cannot proceed until the requirement is satisfied.
The order in which you install components on multiple hosts is determined by the interdependencies of the components that you select.
A person who is experienced in installing Sun Java Enterprise System might be able to adjust an installation sequence in a number of ways to shorten the time required. The following installation scenarios can give you some ideas on this.
What Setup Type Is the Best?The Sun Java Enterprise System installer offers two setup options:
Default Option
The installer selects all Java Enterprise System components for installation and automatically configures the products by establishing dependencies. You will be able to set administrator settings that will be applied to all products. You will not be able select a subset of products and you will not be able to select configuration type. This installation type is most suitable for single system evaluation installations.
Custom Option
The installer displays the Product Selection Panel and allows to select the 'components' to be installed in this session. You will also get to choose the configuration for the subset of products being installed.
Which Is the Best Configuration Option?The Sun Java Enterprise System installer offers two options for configuring the system components:
- Configure Automatically During Installation. Configuration takes place immediately after installation using default settings dictated by the installer.
- Configure Manually After Installation. Only installation takes place in this session, configuration is done in a later session using batch files.
You will be prompted to select the configuration type only during the first session of running the installer. For any later session, the installer will consider the configuration option chosen during the first session as the input. For details on multiple sessions, refer to Multiple Installation Sessions.
Configure Automatically During Installation
When you select this option, the installer considers the default values for each product and completes the configuration. You can select or deselect the products from the product selection panel. All the selected products are configured during this type of installation.
Configure Manually After Installation
When you select this option, the installer installs the component files in their respective directories. No parameter setting is done and most components are not operational because runtime services are not available. After installation, you must run the configuration tools for each installed component.
How Many Installation Sessions Are Needed?For installing various Java ES components on multiple systems in a distributed deployment scenario, you will require multiple install sessions on each of the systems. Using 'Configure Manually After Installation' mode is recommended for such situations. While creating an evaluation installation, you can choose to install everything in single session or run the installer several times to incrementally add more components. Either configuration modes can be used for single system installation.
Single Installation Session
A single installation session is useful under the following circumstances:
Multiple Installation Sessions
In multiple installation sessions, you run the installer once to install some components, and then run the installer again to install other components on other hosts.
When you use multiple installation sessions for components that are related (for example, Directory Server, Directory Proxy Server, and Administration Server), parameter settings must be the same through each session.
Next StepsIf you have not yet surveyed your existing hosts and have not done any upgrading required, refer to:
Sun Java Enterprise System Upgrade Guide for Microsoft Windows (http://docs.sun.com/app/docs/doc/819-4461)
For information on installation prerequisites and component interdependencies, proceed to Chapter 3, "Installation Process and Prerequisites".
