This Release Notes for Microsoft Windows document contains important information about SunTM JavaTM Enterprise System (Java ES) 5. You can also access this document at http://docs.sun.com/coll/1286.2.
Read this document before you begin using Java ES in order to improve your overall installation and operation experience. Also read the component-level release notes for the Java ES components you will be using. This document covers the highlights of the issues affecting Java ES 5, whereas the component-level release notes describe application issues in detail. See Component Release Notes for a listing of the available component-level release notes.
This Release Notes for Microsoft Windows document discusses the following topics:
All the component specific information appears in the respective component release notes. The following component release notes can be found at http://docs.sun.com/coll/1315.2.
Access Manager – Sun Java System Access Manager 7.1 Release Notes for Microsoft Windows
Application Server – Sun Java System Application Server Enterprise Edition 8.2 Release Notes for Microsoft Windows.
Directory Server and Directory Proxy Server – Sun Java System Directory Server Enterprise Edition 6.0 Release Notes
Message Queue – Sun Java System Message Queue 3.7 UR1 Release Notes for Microsoft Windows
Portal Server – Sun Java System Portal Server 7.1 Release Notes for Microsoft Windows
Service Registry – Service Registry 3.1 Release Notes for Microsoft Windows
Web Proxy Server – Sun Java System Web Proxy Server 4.0.4 Release Notes for Microsoft Windows
Web Server – Sun Java System Web Server 7.0 Release Notes for Microsoft Windows
The following list summarizes the major enhancements and additions. For more details, see the release notes for the individual components of Java ES.
A new major version of Directory Server, including a new major version of Directory Proxy Server as a subcomponent
A new major version of Portal Server
A new major version of Web Server
Java DB (Access Manager dependent)
Improved system-wide monitoring capabilities and the addition of a monitoring console
Sun Microsystems has excluded the communication products from the Sun Java Enterprise System entitlement.
Beginning with the upcoming Java ES 5 release, communication products will be available as part of the Sun Java Communications Suite or as individual products. Communication products will no longer be installed through the Java Enterprise System installer.
Communication products affected include:
Sun Java System Messaging Server
Sun Java System Calendar Server
Sun Java System Instant Messaging
Sun Java System Communications Express
Sun Java System Directory Preparation Tool
Sun Java System Communications Services Delegated Administrator
This change in entitlement does not affect the currently shipping communication products in Java Enterprise System 2005Q4. If you have communication products installed, no change will occur to your current entitlement.
Java ES 5 supports these operating systems:
Windows 2000 Advanced Server SP4
Windows XP SP2
Windows 2003 Enterprise Server SP1 (32-bit)
Windows 2003 Enterprise Server SP1 (64-bit)
The following table lists the disk installation and RAM requirements for the various components that comprise Java ES 5.
Component |
Minimum Disk Space for Installation |
RAM Requirements for Installation |
---|---|---|
Access Manager |
Minimum 512 MBytes of disk space for Access Manager and associated applications. 1 GByte is recommended. |
512 MBytes RAM for initial testing. 1 GByte for threads, Access Manager SDK, HTTP server, and other internals. |
Application Server |
With Sun Java System Studio: Minimum 512 MBytes of disk space. 1 GByte is recommended. |
Minimum 512 MBytes RAM. 1 GByte is recommended. |
Message Queue |
100 MBytes of disk space. |
256 MBytes RAM |
Portal Server, Portal Server SRA |
1 GByte of disk space. |
Minimum 1 GByte RAM. 2 GBytes is recommended. |
Service Registry |
512 MBytes |
Minimum 512 MBytes RAM. 1 GBytes is recommended. |
Web Proxy Server |
512 MBytes of disk space. |
512 MBytes RAM |
Web Server |
Minimum 512 MBytes of disk space. 1 GByte is recommended. |
Minimum 512 MBytes RAM. 1 GByte is recommended. |
Directory Proxy Server |
300 MBytes disk space. For evaluation purposes, an additional 2 GBytes local disk space per server instance is sufficient to hold server logs when the default configuration is used. |
1-2 GBytes for evaluation purposes. At least 4 GBytes for production servers. |
Directory Server |
300 MBytes disk space. For evaluation purposes, an additional 2 GBytes local disk space for server software might be sufficient. |
1-2 GBytes for evaluation purposes. At least 4 GBytes for production servers. |
For more information on disk space and RAM requirements, refer to the respective component release notes.
Web-based administrative interfaces provided by Java ES 5 components support at least the following web browsers:
Firefox 1.0.7 on Windows 2000 and XP
Mozilla 1.7.12 on Windows 2000 and XP
NetscapeTM Communicator 8.0.4 on Windows 2000 and XP
Microsoft Internet Explorer 6.0 SP1 on Windows 2000
Microsoft Internet Explorer 6.0 SP2 on Windows XP
For information about the web browsers supported by the end user web interfaces provided by Java ES 5 components, refer to the release notes for the component that provides the interface. Release notes for Java ES 5 components are available at http://docs.sun.com/coll/1315.2.
Java Enterprise System is certified with and includes Java 2 Platform Standard Edition (J2SETM platform) 1.5 update 7.
This section lists known issues in this release.
In passwords such as for amadmin and the Directory Server root suffix, Access Manager does not support a single quote (\q). However, the back-slash (\\) is supported.
If Directory Server is already installed and SSL is enabled, the Directory Server must also listen on a non SSL (LDAP) port. Access Manager must be configured to use the LDAP port, otherwise the installation of Access Managerfails.
After Access Manager has been configured to use the LDAP port, the user may disable the LDAP port.
InAccess Manager's SDK configuration, the 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:
com.iplanet.am.directory.host
com.iplanet.am.server.host
com.iplanet.am.console.host
com.iplanet.am.profile.host
com.iplanet.am.naming.url
com.iplanet.am.notification.url
Solution On node B, where Access Manager SDK is installed with Web Server, modify the webserver-instance-dir/config/server.xml file and add the required Access Manager JAR files to the classpath.
After installing Web Server in eval config mode on Windows operating system, Web Server services are not started automatically.
Workaround: Manually start the Web Server services.
After installing Web Server in eval config mode on Windows operating system, Web Proxy Server services are not started automatically.
Workaround: Manually start the Web Proxy Server services.
While using the IP address in the netlet, if the reverse lookup entry for a particular host is not configured in the DHCP server, then the operation associated with that host does not work.
For example, if nslookup.exe ipaddress fails to return the host name then the netlet operations will not work for these IP addresses.
Workaround: Use hostnames instead of IP addresses.
If a Windows machine is not connected to the network, the HADB instance does not start.
Workaround: Connect Windows machine to the network.
Workaround: Use one of the following workarounds:
Remove the Sun Java Web Console version already installed on the Windows machine before actually proceeding with Java ES 5 installation.
Re-register the applications that were registered with previous Sun Java Web Console version again with the newer version in order to continue accessing those applications
On the Windows platform, installing with Install all in Configure Automatically During Installation mode fails unpredictably in post configuration stages on machine with low memory.
Workaround: Use one of the following workarounds:
Optimize your Windows OS Virtual memory setup.
Maximize free RAM before you start the Java ES installer Stop all unecessary programs and services.
Do a selective install, use the Custom option to install products selectively.
This problem occurs when certain DLLs are in the Windows system32 folder, such as libnspr4.dll, nss3, and smime.
These DLLs conflict with Java ES versions of DLLs that are installed in the install-dir/share/liband prevent proper functioning of Java ES servers.
Workaround:
Rename these DLLs in the system32 folder so Java ES servers will use the correct versions of these DLLs.
Renaming these DLLs could cause some legacy applications that installed these DLLs in system32 folder not to function.
Workaround:
On Windows XP Professional, the guest account must be disabled.
The registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\ForceGuest must be set to 0 in order for authentication to succeed.
Whenever a product component is installed or upgraded in Configure Manually After Installation mode, the product's shortcuts are created only after the product is configured manually.
Message Queue is not affected by this problem.
Workaround: None.
When installation is done in a remote session, the installer logs are stored in the temp directory.
If the system reboots during installation or uninstallation, the temp is deleted. Therefore, the log files are not available when you click the View Log button.
Workaround: None.
Sun Java Enterprise System 5 does not contain any files that you can redistribute.
To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at http://sun.com/software/javaenterprisesystem/get.html.
For more information on Sun's commitment to accessibility, visithttp://sun.com/access.
The Sun web site provides information about the following additional resources:
Documentation (http://www.sun.com/documentation/)
Support (http://www.sun.com/support/)
Training (http://www.sun.com/training/)
Third-party URLs are referenced in this document and provide additional, related information.
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 or alleged to be caused by or in connection with use of or reliance on any such content, goods, or services that are available on or through such sites or resources.
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 full document title and part number. The part number is a 7-digit or 9-digit number that can be found on the book's title page or in the document's URL. For example, the part number of this book is 819-4893.