Sun Java logo     Previous      Contents     

Sun logo
Sun Java Enterprise System 2005Q1 Release Notes 

Sun Java Enterprise System Release Notes

2005Q1

Part Number 819-0057-11

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

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/coll/entsys_05q1. 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.

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

Component Release Notes

The following component release notes can be found at: http://docs.sun.com/coll/entsysrn_05q1

Third-party URLs 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.

Release Notes Revision History

Table 1  Revision History 

Date

Description of Changes

April 2005

Deprecation Notices; Messaging Server issues; Documentation errata

February 2005

revenue release version

November 2004

beta version

About Java Enterprise System 2005Q1

This section includes:

What’s New in This Release

System Level

For detailed information on the following, refer to the respective Release Notes, all of which can be found at: http://docs.sun.com/coll/entsysrn_05q1

Table 2  New Features in Java Enterprise System Components 

Component Product

Features

Access Manager

  • Product name has changed from Identity Server to Access Manager
  • Support for new web containers: BEA WebLogic 8.1 SP2 and IBM WebSphere Application Server 5.1
  • New authentication modules: Java Database Connectivity (JDBC), Mobile Station ISDN, (MSISDN), Active Directory, and Security Assertion Markup Language (SAML)
  • Policy Management includes a new Resource Name plug-in: HttpURLResourceName

