Sun Java Enterprise System 2003Q4 Release Notes

These release notes contain important information available at the time of release of Sun Java^™ Enterprise System 2003Q4. Known limitations and problems, technical notes, and other information are addressed here. Read this document before you begin using Java Enterprise System 2003Q4.

The most up-to-date version of these release notes can be found at the Java Enterprise System documentation web site: http://docs.sun.com/prod/entsys.03q4. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals.

All other component product-specific information appears in the respective component product release notes.


Component Product	Link to Release Notes
Sun ONE Directory Proxy Server 5.2	http://docs.sun.com/doc/816-6392-10
Sun ONE Directory Server 5.2	http://docs.sun.com/doc/816-6703-10
Sun ONE Identity Server 6.1	http://docs.sun.com/doc/816-6779-10
Sun ONE Calendar Server 6.0	http://docs.sun.com/doc/816-6715-10
Sun ONE Web Server 6.1	http://docs.sun.com/doc/817-1828-10
Sun ONE Messaging Server 6.0	http://docs.sun.com/doc/816-6736-10
Sun ONE Portal Server 6.2	http://docs.sun.com/doc/816-6746-10
Sun ONE Application Server 7 Update 1	http://docs.sun.com/doc/817-2164-10
Sun ONE Message Queue 3.0.1 Service Pack 2	http://docs.sun.com/doc/817-3731-10
Sun ONE Instant Messaging 6.1	http://docs.sun.com/doc/817-4112-10
Sun Cluster 3.1 and Agents	http://docs.sun.com/doc/816-5317

Release Notes Revision History

Table 1 Revision History
Date	Description of Changes
June 10, 2004	New instructions on upgrading J2SE for Solaris 9
April 8, 2004	2003Q4 revenue release, final revision. Added issues 5004406 and 5016000 with workarounds.
February 11, 2004	2003Q4 revenue release, revision 2. Corrects some workarounds; removes fixed bugs
December 18, 2003	2003Q4 revenue release, revision 1. Includes two additional required patches; amended workaround for 4958324
December 11, 2003	2003Q4 revenue release
September 29, 2003	Sun Java Enterprise System 2003Q4 initial release SPARC

General Software and Hardware Requirements

The following software and hardware required for this release of Java Enterprise System.

Table 2 Hardware and Software Requirements
Component	Solaris Requirement
Operating environment	Solaris 8 SPARC^� Platform Edition with patches required for Java Enterprise System (Sun Cluster 3.1 Release 05/03 has been qualified to run on Solaris 8 02/02 and Solaris 8 HW 05/03 (PSR 2)) Solaris 9 SPARC^� Platform Edition Solaris 9 x86 Platform Edition
RAM	2.5 GB recommended
Disk space	5 GB in addition to operating system requirements, with a minimum of 700 MB in the root partition (if you are installing there), and 250 MB for /var

Table 3 Component Product Disk Installation Space and RAM Requirements
Component	Minimum Disk Space and RAM Requirements for Installation
Messaging Server	1 GB for production deployment or 500 MB for evaluation installation; 256 MB RAM for production systems or 128 RAM for evaluation installation Adequate space for message store, database configuration directory, log files, depending upon your site size
Message Queue	8 MB of disk space; 128 MB RAM
Instant Messaging	300 MB of disk space; 256 MB RAM
Directory Server	3 GB of disk space for production deployment (with 10,000 to 250,00 entries) or 200 MB of disk space for an evaluation; 256 MB RAM
Web Server	256 MB of disk space; 64 MB RAM
Application Server	with Sun ONE Studio: 500 MB of disk space; 512 MB RAM
Portal Server, Portal Server SRA	1 GB of disk space; 1.2 GB RAM for production deployment or 512 MB for an evaluation
Calendar Server	1 GB of disk space for production deployment or 500 MB for an evaluation; 256 MB to 1 GB of RAM for production or 128 MB RAM for an evaluation
Sun Cluster (per node)	512 MB of disk space for swap space and 20 MB for Volume Manager; 128 MB RAM plus ten percent of a node’s regular requirement

Solaris Software Group Requirements

Installation of the Java Enterprise System requires at least the Solaris End User System Support software group. In addition to the End User System Support software group, you must ensure that the following software components are installed on your system:

Zip Compression Library The Zip Compression Library packages, SUNWzlib and SUNWzlibx, must be installed on your system. Since the SUNWzlib packages are not part of the End User software group on Solaris 8, you may have to manually add these packages to your Solaris 8 system. You can find these packages on the Solaris 8 media.

Perl Programming Language The Perl programming language packages, SUNWpl5u for Solaris 8 and SUNWpl5u and SUNWpl5v on Solaris 9, must be installed on your system. Since early releases of Solaris 8 did not include SUNWpl5u in the End User software group, you may have to manually add this package to your system. You can find the Perl packages on the Solaris media.

Java 2 Standard Edition Requirements

Java Enterprise System 2003Q4 is certified with Java 2 Standard Edition (J2SE) 1.4.1_06 from Sun Microsystems. Subsequent releases of Java 2 Standard Edition 1.4.x are expected to function properly with the Java Enterprise System, but have not yet been certified with Java Enterprise System 2003Q4.

Java Enterprise System 2003Q4 includes the appropriate version of J2SE. The Java Enterprise System installation program is capable of either upgrading an existing, package-based installations of J2SE 1.3.x and 1.4.x or installing an additional instance of the J2SE packages. Refer to the Java Enterprise System Installation Guide at http://docs.sun.com/doc/816-6874 for details on J2SE installation and upgrade options.

If your system already has J2SE 1.4.1_06 runtime environment package SUNWj3rt, installed without the J2SE 1.4.1_06 development tools package, SUNWj3dev, install the development tools package prior to installing the Java Enterprise System. This package contains several facilities required by the Java Enterprise System. See the Java Enterprise System Installation Guide at http://docs.sun.com/doc/816-6874 for details on how to determine the version of J2SE installed on your system and how to prepare your system prior to installing Java Enterprise System.

Sun ONE Portal Server and Sun ONE Identity Server support J2SE 1.3.x only when these component products are deployed to IBM WebSphere Application Server and BEA WebLogic Server. Refer to the Sun ONE Portal Server and Sun ONE Identity Server documentation for details on J2SE 1.3.x support with these application servers.

