test

Sun Java Enterprise System 5 Installation FAQs for UNIX

Sun Java Enterprise System 5 Installation FAQs for UNIX

Sun Java Enterprise System (Java ES) provides a single installer for installing Java ES components in various combinations. Due to the interrelationships of these components, Java ES installation requires more preinstallation and postinstallation effort than simpler installations. This document contains some of the most frequently asked questions (FAQs) about Java ES installation.

Learning About Java ES Installation

This section contains questions that deal with learning about Java ES and the contents of the particular release.

Q1: How should I start?

Answer: If you are new to Java ES installation, the following materials can help you become familiar with the installation process. In fact, you should not attempt to install Java ES software until you understand the process and have developed an installation plan.

  1. Read about how the installer works. See How the Java ES Installer Works in Sun Java Enterprise System 5 Installation Guide for UNIX.

  2. View the Sun Java Enterprise System 5 Installer Tutorial for UNIX.

  3. Review the and create an installation plan. Refer to the Sun Java Enterprise System 5 Installation Planning Guide.

  4. Determine if any of the examples in apply to your installation. See Chapter 2, Example Installation Sequences, in Sun Java Enterprise System 5 Installation Guide for UNIX.

  5. Review the known issues for installation. Refer to the Installation Issues in Sun Java Enterprise System 5 Release Notes for UNIX.

  6. Perform an evaluation installation on a single host. See Q2: Is there an installation tutorial or demo available? Additional information is available in the Evaluate page of the Java ES hub.

  7. Plan your production deployment. Refer to the Sun Java Enterprise System Deployment Planning Guide.

Q2: Is there an installation tutorial or demo available?

Answer: Yes, a free installer tutorial is available on UNIX platforms. See Sun Java Enterprise System 5 Installer Tutorial for UNIX. In approximately 15 minutes, you walk through the pages of the installer, learn how the installer works, and gain some insight into what you need to consider before you begin your Java ES installation.

Q3: How can I find Java ES documentation?

Answer: Java ES 5 documentation is stored in the docs.sun.com repository as follows:

Q4: What components are included in this Java ES release?

Answer: The Java ES software consists of a collection of Sun server-side products and their supporting components that work together to support distributed applications across a network.

Product components These are the Java ES components that can be selected for installation by the Java ES installer. For a list of product components, see Java ES Components Used in This Release in Sun Java Enterprise System 5 Installation Guide for UNIX. For brief descriptions of these components, refer to Appendix A, Java ES Components, in Sun Java Enterprise System 5 Technical Overview.

Shared components These components support the product components and are selected automatically by the installer. For a list of shared components, see Shared Components in Sun Java Enterprise System 5 Installation Guide for UNIX.

Java ES components are combined into different suites that provide particular sets of services. Depending on your deployment, you might be interested in downloading a suite rather than the entire Java ES distribution. See Q17: What download media is available?

Q5: Is there a quick installation for evaluating Java ES software?

Answer: Yes, for the Java ES installer on the Microsoft Windows platform. This Quick Install creates a Java ES deployment on a single Windows host using default configuration values. The basic components (excluding Monitoring Console and Sun Cluster software) are automatically started and ready to go. For instructions on using Quick Install, refer to the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

On UNIX platforms (Solaris OS, Linux, HP-UX), two documents exist that provide instructions for creating a single-host evaluation deployment using the installer:

Additional information on evaluating Java ES is contained on the Evaluate page of the Java ES hub.

Tip –

Doing an evaluation installation on a single host is a good way to learn how the installer works.

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:

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

  2. Developing an installation plan Based on the deployment architecture, the installation plan determines how to implement Java ES to meeting 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 Installation Guide for UNIX. Instructions for creating an installation plan are contained in the Sun Java Enterprise System 5 Installation Planning Guide.

  3. 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 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 Upgrade Guide for UNIX.

  4. 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 Installation Reference for UNIX.

  5. Additional tasks for specific deployment needs

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

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

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 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 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 Java ES 5.

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 Installation Guide for UNIX.

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

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 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 Installation Reference for UNIX. Use the following commands to view packages:

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 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 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 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 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:

  1. Install the Java ES Sun Cluster component.

  2. Configure the Sun Cluster framework.

  3. Install the additional Java ES components that are required for a component (agent) to operate in the cluster.

  4. 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 Installation Guide for UNIX.