Console enhancements:

  • Ability to customize the view of each object type in the navigation pane by displaying one or more of the attributes of the object
  • Ability to add new object types in the navigation pane drop-down menu (for example, adding an entry for printers or buildings

 

Federation Management:

  • Support for the Liberty Alliance Project (LAP) Name Identifier Mapping Protocol
  • Support for the LAP Identity Web Services Framework (ID-WSF) Discovery Service Specification, Version 1.1
  • Support for the LAP ID-WSF Authentication Service Specification
  • Support for the LAP Metadata Description and Discovery Specification
  • Support for the LAP Liberty Identity Federation Framework (ID-FF) Extended Profiles:
  • Dynamic Identity Provider Proxying
  • Affiliation Federation
  • One-time Federation
  • Name Identifier Mapping Profile
  • Name Identifier Encryption Profile

Client SDK:

  • Repackaged SDK (Authentication, Service Management, User Management, SAML, Policy Client, and Session components) so that Java application developers can better integrate with Access Manager
  • Removed the dependency on the serverconfig.xml file and minimized the footprint of the jar files

Performance tuning script is available to tune Application Server 8.1 as a web container

Administration Server

  • No new features

Application Server

  • JSEE 1.4 support
  • High performance and scalability
  • High availability
  • JavaServer Faces 1.1 support
  • JavaServer Pages Standard Tag Library 1.1 support

Calendar Server

  • Automatic Backups - csstored is now a service that starts up when start-cal is issued. It must be configured to function properly
  • Read-only database - You can configure Calendar Server to only allow reads but no updates or deletions to your calendar databases. This is recommended when data corruption is suspected but you need to keep your databases available for production work. No updates or deletions are accepted during this time
  • User Management Utility Name Change - The User Management Utility (command-line utility) is now called the Delegated Administrator Utility
  • Delegated Administrator GUI - There is a new Delegated Administrator GUI, but it does not support Calendar Server for the 2005Q1 release
  • Installation Changes for Directory Preparation Script - This post-installation configuration program is now a separately installable component in the Java Enterprise System Installer. It is no longer bundled in the installation of Calendar Server

Directory Proxy Server

  • No new features

Directory Server

  • In versions of Directory Server prior to Directory Server 5.2 2005Q1, you could not rename an entry. With Directory Server 5.2 2005Q1 you can rename and move an entry.
  • Extension of the retro change log to identify the order in which updates are made for each replica

Instant Messaging

  • Updated and Improved Instant Messaging Client
  • XMPP, the IETF instant messaging and presence standard protocol
  • Enhanced Monitoring features
  • Monitoring Via the watchdog Utility
  • Determining the Status of the watchdog Utility
  • Starting and Stopping the watchdog Utility
  • Monitoring the Instant Messaging Server

Message Queue

  • New Technical Overview
  • Reorganized Administration Guide
  • Reorganized Developer Guide for Java Clients
  • Reorganized Developer Guide for C Clients
  • Changes in Linux Installation:
  • New RPM names
  • New Install Location
  • Dead Message Queue
  • No Acknowledgement Mode
  • Connection Failure Detection (Client Ping)
  • Client Message Body Compression
  • JMS Resource Adapter Changes
  • 64-bit C-API support
  • Deprecation of -p/-password Command
  • C-API Certificate Management
  • C-API Basic Authentication Support
  • New Sample Application, MQPing

Messaging Server

  • Sun Java System Communications Services 6 2005Q1
  • Secure/Multipurpose Internet mail Extension (S/MIME), supported by Sun Java System Communications Express Mail
  • Support for anti-spam/anti-virus programs that work with the Internet Content Adaptation Protocol (ICAP)
  • Enhanced logging

Portal Server

No new features

Sun Cluster

  • Ability to Change Global Heartbeat Parameters
  • SPARC: Support for VxVM 4.0 and VxFS 4.0
  • Support for Common Agent Container
  • Changes to the JumpStart Installation Method
  • scversions Command
  • 16–Node Support
  • IPv6 Support for Data Services
  • Enhanced Inter-Resource-Group Dependencies and Inter-Resource Dependencies
  • Ability to Modify Online HAStoragePlus Resources
  • SPARC: Support for Solaris Volume Manager for Sun Cluster With Sun Cluster Support for Oracle Real Application Clusters
  • SPARC: Support for Sun StorEdge QFS With Sun Cluster Support for Oracle Real Application Clusters
  • SPARC: Automated Startup and Shutdown of Oracle Real Application Clusters Instances
  • New Supported Data Services (SPARC Platform Edition)

Web Server

No new features

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 

Operating System

Disk Space

RAM

Solaris SPARC (Ultra Enterprise™ 250)

6096 Mbytes

4096 Mbytes

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

6096 Mbytes

4096 Mbytes

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

6096 Mbytes

4096 Mbytes

The following table lists the requirements for the various components.

Table 4  Component Disk Installation Space and RAM Requirements 

Component

Minimum Disk Space and RAM Requirements for Installation

Access Manager

250 Mbytes disk space for Access Manager and associated applications; 512 Mbytes RAM

Administration Server

50 Mbytes 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

Application Server

with Sun Java System Studio: 500 Mbytes of disk space; 512 Mbytes RAM

Calendar Server

1 Gbytes of disk space for production deployment or 500 Mbytes for an evaluation; 256 Mbytes to 1 Gbytes of RAM for production or 128 Mbytes RAM for an evaluation

Directory Server

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

Directory Proxy Server

300 Mbytes of disk space; 256 Mbytes of RAM

Instant Messaging

300 Mbytes of disk space; 256 Mbytes RAM

Messaging Server

1 Gbytes for production deployment or 500 Mbytes for evaluation installation;1 Gbytes RAM for production systems or 256 RAM for evaluation installation

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

Message Queue

8 Mbytes of disk space; 128 Mbytes RAM

Portal Server, Portal Server SRA

1 Gbytes of disk space; 1.2 Gbytes RAM for production deployment or 512 Mbytes for an evaluation

Sun Cluster 3.1 9/04 (per node)

512 Mbytes of disk space for swap space, 512 Mbytes for a /globaldevices partition, and 20 Mbytes for Volume Manager; 128 Mbytes RAM plus ten percent of a node’s regular memory requirement

Web Server

256 Mbytes of disk space; 64 Mbytes RAM

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

Solaris Software Group Requirements

Installation of the Java Enterprise System requires the ALL and OEM software groups.

Java 2 Standard Edition Requirements

Java Enterprise System is certified with Java™ 2 Platform, Standard Edition (J2SE™ platform) 1.5_01 from Sun Microsystems.

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

If your system already has J2SE 1.5_01 runtime environment package SUNWj5rt, installed without the J2SE 1.5_01 development tools package, SUNWj5dev, 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/819-0056 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.

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. The following is a summary of the three steps you must take.

  1. Gather Information about the J2SE Installation. (See To Gather Information About the J2SE Installation.)
  2. Determine whether you need to update the J2SE Installation. (See To Determine if an Update to J2SE is Required.)
  3. If needed, update the J2SE installation used by Java Enterprise System.

    4. How you update the installation depends on the location of the J2SE installation used by Java Enterprise System:

  To Gather Information About the J2SE Installation
  1. Inspect the symbolic link /usr/jdk/entsys-j2se to determine the location of the J2SE installation used by Java Enterprise System:

    2. # ls -l /usr/jdk/entsys-j2se

  2. Note the location the link points to /usr or /usr/jdk/.j2se1.5.0_01 for example.
  3. Determine the version of the J2SE installation used by Java Enterprise System:

    4. location/j2se/bin/java -fullversion

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

  4. Note down the version number.
  5. Use the pkginfo command to gather information about the instances of each J2SE package required by Java Enterprise System. These packages are:

    6. SUNWj5dev     SUNWj5man     SUNWj5rtx
    SUNWj5dvx     SUNWj5jmp
    SUNWj5dmo     SUNWj5rt

    Note

    The packages SUNWj5dvx and SUNWj5rtx are required only for 64-bit support, and the package SUNWj5jmp is required only for Japanese man page support.

    For each of the required packages, do the following:

    1. Display information about all instances of the package:

      2. # pkginfo -l pkgname.*

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

    2. 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, SUNWj5dev.2 and SUNWj5jmp (without the .2 instance specifier) can both have a BASEDIR of /usr/jdk/.j2se1.5.0_01 What connects the packages of an installation of J2SE is the BASEDIR, not the package instance number.

  To Determine if an Update to J2SE is Required

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:

  To Update the J2SE Installation in /usr
  1. If you are not logged in as superuser, use the su command to become superuser.
  2. If the Java Enterprise System 2005Q1 distribution is not accessible on your network or on the system, insert the distribution CD or DVD.
  3. Navigate to the directory in Java Enterprise System 2005Q1 distribution that contains the J2SE packages:

    4. # cd dist-base/Solaris_arch/Product/shared_components/Packages

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

  4. Shut down services that depend on J2SE.
  5. Set your system to single user mode.
  6. Use the pkgrm command to remove the package instances you noted down in Step 5 as existing and having /usr as the BASEDIR. Remove the package instances in this order:

    7. 1. SUNWj5rtx
    2. SUNWj5dvx
    3. SUNWj5jmp
    4. SUNWj5dmo
    5. SUNWj5man
    6. SUNWj5dev
    7. SUNWj5rt

    For example:

    # pkgrm SUNWj5dmo SUNWj5man SUNWj5dev SUNWj5rt

  7. Add the packages for the version of J2SE that has been certified with Java Enterprise System 2005Q1:

    8. # pkgadd -d . SUNWj5rt SUNWj5cfg SUNWj5dev SUNWj5man SUNWj5dmo SUNWj5dvx SUNWj5jmp SUNWj5rtx

    The packages SUNWj5dvx and SUNWj5rtx are required only for 64-bit support while the package SUNWj5jmp is required only for Japanese man page support.

  8. Restore your system to multiuser mode.
  9. Start services that depend on J2SE.
  To Update the J2SE Installation in Another Location
  1. If you are not logged in as superuser (root), use the su command to become the superuser.
  2. Create a customized installation administration file to specify the non-default installation location of J2SE:
    1. Make a copy of the default installation administration file:

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

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

      3. basedir=default

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

      basedir=/usr/jdk/.j2se1.5.0_01

      Do not change any other values in the file.

  3. If the Java Enterprise System 2005Q1 distribution is not accessible on your network or on the system, insert the distribution CD or DVD.
  4. Navigate to the directory in Java Enterprise System 2005Q1 distribution that contains the J2SE packages:

    5. # cd dist-base/Solaris_arch/Product/shared_components/Packages

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

  5. Shut down Java Enterprise System services that depend on J2SE.
  6. Use the pkgrm command to remove the package instances you noted down in Step 5 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:

    7. 1. SUNWj5rtx
    2. SUNWj5dvx
    3. SUNWj5jmp
    4. SUNWj5dmo
    5. SUNWj5man
    6. SUNWj5dev
    7. SUNWj5rt

    For example:

    # pkgrm SUNWj5rtx SUNWj5dvx SUNWj5jmp SUNWj5dmo.2 SUNWj5man.2 SUNWj5dev.2 SUNWj5rt.2

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

    8. # pkgadd -a /tmp/admin-file -d . SUNWj5rt SUNWj5cfg SUNWj5dev SUNWj5man SUNWj5dmo SUNWj5dvx SUNWj5jmp SUNWj5rtx

    The packages SUNWj5dvx and SUNWj5rtx are required only for 64-bit support while the package SUNWj5jmp is required only for Japanese man page support.

    Start Java Enterprise System services that depend on J2SE.

Deprecation Notices

Unsupported Features

Important Patch Information

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

In addition, visit http://sunsolve.sun.com and go to “Recommended Patch Clusters” and then choose“Java Enterprise System Component Patches” from the drop-down menu. As operating system 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.

Bugs Fixed in This Release

The table below describes the bugs fixed in Java Enterprise System 2005Q1:

Table 5  Bugs Fixed in this Release 

Bug Number

Description

Miscellaneous Installation Issues

5077683

Some installation directories not accessible

5104637

Failed installation of shared components causes subsequent failures

5105238

Defaults not selected while installing Access Manager on Application Server

6176619

Installation summary report page not complete

6179041

slapd process runs after installation is complete

5041865

Erroneous message about need to upgrade uninstaller

5032211

Access Manager values required for Portal Server installation

4932843

Directory Server and Administration Server installation fails due to insufficient disk space

5073647

Explorer component not configured by installer

6179707

Installation of Application Server, Web Server and Directory Server fails in Configure-Later mode

6183147

Problems installing Directory Server and Application Server on multi-node environment

6184053

Component selection page has incorrect versions of components

6178450

Installer cannot upgrade SUNWjhrt on Solaris 9

5110186

Installer detects wrong version of Message Queue

6179033

Installation fails on Solaris 8

6173840

Problems upgrading to J2SE 1.5_01

5041686

Installation Guide button on last page not working

4918824

Installer does not detect partially installed product packages

4922208

Installer ‘welcome page’ launches without Next button

4944839

SUNWj3dmx package not upgraded by the installer

Access Manager Installation

5087959

Installer requires Web container if Access Manager SDK is selected with Portal Server

5067574

Installer cannot install Access Manager with a FQDN with a single dot

6174728

SPARC binaries installed on x86

5110360

Mixed case root suffix causes a problem accessing Access Manager login

6178827

After Access Manager installation on Opteron, Web Server startup output contains JSS related warnings

6174728

Cannot write new C applications for Access Manager on x86

6176934

Cannot install subset of Access Manager sub-components

5045635

Installer does not use values for existing console

5022925

Special characters not allowed in password for Access Manager

5035811

amadmin CLI configuration scripts expect UNIX utilities in PATH

5038433

Portal Server on third-party web container cannot co-exist with Access Manager on same host

5043294

Web application failed to deploy if Application Server admin protocol is HTTPS

5045555

After Directory Server configuration fails, user cannot process with uninstall

5045680

Installation fails due to non-existent Web Server user and group

5046393

Existing console install fails because is.state file is missing passwords

5047710

Cannot install Access Manager console without Directory Server

5041968

Cannot upgrade Access Manager (Identity Server) to Java Enterprise System 2004Q2

5048259

If Application Server is not running, upgrade of Access Manager fails

4959541

Cannot access one Access Manager (Identity Server) administration server console when two point to Directory Server

5013453

Installation over an existing DIT creates security hole

5013600

During remote SDK installation, protocol host name and port are not requested

4928865

Using non-root runtime user causes Access Manager to fail

4933712

Running Web Server instance as nobody/nobody causes Access Manager to fail to deploy on Web Server

Administration Server

4984359

*.ldif files missing after installation of Administration Server

5086071

Missing resource file type for Administration Server

5088607

Installer does not configure Administration Server on Solaris 10

Application Server Installation

5043333

Installer hangs if admin protocol is HTTPS

6185306

Installation fails on Solaris 10

5079673

HADB does not work

6180399

Application Server stops due to file system full

5096295

Cannot execute commands remotely

5099421

Conflicting packages not detected

5081076

Cannot configure Application Server on Solaris 10

Calendar Server Installation

5013230

“Calendar Not Available” error generated by Universal Web Client

Directory Server Installation

6175580

Cannot configure Directory Server on Solaris 10

6177788

JDK files not found

Instant Messaging Installation

6182423

Necessary components not selected; installer hangs

Message Queue

5060892

Installation error for Message Queue

6186336

Installer does not detect old version of Message Queue

Messaging Server Configuration

5015614

Cannot share a single Messaging Server configuration between multiple nodes in an HA environment

4946314

Cannot access Messaging Server in High Availability environment

Portal Server Installation

6179802

Launch Mail link does not work

6179806

Communications Services Express Calendar not displayed

6179807

Communications Services Express Calendar not displayed

Portal Server SRA Issues

5047334

Portal Server Mobile Access upgrade not supported on Application Server

4929710

Calendar links not accessible via Portal Server SRA

Web Server Configuration

4756206

Error message on admin console displays after user login

Sun Cluster Installation

5109313

SUNWscspmr not installed properly

6180646

Problems with SunPlex Manager due to missing SUNWjato

Localization Issues

6177339

GUI installer missing upgrade JDK page

5053554

Must use root/root when installing Web Server in Korean locale

4855688

Application Server locale entry of server.xml is always in en_US

5026804

Bad layout in “custom configuration” window for all UTF-8 locales

5011497

Access Manager installation fails in non-English locales

Uninstallation Issues

6180345

Uninstallation of Application Server fails in silent mode

5047760

Downloaded uninstaller only uninstalls last component that was installed

5044436

Uninstallation of Portal Server and Identity Server fails in single session

Linux Issues

5039744

Installer hangs when progress dialog appears

5057278

Application Server configuration fails with non-default configuration directory

5056218

Portal Server multiserverinstance script not working

5047710

Cannot install subset of Identity Server stack console using text-based installer

5045669

Installer does not flag component configuration failures

5051888

Component selection page truncated

5032211

Graphical installer asks for unnecessary Access Manager (Identity Server) installation information (5032211)

5041686

Installation Guide button on last page not working

5048374

Executing the ps -ef command during installation exposes admin password

5049320

Installer automatically upgrades JDK without warning

5044436

Uninstallation of Portal Server and Identity Server fails in single session

5046805

Directory Manager password appears in uninstaller output

5051063

Redeployment of Portal Server fails during installation of SRA components

5045689

English version of uninstaller runs for all locales

5052770

Electronic registration dialog box hangs at end of installation

5055412

Portal Server SRA dependencies not flagged by installer

5090801

Application Server pointbase script not configured

6179683

Product names appear in installer message file

6178335

Cannot launch Directory Server Admin Console

5059771

Unable to install Portal SRA gateway

4928865

Using non-root runtime user causes Application Server to fail

5031306

Netlet and Proxylet appear in Niggles for all locales

4957879

Existing components not flagged by installer

5043333

Installer hangs if Application Server uses HTTPS

5047760

Download distribution uninstaller uninstalls only last component that was installed

5052944

Directory Server configuration fails if perl packages are missing

5050775

Graphical installer asks for unnecessary Access Manager information

Compatibility Issues

Known Issues and Limitations: Installation

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

Miscellaneous Installation Issues

Multiple versions of comm_dsetup.pl exist (#6225803, 6225809, 6226161)

Workaround
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 specific 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.

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

Workaround
Unmount /share and run the installer again.

# umount /share

Cannot deploy Portal Server using SSL encryption if Access Manager is using SSL (#6211026)

Workaround
None.

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.

Workaround
None.

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

During the installation the of the Sun Cluster HA components, the SUNWasvr package is installed. The existence of SUNWasvr on the system creates a conflict when you go to install Directory Server and Administration Server or Messaging Server and Administration Server.

Workaround
Install the components in the following sequence:

  1. Install Sun Cluster without the HA agents.
  2. Create storage resource groups for the Directory Server, Messaging Server and their respective Administration Servers.
  3. Install Directory Server, Messaging Server and the Administration Servers.
  4. Install the Sun Cluster HA Agents for Directory Server and Messaging Server.
  5. Configure the installed components.
Cannot create new WSRP Consumer Producer with Access Manager if you are running Application Server 7 (#6202285)

Application Server 7 uses an incompatible version of the JAX shared component. You cannot create a new WSRP Consumer Producer with Access Manager if you are using Application Server 7. As a result you cannot deploy Portal Server and Access Manager with Application Server 7.

Workaround
If you have a version of Application Server 7 on your system, or have installed Solaris 9 with a pre-bundled version of Application Server 7, remove the following packages using pkgrm before you install Java Enterprise System:

# pkgrm SUNWasdem SUNWasu SUNWasr SUNWasac SUNWascmn SUNWasman

# pkgrm SUNWiqdoc SUNWiqfs SUNWiqjx SUNWiqr SUNWiqu SUNWiquc

Then, remove additional packages in the following order:

# pkgrm SUNWxrgrt SUNWxrpcrt SUNWxsrt SUNWjaxp

Then, proceed with installation. After installation is complete, manually add the packages using pkgadd.

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.

If installer cannot connect to X11 window server, silent install fails (#6182249)

This problem occurs if you set a DISPLAY variable and you do not have permission to access the DISPLAY.

Workaround
Unset the value of DISPLAY by doing the following:

# unset $DISPLAY

Several shared packages do not get installed on Solaris 10 (#6174538)

The installer does not flag existing packages that need to be upgraded. This causes installation of upgraded components to fail.

Workaround
Check for the existence of and remove the following packages manually:

NSPR
NSS
JSS
NSPR
NSPRD
ICU
ICUX
NSSU
NSSUX
NSSX
NSPRX
SASLX

When installing Administration Server, GUI Installer does not prompt for FQDN (#5103675)

A fully qualified host name (FQHN) is required for servers in a cluster environment. However, the GUI installer does not require you to enter a FQHN during the configuration of Administration Server. Instead, the physical host name is used, which results in errors.

Workaround
Use the /usr/sbin/mpsadmserver configure command to configure Administration Server. You are prompted to fill in the values for ‘${hostname}.domainname.com’. Enter the value of the FQHN there.

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.

Workaround
None.

Password exposed during CD installation (#5020621)

During the CD installation, the installer echoes the administration password on the screen after you enter it.

Workaround
Install Solaris first, reboot the system, and then install Java Enterprise System using either the CLI or GUI installer.

Selected component notation inconsistent from page to page (#5033467)

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

Workaround
None.

Access Manager Installation

How to Configure Web Server to Work With a Load Balancer or an SSL Offloader

If you are using Web Server as the Access Manager web container with SSL termination at the load balancer, refer to the following document to configure Web Server:

http://sunsolve.sun.com/search/document.do?assetkey=1-9-77007-1&searchclause

SUNWxrpcrt package incompatible with Access Manager SOAPClient/JAXRPC servlet (#6215206)

The JAXRPC servlet throws an exception while running the remote Access Manager client sdk.

Workaround
None.

Protocol cannot be entered for an existing console (#5045612)

The “Access Manager: Web Container for running Access Manager Services (4 of 6)” page allows you to enter the details of an existing console with the Use existing console option. However, this page does not include a field for Console Protocol.

The web container in which the Access Manager services are running and the web container on which the Access Manager console are running do not have to use the same protocol (http or https). The installer assumes that the existing console and the system running the Access Manager services have the same protocol.

Workaround
Perform an Existing Console (server only) install 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.
  3. After the second session is finished, change to the Access Manager utilities directory. For example, on Solaris systems:

    4. # 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 the Console Protocol. For example:

    6. DEPLOY_LEVEL=6
    CONSOLE_PROTOCOL=protocol-value
    ...

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

    7. # ./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 2005Q1 Administration Guide.

Console-only install configuration fails (#5047119)

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

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

    4. # 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:

    7. # ./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 2005Q1 Administration Guide.

Instance creation on Web Server throws exception (#5048518)

If you are running the amconfig script to deploy a new instance of Access Manager on Web Server, the Web Server web container configuration script throws an exception if the new instance does not have the same instance name as the host name. In addition, the Access Manager deployment for the new instance is not complete.

Workaround
Edit the Access Manager configuration script for Web Server (amws61config):

  1. Change to the Access Manager utilities directory. For example, on Solaris systems:

    2. # cd AccessManager-base/SUNWam/bin/

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

  2. Edit the amws61config script: In configNewInstance(), change the “addServerEntry $WS61_HOST” line to “addServerEntry $WS61_INSTANCE_HOST”.
  3. Re-run the amconfig script to add the Access Manager instance.
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.

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

Installing the first instance of Access Manager (no specific ID)

This release of Access Manager separates installation of Access Manager packages from the configuration steps you must take. In this release, you must use the Java Enterprise System installer to install the first instance of Access Manager.

Installing Access Manager 2005Q1 With SSL Enabled Directory Server (no specific 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 specific ID)

In passwords (such as for amadmin) and the Directory Server root suffix, Access Manager does not support a single quote ('). 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.

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

Administration Server Installation

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.

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

Application Server Installation

If previous versions of Application Server exist on system installation fails (#5110257)

If Application Server packages (from a previous version) exist on your system, you cannot install Java ES.

Workaround
Before running the installer make sure that no Application Server packages exist on your system.

Manually remove the following packages:

SUNWasclg
SUNWasac
SUNWascmn
SUNWasdem
SUNWasdev
SUNWasman
SUNWaspx
SUNWasr

In addition, manually remove the corresponding L10n packages.

If a port which is already in use is chosen installation fails (#4922417)

Workaround
None.

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.

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

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

Then, change the file contents appropriately.

Directory Server Installation

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.

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

Workaround
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 specific 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.

Workaround
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

msuserpurge Does Not Set mailDomainStatus to Removed if inetDomainstatus=deleted. (#6245878)

If a domain is deleted using the commadmin utility, it cannot be purged using commadmin because its mailDomainStatus is still active.

Workaround:
Set mailDomainStatus to “removed” by using ldapmodify.

Need tools to correct bad store.sub (#6206104)

In the next Messaging Server patch release (6.2 patch 1), reconstruct will remove entries with invalid mailbox names in the subscription.db. Additionally, mboxutil command will identify and optionally unsubscribe to non-existing mailboxes from a list of entries.

To remove corrupted data in the subscription database, use reconstruct with the new -s option:

reconstruct -s

where:

-s: repair subscriptions

To list and unsubscribe to non-existing folders, use the following options with mboxutil:

mboxutil -S [-n [-f file] | -u -f file]

where:

-n: list personal non-existing mailbox subscription
-u: unsubscribe personal non-existing mailbox subscription
-f: input/output file

Vacation text is garbage when saved. Hard returns are not retained. (#6199714)

In the next patch release (6.2 patch 1), the MTA will interpret $$ appearing in autoreply text as a line break pair. Customers wanting to use literal dollar signs in autoreply text should use a \ (backslash). For example, \$5.00 instead of $$5.00.

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

Workaround

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

Messenger Express/Communications Express

This section describes additional information and workarounds for recent Messenger Express/Communications Express known and fixed issues.

Save attachment no longer works. (#6196347)

Workaround
End users may need to clear their browser cache and restart their browsers after installation.

Regression: Automatic Spell Check was Removed (#6192219)

Automatic spell check prior to sending a message has been added back to the product through a new configuration option:

Uncomment the following line in html/main.js file to show the 'Check spelling before message is sent' checkbox in the Compose window and Settings Tab in the Options menu.

// spellCheckBeforeSendFlag = true;

Internet Explorer browser users may see that duplicate messages are sent if they decide not to use spell check features.

Delegated Administrator

This section describes known issues in Communications Services Delegated Administrator. (In earlier releases, this component was called User Management Utility.)

The Domain Disk Quota value is lost if you change the Domain status or Mail Service status of a full organization. (#6239311)

This problem occurs if you edit a full organization with a Domain Disk Quota value set to any numeric value, and you change the Domain Status or Mail Service Status from Active to any other value (such as Inactive or Hold).

A message indicates that the properties of the organization have been successfully modified, but the value of the Domain Disk Quota field is set to unlimited, and the LDAP attribute (mailDomainDiskQuota) is lost for the organization.

Workaround
Reset the value of the Domain Disk Quota field and save the properties of the organization again.

Server error; administrator is logged out when trying to create a new user or edit an existing user. (#6234660)

This problem occurs when you open a User page in an organization that contains many users, and you try to create or edit a user while the page is still loading the existing users. While the page is loading, a message asks you to wait. Do not click any buttons or links until the page is ready.

A similar problem occurs when you open an Organization page that contains many organizations.

Workaround
If the User page takes too long to load, you can set the jdapi-wildusersearchresults property to a sufficiently low value to allow the page to load quickly. For example:

jdapi-wildusersearchresults=50

If an Organization page takes too long to load, you can set the jdapi-wildorgsearchresults property to a low value. For example:

jdapi-wildorgsearchresults=10

jdapi-wildusersearchresults and jdapi-wildorgsearchresults are properties in the resource.properties file.

The resource.properties file is located in the following default path:

da_base/data/WEB-INF/classes/sun/comm/cli/server/servlet/
resource.properties

On the User Properties page, you cannot uncheck the Forward box, select the Local Inbox, and save the modification. (#6230702)

If a forwarding address has been specified for a user, you cannot uncheck the Forward box in the User Properties page and check the Local Inbox in one operation.

Workaround
First check the Local Inbox and click Save.

Next, uncheck the Forward box and click Save.

Values in the resource.properties files are overwritten when Delegated Administrator is reconfigured with the config-commda program. (#6218713)

If you configure an existing, configured installation of Delegated Administrator by running the config-commda program again, the properties in the resource.properties file are reset to their default values.

For example, if you previously set the following properties to these values:

jdapi-wildusersearchresults=50

jdapi-wildorgsearchresults=10

and then run config-commda, these properties would be reset to their default values, as follows:

jdapi-wildusersearchresults=-1

jdapi-wildorgsearchresults=-1

This issue is of concern only if you have changed the Delegated Administrator configuration (if you have enabled plug-ins or modified the values of any properties in the resource.properties file).

Workaround
If you need to upgrade Delegated Administrator, or if you need to rerun the config-commda program for any other reason, you can preserve your existing configuration by taking the following steps:

  1. Back up the resource.properties file.

    2. The resource.properties file is located in the following default path:

    da_base/data/WEB-INF/classes/sun/comm/cli/server/servlet/
    resource.properties

  2. Run the config-commda program.
  3. Edit the new resource.properties file created by the config-commda program, as follows:
The commadmin user modify command fails if you assign both the sunpresenceuser and sunimuser object classes to a user entry. (#6214638)

Workaround
None.

A newly created user does not inherit the domain’s timezone (TZ). (#6206160)

If you create a domain with a non-default timezone, and then create a new user without explicitly using the -T <timezone> option, the user is given the default timezone (America/Denver).

For example, assume you create a domain named sesta with a timezone of Europe/Paris. Next, create a new user in sesta. The user is given the default timezone, America/Denver.

Workaround
When you create or modify a user, pass -T <timezone> explicitly to the commadmin user create or commadmin user modify command.

The commadmin domain purge command does not purge calendar resources. (#6206797)

Workaround
None.

You need to save the Organization Properties page to successfully add an administrator. (#6201912)

If you open the Organization Properties page and assign an administrator role to a specified user, you must then save the Organization Properties page to add the administrator successfully. If you log out after assigning the new administrator, the administrator is not added.

A TLA or SPA cannot update the “Alias Names for Domain:” text field for a shared organization. (#6200351)

This problem occurs if you perform the following procedure:

1. Log in to the Delegated Administrator console as a TLA or SPA.

2. Select a shared organization (such as DEF).

3. Select Properties for this organization from the Show: drop-down list.

4. Enter valid values in the Alias Names for Domain: text field.

5. Click Save.

The following message is displayed: “Properties of this Organization have been successfully modified.”

However, the new alias names for the domain do not appear when you navigate to the organization’s properties page. The new values are not saved in the LDAP directory.

If you remove all Service packages from a user in an organization and then assign a new Service package from the Service Packages page, the new Service package assignment fails. (#6198361)

This problem occurs if all Service packages are removed from a user and then you add a Service package to that user from the Service Packages page.

You can add a new Service package to a user in either of the following cases:

Workaround
Take the following steps:

  1. Open the “Show users in this organization” page.
  2. Select the user.
  3. Check the Allocate Service Package button and select the desired Service package.
New non-ascii organizations cause an error because the default administrator’s email address cannot be specified. (#6195040)

The default administrator’s uid defaults to “admin_new_organization_name.” If the new organization name contains non-ascii characters, the email address that uses this uid is invalid.

Removing a Service package from an organization causes the following message to be displayed: “No changes in service packages allocation.” (#6190486)

If you remove a Service package from an organization and click Save, the service package is removed, but the “No changes in service packages allocation” message is erroneously displayed.

You cannot edit a user’s login ID in this release of Delegated Administrator. (#6178850)
The advanced search feature does not return correct results for organizations. (#5094680)

This issue occurs if you perform the following steps:

  1. Select the Advanced Search feature.
  2. Select “Organizations” from the drop-down list.
  3. Click the Match All or Match Any radio button.
  4. Select an organization name from the drop-down list.
  5. Enter valid values in the text field.
  6. Click Search.

Instead of returning only the organizations that match the search criteria, Delegated Administrator displays all organizations.

The Summary page in the New Organization wizard does not display all the organization details. (#5087980)

When you create a new organization with the New Organization wizard, certain details, such as Disk Domain Quota and Mail Service Status, are not displayed in the wizard’s Summary page.

Net Connect Installation

If you have Net Connect already installed on your system, review the customer installation guide at http://docs.sun.com/doc/817-2390-01.

The Configuration and Service Tracker (CST) 3.5 agent component is installed as part of the SRS Net Connect installation. However, the Net Connect installation does not install a CST server component. To view the CST console and data, download the CST 3.5 package from the Sun Download Center at http://www.sun.com/service/support/cst and manually install the CST server. The CST agents can then be attached to the CST server by following the documented attach process.

Portal Server Installation

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.

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.

Workaround

  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.

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

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

Shared Component Issues

pkgchk fails for SUNWcacaocfg due to post-installation configuration changes (#6195465)

The pkgchk command with the -n option occasionally fails for SUNWcacaocfg.The common agent container causes changes in ownership and configuration settings of some files during start up. As a result, running pkgchk -n SUNWcacaocfg can return an error message about file ownership. This issue exists for Solaris x86 and Solaris SPARC only.

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

The installer does not upgrade the SUNWtcatu package.

Workaround
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)

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

Sun Cluster Installation

JDMK and Common Agent Container packages removed with “scinstall -r” (#5077985)

Workaround
Before running scinstall with the -r option, manually remove SUNWcacao and SUNWcacaocfg from /usr/cluster/lib/scadmin/dot.order

SunPlex Manager install module is not supported (#4928710)

You cannot use the SunPlex installer to install Sun Cluster.

Workaround
Use the Java ES installer to install Sun Cluster minimally. Then, use scinstall to complete the installation and configuration procedures. See the Sun Cluster Software Installation Guide for more information.

Cannot install Sun Cluster HA Administration Server agents from CD (#6212471)

If you attempt to install the Sun Cluster HA Administration Server from the Java Enterprise System CD (#2), installation fails. One of the agents depends on the SUNWasvr package which is located on CD #1. As a result, the installer does not find SUNWasvr. The installer then removes all the existing packages and quits.

Workaround
Install the HA Administration Server agents after installing Administration Server. Or, minimally, make sure SUNWasvr is installed on the system before you install the agents.

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.

Workaround
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 specific 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 specific 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 specific 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.

Workaround
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 specific ID)

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

Localization Issues

Delegated Administrator: The function of the Available Languages list is not clear. (#6234120)

To add a language-tagged cn, sn, and givenname to the LDAP directory, you first must create the user, adding the English, untagged names in the New User wizard.

Next, on the User Properties page, select the required language for the language-tagged names from the Available Languages list, which is displayed alongside the First Name, Last Name, and Display Name fields. For example:

Select French from the list of available languages, enter First Name=Jacques, Last Name=Chirac. This will set the following values in LDAP:

givenname;lang-fr=Jacques

sn;lang-fr=Chirac

cn;lang-fr=Jacques Chirac

Delegated Administrator: An error message, “The organization already exists,” is not localized. (#6201623)

If you attempt to create an organization with the same name as an existing organization, Delegated Administrator displays the following error message: “The organization already exists.” This message appears in English and is not translated.

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

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

Workaround
Add the localization packages manually after installation.

Known Issues and Limitations: Uninstallation

Wrong default installation directory for Web Server and Application Server (#6197056)

When you install Web Server or Application Server on Linux, the installer installs in the wrong default directory.

Workaround
Do not accept the default installation directories given by the installer. Manually type in the correct values as listed above.

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.

Workaround
Manually remove all remaining packages, directories and files from the previous installation of Java ES.

Uninstalling Sun Cluster Console causes locale packages to be removed (#4994462)

You cannot use the Java ES uninstaller to uninstall Sun Cluster. If you remove the Sun Cluster Console package, SUNWccon, the uninstaller attempts to remove all the locale packages related to Sun Cluster as well.

Workaround
Re-add the locale packages using pkgadd.

To reinstall the locales packages except for Sun Cluster, do the following:

  1. On the media, go to the directory of ${Media}/Product/${PP}/Packages/locale/${locale}
  2. Reinstall all packages listed. Repeat for other component products or locales.

To reinstall the locales packages for Sun Cluster, do the following:

  1. On the media, go to the directory of ${Media}/Product/sun_cluster/Solaris_version/Packages or ${Media}/Product/sun_cluster_agents/Solaris_version/Packages
  2. List all packages for one locale.

    3. # grep -i "<locale full name>" */pkginfo

  3. Reinstall the packages you list above using pkgadd. Repeat for other locales.

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.

If Message Queue is installed with Java ES installer you must use uninstaller to uninstall (no specific 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.

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

Problem installing Directory Server due to broken links to shared components in library (#6199933)

Several links in /opt/sun/identity/lib are broken.

Workaround
Modify /opt/sun/identity/lib by doing the following:

  1. Go to the /lib directory.

    2. # cd ${AM_INSTALL_DIR}/identity/lib

  2. Remove .jar files.

    3. # rm -rf jaxrpc-spi.jar relaxngDatatype.jar xsdlib.jar

  3. Create new links.

    4. # ln -s /opt/sun/private/share/lib/jaxrpc-spi.jar

    # ln -s /opt/sun/private/share/lib/relaxngDatatype.jar

    # ln -s /opt/sun/private/share/lib/xsdlib.jar

savestate file is exposed (#5062553)

During installation, you can specify that the values you input get recorded in a state file for later use by issuing the following command:

# ./installer -savestate=/var/tmp/save.state.output.txt

The default permissions for this state file allow for users other than root to view its contents.

Workaround
After installation is complete, change the permissions on the file using the chmod command.

# chmod 600 save.state.output.txt

Cannot install Instant Messaging Server in separate session (#6175419)

If you try to install Instant Messaging Server and Access Manager in separate sessions, installation fails.

Workaround
Install Instant Messaging Server and Access Manager SDK in the same installation session.

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.

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

Workaround
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 specific 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 (#5052226, #5041569)

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

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

Workaround
Manually resize the window.

Directory Server and Administration Server continue to run after user exits installer (#5010533)

Workaround
Manually stop Directory Server and Administration Server. Become superuser and do the following:

#/opt/sun/directory-server/stop-admin

#/opt/sun/directory-server/slapd-hostname/stop-slapd.

Installer takes 3 to 4 minutes to display Welcome Page (#5051946)

Upon start-up, the graphical installer takes 3 to 4 minutes to display Welcome Page. The delay does not mean that the installer has hung.

Workaround
None.

Graphical installer summary page sometimes empty for ja and ko locales (#5043169)

Workaround
None.

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 2005Q1

Incorrect Chapter Reference in Messaging Server Release Notes (no specific ID)

In the Sun Java System 6 2005Q1 Messaging Server Release Notes, bug 6175770 incorrectly references “Chapter 3: Installation Scenarios” in the Sun Java Enterprise System 6 2005Q1 Installation Guide. The chapter title should be “Chapter 3: Example Installation Sequences.”

Incorrect Bug ID in Messaging Server Release Notes (#6234214)

In Table 5 (Fixed Messaging Server Bugs) of the Sun Java System 6 2005Q1 Messaging Server Release Notes, bug 6196942 should be 6191942.

imexpire's Exclusive Rule Documentation Information is Incorrect. (#6232732)

In the “exclusive” entry of Table 18-8 of the Sun Java System Messaging Server 6 2005Q1 Administration Guide, the attribute value choices should be 0 or 1, not yes or no.

Erroneous instructions regarding comm_sssetup.pl in Messaging Server Administration Guide (#6225803)

The Messaging Server Administration Guide advises to use comm_dssetup.pl in /opt/SUNWmsgsr/install/dssetup.zip. Do not use this comm_dssetup.pl.

Workaround
Use the version located in /opt/SUNWcomds/sbin.

New Chapter Added to Access Manager 2005Q1 Administration Guide

The “Installing and Configuring Third Party Web Containers” chapter details the procedures for installing and configuring BEA WebLogic 8.1 and IBM WebSphere 5.1 as web containers in an Access Manager deployment.

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.05q1 for the complete set of Sun Cluster 3.1 documentation.

The following books have been deprecated, with their respective information now part of the Sun Java Systems Communications Services 6 2005Q1 Deployment Planning Guide.

In addition, the Sun Java System Instant Messaging 6 2004Q2 Installation Guide information has been ported to the Java Enterprise System Installation Guide.

Directory Proxy Server 5 2005Q1 Release Notes

Redistributable Files

Sun Java Enterprise System 2005Q1 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:

You might also find it useful to subscribe to the following interest groups, where Sun Java Enterprise System topics are discussed:

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-0057-11.

Additional Sun Resources

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



Previous      Contents     

Part Number 819-0057-11.   Copyright 2005 Sun Microsystems, Inc. All rights reserved.