test

Sun Java Enterprise System 2005Q4 Release Notes

Sun Java Enterprise System Release Notes

These Release Notes contain important information available at the time of release of Sun JavaTM Enterprise System (Java ES) 2005Q4. Known limitations and problems, technical notes, and other information are described here. Read this document before you begin using Java Enterprise System in order to improve your overall installation and operation experience. It is also highly recommended that you read the pertinent component-level release notes for each individual application that comprises your Java Enterprise System 4. The system-level release notes (this document) covers the highlights of the issues affecting Java Enterprise System 4, whereas the component-level release notes describe application issues in detail.

The most up-to-date version of these release notes and the system documentation can be found at the Java Enterprise System documentation web site at http://docs.sun.com/coll/1286.1 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 product documentation.

Third-party web sites are referenced in this document and provide additional, related information.

Note –

Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

This release note discusses the following topics:

Component Release Notes

All the component specific information appears in the respective component release notes. The following component release notes can be found at:

Release Notes Revision History

Table 1 Revision History

Version 

Date 

Description of Changes 

13 

November 2005 

Added issue 6300530 to Installation Bugs Fixed in This Release; added Changes to Component Placement on Distribution CDs section; corrected references to Application Server version, changing 8.1 2005Q4 to 8.1 2005Q2 Update 2.

12 

October 2005 

Removed documentation of issue 6330966, which was incorrectly added in version 11. 

11 

October 2005 

Added documentation of issues 6330966 and 6223676.

10 

October 2005 

Release version. 

05 

June 2005 

Beta version. 

What's New in This Release?

This section lists the new features for Java ES 2005Q4. To continue adding value for Sun customers, Sun has added enhancements to the existing products. The following fully supported products have been added to the Java Enterprise System license and are maintained by the same systematic features as the rest of the Java Enterprise System portfolio:

Platform Support for System Level

This section describes the current OS and browser support for Java ES 2005Q4.

Note –

Solaris minimal installation is not supported in Java ES 4. Of the required OS installations allowed to run Java ES 2005Q4, only 1, 2 and 3 (shown below) are allowed to perform a Java ES 2005Q4 installation:

1) Entire installation plus OEM

2) Entire installation

3) Developer installation

4) End user installation

5) Core installation

Operating Systems:

Note –

Please note that this is the last release that Sun will ship new versions of Java Enterprise System for Solaris 8 and RedHat 2.1. The next release of Java Enterprise System will support Solaris 9 and 10 (x86 and SPARC) and RedHat 3 and 4. This does not affect the support life that customers obtain for Java Enterprise System released prior to that date. We recommend customers commence their transition planning to a newer version of Solaris and RedHat.

Table 2 New Features in Java Enterprise System Components

Component  

New Features 

Access Manager 

  • New delegated administration model

  • Improved log files

  • Personalization attributes

  • Policy status (active / inactive)

  • Bulk federation

  • Authentication named configuration or chaining name space

  • Multiple Authentication instances support

  • Refer to the Access Manager release notes for new feature content:

Instant Messaging 

Failover support using Sun TMCluster

Service Registry 

New product in this release 

Web Proxy Server 

New product in this release 

Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available form Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at:

For more information on Sun's commitment to accessibility, visit

Java 2 Platform Standard Edition Requirements

Java Enterprise System is certified with Java 2 Platform Standard Edition (J2SETM platform) 1.5_04 from Sun Microsystems.

Java Enterprise System 2005Q4 includes the appropriate version of the J2SE.

For detailed information on which versions of J2SE are supported in Java ES 4 and how to install them, refer to the Sun Java Enterprise System 2005Q4 Upgrade Guide.

Unsupported Features

If You Have Installed Delegated Administrator

After you use the Sun Java System Installer to install Sun Java System Communications Services Delegated Administrator 2005Q4, it is recommended that you download and install the latest patch for Delegated Administrator.

Go to and select either “Patches” or “Patch Portal” . The current patch number for Delegated Administrator is :

Changes to Component Placement on Distribution CDs

The following components have been moved from CD 1 to CD 2 in the Solaris distribution:

Due to this change, you must now use both CDs to install these components on Solaris.

Patch Information

For patch information for a given component, refer to the Component Release Notes.

In addition, go to SunSolve at http://sunsolve.sun.com. Navigate to the Patch Portal. Click “Recommended Patch Clusters” and choose“Java Enterprise System Component Patches”. You can find the product in which they are looking for patches and click on that product link.

For component specific patches you can go to this site:

Also, apply any recommended Cluster patch before installing or upgrading Java ES 2005Q4. This applies for Solaris OS 8, 9, and 10. The Cluster patch obsoletes any Solaris 8 or Solaris 9 information that might have carried over from Java ES 2004Q2 or Java ES 2005Q1.

Hardware and Software Requirements

Note –

Current plans are that Sun will not ship new versions of Java Enterprise System for Solaris 8 beyond June 30, 2005. This does not affect the support life for Java Enterprise System prior to June 30, 2005. If you are running Java Enterprise System on Solaris 8, it is recommended that you commence transition planning.

Table 3 Hardware and Software Requirements for complete installation of Java ES 2005Q4

Operating System 

Disk Space 

RAM 

Solaris OS SPARC (Ultra Enterprise 250) 

6096 MB 

4196 MB or above 

Solaris OS x86 (Intel Pentium P4 1GHz / AMD Opteron 248 (/ Sun v20/40/60z)) 

6096 MB 

4196 MB or above 

Linux (Intel Pentium P4 1GHz / AMD Opteron 248 (/ Sun v20/40/60z)) 

6096 MB 

4196 MB or above 

The following table lists the disk installation and RAM requirements for the various components that comprise Java ES 2005Q4.

Table 4 Component Disk Installation Space and RAM Requirements

Component 

Minimum Disk Space for Installation 

RAM Requirements for Installation 

Access Manager 

512 MB disk space for Access Manager and associated applications  

512 MB RAM for initial testing. 1 GB for threads, Access Manager SDK, HTTP server, and other internals. 

Administration Server 

50 MB of disk space for binaries. By default, most binaries are in /usr. Administration Server requires no disk space provision for data and limited disk space provision for logs. By default, logs and databases are in /var/opt.