See Also

Java ES installation guidelines in the Sun Cluster documentation:

Sun Cluster Postinstallation Configuration in Sun Java Enterprise System 5 Installation Guide for UNIX

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.0 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:

Getting the Java ES Software

This section contains questions about the various ways of getting the Java ES software, including how to make it available within your workplace.

Q16: How do I get the Java ES software?

Java ES software is available three ways:

Additional information is contained in Getting the Java ES Software in Sun Java Enterprise System 5 Installation Guide for UNIX.

Q17: What download media is available?

Answer: There are a number of Java ES distribution bundles that can be downloaded from the Web. These are available by platform (Solaris OS, Linux, HP-UX, Microsoft Windows). You can also choose suite downloads. ISO images are not available for download. The Download FAQ answers questions you might have, such as how long a download will take or how to resolve download problems.

To access the Java ES download files, do the following:

  1. At the main Sun page, click the Downloads tab.

  2. Under Enterprise Computing, click Java Enterprise System.

  3. In the Java ES table, click Download.

  4. Scroll to the software list and put a checkmark in the box next to Java Enterprise System.

  5. Scroll to the bottom of the page and click Get Downloads & Media.

  6. Click the link called Multiplatform.

  7. After you register and accept the license agreement, scroll the Downloads page to select the download you want.

  8. Click the link called Download selected with Sun Download Manager.

The following platform downloads are available:

Distribution File Name 

Description 

java_es-5-ga-solaris-sparc.zip

java_es-5-ga-solaris-x86.zip

java_es-5-ga-linux-x86.zip

java_es-5-ga-windows-x86.zip

java_es-5-ga-hpux-parisc.zip

Integrated Java ES installer, full distribution. Uses native OS packaging, and contains all the Java ES Components Used in This Release in Sun Java Enterprise System 5 Installation Guide for UNIX.

sjsasee8_2.zip

Application Server EE 8.2 zip distribution. An alternate distribution for Application Server 8.2 that does not use native OS packaging. Can be installed by non-root users. Support for all platforms is included in the single zip file. 

DSEE.6.0.Solaris-Sparc-full.tar.gz

DSEE.6.0.Solaris9-X86-full.tar.gz

DSEE.6.0.Solaris10-X86_AMD64-full.tar.gz

DSEE.6.0.Redhat-X86-full.tar.gz

DSEE.6.0.Windows-X86-full.zip

DSEE.6.0.Windows-X86-full.zip

DSEE.6.0.HP-UX-full.tar.gz

Directory Server EE 6.0 zip distributions. Alternate distributions for Directory Server 6.0 that do not use native OS packaging. Can be installed by non-root users. Include Directory Server components not available in the integrated Java ES installer, specifically: 

  • Directory Editor 6

  • Directory Server Resource Kit 6

  • Identity Synchronization for Windows (HP-UX not supported)

iWay55sp1.zip

iWay Adapters 5.5 zip distribution. iWay Adapters are not included in the integrated Java ES installer. 

For Solaris OS, the full Java ES distribution contains Sun Cluster 3.1 8/05 and Sun Cluster Geographic Edition 2006Q4 software. The individual Sun Java Availability Suite download contains Sun Cluster 3.2 and Sun Cluster Geographic Edition 3.2 software.

The following suite downloads are available:

Distribution File Name 

Description 

java_es-5-appsuite-ga-*-*.zip

java_es-5-availsuite-ga-*-*.zip

java_es-5-identsuite-ga-*-*.zip

java_es-5-websuite-ga-*-*.zip

Integrated Java ES installer, suite distributions use native OS packaging and contain suite subsets of the Java ES 5 components.

Q18: How do I put the software in a shared location?

Answer: After you expand the distribution bundle, you can put the software in a shared location for others to access by following the instructions in Making an Installation Image on Your Network in Sun Java Enterprise System 5 Installation Guide for UNIX.

Q19. What is in the Java ES 5 media distribution kit?

Answer: The Java ES media distribution kit is the physical media you receive, based on what you requested at the time of purchase. The full Java ES 5 media kit contains the following material:

Running the Installer

