Sun Java Enterprise System 5 Update 1 Installation FAQs for UNIX

Preparing to Install Java ES Software

This section contains questions that are often asked about what needs to be done before running the installer.

Q6: How much planning do I need to do before I install Java ES?

Answer: If you are installing for evaluation only, the best preparation is to install on a host that contains only the operating system. You select all components except Monitoring Console and Sun Cluster software, and accept most defaults offered by the installer.

However, for a production deployment across multiple hosts, the following planning activities are important for ensuring a successful installation:

Developing a deployment architecture In general, the deployment architecture and deployment design indicate what needs to be done, the implementation specifications indicate how to implement the design, and the installation plan indicates how to perform installation tasks to meet the technical requirements. Refer to the instructions for creating a deployment architecture and deployment design in the Sun Java Enterprise System Deployment Planning Guide. For additional specifics, refer to the Planning page on the Java ES hub: Planning tasks.
Developing an installation plan Based on the deployment architecture, the installation plan determines how to implement Java ES to meet the technical requirements for the deployment. The installation sequence examples can be helpful in determining the sequence of events for installation. See Chapter 2, Example Installation Sequences, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX. Instructions for creating an installation plan are contained in the Sun Java Enterprise System 5 Installation Planning Guide.
Surveying your hosts By surveying the software that is already on your hosts, you can take steps to bring hosts to the optimum state before installation. See Surveying Existing Hosts in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX. Activities might include upgrading or removing some installed components. Instructions for upgrading are contained in the Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX.
Determining your configuration values Some product components can be configured during installation, so you must determine the configuration values that you are asked to supply during installation. See Chapter 3, Configuration Information, in Sun Java Enterprise System 5 Update 1 Installation Reference for UNIX.
Additional tasks for specific deployment needs
- Single sign-on This type of configuration is done after postinstallation configuration is complete. Example instructions on how to implement single sign-on for your components are contained in the evaluation deployment example. Substitute your configuration specifics in these Chapter 8, Configuring and Using Single Sign-On, in Sun Java Enterprise System 2005Q1 Deployment Example Series: Evaluation Scenario.
- Redundancy Most production deployments include a redundancy requirement, such as load balancing, clustering, or multimaster replication. These methods help to increase throughput or to protect against downtime or data loss. Java ES redundancy strategies are discussed in Installation Planning Issues in Sun Java Enterprise System 5 Installation Planning Guide. Additional material is contained in Availability in Sun Java Enterprise System Deployment Planning Guide. Also refer to Q14: What do I have to do if my Java ES installation will include Sun Cluster software? (for Solaris OS only).
- User management This type of configuring is done after postinstallation configuration is complete. Example instructions on how to implement user management for your components are contained in the evaluation deployment example. See Chapter 7, User Management for the Evaluation Solution, in Sun Java Enterprise System 2005Q1 Deployment Example Series: Evaluation Scenario. Substitute your configuration specifics in these example user management instructions. To plan your schema, see Q15: What is the significance of LDAP Schema 1 and LDAP Schema 2 for Java ES?. For extensive schema instructions, see the Directory Server documentation.

Q7: Are there examples that I can use to plan my installation?

Answer: Yes, there are several type of examples associated with Java ES.

The Java ES deployment examples describe how to implement a production deployment architecture. High availability, scalability, and serviceability are addressed.
To understand the task order for common installations, see Chapter 2, Example Installation Sequences, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX. These examples list the high-level tasks for installing, configuring, and starting the components in the examples.
A view into Sun's use of Java ES is provided in the Reference Configuration Series: Portal Server on Web Server.

Q8: What are the system requirements for installation?

Answer: Before running the installer, verify that the hosts on which you will be installing are set up correctly. System requirements are listed in the following release notes:

Operating system patches might be missing from your host, in which case the installer will not be able to proceed. For information on what to do about missing patches, see Q26: How do I get patches that the installer indicates are missing?

Solaris OS Patch Clusters Refer to the Sunsolve patch cluster page to see the recommended Java ES patch clusters. Information on patch clusters is provided in System Requirements in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX. Because the patch cluster installs all patches required for any of the Java ES components, you might want to install the Java ES required OS patch cluster before installation. However, if you prefer to install only the patches required for the specific components you select, you can let the Java ES installer tell you exactly which patches are needed.

A number of situations exist that might require preinstallation tasks for your particular combination of components. Be sure that relevant installation prerequisites are met before starting your installation. See Verifying Installation Prerequisites in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

Q9: Does it matter if other Java ES components are already on my host?

Answer: Yes, if the versions of those components are incompatible with Java ES 5 Update 1.

An initial Java ES installation goes most smoothly if you are installing on a computer that has only the operating system installed, but this is not always possible. You can install Java ES on a host that already contains Java ES components. However, your installation might be interrupted if the installer finds incompatible versions of those components on the host. In this case, the installer cannot proceed until you either remove or upgrade to supported versions of the Java ES components. See Java ES Components Used in This Release in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

Full instructions for upgrading individual components are in the Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX. Additional information on upgrading is contained on the Upgrade page of the Java ES hub.

Upgrading product components Generally, the installer cannot upgrade the product components.

Note –
If the installer finds upgradable versions of Application Server, HADB, Java DB, or Message Queue on the host, it marks them as upgradable in the Choose Software Components page and will upgrade them if you select them. Upgradable versions can mean earlier versions of Java ES, or Solaris-bundled versions of Application Server and Message Queue. However, if you want to upgrade Application Server from Java ES 2 (2004Q2) on Solaris OS, you must first manually remove the Solaris-bundled version of Application Server.
Upgrading shared components The installer upgrades shared component components automatically during installation.
Removing components For product components that were installed using the Java ES installer, remove them using the Java ES uninstall utility that was put in place during the original installation. See Running the Uninstaller in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX. If no uninstaller is present, the components were probably installed by another method, or an uninstallation has already been done. If you cannot use the uninstaller, you can remove the packages for the components manually. For a list of packages, see Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Update 1 Installation Reference for UNIX. Use the following UNIX commands to remove packages manually:
- Solaris OS: pkgrm
- Linux: rpm -e

Q10: How can I find out which Java ES components are installed on my host?

Answer: One way to identify what Java ES components are on the host is to perform a test installation using the installer -no command. The installer indicates the incompatible and upgradable components that are on the host. For guidelines on how to survey your hosts before doing an installation, refer to instructions for identifying incompatible components in When Incompatible Components Are Installed in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

Another way to survey the software on a host is to examine the product registry. See Q40: What is the product registry and why should I care about it?

You can also view the installed packages using the following UNIX package display commands to see if any Java ES component packages are present. For a list of packages, see Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Update 1 Installation Reference for UNIX. Use the following commands to view packages:

Solaris OS: pkginfo
Linux: rpm -qa

Q11: How do I upgrade from another version of Java ES?

Answer: Full instructions for upgrading Java ES software are in the Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX.

Q12: Are there component interdependencies that I need to know about?

Answer: The Java ES installer checks component dependencies for the components you select. If your selected components require additional components, the installer automatically selects the additional components. To understand how this works, refer to the information in Component Dependencies in Sun Java Enterprise System 5 Installation Planning Guide. Table 3-1 shows the interdependency matrix. To satisfy interdependencies, installation sessions must be run in a particular order, with some components being installed, configured, and started before other components are installed. You might be able to model your deployment on suggested installation sequences. See Chapter 2, Example Installation Sequences, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

After installation, follow the preferred startup sequence for Java ES components. Refer to Table 7–1 in Verifying After Postinstallation Configuration in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

Q13: What do I need to know about Solaris 10 zones for Java ES?

Answer: If you want to install Java ES into Solaris 10 zones, you must keep in mind some Solaris 10 zones guidelines and limitations for Java ES. See Solaris 10 Zones Examples in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX. The guidelines in this section are extracted from a general description of how to use Java ES with Solaris 10 zones in Appendix A, Java ES and Solaris 10 Zones, in Sun Java Enterprise System 5 Installation Planning Guide.

Q14: What do I have to do if my Java ES installation will include Sun Cluster software?

Answer: Sun Cluster software is supported only on Solaris OS. Installing, configuring, and starting the components in the correct order is crucial for a successful Sun Cluster implementation. At least two installation sessions are performed on each node in the cluster. The following are the general tasks:

Install the Java ES Sun Cluster component.
Configure the Sun Cluster framework.
Install the additional Java ES components that are required for a component (agent) to operate in the cluster.
Configure the Sun Cluster data services using the agents for the relevant Java ES components.

To see the high-level installation tasks, refer to the installation sequence example in Sun Cluster Software Example in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

See Also

Java ES installation guidelines in the Sun Cluster documentation:

Q15: What is the significance of LDAP Schema 1 and LDAP Schema 2 for Java ES?

Answer: Java ES solutions that use Directory Server can use either of two versions of a standard LDAP schema: Schema 1 or Schema 2. An explanation of the schema issues for Java ES is contained in Developing Your User Management Specifications in Sun Java Enterprise System 5 Installation Planning Guide. More extensive schema instructions are contained in the Directory Server documentation Designing a Directory Schema in Sun Java System Directory Server Enterprise Edition 6.2 Deployment Planning Guide and the Access Manager documentation To Add Indexes to Directory Server in Sun Java System Access Manager 7.1 Postinstallation Guide.

The installation process configures the directory for the specified schema as follows:

To establish a Schema 1 directory, install Directory Server. Schema 1 is the default schema version.
To establish a Schema 2 directory, install Directory Server and Access Manager. Installing Access Manager modifies the directory and converts a Schema 1 directory to a Schema 2 directory. Schema 2 supports the Access Manager single sign-on feature. If your solution includes Access Manager, you must use Schema 2.