Applying a Solaris 9 Update After Java Enterprise System Is Installed

After applying a Solaris 9 update to a system where Java Enterprise System is already installed, you need to check that the Java Enterprise System installation of Java 2 Standard Edition (J2SE) is still complete and of the appropriate version. You need to:

Gather information about the J2SE installation used by Java Enterprise System

Inspect the symbolic link /usr/jdk/entsys-j2se to determine the location of the J2SE installation used by Java Enterprise System:

ls -l /usr/jdk/entsys-j2se

Note down the location the link points to; /usr or /usr/jdk/.j2se1.4.1_06 for example.

Determine the version of the J2SE installation used by Java Enterprise System:

location/j2se/bin/java -fullversion

where location is the location you noted down in Step 2; /usr for example.

Note down the version number.

Use the pkginfo command to gather information about the instances of each J2SE package required by Java Enterprise System. These packages are:

SUNWj3dev     SUNWj3man     SUNWj3rtx
SUNWj3dvx     SUNWj3jmp
SUNWj3dmo     SUNWj3rt



Note	The packages SUNWj3dvx and SUNWj3rtx are required only for 64-bit support, and the package SUNWj3jmp is required only for Japanese man page support.

For each of the required packages, perform these steps:

Display information about all instances of the package:

pkginfo -l pkgname.*

where pkgname is the name of the package; SUNWj3dev for example.

Note down information about the package based on the output of the pkginfo command:

If the pkginfo command reports that the package was not found, note down that the required package is missing and continue to the next package.

If the pkginfo command displays information about a single package instance, check that the BASEDIR value matches the location you noted down in Step 2. If it does, note down the PKGINST value and continue to the next package. Otherwise, note down that the package is missing and continue to the next package.

If the pkginfo command displays information about multiple package instances, look for an instance whose BASEDIR value matches the location you noted down in Step 2. If you find an instance that matches, note down its PKGINST value and continue to the next package. If you do not find an instance that matches, note down that the package is missing and continue to the next package.



Note	Different packages installed in the same BASEDIR can have different package instances. For example, SUNWj3dev.2 and SUNWj3jmp (without the .2 instance specifier) can both have a BASEDIR of /usr/jdk/.j2se1.4.1_06. What connects the packages of an installation of J2SE is the BASEDIR, not the package instance number.

Determine whether you need to update the J2SE installation used by Java Enterprise System

You need to update the J2SE installation used by Java Enterprise System if any of the following conditions applies:

If you need to update the J2SE installation used by Java Enterprise System, the procedure you use depends on the location of the J2SE installation used by Java Enterprise System:

Update the J2SE installation in /usr

If you are not logged in as superuser (root), use the su command to become the superuser.

If the Java Enterprise System distribution is not accessible on your network or on the system, insert the distribution CD or DVD.

Navigate to the directory in Java Enterprise System distribution that contains the J2SE packages:

cd dist-base/Solaris_arch/Product/shared_components/Packages

where dist-base is the base path to the Java Enterprise System distribution, and arch is the architecture of the system, either sparc or x86.

Shut down services that depend on J2SE.

Set your system to single user mode.

Use the pkgrm command to remove the package instances you noted down in Step 5 on page 7 as existing and having /usr as the BASEDIR. Remove the package instances in this order:

1. SUNWj3rtx
2. SUNWj3dvx
3. SUNWj3jmp
4. SUNWj3dmo
5. SUNWj3man
6. SUNWj3dev
7. SUNWj3rt

For example:

pkgrm SUNWj3dmo SUNWj3man SUNWj3dev SUNWj3rt

Add the packages for the version of J2SE that has been certified with Java Enterprise System 2004Q2:

pkgadd -d . SUNWj3rt SUNWj3cfg SUNWj3dev SUNWj3man SUNWj3dmo SUNWj3dvx SUNWj3jmp SUNWj3rtx

The packages SUNWj3dvx and SUNWj3rtx are required only for 64-bit support while the package SUNWj3jmp is required only for Japanese man page support.

Restore your system to multiuser mode.

Start services that depend on J2SE.

Update the J2SE installation in another location

If you are not logged in as superuser (root), use the su command to become the superuser.

Create a customized installation administration file to specify the non-default installation location of J2SE:

Make a copy of the default installation administration file:

# cp /var/sadm/install/admin/default /tmp/admin-file

Edit the file /tmp/admin-file, customizing its basedir value. In the line

basedir=default

change default to the location of the J2SE installation used by Java Enterprise System, which you noted down in Step 2 on page 6. For example:

basedir=/usr/jdk/.j2se1.4.1_06

Do not change any other values in the file.

If the Java Enterprise System distribution is not accessible on your network or on the system, insert the distribution CD or DVD.

Navigate to the directory in Java Enterprise System distribution that contains the J2SE packages:

cd dist-base/Solaris_arch/Product/shared_components/Packages

where dist-base is the base path to the Java Enterprise System distribution, and arch is the architecture of the system, either sparc or x86.

Shut down Java Enterprise System services that depend on J2SE.

Use the pkgrm command to remove the package instances you noted down in Step 5 on page 7 as existing and having a BASEDIR matching the location of the J2SE installation used by Java Enterprise System. Remove the package instances in this order:

1. SUNWj3rtx
2. SUNWj3dvx
3. SUNWj3jmp
4. SUNWj3dmo
5. SUNWj3man
6. SUNWj3dev
7. SUNWj3rt

For example:

pkgrm SUNWj3rtx SUNWj3dvx SUNWj3jmp SUNWj3dmo.2 SUNWj3man.2 SUNWj3dev.2 SUNWj3rt.2

Add the packages for the version of J2SE that has been certified with Java Enterprise System, making sure you use the customized installation administration file:

pkgadd -a /tmp/admin-file -d . SUNWj3rt SUNWj3cfg SUNWj3dev SUNWj3man SUNWj3dmo SUNWj3dvx SUNWj3jmp SUNWj3rtx

The packages SUNWj3dvx and SUNWj3rtx are required only for 64-bit support while the package SUNWj3jmp is required only for Japanese man page support.

Start Java Enterprise System services that depend on J2SE.

List of Required OS Patches