This section contains questions about running the Java ES installer.

Q20: How do I run the Java ES installer?

Answer: To run the Java ES installer, you must be superuser on a host. You can install Java ES interactively using the graphical or text-based interface, or silently by means of a reusable script called a state file. The Java ES product documentation contains syntax and examples for using the installation commands in Appendix B, Installation Commands, in Sun Java Enterprise System 5 Installation Guide for UNIX.

At the end of a successful interactive installation session, you are given an option of registering your installation with Sun by using the Java ES Reporter utility. For a description of Java ES Reporter, refer to How Java ES Reporter Works in Sun Java Enterprise System 5 Installation Guide for UNIX.

Tip –

To practice using the installer, type the following command which runs the graphical installer without installing software: ./installer -no

Q21: Can the installer upgrade components that are already on my host?

Answer: Yes and no, depending on the type of component you want to upgrade.

Q22: What is the difference between the Configure Now and Configure Later configuration types?

Answer: The installer gives you the option of performing initial configuration for many of the Java ES components during installation.

The configuration type that you selected (Configure Now or Configure Later) applies to an entire installation session.

Regardless of whether you perform the initial configuration in the installer (Configure Now) or manually after installation, there is usually some additional postinstallation configuration required. See Q28: What postinstallation configuration is required?

Q23: How can I reproduce the same installation on another host?

Answer: You can propagate one configuration across multiple hosts in your enterprise by using silent mode of the Java ES installer. For instructions, see Chapter 5, Installing in Silent Mode, in Sun Java Enterprise System 5 Installation Guide for UNIX.

Q24: Does the installer check dependencies on remote components?

Answer: In general, the installer checks dependencies and versions on the local host only. However, one situation exists where the installer interacts with a remote host: if you select the Configure Now configuration type and are using a remote component (such as Directory Server or Access Manager) to satisfy a dependency. In this case, the installer tries to connect with the remote component during the installation session. If the remote component is not available, installation stops, and you receive an error message. To avoid this situation, install, configure, and start any remote components before starting an installation session.

In a Configure Later installation, the installer runs as though the remote component is available and does no checking. Installation succeeds, and you can proceed to postinstallation configuration. However, if the remote component is not available, you receive errors when you try to run any component that depends on that remote component.

Tip –

To indicate to the installer that you will be using a remote component, select all the components that you will install locally and then deselect any dependency that will be fulfilled by a remote component. When you attempt to proceed, the installer prompts you to fulfill any requirements for the component that you deselected. At this point, you indicate to the installer that you are using a remote component to fulfill a dependency.

Q25: How do I use a third-party web container?

Answer: On Solaris OS, Access Manager and Portal Server can use the third-party web containers BEA WebLogic Server or IBM WebSphere Application Server. On Linux, both are supported for Configure Later, but only BEA WebLogic is supported for Configure Now. HP-UX does not support third-party web containers.

To indicate a third-party web container to the installer, select all of your components, then deselect Sun Java Application Server or Sun Java Web Server. When you click Next, the installer displays the Web Container Selection page telling you that a web container is needed. Select Use Third-Party Web Container.

Tip –

Tip Install, configure, and start any third-party web container in your deployment before installing Java ES. For installation, configuration, and startup instructions, refer to the BEA or IBM product documentation.

Q26: How do I get patches that the installer indicates are missing?

Answer: When the installer performs a system check, the installer might identify missing patches. In most cases, the installer cannot proceed until you install the patches. On Solaris OS, patch clusters offer all the needed Java ES patches. See Q8: What are the system requirements for installation?

In some situations, you need to cancel the installation, but in others you can leave the installer running while you apply the patch. The Sun Java Enterprise System Installation Guide contains an example procedure for installing a patch.

For a Kernel Patch Any patch which is kernel-related will not be able to be applied with the installer running. For such patches, such as patches on libc, do the following:

  1. Exit the installer.

  2. In a browser, go to the patch site for your operating system and find the patch you need:

  3. Download the patch to the local host.

  4. Bring the host to single user mode.

  5. Apply the patch.

  6. Reboot the host.

  7. Restart the installer.

For a Non-Kernel Patch For required patches that are not kernel-related, do the following:

  1. Leave the installer running and open a separate terminal window.

  2. In a browser, go to the patch site for your operating system and find the patch you need:

  3. Download the patch to the local host.

  4. In the new terminal window, apply the patch.

  5. Tell the installer to recheck the host and continue with installation.

Q27: How do I know if my Java ES installation succeeded?

Answer: After the installer indicates that installation is complete, you can view directories or the product registry, or perform some component exercises to verify that the software packages have been successfully copied to your host. See Verifying After Installation in Sun Java Enterprise System 5 Installation Guide for UNIX.

Performing Postinstallation Configuration and Verification

This section contains questions about completing postinstallation configuration and then verifying that the Java ES components work.

Q28: What postinstallation configuration is required?

Answer: When the Java ES installer finishes, most product components require additional configuration to work together. The extent of the configuration tasks varies depending on the configuration type you selected during installation (Configure Now or Configure Later), whether you installed Sun Cluster software or Monitoring Console, and how much extended configuration is needed to build your deployment.

For product components that require postinstallation configuration, refer to Chapter 6, Completing Postinstallation Configuration, in Sun Java Enterprise System 5 Installation Guide for UNIX. (If components are not included in this listing, postinstallation configuration is not required.)

After any type of Java ES deployment, you can use the component configuration tools to make additional changes or enhancements to your configuration.

Q29: How do I know if the postinstallation configuration succeeded?

Answer: After you complete postinstallation configuration, follow the postinstallation verification procedure to verify that your Java ES components have basic functionality. See Verifying After Postinstallation Configuration in Sun Java Enterprise System 5 Installation Guide for UNIX. The installer does not start the Java ES components, so starting the components is part of verifying success of the installation and the initial configuration.

The verification procedure determines only whether the basic installed Java ES is working, not whether you installed the components correctly according to your deployment plan. If the resulting installation does not meet your needs, you can run the uninstaller to uninstall all of the product components, and then perform a new installation.

Q30: How do I start and stop Java ES components?

Answer: You activate Java ES by starting the components in a specific sequence, beginning with the basic services provided by Directory Server and your web container (Web Server or an application server). When you start the web container, the components that run in that web container, such as Portal Server and Access Manager, are automatically started. The preferred startup sequence is described in Table 7–1 in Verifying After Postinstallation Configuration in Sun Java Enterprise System 5 Installation Guide for UNIX. To stop Java ES, stop the components in the reverse order. Instructions for starting and stopping individual product components are contained in Chapter 7, Verifying Installed Product Components, in Sun Java Enterprise System 5 Installation Guide for UNIX.

What to Do After Installation

This section contains questions about how to proceed after installation if verified.

Q31: How do I install more components on a host after I've already done an installation?

Answer: To install additional components, run the installer again. The installer surveys the host to find any installed Java ES components. If the installed component versions are correct, the installer uses the installed components to satisfy the dependencies and requirements for the additional components you are adding to the host. Any version-compatible components that are already installed are not available on the selection page of the installer. For example, you have installed Access Manager and its required components. In a later installation session you decide to install Portal Server. The installed instance of Access Manager is the correct Java ES version, and so is used to meet the Portal Server dependency on Access Manager. You are not asked to install Access Manager again.

Note –

When adding components to a host where a Java ES installation has already been done, you will need to specify the correct paths and passwords if the new component depends on a component that is already installed and configured. If you do not remember the paths or passwords, refer to the Installation Summary for the original installation before you add any components to the host. Default installation directories and ports are listed in the Chapter 2, Default Installation Directories and Ports, in Sun Java Enterprise System 5 Installation Reference for UNIX.

Q32: How do I start using the Java ES components after installation?

Answer: After you have installed and verified the Java ES components, you can refer to the documentation for a particular Java ES 5 component. If you are a new user, look for introductory or getting started material for the product component. This information is often in a document called technical overview.

Q33: If I did an evaluation installation, can I reconfigure the evaluation installation to create a production environment?

Answer: No, reconfiguring your evaluation installation does not usually result in a viable production deployment. Instead, do the following:

  1. Remove your evaluation installation of Java ES using the uninstaller. See Chapter 8, Uninstalling, in Sun Java Enterprise System 5 Installation Guide for UNIX.

  2. Examine the product registry to verify that all of the Java ES files from the previous release have been removed. See Q40: What is the product registry and why should I care about it?

  3. Examine your host files to verify that no Java ES packages are present.

  4. Install your production deployment on multiple hosts based on your formal deployment and installation plans. See Q6: How much planning do I need to do before I install Java ES?

Running the Uninstaller

This section contains questions about running the Java ES uninstaller.

Q34: Where can I find the uninstaller?

Answer: When you expand the Java ES distribution bundle, you will not find the uninstall utility because it does not yet exist on your host. During installation, the Java ES installer places the uninstaller in the following location:

If you do not see the uninstaller at this location, two possibilities exist:

Before performing an uninstallation, you must understand component uninstallation behavior. See Reviewing Uninstallation Behavior for Java ES Product Components in Sun Java Enterprise System 5 Installation Guide for UNIX. Not all product components behave in the same way during uninstallation.

To perform uninstallation, see Chapter 8, Uninstalling, in Sun Java Enterprise System 5 Installation Guide for UNIX.

Tip –

To run the uninstaller without uninstalling any software, use the uninstall -no command. The -no option is useful for familiarizing yourself with the uninstaller or for creating a state file for a subsequent silent uninstallation.

Q35: What can be uninstalled with the Java ES uninstaller?

Answer: The Java ES uninstaller removes only product components that were installed by the Java ES installer. You must use the version of the uninstaller that was placed on your host during initial Java ES installation.

You cannot use the uninstaller to remove shared components. When you install a new version of Java ES, the shared components are automatically upgraded to correct versions by the installer. If you need to manually uninstall shared components, refer to the Sun Java Enterprise System 5 Upgrade Guide for UNIX.

You cannot use the uninstaller to remove Sun Cluster software unless the Sun Cluster software has never been configured.

To remove components that were not installed by the Java ES installer, follow instructions in the documentation for that component.

Before uninstalling, you must be familiar with the following information in the product documentation:

Q36: How do I know if my Java ES uninstallation succeeded?

Answer: One way to determine if the uninstallation succeeded is to compare the packages listed in the installation log with the packages listed in the uninstallation log. You can also check the product registry to verify that Java ES components have been removed. See Q40: What is the product registry and why should I care about it?

In some cases, the uninstaller does not remove all of the packages or directories. You might not discover this situation until you try to do a new Java ES installation. If this occurs, check the appropriate troubleshooting write ups for guidance on removing files or components that are left behind. See Resolving Uninstallation Problems in Sun Java Enterprise System 5 Installation Guide for UNIX.

Troubleshooting Java ES Installation Problems

This section contains questions about troubleshooting problems with Java ES installation or uninstallation.

Q37: What do I do if I have trouble during installation?

Answer: When troubleshooting, try to identify the first problem you encountered. The first problem often leads to subsequent problems, so solving the first problem could resolve other problems. The general process for troubleshooting Java ES installation includes the following activities:

  1. Examine the logs to see if errors exist that indicate what is wrong. See Q38: What logs are available and how will they help me?

  2. Verify that you met all of the installation prerequisites for the components you installed. See Verifying Installation Prerequisites in Sun Java Enterprise System 5 Installation Guide for UNIX.

  3. Check to see if your resources fulfill Java ES system requirements. See System Requirements in Sun Java Enterprise System 5 Installation Guide for UNIX.

    • Adequate disk space

    • Adequate memory

    • Correct patches applied

    • Correct ports specified

    • Correct IP addresses specified

  4. Check the media for dirt or damage.

  5. Verify that you have installed correctly with regard to the interdependencies of the Java ES components you installed. See Q12: Are there component interdependencies that I need to know about?

  6. Verify that you have configured the Java ES components correctly according to the postinstallation configuration instructions. See Chapter 6, Completing Postinstallation Configuration, in Sun Java Enterprise System 5 Installation Guide for UNIX.

  7. Check your Directory Server connectivity.

  8. Verify that the Java ES packages that should be installed are installed. See Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX.

  9. Verify that the passwords you are using are correct.

    Note –

    In the Java ES installer, neither white space nor the following symbols can be used in administrator passwords: ; & ( ) ! | < > ' ? $ ^ \ # / , @ %

For additional material on these activities, see How to Troubleshoot Problems in Sun Java Enterprise System 5 Installation Guide for UNIX.

Q38: What logs are available and how will they help me?

Answer: Information on all installation events is captured in the installation logs described in Examining Installation Log Files in Sun Java Enterprise System 5 Installation Guide for UNIX. Always start any troubleshooting by scanning the log events to see what errors occurred. The logs usually give you an idea of what to do next. Two types of tracking files are available after Java ES installation:

The graphical Log Viewer is a utility that can be used to view Unified Logging Format (ULF) messages from the Java ES installation log. See Using the Log Viewer in Sun Java Enterprise System 5 Installation Guide for UNIX.

Links to the installation logs and summary are on the last page of the installer. Log files are located here:

If a problem occurs when starting a particular component, examine the troubleshooting tips tables to find the location of log files for the individual Java ES components. See Product Component Troubleshooting Tips in Sun Java Enterprise System 5 Installation Guide for UNIX.

Q39: What are the known Java ES installation issues?

Answer: Known issues (bugs) are problems in the Java ES software or documentation. Some of these issues might impact installation. You should be aware of all known installation issues before doing an installation. Known issues are discussed in the following Java ES release notes:

Q40: What is the product registry and why should I care about it?

Answer: The product registry is a repository where all packages are registered when they are installed. The registry contains information such as installation location, product version, and component dependencies. All installed packages have entries in the product registry. The Solaris product registry provides a graphical interface.

Note –

Before installation, make a copy of your product registry so that you can restore it if installation fails. The product registry is located here:

When packages are removed by the uninstaller or the package remove commands (Solaris pkgrm, Linux rpm -e, or HP-UX swremove), those package entries are deleted from the product registry. However, you might encounter a situation where your product registry has not been fully updated. This situation causes a subsequent installation to fail because those components are still considered to be on the host (they are still in the product registry). In this case, update the product registry to correctly reflect the packages that are actually installed on your host.

In rare cases, the installer allows installation to proceed but only installs and registers some of the packages. You might not discover this fact until you try to start the components. In this case, run the uninstaller allowing it to update the registry. If the registry is still not correct after uninstalling the Java ES components, the registry might be corrupted. In this case, restore the original product registry and perform a new Java ES installation.

Q41: What troubleshooting topics are addressed in the Java ES Installation Guide?

Answer: The following topics are addressed in the Chapter 9, Troubleshooting, in Sun Java Enterprise System 5 Installation Guide for UNIX:

Q42: If I made a mistake and want to erase everything and start over, what do I do?

Answer: You can cancel an installation up to the point where the installer has begun copying the software to the host. If you have gone past the point where you can cancel the installation, you need to complete the installation, and then run the uninstaller. The high-level steps for this process are as follows:

  1. Complete the installation, even if it is wrong. You need the uninstaller, which is not available until the installation is complete.

  2. Run the uninstaller and uninstall everything. The uninstaller will also uninstall itself. See Chapter 8, Uninstalling, in Sun Java Enterprise System 5 Installation Guide for UNIX.

  3. Examine the product registry to see what is recognized on the host. The Java ES components should be removed. See Q40: What is the product registry and why should I care about it?

  4. Check to see if any Java ES directories or packages are present. See Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX. If any packages are present, remove them manually using the UNIX remove commands:

    • Solaris OS: pkgrm

    • Linux: rpm -e

    • HP-UX: swremove

  5. Recheck the product registry to verify that any Java ES components you removed are no longer present.

  6. Start a new installation.

Note –

If you cannot resolve issues that are preventing a new installation, you might have to reinstall the operating system on the host. Be sure to back up any important data before reinstalling the operating system.

Q43: What packages are installed for Java ES 5?

Answer: The Java ES packages are listed here:

See Also

Default Installation Directories in Sun Java Enterprise System 5 Installation Reference for UNIX

Q44: Where do I get troubleshooting information for individual components?

Answer: The Java ES documentation contains various troubleshooting tools and tips for the product components. See Product Component Troubleshooting Tips in Sun Java Enterprise System 5 Installation Guide for UNIX. In addition, the Java ES Troubleshooting task page contains links to more specific troubleshooting solutions for the product components. See the Troubleshooting page.