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 the Java ES installation process.
Learning About
Java ES Installation
Q1: 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 process and have developed an installation plan.
- Read about how
the installer works.
- View the Java ES installer
tutorial.
- Review the installation
planning material and create an installation plan.
- Determine if any of the installation
sequence examples apply to your installation.
- Review the known issues for installation in the Sun
Java Enterprise System 5 Release Notes for UNIX.
- Perform an evaluation
installation
on a single host.
- Plan your production deployment by referring to the Sun Java Enterprise
System Deployment Planning Guide.
Q2:
Is there
an installation tutorial or demo available?
A:
Yes, a free
Java
ES installer tutorial
is
available on UNIX platforms.
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?
A:
Java ES 5 documentation is
stored in the docs.sun.com
repository as follows:
Q4:
What
components are included in this Java ES release?
A:
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 are the
Java
ES components
that can be selected for installation by the Java ES
installer.
The
Sun Java
Enterprise System Technical
Overview contains brief
descriptions
of the product components.
Shared
components support
the product components and are selected
automatically by the installer.
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
information
on suite downloads).
Q5:
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 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 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:
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
Q6:
How much planning do I need to do before I install Java ES?
A:
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 deployment
planning guides for specific Java ES components.
- 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. Refer to instructions for creating
an installation plan in the Sun Java Enterprise
System 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. Activities might include upgrading
or
removing some installed components. Instructions for
upgrading are contained
in the Sun Java Enterprise
System
Upgrade Guide.
- 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.
- 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. You
substitute your configuration specifics in
these example single
sign-on instructions.
- Redundancy
Most production deployments include a redundancy requirement,
such as load balancing, clustering, or
multimaster replication. These methods are helpful to increase
throughput or to protect
against downtime or data
loss. Java ES redundancy strategies are
discussed in the Installation
Planning Issues section of the Sun
Java Enterprise System Installation Planning Guide. Additional
material is contained in availability
strategies in the Sun Java
Enterprise System Deployment Planning Guide, including Clustering
with 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
is contained in the evaluation deployment example. You substitute your
configuration specifics in
these example user
management instructions. You must plan
your schema. For extensive schema instructions, see the Directory
Server documentation.
Q7:
Are there
examples that I can use to plan my installation?
A:
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, refer to the installation
sequence examples. These examples
list the
high-level tasks for installing, configuring, and starting
the
components in the examples.
- A view into Sun using Java ES is
provided in the SunWeb
4.0
Technical Case Study.
Q8: 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:
Operating system patches might be
missing from your host, in which case the installer will not be able to
proceed. Refer to
information
on what to do about missing patches.
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 the
Sun
Java Enterprise System
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.
Q9: Does it
matter if other Java ES components are already on my host?
A:
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.
- Upgrading product
components Generally, the installer
cannot upgrade
the selectable 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 uninstaller
utility
that was
put in in place during the original installation. 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 using the following UNIX package remove commands:
- Solaris OS: pkgrm
- Linux: rpm -e
- HP-UX: swremove
Q10:
How can I find out which Java ES components are installed on my host?
A:
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 surveying your hosts before doing an
installation, refer to
instructions
for identifying incompatible components.
Another way to survey the software on a host is to examine the
product
registry.
You can also view the installed packages
using the following UNIX package display commands to see if any
Java
ES component packages are present:
- Solaris OS: pkginfo
- Linux: rpm -qa
- HP-UX: swlist
Q11:
How do I upgrade from another version of Java ES?
Q12:
Are there component interdependencies that I need to know about?
A:
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 the
Component
Dependencies section, where 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.
After installation, you must follow the
preferred
startup
sequence for Java ES components described in Table 7-1 to ensure
that the
components
function
correctly together.
Q13:
What do I
need to know about Solaris 10 zones for Java ES?
Q14:
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. 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.
Q15:
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. More extensive schema instructions
are contained
in the
Directory
Server schema information and the
Access
Manager schema information.
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.
Getting the Java ES
Software
Q16:
How do I get
the Java ES software?
Q17. What
download media is available?
A:
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:
- At the main Sun page,
click the Downloads tab.
- Under Enterprise Computing, click Java Enterprise System.
- In the Java ES table, click Download.
- Scroll down to the software list and put a checkmark in the
box next to Java Enterprise System.
- Scroll to the bottom of the page and click Get Downloads
& Media.
- Click the link called Multiplatform.
- After you register and accept the license agreement, scroll
the Downloads page to select the download you want.
- Click the link called Download selected with Sun Download
Manager.
The following platform downloads are available:
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
Java ES 5 components. |
| 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. |
Note
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:
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 a
subset of the Java ES 5 components. |
Q18: How do
I put the software in a shared location?
Q19.
What is in the Java ES 5 media distribution kit?
A:
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:
- DVD 1: Java ES 5 Integrated Installers, all platforms
- DVD 2: Java ES 5 Supplemental Software, all platforms
- Application Server EE 8.2 zip distribution
- Directory Server EE 6.0 zip distribution
- iWay Adapters 5.5
- CD 3: Identity Manager 7.0
- DVD 4, 5: All Access Tools---developer tools
- DVD 6-10: Java Composite Application Suite (CAPS)
5.1.2
- DVD 11: Java Availability Suite---Sun Cluster 3.1 8/05
and
Sun Cluster Geographic Edition 2006Q4
Running the
Installer
Q20: 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 called a
state
file. The Java ES product
documentation contains
syntax
and examples
for using the installation commands.
- Graphical mode This interactive
mode provides
a wizard that leads you through the process of
installing Java ES software
on a graphical workstation. Instructions
for using the graphical installer are in the Sun
Java Enterprise System Installation Guide for UNIX. The installer tutorial
provides a walkthrough of the graphical
installer.
To run
the graphical installer, type the following at the command
line:
./installer
- Text-based mode This interactive
mode provides
the same functionality as graphical mode, but you are prompted
for responses
on a line-by-line basis in a terminal window. Instructions
for using the text-based installer are in the Sun Java Enterprise System Installation
Guide for UNIX.
To run
the text-based installer, type the following at the command
line:
./installer
-nodisplay
- Silent mode
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 as well as an example
state file.
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. A description of how
Java ES Reporter works is contained in the Sun Java Enterprise System 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?
A:
Yes and no, depending on
the type of component you want to upgrade. For a brief
description of the Java ES components, click
here.
- Product components
In general, product components cannot be upgraded by the installer. If
the
installer detects incompatible
versions of product components on the host, you must remove
or upgrade these components before installation can proceed.
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.
Q22:
What is
the difference between the Configure Now and Configure Later
configuration types?
A:
The installer
gives you the option of performing initial
configuration for many of the Java ES components during
installation.
- Configure
Now
This configuration
type
prompts you to enter
the
initial configuration
values during the installation session. Configure Now can be selected
for only some components. If you select components for
Configure
Now that cannot be configured during installation, the installer
indicates that it will not configure them. You
will configure them after installation.
Components
that can be configured during installation include Access Manager,
Application Server, Directory Server, Directory
Proxy Server, HADB, Portal Server, Portal Server Secure Remote Access,
Web Server, and Web Proxy Server.
Components that cannot be configured during installation include
Java DB, Monitoring Console, Service Registry, and Sun
Cluster software.
- Configure
Later
This
configuration type 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 create runnable instances after installation by
supplying
configuration values when prompted by component configuration wizards
or
in configuration files. You can select Configure Later for
all components.
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 (Configure Later), there is usually some additional
postinstallation configuration required. See
What postinstallation
configuration is required? for further information.
Q23:
How can I
reproduce the same installation on another host?
Q24:
Does the
installer check dependencies on remote components?
A:
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?
A:
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 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?
A:
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
information on patch clusters.
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:
- Exit the installer.
- In a browser, go to the patch site for your operating
system and find the patch you need:
- Download the patch to the
local host.
- Bring the host to single user
mode.
- Apply the patch.
- Reboot the host.
- Restart the the installer.
For
a Non-Kernel Patch
For required patches that are not kernel-related, do the
following:
- Leave the installer running and open a separate
terminal window.
- In a browser, go to the patch site for your operating
system and find the patch you need:
- Download the patch to the
local host.
- In the new terminal window, apply the patch.
- Tell the installer to recheck the host and continue with
installation.
Q27: How
do I know if my Java ES installation succeeded?
Performing
Postinstallation
Configuration and
Verification
Q28:
What postinstallation configuration is required?
A:
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.
The Java ES
postinstallation
configuration instructions apply to product components that
require postinstallation
configuration. (If components are not included in this listing,
postinstallation configuration is not required.)
- Configure Now or Configure
Later configuration type
- If you selected Configure
Now, the installer prompted you
for
configuration values for the components being configured. Very
little additional
configuration is required for the components you configured, but there
might be some.
- 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. In most
cases, you will use the component
configuration tools and
files to complete
a Configure
Later installation.
- Sun Cluster software
Sun Cluster configurations are supported only on
Solaris OS, using the Configure Later configuration type. If you
installed Sun Cluster software, you need to perform Sun
Cluster postinstallation configuration. The Sun
Cluster installation sequence example might help you understand the
high-level tasks.
- Monitoring Console To
perform monitoring, you must enable and sometimes
configure the monitoring service with each component you have
installed. For instructions, see Monitoring
Console configuration in the Sun
Java Enterprise
System Monitoring Guide.
You can see the basic installation tasks in the Monitoring
Console installation sequence example.
- Man pages
If the product components you installed have man pages, MANPATH
setup applies. Table 6-1 lists the Java ES components that have man
pages.
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?
A:
After you complete postinstallation
configuration, follow the
postinstallation
verification procedure to verify that your Java ES
components have 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 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?
A:
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 listed in
guidelines
for verifying Java ES after postinstallation configuration, Table
7-1. To stop Java ES, stop the components in the reverse order. To
start the components, refer to the individual instructions for
starting
and stopping each component.
What To
Do
After Installation
Q31: How do I
install more components on a host after I've
already done an installation?
A:
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
Sun Java
Enterprise System Installation Reference for UNIX
Q32:
How do I
start using the Java ES components after
installation?
A:
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?
A:
No, reconfiguring your
evaluation installation does not usually result in a
viable production deployment.
Instead, do the following:
- Remove your evaluation
installation of Java ES using the
uninstaller.
- Examine the product
registry to verify that all
of
the
Java ES files from the previous release have been removed.
- Examine your host files to
verify that no Java ES packages are present.
- Install your
production deployment on multiple hosts based on your formal deployment
and installation
plans.
Running the
Uninstaller
Q34:
Where
can I find
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/SUNWentsys5
- Linux and HP-UX: /var/sadm/prod/sun-entsys5
If you do not see the uninstaller
at this location, two
possibilities exist:
- Java ES
software has not been installed on the host.
- All Java ES
software has been
uninstalled. (After all product components are
uninstalled, the uninstaller removes itself from the host.)
Tip
To run the uninstaller
without uninstalling any software, use the uninstaller
-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?
A:
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 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?
A:
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 Java ES
installation. If
this occurs, check the appropriate
troubleshooting write
ups for guidance on removing files or components that are left
behind.
Troubleshooting Java ES Installation Problems
Q37: 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:
- Examine
the logs to see if errors
exist that indicate what is
wrong.
- Verify that you met all of the installation
prerequisites for the components you installed.
- 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
- Check the media for dirt or damage.
- Verify that you have installed correctly with regard
to the interdependencies
of the Java ES components you installed.
- Verify that you have configured the Java ES components
correctly according
to the postinstallation
configuration instructions.
- Check your Directory Server connectivity.
- Verify that the Java
ES packages that should be installed are installed.
- 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:
; & ( ) ! |
<
> ' “ $ ^ \ # / , @ %
Q38: 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 The
installation summary lists
each component
installed and the settings you specified. If you chose Configure
Now, this
summary includes all of the configuration values except passwords.
- Installation log Installation
logs display
the installer’s
log messages. The JavaES_Install_log.timestamp is one of the most
critical logs to examine in the event of a configuration issue. This
log contains the output of the configuration tools for each product
component
that was installed in a Configure Now 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.
Links to the installation
logs and summary are on the last page
of the installer. Log files are located here:
- Solaris OS: /var/sadm/install/logs
- Linux and HP-UX: /var/opt/sun/install/logs
Q39: 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:
Q40: 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.
Important
Before installation, make a
copy
of your product
registry so that you can restore it if installation fails.
The product registry is located
here:
- Solaris OS:
/var/sadm/install/productregistry
- Linux: /var/opt/sun/install/productregistry
- HP-UX: /var/adm/sw/productregistry
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?
A:
See the
following topics in the Sun Java
Enterprise System Installation Guide for UNIX for solutions to
some
common problems:
Q42:
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 this process are as follows:
- Complete the
installation,
even if it is wrong. You
need the uninstaller,
which is
not available until the installation is complete.
- Run the uninstaller and
uninstall everything. The uninstaller will also uninstall itself.
- Examine the product
registry to see what is recognized on the host. The
Java ES components should be removed.
- Check to see if
any Java ES directories or packages are
present. If any packages are
present,
remove them
manually using the UNIX remove commands:
-
Solaris
OS: pkgrm
- Linux:
rpm
-e
- HP-UX: swremove
- Recheck the
product registry to verify that any Java ES components you removed are
no longer present.
- 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?
A:
The Java ES packages are listed in the Sun Java Enterprise System Installation
Reference for UNIX:
Q44: Where do I
get troubleshooting information for individual
components?