Before installing Java Enterprise System on Solaris 8 SPARC, you must ensure that the required OS patches have been installed. These patches can be obtained in the form of a patch cluster or as individual patches from http://sunsolve.sun.com. The required OS patch clusters include an installation script that installs the patches in the correct order. The clusters are updated periodically as new patch revisions are released. Select the “Patches” link on the SunSolve site and follow the Java Enterprise System links to obtain the available required OS patch clusters.

Patches to Solaris 9 SPARC and Solaris 9 x86 Platform Editions

The following SUNWlib patches are required by Java Enterprise System components:

Patches to Solaris 8 SPARC Platform Edition

The following table lists the patches to Solaris 8 SPARC required by Java Enterprise System components. Depending on your Solaris installation, not all of the following patches will apply to your environment. For example, if you do not have X installed on your system, the windowing related patches will not apply. Similarly, if you do not have Japanese language support on your system, the patches specific to this language support will not apply.

The latest available revision of each of these patches should be applied to your system.

Table 4 Required OS Patches for Solaris 8 SPARC
Solaris 8 SPARC Patch	Description	Components Requiring Patch and Minimum Revision
108434	32-bit shared library	Calendar Server S -06 Installer -13 Directory Server -12 J2SE -13
108435	64-bit shared library	Directory Server S -12 J2SE -13
108528	kernel update	Calendar Server -09 Directory Server -22 J2SE -24
108652	Xsun	J2SE -74
108773	IIIM and X Input & Output Method	J2SE -18
108921	CDE 1.4: dtwm	J2SE -17
108940	Motif 1.2.7 and 2.1.1: Runtime library	J2SE -57
108987	patchadd, patchrm	J2SE -13
108989	/usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys	Directory Server -02 J2SE -02
108993 (obsoletes 108827)	LDAP2 client, libc, libthread and libnsl libraries	Application Server -00 Directory Server -20 MS -00 J2SE -26
109147	linker	Calendar Server -16 Directory Server -24 J2SE -26
109326	libresolv.so.2 and in.named	Application Server -06 Directory Server -10
109951	jserver buffer overflow	Calendar Server -01
110380	ufssnapshots support, libadm	Application Server -00 Identity Server -04 Installer -00
110386	RBAC feature	J2SE -03
110615	sendmail	Calendar Server -09
110934	pkgtrans, pkgadd, pkgchk, pkgmk and libpkg.a	Calendar Server -03 Application Server Identity Server -00 Installer -00 Identity Server -13
111023	/kernel/fs/mntfs and /kernel/fs/sparcv9/mntfs	J2SE -02
111111	/usr/bin/nawk	J2SE -03
111308	/usr/lib/libmtmalloc.so.1	J2SE -04
111310	/usr/lib/libdhcpagent.so.1	J2SE -01
112003	fontset in 64-bit Solaris 8 iso-1 or iso-15	J2SE -03
112396	/usr/bin/fgrep	J2SE -02
112438	/kernel/drv/random	J2SE -02
112472	Font2DTest abort when Lucinda Sans Thai Typewriter selected	J2SE -01
114152	Japanese SunOS 4.x Binary Compatibility (BCP)	Applies when 108993 and SUNWjbcp (Japanese BCP feature) exist. See Sun Alert 50747
112611	/usr/lib/libz.so.1	Directory Server, Web Server
116577		Calendar Server -01

Required Patches for Installing and Using Sun Cluster 3.1

The Sun Cluster component product OS patch requirements are described in the following Patch Info Docs:

You can access these Info Docs by searching for “Sun Cluster 3.1” or the Info Doc number in the Search SunSolve area of http://sunsolve.sun.com.

OS Patches for Java 2 Standard Edition

Updates Included in Java Enterprise System 2003Q4

Java Enterprise System 2003Q4 includes updates to previously released component products. These updates have been pre-applied to component products and are automatically installed during installation of Java Enterprise System.

Table 5 Required OS Patches for Component Products on Solaris 9 SPARC
Patch Number	Component Product	Description
113801-04	Sun Cluster	Core
115614-01	Directory Server
116373-01	Directory Proxy Server
115610-01	Administration Server
115342-01	Shared Components	SASL
114049-07; 115926-03	Shared Components	Security
114677-05	Shared Components	ICU

Table 6 Required OS Patches on Solaris 9x86
Patch Number	Component Product	Description
115615-01	Directory Server
116374-01	Directory Proxy Server
115611-01	Administration Server
114678-05	Shared Components	ICU
115927-03	Shared Components	NSPR 4.1.6; NSS 3.3.7; JSS 3.1.2.5
114050-07	Shared Components	NSP 4.1.4; NSS 3.3.4.1

Table 7 Required OS Patches for Component Products on Solaris 8 SPARC
Patch Number	Component Product	Description
11488-07	Sun Cluster	Mediator
113800-04	Sun Cluster	Core
115614-01	Directory Server
116373-01	Directory Proxy Server
115610-01	Administration Server
115328-01	Shared Components	SASL
115924-03	Shared Components	Security
114045-02	Shared Components	Security
116103-03	Shared Components	ICU

How to Obtain Updates

Visit http://sunsolve.sun.com and select either “Patches” or “Patch Portal” and then follow the Java Enterprise System links. As OS patch requirements change and patches to Java Enterprise System components become available, updates will be made available on SunSolve, initially in the form of recommended patch clusters.

Installation Notes

The following information pertains to the installation process using the Java Enterprise System installer.

Miscellaneous Installation Issues

Running services with non-root users (4950028)

When configuring Java Enterprise System components through the installation program, the default runtime user ID assigned to services is root. Before accepting this setting, it is recommended that you familiarize yourself with the installation and administration documentation of each component product to determine how to use non-root user IDs in your deployment environments. Many of the services associated with the component products can be operated using a non-root user ID.

Identity Server and Portal Server can both be deployed to Web Server and Application Server instances that are not owned by root. Refer to the “Preparing for Installation” section of the Java Enterprise System Installation Guide for configuration details.

Text-based (CLI) installation mode does not support pagination when reviewing summary logs (4934506)

At the end of the installation using the text-based installer, you are given the option to review the installation logs by selecting ‘1’ or ‘2’. The summary and logs are not readable, due to a scrolling problem.

Workaround
Review the installation logs and summary after installation in complete and you have exited the installer.

Unnecessary components automatically selected when Identity Sever Instant Messaging is selected (4956976)

All components under Identity Server are selected when the Identity Server Instant Messaging Service is selected. Only the Identity Server SDK component should be automatically selected.

Workaround
If you do not desire to install Identity Server on this same system, then manually deselect the Identity Server components other than the Identity Server SDK.

When only SUNWj3rt already exists, SUNWj3dev is not installed by the installer (4947605)

If your system has only SUNWj3rt installed and this version of Java 2 Standard Edition (J2SE) is compatible with the Java Enterprise System, the installation program will not install the companion J2SE development package that is required by Java Enterprise System. Configuration and operation of several component products will fail unless this package is present on your system.

Workaround
Prior to installing Java Enterprise System, determine whether or not your installation of J2SE is compatible. If it is compatible and the SUNWj3dev package does not exist, obtain the corresponding version of this package and install it on your system prior to installing Java Enterprise System. Refer to the Java Enterprise System Installation Guide for more details on J2SE support.

Long delays occur without feedback in interactive installation modes (4955348)

On several panels and screens of the interactive installation modes, delays occurs when moving from one panel or screen to the next. No feedback is provided to indicate that the installation program is active and operating normally. The specific points at which a delay should be expected are:

Workaround
Wait for the installation program to respond under these specific circumstances.

Silent installer does not flag component product configuration problems

After performing a silent install, make sure to check the logs (var/sadm/install/logs) for any errors. The silent installer will not necessarily catch all of the component product configuration errors and will complete without flagging the errors.

Stop processes before allowing installer to upgrade shared components (4918674)

Before allowing the installation program to update shared components, it is recommended that you stop all processes that may be using those components. After allowing the installation program to update the shared components and completing the installation program, it is recommended that you restart your system.

In console mode, no progress indicator during installation or upgrade of shared components (4943140)

After choosing to install from the following screen, the installation program does not provide an immediate progress indication while the program either installs or upgrade shared components. Since this phase may take at least several minutes to complete (as in the case of installing or upgrading J2SE packages), it might appear that the installation program has stalled.

Workaround
Wait for the installation program to complete installation or upgrade of shared components. After the phase is complete, the installation program will display the progress of installing component products.

Installer detects partial JDK 1.4.1_06 installation but does not correct it (4935666)

Workaround
Make sure the JDK installation of 1.4.1_06 is complete before you start the installer. At the very least, make sure SUNWj3dev or SUNWj3rt are present on your system. Installation will fail if those packages are not present.

Installer does not detect partially installed component product packages (4918824)

Disk Space Check for Solaris packages checks wrong file system (4747235)

This behavior has been noticed during a package-based installation of Application Server built with SetupSDK 5.5 RTM. The default relocation locations are /var, /etc and /opt. If you choose a different mount point, in /export, for example, the disk check mechanism will not check that location. It continues to check the default locations. Therefore, the disk space information it reports is erroneous.

Workaround
If you want to install the entire Java Enterprise System product suite on one partition, you need a minimum of 80 MB in that partition. Verify the amount of available space before you attempt the install.

Installer does not enforce dependency on SUNWzlib (4918976)

Workaround
For 32-bit and 64-bit SPARC installations, use pkgadd to manually add the SUNWzlib and SUNWzlibx packages before running the installer.

Installer ‘welcome page’ launches without Next button (4922208)

Workaround
Click Cancel and exit the installer. Then, re-launch the installer.

NEXT button disabled on “Check System Requirements” panel (4927699)

If there is insufficient disk space, the “next” button is disabled. If you go back to the Installation Directories panel to make modifications, you cannot go forward again.

Installation Directories panel allows blank spaces and file names (4933567)

In the installation directories field, if you have blank spaces between the directory path or an absolute path to a file, the installer hangs at the package verification step.

Workaround
Do not include blank spaces in the installation directories field. Do not enter a file name in the directories field.

Name of Administration Server in component selection panel incorrect (4933567)

Under “Administrative Services”, Sun ONE Administration Server and Console should appear instead of Sun ONE Administration Server 5.2”.

Directory Server and Administration Server configuration fails with insufficient disk space (4932843)

If you install Directory Server and Administration Server using any of the installer modes (text-based, graphical or silent) and there is limited or no extra disk space in the partition targeted for installation, installation could fail. This problem results from the fact the that installer does not account for any extra disk space required by the component products for their respective post-installation configuration. See also Disk Space Check for Solaris packages checks wrong file system (4747235).

Workaround
Manually make sure there is plenty of extra disk space before running the installer.

Failed component product installation message is misleading (4929897)

If a single component product installation fails, the installation summary indicates that all component product installations failed, even though the installer did not attempt to install the remaining component products after failing to install the first component product.

Workaround
In order to obtain the correct failed installation information, review the detailed version of the install log. pkgadd output indicates which component installation failed and why. The log files are located in: /var/sadm/install/logs.

SUNWj3dmx package not upgraded by the installer (4944839)

If the package SUNWj3dmx is installed under /usr/j2se on your system and you choose to have the installation program upgrade the copy of J2SE as installed under /usr/j2se, the SUNWj3dmx package will not be upgraded by the installer.

Workaround
Manually install the newer version of SUNWj3dmx. First remove the existing copy of this package using pkgrm. Then obtain the newer version and install it according to the following instructions.

When the installer upgrades JDK, it prompts the user to choose between upgrading the existing JDK in /usr/j2se or to install a new version of JDK in /usr/jdk/.j2se1.4.1_06.

Parallel installation of Application Server and Identity Server partially fails (4946125)

After installing Directory Server, if you create a statefile to install Application Server and Identity Server on two machines in parallel, only one amconsole gets configured and becomes available.

Cannot upgrade version of JDK in non-default directory (4946938)

If you have an earlier version of JDK (earlier than 1.4.1_06) that is installed in a non-default directory, such as /export or /opt, the installer detects the JDK package and shows it in the Incompatible Shared Components panel. You are not given the choice to install a new JDK package in the non-default directory. The new JDK package (version 1.4.1_06) is automatically installed in /usr/jdk/.j2se1.4.1_06.

If you have JDK 1.4.1_06 already installed in a non-default directory and you want to keep it there, before you run the installer, create a symbolic link in /usr/jdk as follows:

Silent installer throws exception if incorrect command syntax used (4940314)

If you forget to include the -nodisplay option when you attempt a silent mode installation, the installer throws an exception. For example, you generate a silent file using the following command:

Messaging Server Installation

Problem installing Messaging Server and Directory Server on different machines

Cannot access Messaging Server in High Availability environment (4946314)

When you attempt to connect to Messaging Server by way of HTTP, for example, you get a “file not found” error. This problem results from the fact that the installer does not set two configuration parameters, local.hostname and local.servername.

Workaround
The Messaging Server configuration parameters local.hostname and local.servername define the hostname of the mailhost. In a high availability environment, if Directory Server and Administration Server are configured to use a different logical host than is used by Messaging Server, mail users cannot log in. Therefore, you must change the Administration Server and Directory Server parameters to the same value of Messaging Server’s LOGICAL HOSTNAME.

Become mailsrv. Set local.hostname and local.servername to point to your LOGICAL HOSTNAME:

Using Messaging Server (and Directory Server) with Schema 2 support (4916028)

In order to use Messaging Server with Schema 2 support, you must install Identity Server and Directory Server. Currently, the only way to get Schema 2 support into Directory Server is to install Identity Server.

Identity Server also requires Web Server (or Application Server) to act as its web container. If Identity Server is not installed with Directory Server, then only Schema 1 is used by Messaging Server. Because there are no user selectable options for Schema 1 or 2 during the Java Enterprise System installation, Identity Server must be installed to update Directory Server.

Messaging Server Configuration

Administration Server configuration error appears during Messaging Server configuration (4915459)

If Directory Server is up and running on one node and Administration Server and Messaging Server have been installed through the installer GUI on another node, an Administration Server configuration error appears when you try to configure Messaging Server using configure:

Unable to read the AdminServer ServerRoot Configuration file /etc/mps/admin/v5.2/shared/config/serverroot.conf.
Is the Admin Server configured properly ?

Workaround
Execute the Administration Server Configuration script before configuring the Messaging Server.

Message Queue Installation

If the machine on which Message Queue is installed has a previously installed version Message Queue 3.0 and above, then the Message Queue line item on the installer Product Selection Panel appears grayed out. If Message Queue version is compatible then you do not need to reinstall the Message Queue (unless you want to upgrade the user license for Enterprise Edition and it is not the Enterprise Edition version that is being installed.

Workaround
To upgrade from Message Queue Platform Edition to Message Queue Enterprise Edition, uninstall the Platform Edition and then do a full installation of Enterprise Edition.

Directory Server Installation

Directory Server root directory not validated during Administration Server installation (4938089)

When you install Administration Server after installing Directory Server, the installer does not verify that root directory you choose for Directory Server and the root directory you choose for Administration Server are indeed the same. If you happen to enter two different directories, the installer proceeds without a warning and configuration of Administration Server fails.

Workaround
Make sure that you enter the same root directory for Directory Server and Administration Server.

Directory Server fails to launch after reboot due to “bootstrap-config” errors (4938519)

Note that this problem occurs when you perform the integrated installation of Java Enterprise System and Solaris. If you install Java Enterprise System separately (after you install Solaris), Directory Server should launch properly.

The second workaround is not recommended for production systems, given that the max descriptors value is increased to such a large number. The second workaround is appropriate for quick sanity tests.

Console-based installer does not give option to populate directories with real data (4939154)

When using the console-based installer, you are forced to populate the directories with sample data. The graphical installer appears to allow you to choose between sample data and real data.

Workaround
Select option 1, “1. Populate with sample organizational structure”. After you have finished with the Directory Server installation and configuration, run the Directory Server utility, db2ldif. Export the sample data in dc=example,dc=com. Then, remove the sample data and re-import into Directory Server.

Cannot register the resource type for Directory Server (4921882)

Workaround
Before performing the scrgadm, edit the SUNW.dsldap file and modify the RT_BASEDIR by adding /opt to the path.

Cannot create new instance from console with admin user

Workaround
Use rootdn to create the directory server instance, which is usually cn=Directory Manager.

Web Server Installation

Web Server installation fails if the Web Server install directory is not empty (populated with files from a previously installed version).

Workaround
Back-up all your configuration files. Then, remove the install directory before installing Web Server using the Java Enterprise System installer.

Unnecessary error “User and group ID adds fail” if 80 is already in use (4923647)

f uid and gid values of 80 are already in use on the system and they are not assigned the value of “webservd”, the package add of SUNWwbsvr will issue an error message, but the installation of Web Server proceeds successfully.

Workaround
If you do not plan to use the “webservd” user ID and group ID value, you may ignore this error message. If you plan to use the “webservd” value for your Web Server instances, your can either correct the conflict with the value of 80 or create the “webservd” user and group IDs using a different ID value.

Changing docroot for Web Server causes loss of amconsole and portal web modules (4949922)

When the DocRoot for Web Server is changed and then restored, you can no longer access to amconsole and portal. For example, if you change the DocRoot directory for Web Server to point to the DocRoot directory of Instant Messaging (so that you use the Java Web Start for Instant Messaging) and then change the DocRoot back to its default value, the /amconsole and /portal modules disappear.

Instant Messaging links do not appear on Web Server home page (4950828)

If Instant Messaging, Identity Server and Web Server are all installed with /opt/SUNWiim/html as the doc root directory, no Java Web Start or Java Plug-ins links appear on the Web Server homepage.

Workaround
The Web Server DocRoot is set to /opt/SUNWiim/html and appears so in the console. Change the directory to /tmp and hit ‘Apply’.

Then, change the directory back to /opt/SUNWiim/html and hit ‘Apply’ again. The links to the Instant Messaging page should then be on the Web Server home page.

If using a Korn shell and “set -o noclobber” exists in .env file an error occurs, halting installation (4912254)

You may find that although installation of Web Server completed successfully, configuration failed with an error indicating that “.../setup/configure[1369]: /work/ws61/setup/setup.inf: file already exists”.

Workaround
Remove the set -o noclobber setting from your environment. Configure Web Server by running the Web Server configuration program, web_server_install_dir/setup/configure. The configuration program creates a runtime configuration, including an admin server and a default instance.

Web server start up displays “locale-charset-info” warning messages (4931128)

Upon start-up, ‘locale-charset-info” warning messages are displayed, such as the following:

warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding

info: WEB0100: Loading web module in virtual server [https-tombombadil.red.iplanet.com] at [/amcom]

Web Server Configuration

Error message on admin console displays after user login (4756206)

After installing Identity Server, when you log in to the Web Server administration console, the following message might appear:

“Warning manual edits not loaded. Some configuration files have been edited by hand. Use the Apply button on the upper right side of the screen to load the latest configuration files.” If the message appears, click ‘Apply’ to apply the changes. You do not have to restart Web Server. However, if you proceed without clicking on the “Apply” button, the Identity Server configuration changes will be lost. If Identity Server configuration is lost copy server.xml from the Web Server's primary configuration directory to its backup configuration directory as follows:

# cp /opt/SUNWwbsvr/https-hostName.domain/config/server.xml /opt/SUNWwbsvr/https-hostName.domain/conf_bk

Application Server Installation

Application Server fails to start due to Message Queue Broker port conflict (4939399)

During configuration of Application Server, an unused port number is assigned to the Message Queue Broker (also known as the JMS Service in the Application Server administration UI). If another service occupies this port before the Application Server instance is started, the Application Server instance will fail to start.

Workaround
Determine an unused port number and modify the JMS Service port number in the Application Server administrative UI. Specifically, JMS Service Port number.

Installer does not detect bundled packages (4928796)

During the component product selection, the installer ignores the presence of Application Server bundled packages. The installer only checks for unbundled packages.

Workaround
To avoid installing more than one Application Server, make sure to deselect the Application Server unbundled component in the component selection panel.

Application Server Configuration

passwordfile does not work with mix of upper/lowercase characters (5004406)

If you use a mix of upper case and lower case characters in the Application Server administative password, you get a “Unable to deploy DSAME services” when you attempt to deploy Identity Server on Application Server.

Workaround
Do not use uppercase characters in the administrator password for the Application Server. Or, if you have already tried to configure Application Server using a mixed case password, and have gotten the “Unable to deploy DSAME services” error, do the following:

If you need to use mixed characters in the Application Server’s admin password, install Application Server and confgure it after installation, using either the asadmin interactive text-based installer (the CLI) or the administrative console.

Configuration fails if Perl packages are not present (4951380)

Workaround
Before you configure Application Server and Directory Server, make sure the SUNWpl5* packages (the Perl packages) are installed. The Perl packages can be found on the Solaris 8 and Solaris 9 media. Use pkgadd to add the packages.

Installer does not recognize host name user enters in configuration panel (4931514)

The installer prompts you for the “server name” for the Application Server. However, the installer uses the actual host name of the machine regardless of what you input in the text field.

Workaround
If the server name is different from the server’s host name, become superuser and do the following in the domain directory of interest (the “server root” directory):

Identity Server Installation

Default Application Server values might not always be correct (4943674)

During configuration of Identity Server, make sure that the Application Server settings such as port values are correct. The initially listed values might not always be correct.

Application server automatically selected as container for Identity Server (4933352)

When you install Identity Server, you can choose to have either Application Server or Web Server as the container. However, the installer prompts you to enter path information for Application Server even if you selected Web Server to be the container.

Workaround
If you want to install Identity Server on Web Server, de-select the Application Server + Message Queue before proceeding to the next installation panel.

amconsole errors generated after install (4928865)

Workaround
Set the same values for user and group, such as sunone and sunone respectively. Or, specify root and other as the web server runtime user and group.

pkgadd fails if Weblogic instance is not running (4918174)

Workaround
Make sure BEA Weblogic is up and running before starting the installer.

Non- US top level domain names not recognized (4928869)

If you are using Internet Explorer with Identity Server or Portal Server, the browser does not recognize some top-level domain names when it chooses the cookie domain name. While Internet Explorer chooses example.com for the cookie domain for www.example.com, it would incorrectly choose co.jp for the cookie domain for www.example.co.jp.

Cannot install with Secure Deployment if installing with Application Server and Web Server (4932659)

If you are installing the web container (Application Server and Web Server) and Identity Server in the same session, you cannot select the “[Identity Server] secure instance” option.

Workaround
Do not choose the secure deployment option if Identity Server and its web containers are installed in the same session.

Portal Server Installation

Minimal mode installation for IBM WebSphere does not work (4946769)

Even if you select “minimal mode installation” for the IBM WebSphere container, you are forced to perform a custom (full) installation.

Workaround
Use the custom mode of configuration when configuring Portal Server against third-party web containers.

Unnecessary warning message regarding Application Server dependency appears (4930028)

During the Portal Server installation, a warning appears which says that Portal Server depends upon Application Server and that Application Server must be installed. The warning appears even if you have already installed Application Server successfully. If you have indeed installed Application Server successfully, ignore the warning and proceed with the Portal Server installation.

Web Server instance not validated during Portal Server installation (4934364)

When you enter the Web Server instance in the Portal Server panel, the validity of your entry is not checked. Installation and configuration appear to be successful when in fact configuration is not successful.

Workaround
Uninstall Portal Server. When reinstalling Portal Server and entering configuration information, ensure that the Web Server instance name is accurate.

Search broken: database JNI libraries not found (4932661)

Workaround
Edit the server.xml file. Assign base-dir/SUNWps/lib directory as the value for the native-library-path-prefix attribute. For example,

Installer does not verify that Portal instance in running with installation on BEA Web Logic (4918174)

Workaround
Verify that the BEA WebLogic instance is running before invoking the installer to install Portal on BEA WebLogic.

Portal SRA Issues

Rewriter proxy fails to start and throws exception (5016000)

To have the rewriter proxy run properly, the netletd and rwproxyd scripts need to be modfied as follows:

if [ "${JDK_VERSION}" = "1.3" ]; then BOOT_CLASSPATH="-Xbootclasspath:$JAVA_HOME/lib/tools.jar:$JAVA_HOME/jre/lib/rt.jar:$JAVA_HOME/ jre/lib/i18n.jar:$IS_HOME/lib/jdk_logging.jar"

if [ "${JDK_VERSION}" = "1.4" ]; then BOOT_CLASSPATH="-Xbootclasspath/p:$JAVA_HOME/lib/tools.jar:$JAVA_HOME/jre/lib/rt.jar:$JAVA_HOM E/jre/lib/i18n.jar:$IS_HOME/lib/jdk_logging.jar:$JAVA_HOME/jre/lib/jce.jar" fi

if [ "${JDK_VERSION}" = "1.3" ]; then BOOT_CLASSPATH="-Xbootclasspath:$JAVA_HOME/lib/tools.jar:$JAVA_HOME/jre/lib/rt.jar:$JAVA_HOME/ jre/lib/i18n.jar:$IS_HOME/lib/jdk_logging.jar"

Installing Portal Gateway without unnecessary components

After you select Portal Gateway for installation, several other component products are automatically selected. De-select everything except the following two sub-components:

SRA Core configuration fails in multi-session, customized directories installation (4940974)

During a multi-session installation, configuration fails for SRA Core components if you choose custom directories.

Workaround
You must install Secure Remote Access Core in the same location as Portal Server.

Sun Cluster Installation

Clients unable to connect after scshutdown and reboot of a cluster (4941371)

Workaround
After rebooting the cluster, switch the SUNW.SharedAddress resource to another cluster node. Alternatively, stop and then restart SUNW.SharedAddress resource on the same node. If you do the latter, you must stop the scalable service resource before stopping SUNW.SharedAddress resource.

Sun Cluster Data Services for previous versions Directory Server

Java Enterprise System 1 includes the Sun Cluster Data Service for the Sun ONE Directory Server 5.2. If you need the Sun Cluster Data Service for Sun ONE Directory Server 5.0 or 5.1 or for Netscape HTTP, version 4.1.6, it is available in the Sun Cluster 3.1 Data Services 10/03 release. To request this release, contact your Sun customer service representative.

Sun Cluster Data Service for Oracle Parallel Server/Real Application Clusters not installed from Sun Cluster 3.1 CD

Instead, it is installed from the Java Enterprise System 1 Accessory CD, volume 3. Also, the data services are not installed from the agents CD. Instead, they are installed from the Java Enterprise System 1 Accessory CD, volume 3.

Installer does not recognize uninstallation by scinstall -r (4915796/4919514)

If you uninstall Sun Cluster using scinstall -r and then go to reinstall, the Java Enterprise System installer sees Sun Cluster as still being installed. Additionally, not all packages are removed during the install.

Workaround
After uninstalling Sun Cluster using scinstall -r, you must also uninstall Sun Cluster using the Java Enterprise System uninstaller. Run the uninstaller and select the Sun Cluster components for removal.

Upgrade to Sun Cluster 3.1 data services using scinstall partially fails (4932006)

When you upgrade the Sun Cluster data service, the SUNWCscdab package is “not found”. The upgrade will have succeeded, but the data service documentation will not have been upgraded.

Workaround
To upgrade the documentation, use pkgadd to add the SUNWscdab package from the Java Enterprise System Accessory Pack CD.

Value shown for utilized disk space is incorrect (4929350)

If you install Sun Cluster Agent only, the amount of utilized disk space displayed on the installer screen is incorrect.

If a Sun Cluster Agent for a component product is installed outside of Java Enterprise System, installer does not allow selection of the Sun Cluster Agents (4916722)

Workaround
Install the Sun Cluster Agent packages using the pkgadd on the Java Enterprise System CD.

The SunPlex Manager install module is not supported (4928710)

Workaround
Use the Java Enterprise System installer to perform a minimal installation of Sun Cluster. Then, use scinstall to complete the installation and configuration. See the Sun Cluster Software Collection for more information at: http://docs.sun.com/coll/572.12.

Cannot install Sun Cluster Agents if Sun Cluster was not installed using the Java Enterprise System installer (4937337)

If you attempt to install Sun Cluster agents after using Sun Cluster Jumpstart to install Sun Cluster, a Product Dependencies Checks error appears.

High Availability Web Server does not start on all nodes after a reboot (4935318)

This problem occurs if you check “Automatically start Web Server when system restarts” during the installation of Web Server with Sun Cluster.

Workaround
Remove the /etc/rc* script that starts Web Server at the time of node reboot.

If Calender Server is not installed Sun Cluster agent for calender fails (4923738)

If later versions (than are compatible with Java Enterprise System) of agents for Calendar Server, which are included in the SUNWasha and SUNWdsha packages are installed, they are not detected by the installer. The Agents (in the Java Enterprise System compatible version) appear to be available for installation, as are not grayed out on the product selection panel. If you choose to install the Agents, the install fails.

Workaround
Using pkgrm, remove all existing Sun Cluster agent packages. Then, restart installation.

Installer does not allow for additional Sun Cluster agents to be installed if one exists on system (4945651)

If you have installed a Sun Cluster Agent prior to running the Java Enterprise System installer, the installer does not allow you to install additional agents.

Localization Issues

Some localized messages are wrapped at the wrong position in the text-based installer (4938764)

locale entry of serverl.xml is always in en_US (4855688)

Workaround
Edit /var/opt/SUNWappserver7/domains/domain1/admin-server/config/server.xml. Change “en_US” to the appropriate locale value.

Search providers fields installed in wrong location (4935315)

The files for SUNW[d|e|f|k|c|h|]pss (search providers) are installed in a different directory than are the base packages.

Directory Server console displays broken multibyte root suffix name (4929282)

Calendar Server uninstall log file has errors if Calendar Server was installed in all languages (4937876)

Uninstallation Notes

The uninstaller for text-based (CLI) mode does not allow multiple selection (or deselection) of component products for uninstallation (4958324)

When you run the Java Enterprise System uninstaller in text-based (CLI) mode, the uninstaller automatically selects for removal any Java Enterprise System components it finds on your system.

Text-based (CLI) mode uninstaller confusing for uninstall of multiple component products (4958324)

If you install Java Enterprise System component products in multiple sessions, you must loop through the Product Selection List of the text-based installer multiple times to select the products for uninstallation. You cannot specify a comma separated list during the selection.

For example, suppose you have installed Product A in the first installation session, product B in the second installation session, and product C in the third installation session. When you run the uninstaller in text-based (CLI) mode, the Product Selection List will only have the last installed product C selected. A and B will not be selected.

To select A and B, you must select A (or B) in the next loop, and then select B (or A) in the following loop.

/var/sadm/prod/entsys does not contain uninstall script (4954478)

Workaround
Use pkgadd to install SUNWentsys-uninstall (and SUNWentsysl10n-uninstall if any languages were installed) from the media kit.

After Portal Server uninstallation web applications from Application Server still deployed (4943052)

You cannot restart the Application Server after uninstalling Portal Server. This problem results from the fact that the admin password is not being passed to the configurator during Portal Server uninstallation.

Workaround
Using Web Server’s admin console, manually undeploy web applications after uninstalling Portal Server.

Cannot reinstall Web Server package if install directory is not empty (4925690)

If you have uninstalled Web Server and are going to reinstall, pkgadd of SUNWwbsvr fails if the install directory is not empty.

For example, if you choose to install Web Server in /opt/SUNWwbsvr do the following:

Uninstallation panels do not have expected functionality (4907964)

There are certain layout and functionality differences between the installation panels and the uninstallation panels. For example, when you select a component on the installation panel, all the sub-components are automatically selected. When you select a component on the uninstallation panel, however, the sub-components are not automatically selected.

Uninstallation throws exception if some components failed during installation

Workaround
If you are uninstalling due to an installation which failed mid sequence, you must manually remove all the packages and clean the Product Registry. Then, you can back out all the remaining Products installed as a part of the failed install sequence.

Problems with uninstallation of Directory Server if installation was run in silent mode (4922375)

The uninstaller prompts you for configuration settings, even though none were entered during the install.

Workaround
Enter random values the fields and continue with the uninstallation.

Web server processes remain after uninstall on Solaris OS x86 (4933968)

Uninstallation of Identity Server deployed on IBM Web Sphere incomplete (4926383)

After an uninstallation is performed, the classpath for the IBM Web Sphere Application Server still contains the Identity Server jar file paths. Also, the Identity Server web-apps directory remains.

Workaround
Manually remove remaining directory and file paths before reinstalling to the same container.

Uninstallation of Java Enterprise System does not remove all packages (4941170)

After uninstalling the last remaining component product of Java Enterprise System, the following packages might remain on a system after uninstallation:


SUNWasvc
SUNWcjafo
SUNWcjmailo
SUNWebnfs

SUNWhjafo
SUNWhjmailo
SUNWjjafo
SUNWjjmailo
SUNWkjafo
SUNWkjmailo
SUNWldk
SUNWprd
SUNWsasl
SUNWtlsu
SUNWiqcko
SUNWiqctw
SUNWiqiko
SUNWiqitw
SUNWjato
SUNWktse

Workaround
Many of these packages are shared components that may be used by other parts of your system. It is not advised that you manually remove these packages unless you are certain that they are not in use by other parts of your system.

The following packages belong to Java Enterprise System component products and may removed through pkgrm as long as you are certain that you have already removed the corresponding component product:

Component Product Compatibility

Table 8 Component Product Dependencies Matrix
Component Product	Component Product or Shared Component
Sun ONE Application Server 7 Update 1	Sun ONE Message Queue 3.0.1 SP2; shared components
Sun ONE Calendar Server 6.0	Sun ONE Directory Server 5.2; shared components
Sun ONE Directory Server 5.2	shared components
Sun ONE Directory Proxy Server 5.2	shared components
Sun ONE Instant Messaging 6.1	Sun ONE Directory Server 5,2; Sun ONE Web Server 6.1; shared components
Sun ONE Messaging Server 6.0	Sun ONE Directory Server 5,2; Sun ONE Web Server 6.1; shared components If using Schema 2, Identity Server must be installed with Directory Server
Sun ONE Message Queue 3.0.1 SP2	shared components
Sun ONE Identity Server 6.1	Sun ONE Web Server 6.1; Sun ONE Application Server 7 Update 1; Sun ONE Directory Server 5.2; shared components
Sun ONE Portal Server 6.2; Sun ONE Portal Server, 6.2 SRA	Sun ONE Web Server 6.1; Sun ONE Identity Server 6.1; Sun ONE Application Server 7 Update 1; Sun ONE Directory Server 5.2; shared components
Sun ONE Web Server 6.1	shared components

Support for Netscape Security Services 3.3.5 and 3.3.4

Two versions of the Netscape security libraries are included in Java Enterprise System. Directory Server, Directory Proxy and Administration Server depend on the version of the libraries installed under /usr/lib/mps/ while all other component products that depend on these libraries depend on the newer version installed under /usr/lib/mps/secv1/.

Documentation Errata

Location of Sun Cluster documentation

Sun Cluster documentation is available on the Java Enterprise System Accessory CD Volume 3, as well as on docs.sun.com. Go to http://docs.sun.com/prod/entsys.03q4 for the complete set of Sun Cluster 3.1 documentation.

Erroneous information listed on Installer Help screens (4935895/4944849)

Some of the Installer Help screens contain inaccurate information for configuring component products, and should be ignored. The DNS terminology is used inconsistently.

The “Gathering Information” chapter in the Installation Guide contains the correct information. Refer to this chapter for help in configuring Java Enterprise System component products during installation.

Uninstalling in Text-based (CLI) Mode

The section “Uninstalling Using the Text-Based Interface” in Chapter 10, “Uninstalling Software” of the Java Enterprise System Installation Guide does not completely explain how to select and deselect component products for uninstallation. Refer to the following topics for information on selecting and deselecting component products. See Text-based (CLI) mode uninstaller confusing for uninstall of multiple component products (4958324).

How to Report Problems and Provide Feedback

If you have problems with Java Enterprise System, contact Sun customer support using one of the following mechanisms:

So that we can best assist you in resolving problems, please have the following information available when you contact support:

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Use the web-based form to provide feedback to Sun:

Please provide the full document title and part number in the appropriate fields. The part number can be found on the title page of the book or at the top of the document, and is usually a seven or nine digit number. For example, the part number of this document is 816-6876-14. The full title is Sun Java Enterprise System 2003Q4 Release Notes.

Additional Sun Resources

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.

Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plus des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.

Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.

Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.

Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.

Sun Java Enterprise System Release Notes

Version 2003Q4