512 MB RAM 

Application Server 

with Sun Java System Studio: 500 MB of disk space  

512 MB RAM 

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 

Directory Server 

200 MB of disk space for binaries. By default, most binaries are in /usr. 1.2 GB of disk space for logs and databases for an evaluation configuration. By default, logs and databases are in /var/opt. Add 4 GB for a sample production deployment with a maximum of 25,000 entries and no binaries attributes such as photos.

512 MB RAM 

Directory Proxy Server 

300 MB of disk space  

256 MB RAM 

Instant Messaging 

300 MB of disk space  

256 MB RAM 

Messaging Server 

1 GB for production deployment or 500 MB for evaluation installation;  

Adequate space for message store, database configuration directory, log files, depending upon your site size. 

1 GB RAM for productions systems or 256 MB RAM for evaluation installation. 

Message Queue 

30 MB of disk space  

256 MB RAM 

Portal Server, Portal Server SRA 

1 GB of disk space  

1.2 GB of RAM for production deployments or 512 MB for an evaluation. 

Service Registry 

50 MB of disk space minimum, but 120 MB is recommended.  

1 GB minimum of RAM, but 2 GB is recommended.  

Sun Cluster Software (per node) 

512 MB of disk space for swap space, 512 MB for a /globaldevices partition, and 20 MB for Volume Manager

128 MB of RAM plus ten percent of a node's regular memory requirement. 

Web Proxy Server 

512 MB of disk space  

512 MB RAM 

Web Server 

256 MB of disk space  

64 MB RAM 

For more information on disk space and RAM requirements, refer to the respective component release notes.

Pre-installation Issues

This section lists the Java ES 2005Q4 CR issues that provide valuable information you should be aware of before performing a Java ES 2005Q4 installation. Also, apply any recommended Cluster patch before installing or upgrading Java ES 2005Q4. This applies for Solaris OS 8, 9, and 10.

Compatibility Information

For detailed information about component-level compatibility information, refer to the specific component-level release note:

Sun Java System Calendar Server 6 2005Q4 Release Notes:Compatibility Issues in Sun Java System Communications Services 2005Q4 Release Notes.

Sun Java System Messaging Server 2005Q4 Release Notes:Compatibility Issues in Sun Java System Communications Services 2005Q4 Release Notes.

Sun Java Instant Messaging 7 2005Q4 Release Notes:Compatibility Issues in Sun Java System Communications Services 2005Q4 Release Notes.

Sun Java Communications Services Delegated Administrator 6 2005Q4 Release Notes: Compatibility Issues in Sun Java System Communications Services 2005Q4 Release Notes.

Also refer toChapter 5, Sun Java System Communications Express 6 2005Q4 Release Notes, in Sun Java System Communications Services 2005Q4 Release Notes.

Sun Java System Connector for Microsoft Outlook 7 Release Notes:Compatibility Issues in Sun Java System Communications Services 2005Q4 Release Notes.

Sun Java System Portal Server 6 2005Q4 Release Notes.

Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Release Notes.

Service Registry 3 2005Q4 Release Notes.

Compatibility Issues Between Components

The table below highlights some of the compatibility issues in Java ES 2005Q4 components. For specific information, use the links above to access the appropriate component-level release note.

Component 

Issue 

Access Manager 7 2005Q4 

The new functional capabilities of Release 4 Access Manager involve a number of new interfaces. Access manager support for these new interfaces is enabled by configuring Access Manager to run in enhanced (Realm) mode. However, Realm mode is not compatible with the earlier Java ES 2005Q1 or 2004Q2 Access Manager. For example, directory data has to be migrated to support Realm mode operation. The enhanced Access Manager Console is needed to support enhanced Access Manager services. In addition, Realm Mode does not support other Java ES components, such as Portal Server, Communications Express, Messaging Server, and others. To support backward compatibility, Release 4 Access Manager can be configured to run in Legacy mode.  

Legacy mode is necessary to support other Java ES components, as well as Access Manager policy agents, which cannot currently interoperate with Access Manager in Realm mode. This incompatibility is an important upgrade consideration, and means in most Java ES deployments, that Access Manager should be upgraded to Release 4 Legacy mode. 

 

Application Server Enterprise Edition 8.1 2005Q2 

The asaadmin commands —secure and —s options do not have the same behavior as in previous releases. See the product release notes for a detailed solution (as well as CR 6296862).

Also, Application Server 7 does not work with J2SE 5.0. Refer to the product release note for detailed information (as well as CR 6203688). 

Communications Express Java ES 2005Q4 

An incompatibility was introduced in Java ES 2005Q4 Communications Express user interface(UI): 

Java ES 42005Q4: You must supply the Start Time and End Time of the event.  

Java ES 2005Q1: You must supply the Start Time and Duration of the event.  

Communications Services Delegated Administrator 6 2005Q4 

This component has two issues: 

(1) Access Manager now has two install types: Realm mode and Legacy mode. Legacy mode is the default.  

(2) Upgrading Access Manager from version 6.x to 7.0 (Java ES Release 4) without upgrading Delegated Administrator to version 6 2005Q4 (Java ES Release 4). In the Delegated Administrator console or utility, user creation with mail or calendar service will fail. See the release notes for a detailed solution. 

Message Queue 3 2005Q1 (3.6)

Interface Stability: Sun Java Message Queue uses many interfaces that can help administrators automate tasks. Appendix B in the Message Queue Administration Guide classifies the interfaces according to their stability. The more stable an interface, the less likely it is to change in subsequent versions of the product.

Deprecation of Password Options: The following options have been deprecated for security reasons:

-p

-password

-dbpassword

-ldappassword

JDK 1.3 Client Support (Solaris and Linux Platforms): The following packages contain jar files used to support JNDI and JSSE for client development and deployment on JDK 1.3. These packages are shipped with Message Queue, Platform Edition only. These packages will not be delivered in a future release and are not installed by default. The packages are listed below:

SUNQiqsup— Solaris platform

sun-mq-sup— Linux platform

Messaging Server 6 2005 Q4 

