Skip to Content Java Solaris Communities Partners My Sun Sun Store United States Worldwide

Sun Java Enterprise System 2005Q4 Frequently Asked Questions
Installation and Uninstallation FAQs (UNIX Platforms)

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 is complicated and requires more preinstallation and postinstallation effort than is required for simpler installations. This document contains some of the most frequently asked questions (FAQs) about the Java ES installation process.

Learning About Java ES Installation

Q: How should I start?

A:  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 entire process and have a working installation plan.
  1. Read about how the installer works.
  2. View the Java ES installer tutorial.
  3. Take the online training course, Sun Java Enterprise System Installation and Getting Started (WMO-ECR-2389).
  4. Review the installation planning material and create an installation plan.
  5. See if any of the installation sequence examples apply to your installation.
  6. Review the known issues for installation in the Sun Java Enterprise System 2005Q4 Release Notes.
  7. Perform an evaluation installation on a single host.
  8. Plan your production installation by referring to the following:

Q: Is there an installation tutorial or demo available?

A: Yes, a free tutorial is available for the installer on the UNIX platform. In approximately 15 minutes, you walk through the pages of the installer, learn how the installer process works, and gain some insight into what you need to consider before you begin your installation. View this tutorial by clicking here.

See Also An online training course is available: Sun Java Enterprise System Installation and Getting Started (WMO-ECR-2389).

Q: How can I find the Java ES documentation?

A: The Java ES 2005Q4 documentation s stored in the docs.sun repository as follows:
  • Java ES collection provides links to the manuals associated with the system-level Java ES tasks, including installation. You can view these manuals in either HTML or PDF format.
  • Java ES installation documentation center provides links to the information used to run the Java ES installer.
  • Java Enterprise System complete collection provides the HTML and PDF versions of the product documentation for the Java ES products that are installed by the Java ES installer. In this listing you will also find links to specialized collections, such as component Release Notes Collection, Technical Notes and Deployment Examples Collection, HP-UX documentation, and so on.
  • The Sun Java System suites collections provides links to the product documentation for the components included in the suites.

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

A: Click to see a list of the individual components for the 2005Q4 release of Java ES. Java ES components are combined into different suites that provide particular sets of services. For information on the Sun Java System suites, see the following:

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

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

On UNIX, the process is not so quick. However, two documents exist that provide instructions for creating a single-host evaluation deployment using the installer on UNIX platforms:
Tip Doing an evaluation installation on a single host is a good way to learn about the installer.

Preparing to Install Java ES Software

Q: How much planning do I need to do before installation?

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

However, for a production deployment across multiple hosts, the following planning activities are important for a successful installation:
  1. Work from 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 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 deployment planning guides for specific Java ES components.
  2. Create an installation plan. Using this plan, you can determine the sequence of events for installing on each host in your deployment. Refer to instructions for creating an installation plan in the Sun Java Enterprise System Installation Planning Guide.
  3. Survey your hosts. By knowing what is already on your hosts, you can take steps to bring them to the optimum state before installation, which might include upgrading or removing some installed components. Refer to the instructions for upgrading in the Sun Java Enterprise System Upgrade Guide.
  4. Determine your configuration values.  Some components can be configured during installation, so you must determine the configuration values that you will supply during installation.
  5. Select an example installation sequence (if applicable). If any of the installation sequence examples can be applied to your deployment, adjust your installation plan as needed.
  6. Plan the deployment tasks needed, for example:
    • Single sign-on: This type of configuration is done after all post-installation configuration is complete. Example instructions on how to implement single sign-on for your components are contained in the evaluation deployment example. You will need to substitute your configuration specifics in these example single sign-on instructions.
    • Redundancy: Most production deployments include some type of redundancy requirement, either to increase throughput or to protect against downtime or data loss. Three strategies are available for using redundant instances of Java ES components:
These strategies are discussed in the Installation Planning Issues section of the Sun Java Enterprise System Installation Planning Guide (see the Redundancy Strategies section). Additional material is contained in availability strategies in the Sun Java Enterprise System Deployment Planning Guide.
            • User management: This type of configuration is done after all postinstallation configuration is complete. Example instructions on how to implement user management for your components is contained in the evaluation deployment example. You will need to substitute your configuration specifics in these example user management instructions. You will also need to plan your schema. More extensive schema instructions are contained in the Directory Server documentation.

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

A: Yes, a collection of installation sequence examples can help you understand the task order for common installations. These are not full procedures, but instead provide the high-level sequence in which you should install, configure, and start the components in the examples.

There are also complete deployment examples that provide detailed procedures for specific deployments:

Q: What are the system requirements for installation?

A: 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:
In addition, a number of situations exist that might require additional tasks for your combination of components. Be sure that installation prerequisites are met before starting your installation.

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