The User Administration console does not work for Messaging Server 6 2005Q4 on Java ES 2005Q1 (Linux). If you open an Administration console you can manage to start and stop other product components. But when you select Messaging Server, the Administration console does not open a new window for Messaging Server 6. See the release note for a solution. 

Java ES 2005Q4 Installer 

The Java ES 2005Q4 installer presents a new alert regarding the selection of a web container. For each component in the following list, you can install a Java ES web container or you can use a compatible web container that is already installed. This alert does not appear in Java ES 2004Q2 or Java ES 2005Q1: 

- Sun Java System Web Server 6.1 SP5 2005Q4 

- Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Update 2 

- A compatible Web container previously installed on this system. 

Instant Messaging 7 2005Q4 

This issue is applicable to administrators who do not wish to upgrade the Instant Messaging Server from Java ES 2004Q2 to Java ES 2005Q1 or Java ES 2005Q4. For more information see The default factory is different in Java ES 2004Q2 and Java ES 2005Q1 (6200472). Also, after upgrading (on a Java ES 2004Q2 system) all shared components to Java ES 2005Q4 Instant Messenger multiplexor throws an exception. See the product release for the latest resolution. Essentially, Java ES 2004Q2 Instant Messaging is incompatible with Java ES 2005Q4 shared components.

Portal Server 6 2005Q4 

 

Installation Bugs Fixed in This Release

The table below describes the bugs fixed in Java Enterprise System 2005Q4. If a component is not listed, no bugs were fixed for 2005Q4.

Table 5 Bugs Fixed in this Release

Bug Number 

Description 

Miscellaneous Installation Issues

 

6225803, 6225809 

Multiple versions of comm_dsetup.pl exist

6210690 

Cannot install Directory Server and Messaging Server with their respective Administration Servers on Sun Cluster HA environment 

6182249 

If installer cannot connect to X11 window server, silent install falls 

6174538 

Several shared packages are not installed on Solaris 10 

5103675 

When installing Administration Server, GUI Installer does not prompt for FQDN 

5020621 

Password exposed during CD installation 

Access Manager Installation

 

5045612 

Protocol cannot be entered for an existing console 

5048518 

Instance creation on Web Server throws exception 

Application Server Installation

 

5110257 

If previous versions of Application Server exist on system installation fails 

6300530 

Cannot install Application Server load balancing plug-in without also installing Web Server 

Messaging Server Configuration

 

6206104 

Need tools to correct bad store.sub.

6199714 

Vacation text is garbage when saved. Hard returns are not retained 

Messenger Express/Communications Express 

 

6196347 

Save attachment no longer works 

6192219 

Regression: Automatic Spell Check was Removed 

Delegated Administrator 

 

6239311 

The Domain Disk Quota value is lost if you change the Domain status or Mail Service status of a full organization 

Portal Server

 

5106639 

Installation and removal of Portal Server appears to hang 

6304201 

SRA needs rule update for amconsole CSS. 

6265800 

Wrong version displayed after upgrade. 

6186633 

Netlet crashes after making connection (approximately 10 to 15 seconds) with remote server. 

6267944 

The version of Portal Server Secure Remote Access is not displayed after upgrade.  

6267783 

Informative and useless page provided to the user when logging in to Portal Server. 

6278810 

Cannot deploy portal on port 443. 

6286949 

pdeploy fails when portal is SSL enabled.

5085361 

Portal Server desktop does not work correctly with a Load Balancer that does SSL termination 

6285755 

Invoking proxylet rules window, error is shown in the page. 

6273080 

Get blank page exception in server.log instead of anonymous portal desktop

6211569 

UWC address book channel does not work with proxy authentication 

6229250  

MS Address Book is not accessible on Portal Desktop 

6254381 

XMLProvider is not synchronized properly. 

5082722 

Hard Limit of 30 netlet rules 

6216175 

UWC address book channel fails (also requires 118540–09 or later) 

6224122 

Applet signing certificate has expired. 

6225341 

proxy-auth fails for MS addressbook

6229071 

UWC Calendar Mail Tab link 

6230844 

Unable to save proxylet rules after upgrade 

5101574 

perftune not up to date with AS 8.1

6184747 

Provide reset option in context for mail, addressbook, and calendar 

6189951 

AS 8.1 Multibyte characters garbled in Portal service Admin console. 

6192579 

Gateway doesn't start after upgrade. 

6201701 

After proxylet is downloaded the desktop pages does not get downloaded. 

6207552 

The proxylet admin window appears different after upgrade. 

6208239 

IllegalStateException accessing authless Mobile desktop.

6209451 

During upgrade the deploy of portal-webapp fails. 

6209931 

After upgrade (6.3 to 6.3.1) gateway does not start. 

6209932 

psupgrade script prompts to run wcconfig when it is not needed.

6211208 

Portal product name is displayed incorrectly. 

6212866 

Portal Services not loaded during configuration after psconfig with scrubds option.

6212868 

Portal reconfig fails after psconfig with unconfigure.

6213441 

perftune does not pass passwords to amtune.

6214157 

netlet does not load with Java webstart after upgrade.

6214602 

netlet proxy not working after upgrade from Java ES 2004Q2 to Java ES 2005Q1. 

6214609 

WSRP broken on appserver 7.0 after upgrade. 

6216521 

upgradePS script fails to deploy portal.

6218094 

Gateway starts in chroot mode only with debug option.

6218887 

Policy evaluation is disabled in desktop. 

Portal Server SRA Issues

 

6215043 

Deploy fails in interactive mode of portal server SRA configuration. 

Shared Component Issues 

 

6195465 

pkgchk fails for SUNWcacaocfg due to post-installation configuration changes.

Sun Cluster Installation

 

5077985 

JDML and Common Agent Container packages removed with “scinstall —r”

49828710 

SunPlex Manager install module is not supported 

6212471 

Cannot install Sun Cluster HA Administration Server agents from CD 

Web Proxy Server 

 

6265163 

Java ES 2005Q4: Web Proxy Server reinstallation fails 

Localization Issues

 

6234120 

Delegated Administrator: The function of the Available Languages list is not clear 

Uninstallation Issues

 

4994462 

Uninstalling Sun Cluster Console causes locale packages to be removed. 

Linux Issues

 

6197056 

Wrong default installation directory for Web Server and Application Server 