A: Yes, if those components are incompatible with the release of Java ES you are going to install. An initial Java ES installation goes most smoothly if you are installing on a computer that has only the operating system installed. 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 components on the host. In this case, the installer cannot proceed until you either remove or upgrade these components to supported versions for Java ES 2005Q4.

Exception: If your host contains incompatible Java ES components that were installed when the Solaris operating system was installed (Application Server or Message Queue), the installer asks if you want the installer to remove them. If you select Yes, those components are removed and correct versions are installed when the Java ES software is installed on the host.
  • Upgrading Components  Although the Java ES installer can upgrade shared components, the installer cannot upgrade selectable components. Full instructions for upgrading are in the Sun Java Enterprise System Upgrade Guide.
  • Removing Components  For components that were installed using the Java ES installer, you should remove them using the Java ES uninstaller. If no uninstaller is present, then the components were probably installed by another method. You can remove the packages for the components using the UNIX package remove commands:
  • pkgrm  (Solaris OS)
  • rpm -e (Linux)
  • swremove (HP-UX)

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

A: One way to identify what Java ES components are on the host is perform a dry-run installation using the installer -no command. When you select components at the Component Selection page, the installer will indicate what incompatible components are on the host. Refer to  instructions for identifying incompatible components for guidelines on surveying your hosts before doing an installation.

Another way to survey the software on a host is to refer to the product registry. You can also examine the installed packages using the UNIX package display commands to see if any Java ES component packages are present:
  • pkginfo (Solaris OS)
  • rpm -qa (Linux)
  • swlist (HP-UX)

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

A: The Java ES installer cannot upgrade from one version of Java ES to another. Full instructions for upgrading are in the Sun Java Enterprise System Upgrade Guide.

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

A: Due to the dependencies between the components, the Java ES installer does extensive dependency checking. If your selected components require additional components, the installer automatically selects the additional components. Installation sessions must be run in particular sequences, with some components being installed, configured, and even started before other components are installed. To understand how this works, refer to the information in the Component Dependencies section where Table 3-1 shows the interdependency matrix.

After installation, you must follow the correct startup sequence for Java ES components so the components function correctly together.

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

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

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

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

At least two installation sessions are performed on each node in the cluster. 

Refer to the Sun Cluster Installation Sequence Example to see the high-level installation guidelines. To complete your installation, refer to instructions for Sun Cluster postinstallation configuration.

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

A: Java ES solutions that use Directory Server can use either of two versions of a standard LDAP schema: Schema 1 or Schema 2.  A full explanation of the schema issues for Java ES is contained in the user management section of the Sun Java Enterprise System Installation Planning Guide. Refer to the Access Manager product documentation for more specific information on Access Manager schema.

 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 uses Access Manager, you must use Schema 2.

Running the Installer and Uninstaller

Q: How do I get the Java ES software? How do I put the software in a shared location?

A:  Java ES software is available on CD or DVD, as a download, or preloaded on your Sun system. See instructions for getting the software.

After you expand the distribution bundle, you can put the software in a shared location for others to access by following the instructions for creating an installation image on your network.

Q: How do I run the Java ES installer?

A: 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 (state file). The Java ES product documentation contains syntax and examples for using the installer and uninstall commands.
  • Interactive installation
    • Graphical mode provides an interactive wizard that leads you through the process of installing the Java ES software on a graphical workstation.  The Installer Tutorial provides a walkthrough of the graphical installer. To run the graphical installer:  

    • Text-based mode provides the same functionality as graphical mode, but you are prompted for responses on a line-by-line basis in a terminal window. To run the text-based installer:  
      ./installer -nodisplay
  • Script-based silent installation
Silent mode is a non-interactive method used for installing Java ES on multiple hosts that share similar configurations. This process allows you to propagate one configuration across multiple hosts in your enterprise.
  1. You first perform an interactive installation where your responses to the installer are captured as a set of name-value pairs in a state file. This could be either a dry-run installation where no software is installed, or an active installation.
  2. You edit the state file for host specifics, then run the installer on other hosts using the state file as input. 

Tip A way to practice with the installer is to use the following command which runs the graphical installer but does not install software:
./installer -no

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

A: Yes and no, depending on the type of component you want to upgrade.
  • Selectable components cannot be upgraded by the installer.
These are the product components that you are allowed to select in the Java ES installer. If the installer detects incompatible versions of selectable Java ES components on the host, you must remove or upgrade these components before installation can proceed. The installer cannot upgrade the selectable components.
Exception: If your host contains incompatible Java ES components that were installed when the Solaris operating system was installed (Application Server or Message Queue), the installer asks if you want the installer to remove them. If you select Yes, those components are removed and correct versions are installed when the Java ES software is installed on the host.
  • Shared components can be upgraded by the installer.
These components support the selectable components and are selected automatically by the installer. If some shared components are already on the host but the versions do not match the Java ES release requirements, the installer indicates which shared components need to be upgraded. If you allow the installer to proceed, the shared components listed are upgraded to the correct versions when the Java ES software is installed on the host.
The Java ES installer cannot upgrade from one version of Java ES to another. Full instructions for this type of upgrading are in the Sun Java Enterprise System Upgrade Guide

Q: What is the difference between Configure Now and Configure Later?

A:  The installer gives you the option of performing initial configuration for many of the Java ES components. However, other components can be configured only after the installer has installed the Java ES software. The two types of configuration that you can choose from are Configure Now or Configure Later.
  • Configure Now prompts you to enter the initial configuration values during the installation session. The Configure Now type can only be selected for some components. If you select components for Configure Now that cannot be configured during installation, you are notified that the installer will not configure them.
    • Components that can be configured during installation include Access Manager, Administration Server, Application Server, Directory Server, Directory Proxy Server, HADB, Portal Server, Portal Server Secure Remote Access, Web Server, and Web Proxy Server.
  • Configure Later instructs the installer to copy component software packages to the host. You might be asked to enter a few values that are necessary for copying the packages. The installer proceeds without doing further configuration, and no runnable instances are created. You will create runnable instances after installation by supplying configuration values to component configuration wizards or in configuration files. The Configure Later type can be selected for all components.
    • The components that can only support Configure Now include Calendar Server, Communications Express, Delegated Administrator, Instant Messaging, Messaging Server, Service Registry, and Sun Cluster Software.

The selected configuration type (Configure Now or Configure Later) applies to an entire installation session. Regardless of whether you perform the initial configuration in the installer with Configure Now or independently with Configure Later, some components require postinstallation configuration. See What postinstallation configuration is required? for further instructions.

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

A: You can run a script-based installation by using the silent mode of the installer. Silent mode is a non-interactive method used for installing Java ES software on multiple hosts that share similar configurations. To create the installation script, you first perform an interactive session during which your responses to the installer are captured as a set of name-value pairs in a state file. You edit the state file for host specifics, then use the state file as input to run the installer on other hosts. This process allows you to propagate one configuration across multiple hosts in your enterprise. The product documentation contains detailed instructions for using silent mode. Click to see an example state file.

Q: Does the installer check dependencies on remote components?

A: In general, the installer does dependency and version checking on the local host only . However, one situation exists where the installer does interact 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 process. 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. If the remote component is not available, you receive errors when you try to run any component that depends on that remote component.

To indicate a remote component to the installer, you first 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 prompt 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.

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

A: On Solaris OS and Linux, Access Manager and Portal Server can use the third-party web containers BEA WebLogic Server or IBM WebSphere Application Server. To indicate a third-party web container to the installer, select all of your components except the web container. Do not select Sun Java Application Server or Sun Java Web Server. When you click Next, the installer displays the Web Container Selection page. Select Use Third-Party Web Container.
Tip  Install, configure, and start any third-part web container in your deployment before installing Java ES. For installation, configuration, and startup instructions, refer to the BEA or IBM product documentation.

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

A: When the installer performs a system check, the installer might identify missing patches. The installer cannot proceed until you install the patches, however, you do not need to cancel the installation. Instead, 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 download the patches you need:
  3. In the new terminal window, install the patches.
  4. In the installer, recheck the host.

Q: How do I know if the installation succeeded?

A: 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 installed.

Q: When can I run the uninstaller?

A: When you expand the Java ES distribution bundle, you will not find the uninstall script because it does not yet exist on your host. During installation, the Java ES installer places the uninstaller at the following location:
  • Solaris OS: /var/sadm/prod/SUNWentsys4
  • Linux and HP-UX: /var/sadm/prod/sun-entsys4
If you do not see the uninstaller at this location, there are two possibilities:
  • Java ES software has not been installed on the host.
  • All Java ES software has been uninstalled. (After all Java ES components are uninstalled, the uninstaller removes itself from the host.)
It is especially important to understand component uninstallation behavior before uninstalling. Full instructions for running the uninstaller are contained in the Sun Java Enterprise System Installation Guide.
Tip You can use the uninstaller -no command to run the uninstaller without uninstalling any software. This option is useful for familiarizing yourself with the uninstaller or for creating a state file for a subsequent silent uninstallation.

Q: What can be uninstalled?

A: The Java ES uninstaller removes only selectable components that were installed by the Java ES installer. You cannot use the uninstaller to remove shared components, nor can you 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 need to be familiar with the following information in the product documentation:

Q: How do I know if the uninstallation succeeded?

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.

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 installation. If this occurs, check the troubleshooting information for guidance.

Postinstallation Configuration and Verification

Q: What postinstallation configuration is required?

A:  When the Java ES installer finishes, most components require additional configuration to work together. The extent of this work depends on the configuration type you selected (Configure Now or Configure Later), and whether your components will be configured to operate in a Sun Cluster environment.
  • If you selected Configure Now, the installer prompted you for configuration values for the components being configured. Now, you have very little additional configuration to do on the components you configured. Refer to the following documentation to perform postinstallation configuration: 
  • If you selected Configure Later, the installer placed the component packages in their respective directories, parameter setting was not  done, and most components are not yet operational. Use the component configuration tools and files to complete a Configure Later installation. You can also use these tools to make any additional changes to your configuration. Refer to the following documentation to perform postinstallation configuration:

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

A:  After you have installed the Java ES software and completed all of the postinstallation configuration, follow the Java ES installation verification procedure to verify that your Java ES installation has basic functionality. 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 that you wanted. If the resulting installation does not meet your needs, run the uninstaller to uninstall all of the components, and then perform a new installation.

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

A: You activate Java ES by starting the components one after another, 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 startup sequence is listed in guidelines for starting Java ES. To start the components, refer to instructions for starting and stopping each component.

Installation Troubleshooting

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

A:  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 problems with Java ES installation includes the following activities:
  1. Examine the logs to see if errors exist that indicate what is wrong.
  2. Verify that you met all of the installation prerequisites for the components you are installing.
  3. Check to see if your resources fulfill Java ES system requirements:
      • 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 components you selected.
  6. Verify that you have configured correctly according to the postinstallation configuration instructions.
  7. Check your directory connectivity.
  8. Verify that the passwords you are using are correct.
  9. Verify that the Java ES packages that should be installed are installed.

For additional material on these activities, refer to information in the Java ES Installation Guide.

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

A: Information on all installation events is captured in the installation logs. 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:
  • Installation Summary lists each component installed and the settings you specified. If you chose Configure Now, this summary includes all of the configuration values.
  • Installation Log displays the installer’s log messages.
Links to the installation logs and summary are on the last page of the installer. Log are located here:
  • On Solaris OS: /var/sadm/install/logs
  • On Linux and HP-UX: /var/opt/sun/install/logs
If a problem occurs when starting a component, examine the troubleshooting tips tables to see the location of log files for the component.

Q: What are the known Java ES installation issues?

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

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

A:  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.
Tip Before installation, make a copy of your product registry so that you can restore it if installation fails.
The product registry is located here:
  • On Solaris OS: /var/sadm/install/productregistry
  • On Linux:  /var/opt/sadm/install/productregistry
  • On HP-UX:  /var/adm/sw/productregistry
When packages are removed by the uninstaller or the package remove commands, 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, edit 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, and then edit the registry to reflect what is actually on the host.

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

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

A: 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 doing this process are as follows:
  1. Complete the installation, even if it is wrong because you need the uninstaller, which is installed with the components.
  2. Run the uninstaller and uninstall everything. The uninstaller will also uninstall itself.
  3. Examine the product registry to see what is recognized on the host. The Java ES components should be removed.
  4. Check to see if any Java ES directories or packages are present. If any are present, remove them manually using the UNIX remove commands:
    pkgrm (Solaris OS)
    rpm -e (Linux)
    swremove (HP-UX)
  5. Recheck the product registry.
  6. Start a new installation.
Note  If all else fails and you cannot resolve issues that are blocking a new installation, you might have to reinstall the operating system on the host. Be sure to back up any important data before doing this.

Q: What packages are installed for Java ES 2005Q4?

A:  To see complete listings of the Java ES packages, refer to the following:

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

A:  The Java ES components have various troubleshooting tools and tips in the tables here. In addition, the Troubleshooting Documentation Center contains links to specific troubleshooting information for the components.

What To Do After Installation

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

A: To install additional components, you can run the installer again. The installer detects the installed components and uses them to satisfy the dependencies of other components. Any release-compatible components that are already installed are not available for selection at the Component Selection page. 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 used to meet the Portal Server dependency on Access Manager, and you are not asked to install Access Manager again.

When adding components to a host where a Java ES installation has already been done, be sure to specify the correct paths and passwords if the new component will use 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.

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

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

Q: If I have already done an evaluation installation, can I reconfigure this installation to create a production environment?

A: Reconfiguring your evaluation installation does not usually result in a viable production deployment. It is best to remove your evaluation installation of Java ES using the uninstaller. Verify that all of the Java ES files from the previous release have been removed by examining the product registry. For a final check, examine your host manually to verify that no Java ES packages are present. Then install your production deployment on multiple hosts based on your formal deployment and installation plans.

Contact About Sun News Employment Privacy Terms of Use Trademarks
Part Number 819-6552-10 Copyright 1994-2006 Sun Microsystems, Inc.