6199933 

Problem installing Directory Server due to broken links to shared components in library 

6279422 

Configuration of Web Server fails on Linux due to missing libtermcap.so.2

6175419 

Cannot install Instant Messaging Server in separate session 

5010533 

Directory Server and Administration Server continue to run after user exits installer 

5052226 

Last page of installer displays Java exception errors after successful installation 

5051946 

Installer takes three to four minutes to display Welcome Page 

Documentation Updates and Errata for Java Enterprise System 2005Q4 

 

6234214 

Incorrect Bug ID in Messaging Server Release Notes 

6225803 

Erroneous instructions regarding comm_sssetup.pl in Messaging Server Administration Guide

Known Issues and Limitations: Installation

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

Miscellaneous Installation Issues

Installation Media Issues

The Java ES 2005Q4 installer is responsible for installing Java 1.5_03 to your system. You will not have to download a later version of Java in order to complete the installation.

Two versions of Directory Server are installed on Solaris 9 systems. When starting or stopping Directory Server you need to specify which version of Directory Server explicitly (for example, 5.2). This task is documented in the Installation Guide.

Also, a Portal Server log issue appears in the Solaris operating system (6267783). If the installer crashes or you interrupt the installation process, you should delete the /tmp/.jes_CaChE directory before restarting the installation process.

In CLI Mode, the Installer does not let you install Portal Server Gateway Alone (6279513)

A key issue is that the installer does not allow you to perform a deployment in the CLI mode because the installer does not allow you to select only the Gateway sub-components.

Solution Use the installer in the GUI mode.

Java ES 2005Q4 Installer needs a mechanism to query if a product license is of type evaluation (6265136)

The installer should check if shared components is an evaluation component and replace it if in fact it is an evaluation component.

Solution Ensure that the workstation does not have an evaluation component installed before beginning an installation.

Problem with IP Address validation for Netlet Proxy (6317592)

In the Netlet proxy panel, the installer does not accept the valid IP address and asks to enter the valid IP address. This problem also occurs in the GUI mode .

Solution Ensure that the /etc/hosts file contains the correct information.

Zone improvement and physical media installation (6298792)

Any Java ES 2005Q4 installation using CD swaps from within zones will fail. Installation into non-global zones from CDs is not supported in Java ES 2005Q4. Specifically, installation of Sun Cluster on a local zone is also not supported.

Installer requests patch that is not applicable on Solaris 9, update 6 (6315304)

When installing build 10 on Solaris 9, update 6 on the install fails because it requires a patch that is not applicable on update 6 (patch 117714–06).

Solution Install the SUNWced and SUNWcedu packages.

Post installation configurator does not copy localization files into the directory where soar.war is deployed (6274056)

The post installation configurator doe not copy the localization files into the directory where soar.war is deployed. The localization packages are installed under /opt/SUNWsoar/webapps/WEB-INF.

Solution After running the install target of configurator as normal the localization packages may be installed by typing the following command:

ant —f build-install.xml install.l10n

Multiple versions of comm_dsetup.pl exist (6226161)

Solution Only use the version of comm_dssetup.pl found in /opt/SUNWcomds/sbin. Ignore all other versions.

FQDN error when installing Messaging Server on Solaris 10 (no issue ID)

When you install Messaging Server on Solaris 10, you get a “hostname not a fully-qualified domain name” error. Solaris 10 supports IPv6. Ipnodes are found in the hostname resolution path.

Solution Manually add the FQDN to both the /etc/hosts and the /etc/inet/ipnodes files.

Insufficient disk space in /share (5099218)

If /share is an automount directory with nothing mounted to it, the installer flags “not enough space on /share “ when Sun Cluster agents are installed.

Solution Unmount /share and run the installer again.

# umount /share

Installer in silent mode does not upgrade some shared component packages (6208244)

When you run the installer in silent mode, SUNWpr and SUNWtls are not upgraded.

Solution Use pkadd to manually install from the Solaris operating system.

Installation log messages are not always valid (no specific ID)

Please note that log messages are not always valid. For example, the “no software was installed” message appears even if some (but not all) component products are installed after an error of some sort.

Mentions of “Sun ONE” in data services should be “Sun Java System” (no specific ID)

All occurrences of Sun ONE in the names and descriptions of the data services for Java ES applications should read “Sun Java System”. For example, “Sun Cluster data service for Sun ONE Application Server” should read “...for Sun Java System Application Server”.

Auto-selection of components in component selection page confusing (4957873)

When a component product is selected, the installer automatically selects to install any dependent component products. The component product selection page does not indicate that the dependencies have been selected along with the original component product.

Solution None.

Selected component notation inconsistent from page to page (5033467)

The “**” to indicate a disabled selection is not implemented globally.

Solution None.

Access Manager Installation

Amconsole home page is not coming up in multinode installations (6291099)

In multinode installations you may find that the Amconsole home page fails to appear. Refer to the solution listed below:

  1. Login to the realm console of the first instance (for example: <first-node-protocol>://<first-node-fqdn>:<first-node-port>/amserver)

  2. Click on the link corresponding to the default realm.

  3. In the text field for “Realm/DNS Aliases”, enter “<node2–fqdn>” and click Add.

  4. Click Save.

  5. Click on the “Realms” link in the bread crumb above the tabs.

  6. Click on the “Configuration” tab.

  7. Click on the “System Properties” tab

  8. Click on the “Platform” service tab.

  9. Under “Instance Name”, click the “New...” button.

  10. In the “Server” field, enter “<node2–protocol://<node2–fqdn>:<node2–port>”.

  11. In the “Instance Name” field, enter an unused number (for example, the number 2).

  12. Click “OK”.

  13. Click “Save”.

Access Manager SDK configuration causes web server startup failure errors (6293225)

The problem of web server startup failures can be attributed to the Access Manager's SDK configuration. In the current scenario, the AMConfig.properties file contains the wrong information and causes a series a web server startup failures. The following variables do not have the correct information:

Solution On your node B, where Access Manager SDK is installed with Web Server, modify the <Web_Server_Instance_dir>/config/server.xml file and add the required Access Manager JAR files to the classpath.

Unable to install Access Manager (using CLI) without Directory Server in a multi-node deployment (6305887)

While installing Access Manager, using the CLI, you may not be presented with a dialog box that provides warning information concerning your configuration. This dialog box does not appear while using the CLI.

Solution Use the graphical user interface (GUI) to install Access Manager.

Installer doesn't add platform entry for existing directory install (6202902)

The Java ES Installer does not add a platform entry for an existing directory server installation (DIRECTORY_MODE=2).

Solution Edit the platform service Server List attribute to add the second instance. For example. if the first instance is host1.example.com, it will have an entry such as http://host1.example.com:port|01. If the second instance is on host2 and uses the same Directory Server as host1, use the Access Manager administrator console to add an entry such as http://host2.example.com:port|02.

Installing Access Manager on an existing DIT requires rebuilding Directory Server indexes (6268096)

To improve the search performance, Directory Server has several new indexes. Therefore, after you install Access Manager with an existing directory information tree (DIT), rebuild the Directory Server indexes by running the db2index.pl script. For example: # ./db2index.pl -D "cn=Directory Manager" -w password -n userRoot

The db2index.pl script is available in the DS-install-directory/slapd-hostname/ directory.

Access Manager registered portal services are not added to user when created through the Access Manager SDK (6280171)

Solution For every user created through the use of the commadmin command line interface, you will need to register all of the missing services with the Access Manager admin console.

Sub-org creation not possible from one Identity Server by using Identity Server amadmin CLI (5001850)

Solution In both Directory Server, make sure to have inside cn=config, cn=ldbm database,cn=plugins, cn=config, nsslapd-lookthroughlimit set to -1.

Console-only install configuration fails (5047119)

The installer does not configure the web container for a console-only installation on a local server.

Solution Perform a console only installation in two separate installation sessions:

  1. In the first installation session, perform a “Configure Now” install of the web container (Application Server or Web Server).

  2. In the second installation session, perform a “Configure Later” install of Access Manager Administration Console.

  3. After the second session is finished, change to the Access Manager utilities directory. For example, on Solaris systems:


    # cd AccessManager-base/SUNWam/bin/

    where AccessManager-base is the Access Manager base installation directory.

  4. Copy the amsamplesilent file and specify a new file name.

  5. Edit the copy of the amsamplesilent file to specific the configuration information, including DEPLOY_LEVEL (2 for console only) CONSOLE_HOST, CONSOLE_PORT, and SERVER_PORT variables.

  6. Run the amconfig script with the edited amsamplesilent file. For example:


    # ./amconfig -s copy-of-amsamplesilent

    where copy-of-amsamplesilent is the name of the copy of the amsamplesilent file.

    For more information about the amsamplesilent file and amconfig script, see the Access Manager 2005Q4 Administration Guide.

pre61to62upgrade script does not handle DB based logging correctly (5042233)

After the Access Manager upgrade process is finished, the upgrade log indicates that the DB based logging was not handled correctly.

Solution None. The current release of the Access Manager upgrade process does not support DB based logging.

Installing Access Manager 2005Q1 With SSL Enabled Directory Server (no Issue ID)

If Directory Server is already installed and has SSL enabled, the installation of Access Manager 2005Q1 will fail. To install Access Manager 2005Q1, first disable SSL for Directory Server. After the Access Manager installation is finished, then re-enable SSL for Directory Server.

Single Quote Not Allowed in Passwords and Root Suffix (no issue ID)

In passwords (such as for amadmin) and the Directory Server root suffix, Access Manager does not support a single quote (\q). The back-slash (\\), however, is supported.

Installation of Access Manager fails if Directory Server 5.1 SP2 implements the Reset Password (4992507)

When you run the Java Enterprise System installer, the installation of Access Manager 2005Q1 fails if Directory Server 5.1 SP2 is configured to require users to change their passwords the first time they log in.

Solution Set the Directory Server password reset policy to “off”.

Administration Server Installation

Possible security exposure via HTTP administration interface (6252097)

The HTTP administrator interface and related files may be susceptible to DOS attacks.

Solution It is recommended that you temporarily remove the help.exe file until a fix is available. Also, do not run Administration server as a privileged system user. It is also recommended that you firewall and filter Administration Server access to allow trusted hosts only.

Deployment on Administration Server 8.1 with non-default URIs is inaccessible (6308426)

If you install Access Manager 7.0 on Application Server 8.1 and choose non-default URIs for Access Manager (for example, idserver instead of amconsole and idconsole instead of amconsole). Specifically, in the amas81configfile, the configureServerPolicy() does not account for the use case in which Access Manager is being configured with default URIs. Instead it assumes that the Access Manager war files will be deployed with the default URIs and grant permissions to amserver.war, amconsole.war, and ampassword.war.

Solution Perform the following procedure:

  1. Stop the application server instance on which Access Manager was deployed.

  2. Change to the following directory: ${AS_DOMAINS_DIR}/${AS_DOMAIN}/config

  3. Type the following command: cp server.policy server.policy.orig

  4. Locate the following policies grant codeBase: "file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/amserver/-" { permission java.net.SocketPermission "*", "connect,accept,resolve"; permission java.util.PropertyPermission "*", "read, write"; }; grant codeBase "file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/amconsole/-" { permission java.net.SocketPermission "*", "connect,accept,resolve"; permission java.util.PropertyPermission "*", "read, write"; }; grant codeBase "file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/ampassword/-" { permission java.net.SocketPermission "*", "connect,accept,resolve"; permission java.util.PropertyPermission "*", "read, write"; };

  5. Replace "amserver" with the URI for the services web application in the line grant codeBase "file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/amserver/-" {

  6. For legacy mode installations, replace "amconsole" with the URI for the console web application in the line grant codeBase "file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/amconsole/-" {

  7. Replace "ampassword" with the URI for the password web application in the line grant codeBase "file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/ampassword/-" {

  8. Start the application server instance on which Access Manager was deployed.

Administration Server patch fails to apply when server is stopped (6273652)

When stopping the Administration Server and using patchadd to apply a patch the process fails.

Solution You must start the Administration Server before applying the patch.

Application Server Installation

Java ES 2005Q4 Promoted build 08 shows incorrect Application Server Name ( 6297837)

Sun JavaTM System Application Server Enterprise Edition 8.1 2005Q2 Update 2 is the correct notation. The notation Sun JavaTMSystem Application Server Enterprise Edition 8.1 2005Q4 was in error.

Installer does not recognize host name user enters in configuration page (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.

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

# find . -type f -exec grep -l $HOSTNAME {} \\ ;

Then, change the file contents appropriately.

Calendar Server Installation

Calender Server does not work with HA (Sun Cluster) on Solaris 10 without patch 120500–02 (6308379)

Solution Install patch 120500–02.

Directory Server Installation

Slow DPS response causing exceptions in web server and system instability

When too many connections are established to the DPS server from a remote node, the DPS response is slow and exceptions are thrown.

Solution None

Directory Server Agent package SUNWdsha for Sun Cluster needs separating from Directory Server patch (6198729)

Since the agents are separate products, they should have patches that can be applied stand-alone to the agents' products.

Solution None.

Directory Server configuration output splits the progress bar on silent mode (4928102)

When components are configured the corresponding output is sent to the installer's stdout instead of the log. This action places the CLI progress bar on multiple lines in the installer output.

Solution None

Cannot configure Directory Server if you reinstall after uninstalling (6223527)

You cannot configure Directory Server if you are reinstalling after having uninstalled. During the uninstall, /var/opt is not removed. As a result, the Directory slapd is not found and there are errors logged when you try to start Directory Server.

Solution After uinstalling Directory Server, remove /var/opt before you reinstall.

Cannot install Directory Server and Administration Server in separate sessions (5096114)

If you install Directory Server in one session and then try to install Administration Server in a second session, the box for Administration Server is already checked even though it is not installed and configured. You therefore cannot install and configure Administration Server.

Solution Install Directory Server and Administration Server in the same session. Or, refer to the Directory Server Administration documentation to learn how to manually configure Administration Server.

Message Queue Installation

If Message Queue is installed with Java ES installer you must use uninstaller to uninstall (no issue ID)

If you remove the Solaris packages directly, the next time the installer is run, it may see Message Queue as still being installed and not behave correctly.

Solution If you have already removed the Message Queue packages manually, you must uninstall Message Queue using the uninstaller. Run the uninstaller and select Message Queue components for removal.

Messaging Server Installation

The default factory is different in Java ES 2004Q2 and Java ES 2005Q1 (6200472)

Existing deployments who do not wish to upgrade the server will have to explicitly set the property of collaboration session factory object to use the Legacy protocol implementation. In the API place the following constructor to create a ColloaborationSessionFactor: CollaborationSessionFactory factory = newCollaborationSessionFactory(“com.iplanet.im.client.api.ilMSessionFactory”);

Problem installing Messaging Server and Directory Server on different machines (no specific ID)

Solution

ProcedureTo install Messaging Server and Directory Server on different machines

Steps

  1. Install and configure Directory Server and Administration Server on the directory system.

  2. Install Administration Server and Messaging Server on the Messaging system. Administration Server can be configured during the installation, but Messaging Server cannot.

  3. Configure Messaging Server.

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

In order to use Messaging Server with Schema 2 support, you must install Access Manager and Directory Server.

Solution Currently, the only way to get Schema 2 support into Directory Server is to install Access Manager.

Access Manager also requires Web Server (or Application Server) to act as its web container. If Access Manager 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, Access Manager must be installed to update Directory Server.

Portal Server Installation

(Solaris and Linux) Portal Server upgrade failing — cannot find /opt/SUNWappserver7/bin/asadmin (6313972)

Solution Refer to the following publication for the latest upgrade documentation regarding this issue:

Sun Java Enterprise System 2005Q4 Upgrade Guide

SRA init scrips try to run /etc/init.d/cron (6300415)

Solution On a Solaris 10 system, after starting the gateway watchdog process, issue the command:

#svcadm restart cron

Application Server log contains Java exceptions, but install is successful (6320674)

The following exceptions may appear in the Application Server log during Portal installation:

java.lang.ClassNotFoundException: com.sun.mobile.filter.AMLController

Solution This is normal.

Portal Server Upgrade from Java ES 2005Q1 to Java ES 2005Q4 (redeploy) not working — waiting for a key “Y” (6309079)

When upgrading Portal Server from Java ES 2005Q1 into Java ES 2005Q4, using docs Sun Java Enterprise System 2005Q4, Upgrade Guide, July 29, 2005, command deploy does not work. This bug also applies to Administration Server and Access Manager. The bug only occurs when the file $HOME/.asadmintruststore is not present.

Solution Press “Y” and the Enter key, if command “deploy redeploy” stops and the question “Do you trust the above certificate [y/n] appears in a log (/var/opt/SUNWam/debug/deploy.log).

(Solaris and Linux) 10WS, Gateway Redirection is not happening in Multisession installation (4971011)

Solution Launch a browser to access the amconsole. Under the Service Configuration tab, choose gateway. In the right-bottom corner of the web page, choose the default link then choose the security tab. Add URL like "http://IS_HOST:PORT/amserver/UI/Login" into the Non-authenticated URLs: field. For example: http://boa.prc.sun.com:80/amserver/UI/Login. Next, restart gateway using the following command: /etc/init.d/gateway -n default start debug.

Certificates expire on Portal Servers which use JCE 1.2.1 package (6297953)

Current Portal Servers still use JCE 1.2.1 packages which expire on July 27th, 2005.

Solution Although this issue exists for all Java ES releases from Java ES 2003Q4 to Java ES 2005Q4 and the JCE 1.2.1 files appear in the distribution, the files are not being used and will not affect Java ES 2005Q4.

Invalid shell syntax in remove_Wireless process (6301677)

The remove_Wireless process fails during Portal Server unconfigure operation (psconfig and unconfigurewithscrubds).

Solution Edit the remove_Wireless file and comment out the empty if statement. An example is shown below:

#Perform web container specific un-config

#

#if [ “$DEPLOY_TYPE” == “IWS” ]; then

#elif [ “$DEPLOY_TYPE” = “SUNONE” ]; then

#fi

Unable to stop Gateway in two host scenario (6283068)

Solution To start the gateway type ./gateway start -n default. In order to stop the gateway type /gateway stop -n default.

Portal Server Gateway login after Portal Server restart (6191449)

A fix is available in patches 118950–14 (Solaris SPARC), 118951–14 (Solaris/x86), and 118952–14 (Linux).

Solution Each time the Portal Server, Administration Server or Web Server is restarted, the gateway must also be restarted. Enter gateway stop to stop the server and gateway start to start the server.

Login page is not downloaded through proxylet (6216514)

When the proxylet is enabled, SRA still uses the rewriter technology to fetch the login pages and a part of the desktop page before the proxylet starts.

Solution None

Exception thrown after reloading Portal Desktop (218871)

Launching the instant messaging link and refreshing the portal desktop causes the “ERROR: content is not available” to appear. Also, an exception is thrown in this file:

/var/opt/SUNWam/desktop.debug.

Solution Edit the domain.xml file (located in /var/opt/SUNWappserver/domain1/config and perform the following

Modify the Java configuration classpath-prefix with /usr/share/lib/jaxen-core.jar

Type stop-domain domain1

Type asadmin start-domain

Enter your user name and password.

Help file link doe not work for iFrameprovider on the desktop (6199105)

Clicking on the help icon from the SampleIFrame Channel produces “HTTP Status 404 — /portal/docs/en/desktop/iframechann.htm” is not available.

Solution None. No help is provided with iFrame provider.

Installation and uninstallation of Portal Server appears to hang (5106639)

During installation and uninstallation of Portal Server, the installer and uninstaller appear to hang. The delay can be up to 30 minutes before installation/uninstallation finishes successfully.

Solution None.

Gateway redirection not happening in any multi-session installation (4971011)

Regardless of the installation mode, gateway redirection does not occur during a multi-session installation.

Solution

ProcedureTo enable gateway redirection

Steps

  1. Launch a Portal Server browser and access the amconsole.

  2. Under “Service Configuration” tab, select “gateway”.

  3. In the lower right corner of the window, click “default” and “security” tab as well.

  4. Then, add a URL like “http://IS_HOST:PORT/amserver/UI/Login” into “Non-authenticated URLs:” field.

    An example URL is http://boa.prc.sun.com:80/amserver/UI/Login.

  5. Finally, restart the Portal gateway by doing the following as superuser:


    # /etc/init.d/gateway -n default start debug

Shared Component Issues

metaslot needs to return CK_EFFECTIVELY_INFINITE in token info(6276483)

This bug can cause failure of the Java Enterprise System common agent container.

Platform/Architecture: This bug only occurs with the Solaris 10 system running on the x86 architecture or the SPARC architecture and with the Java 2 Runtime Environment, Standard Edition 1.5. Depending on cryptoadm configuration you have, the common agent container could fail on a Solaris 10 system when you open an SSL connection.

Solution Run the following command as root: crypto disable metaslot.

MFWK 1.0 mfwkadm stop and undeploy does not work with Common Agent Container 1.1 build 10 (6262977)

Common agent container displays the version number after the module number.

Solution Two workarounds are available. (1) Stop common agent container (this stops all common agent container modules, including the JesMF module and its dependant modules). (2) Alternatively, you can also use common agent container admin commands to manually undeploy modules that have dependencies on JesMF and then undeploy the JesMF module.

Installer does not upgrade Apache Tomcat 4.0.1 to Apache Tomcat 4.0.5 (6202992)

The installer does not upgrade the SUNWtcatu package.

Solution Before commencing with installation, manually remove SUNWtcatu using pkgrm. Then, when you run the installer, the correct package version for Tomcat 4.0.5 is installed.

Sun Java Web Console set-up script does not upgrade SUNWtcatu package (6202315)

Solution Before commencing with installation, manually remove SUNWtcatu using pkgrm.

Sun Cluster Installation

Updated P2 Common Agent Container/doc Package dependency change from 1.0 to 1.1 causes installation problems

In the Sun Cluster 3.1 8/05 Installation Guide, the instruction for adding common agent container packages in the “How to Upgrade Dependency Software” sections for rolling and non-rolling upgrade is correct only for the common agent container distributed in SC31U4 IFR. The procedure is incorrect for the common agent container shipped in Java ES 2005Q4. For the common agent container shipped in Java ES 2005Q4, the correct instruction should be:

pkgadd —d . SUNWcacaocfg SUNWcacao

Sun Cluster HA Application Server Agent does not support Application Server 8.1 and HADB 8.1 (6212333)

The installer gives you the option of choosing to install the Sun Cluster HA Application Server Agent with Application Server and HADB 8.1. However, the HA Application Server Agent does not support Application Server and HADB 8.1. As a result, you cannot configure HA Application Server.

Solution Do not install the HA Application Server Agent with Application Server and HADB 8.1.

Sun Cluster Data Services for previous versions of Directory Server (no issue ID)

Java Enterprise System 2005Q1 includes the Sun Cluster Data Service for the Sun Java System Directory Server 5 2004Q2. If you need the Sun Cluster Data Service for Sun Java System 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 (no issue ID)

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 allow for additional Sun Cluster agents to be installed if one exists on system (no issue ID)

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.

Solution Install additional Sun Cluster Agents using pkgadd.

Web Server Installation

Web Server installation fails if install directory is populated with files from a previously installed version (no issue ID)

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

Web Proxy Server Issues

Web Proxy Server fails to configure through common installer (6322036)

When startup on boot enabled, after successfully installing Web Proxy Server the installation summary report states that the installation and configuration failed.

Solution Configure the Web Proxy Server after the installation is complete.

Localization Issues

Custom Configuration installer screen sometimes displays with crippled text layout (6210498)

Solution Resize the window. Then, click Back and Next. The window will display correctly.

Cannot use configure later option when installing on all locales (6206190)

Using the configure later option when installing on all locales results in a number of broken links for the SUNWasuee package.

Solution Add the localization packages manually after installation.

Known Issues and Limitations: Uninstallation

Uninstaller hangs and does not remove all packages ( 5091416)

If the installer is interrupted during an install, you cannot restart the installer or run the uninstaller. Even if certain packages have been installed successfully, the installer does not recognize them.

Solution Manually remove all remaining packages, directories and files from the previous installation of Java Enterprise Systems.

Known Issues: Linux

Required Libraries

Linux requires the following compatibility libraries:

If you are running 64-bit Linux, you must install the system libraries for 32-bit Linux.

JVM problems occur when running Access Manager on Application Server (6223676)

When Sun Java System Applications Server 8.1 2005Q2 Update 2 is installed on systems running Red Hat Linux AS 2.1 or 3.0, the stack size of the threads created by the Red Hat AS operating system for Application Server is 10 MB. However, when the number of Access Manager user sessions reaches 200, this stack size causes resource contention, and the JVM either crashes or hangs.

Solution Set the stack size to 256 KB by executing the following command on the console used to start Application Server:

# ulimit —s 256;

Linux unable to configure UWC (6280944)

While configuring UWC on the Linux 3.0 platform all configuration tasks are completed except for one.

Solution In order to prevent this inconsistent behavior from occurring, perform the following tasks:

1. cd to /var/opt/sun/uwc/staging.

2. Type ls —l to display the directory contents.

3. If you self reference a symbolic link, be sure to delete it before proceeding to the next step.

4. Type ./config-appserver8x deploy.

CLI installation: When user clicks backspace key, password becomes visible (6285944)

During the installation process you are prompted to enter your password. If you click the backspace key your password becomes visible (minus the last character).

Solution None.

Ant installed by Java ES 2005Q4 crashes with NoClassDefFoundError on Linux (6283794)

JAVA_HOME is not defined correctly. This error prevents Ant from loading. This also prevents SOAR from loading since it requires Ant.

Solution In the Ant script change line 19 from no_config=false to noconfig=true.

Ant Configuration Files Issue (no issue ID)

Ant 1.6.1. (bundled with Java ES 4) searches for the following configuration files:

/etc/ant.conf

${HOME}/.ant/ant.conf

${HOME}/antrc

In order for Ant to work in Java ES correctly it needs to ignore the settings in the above listed configuration files and use the settings provided by Java ES. In order to do this, you are requested to perform the following workaround:

Solution (1) use –noconfig with ant (ant –noconfig <your command>)

Solution (2) Remove /etc/ant.conf

Notice regarding Linux update releases

Java Enterprise System developers have tested with Red Hat 2.1U2 and 3.0U1. We cannot guarantee that there are no issues with later releases. Please contact your service representative for further information.

tcp_smtp_server core under stress (6274560)

During STH stress testing tcp_smpt_server produces a core dump.

Solution None.

If Message Queue is installed with Java ES installer you must use uninstaller to uninstall (no issue ID)

If you remove the Linux RPMs directly, the next time the installer is run, it may see Message Queue as still being installed and not behave correctly.

Solution If you have already removed the Message Queue RPMs manually, you must uninstall Message Queue using the uninstaller. Run the uninstaller and select Message Queue components for removal.

Cannot configure Directory Server on Red Hat Linux 3.0 (5087845)

During installation, the required shared library, compat-libstdc++-7.3-2.96.122 RPM is not installed. Without the RPM, Directory Server cannot be configured.

Solution Manually install the RPM from the distribution CD.

Uninstaller RPM not always installed during installation (5060658)

Sometimes when a component product is installed, one of the necessary RPMs for the uninstallation, sun-entsys-uninstall-l10n-2.0-1, does not get installed.

Solution Manually install the missing uninstall RPM by doing the following:

# rpm -i sun-entsys-uninstall-2.0.i386.rpm

After installing the RPM, the uninstall script will appear.

Message Queue’s C-API usage of NSPR and NSS on Linux (no issue ID)

In the Linux release of Java Enterprise System, Message Queue delivers its own copies of the NSPR (Netscape Portable Runtime) and NSS (Network Security Services) libraries. The versions installed with Message Queue are older than the versions installed by Java Enterprise System.

If Message Queue was installed in the default location, the older libraries are found in /opt/imq/lib. If you build a Message Queue C application the Message Queue C runtime library (mqcrt.so) links against the older NSPR and NSS libraries in /opt/imq/lib. While this is a supported and tested combination, it is recommended that you use the newer versions installed by Java Enterprise System in /opt/sun/private/lib.

To use the newer versions of the libraries, set the LD_PRELOAD environment variable to:

/opt/sun/private/lib/libnspr4.so:\\
/opt/sun/private/lib/libplc4.so:\\
/opt/sun/private/lib/libplds4.so:\\
/opt/sun/private/lib/libnss3.so:\\
/opt/sun/private/lib/libssl3.so

before running your Message Queue C application.

Last page of installer displays Java exception errors after successful installation (5041569)

Even if installation was successful, the last installer page lists several Java exceptions and does not display a successful installation message.

Solution Ignore the error and look at the logs in /var/sadm/install/logs. The logs will reveal if the installation was successful or not.

Insufficient window width in interface for some locales (4949379)

The window for certain languages like German is not wide enough to display the entire interface. As a result, text of elements like hints get truncated at the right hand side or at the bottom.

Solution Manually resize the window.

Support for Netscape Security Services 3.9.5

Version 3.9.5 of the Netscape security libraries are included in Java Enterprise System. Directory Server, Directory Proxy and Administration Server may depend on the older version (3.3.x) of these libraries also installed under /usr/lib/mps/ while all other component products that depend on these libraries depend on the newer version (3.9.5) installed under /usr/lib/mps/secv1/.

Documentation Updates and Errata for Java Enterprise System 2005Q4

Sun Cluster 3.1 8/05 Installation Guide

In the Sun Cluster 3.1 8/05 Installation Guide, the instruction for adding common agent container packages in the “How to Upgrade Dependency Software” sections for rolling and non-rolling upgrade is correct only for the common agent container distributed in Sun Cluster 3.1 8/05.

The procedure is incorrect for the common agent container shipped in the Java ES 2005Q4, the correct instruction should be pkgadd —d . SUNWcacaocfg SUNWcacao.

Redistributable Files

Sun Java Enterprise System 2005Q4 does not contain any files that you can redistribute.

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.

To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the title of this book is Java Enterprise System Release Notes, and the part number is 819-2329.

Additional Sun Resources

Useful Sun information can be found at the following Internet locations: