Sun Java(TM) System Directory Proxy Server 5.2 Patch 4 - RHEL2.1 |
Status: RELEASED
Patch Id: 118096-08
***********************************************************************
READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT
FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU
AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE
TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE.
***********************************************************************Summary: Sun Java(TM) System Directory Proxy Server 5.2 Patch 4 - RHEL2.1
Date: Oct/03/2005
Installation Requirements:
None
Solaris Release: Note: Redhat
Sun OS Release: Note: RHEL2.1
Unbundled Product: Directory Proxy Server
Unbundled Release: 5.2
Xref: This patch available for SunOS sparc in patch 116373 and for SunOS i386 in patch 116374
Topic:
RHEL2.1: Sun Java(TM) System Directory Proxy Server 5.2 Patch 4
Relevant Architecture: i386
BugId's fixed with this patch:
4916532 4993108 5011001 5041832 5042027 5065752 5078970 5083191 5085510 5089790 5091854 5091862 5100993 5105442 5108039 6174242 6182579 6184500 6186625 6190632 6192536 6195747 6197814 6197846 6199876 6201767 6202487 6228761 6234980 6243035 6247329 6269941 6272376 6285805 6289871
Changes incorporated in this version:
6291684 6303762 6296345
Patches accumulated and obsoleted by this patch:
Patches which conflict with this patch:
Required Patches:
118079-09 (or greater)
Obsoleted by:
Files Included in this Patch:
Note: sun-directory-proxy-server-5.2-13.i386.rpm
Problem Description:
(from current patch)
6291684 DPS 5.2 Patch4 Solaris : unable to backout to previous version
6303762 Patch DPS Linux : /opt/directory-proxy-server/5.2/bin/tcl8.2/ is empty after applying the patch
6296345 DPS PatchZip4 : change the owner of SERVERROOT
(from 118096-07)
6199876 quickstart.tcl does not give the option to specify the instance name
6228761 ldapfwd 5.2.07+ is using 100 CPU on win2k following an referral without closing the TCP connection.
6289871 README files have not been updated for 5.2 P4
(from 118096-06)
4916532 When creating any new log property definitions, log file limits/rotation fails
4993108 Large Entries Are Truncated When Retrieved Over SSL
5042027 Does not change group on anonymous binds
6192536 crash in CAI_LF_AclARProperty::server_rename_dn_attrs when BIND dn has trailing "+"
6234980 JES3 DPS 5.2SP3 - crashes after a "configure now" installation when telneting DPS port from remote
6243035 When writing audit logging to a separate file, DPS can stop writing log info after log file deletion
6247329 ldapfwd crash in malloc
6269941 DPS shows bad version in mpsconsole after upgrade
6272376 bad management of references to CAI_LF_Server objects
6285805 JES4:Linux:DPS: After upgrade DPS Admin console looking for old jar file dps522.jar
(from 118096-05)
(from 118096-04)
6202487 Syntax Error in DPS-prebackout.sh Script
(from 118096-03)
6197814 DPS instance is not visible in the console
6197846 DPS backout returns to 5.2 instead of patch2 version
6201767 DPS upgrade from 52RTM to patch3 fails
(from 118096-02)
5078970 DPS doesn't respond
6182579 SSL Failover in DPS causes looping in failover function
6184500 Upgrade failed on Sol. x86 : libnspr4.so: version `NSPR_4.3' not found
6186625 Upgrade failed in postpatch script (upgrade)
6190632 Failback doesn't work on DPS 5.2
6195747 SJES3_11/14 nightly: OLH of DPS is not shown in all locales
(from 118096-01)
5065752 Bind and Unbind stress with ldclt fails on high performance windows platforms
5083191 Can not install DPS patch if the base dir diffrent from admin server base dir
5091854 Referrals hangs with ldapfwd 5.2.09
5091862 IP Connection Limit Is Not Enforced (doc)
5105442 Persistant search does not return an error code referred sub suffix
5108039 Upgrade doesn't work on Solaris (Sparc & x86)
6174242 Upgrade doesn't work on Solaris
5011001 Internal Failover of DS by DPS52 proxy not transparent
5041832 Error Message Is Produced the First Time the Console Is Launched for a New Insta
5085510 DPS console hangs with JDK 1.5 beta
5089790 Patch are not available on Solaris
5100993 Old version of DPS is installed. 5.2P2 instead of 5.2P3
Revision History:
118096-04
Patch Installation Instructions:
--------------------------------
Upgrading Directory Proxy Server on Linux
You upgrade Directory Proxy Server by applying patches, and
synchronizing settings with the configuration directory server.
This readme provides instructions for upgrading Directory Proxy Server
from Sun Java Enterprise System 2004Q2 and 2005Q1 to 2005Q4. For more information
on upgrading from prior versions, see the Java Enterprise System
Upgrade and Migration Guide.
------------------------------------------------------------------------
Note
1. Directory Proxy Server belongs to a group of products sharing
the same Administration Server. You must patch all of these products at
the same time.
2. You cannot upgrade Directory Proxy Server by applying patches unless
Directory Proxy Server was installed on a Linux system with RPM packages.
3. When you apply patches, you upgrade the SSL certificate database.
If you subsequently decide to back out the patches and you have changed
the content of the certificate database, you must manually replay
the changes after backing out the patches. Consider performing a
backup before you back out the patches.
When you backout patches after having changed the SSL certificate
database, you cannot start in SSL mode. To workaround this problem,
turn off SSL mode, restart Directory Proxy Server, reinstall the
certificate, and then enable SSL mode.
4. Directory Server, Directory Proxy Server, Messaging Server,
Calendar Server, and the associated Administration Server
must run as the same user and group. That is, they must run with
the same UID and GID.
5. If you are planning to upgrade from Linux RH AS 2.1 to Linux RH AS 3,
you must upgrade the Sun Java Enterprise System component products
before you upgrade Linux.
6. In this procedure <oldversion> signifies the RPM for Directory Server,
Directory Proxy Server, and Administration Server 5.2 2004Q2
7. This procedure includes steps for Calendar Server and Messaging
Server. If you are not using a component product, ignore the steps
related to that product.
8. If you installed the previous rpm without the "--prefix" option,
you must upgrade without this option (defaulting to /opt/sun). On the
other hand, if you installed the previous rpm with the "--prefix" option,
you must upgrade with this option, using the same parameter value.
------------------------------------------------------------------------
Caution
Only upgrade from Sun Java Enterprise System 5.2 2004Q2 or 2005Q1 to Sun Java
Enterprise System 5.2 2005Q4 on Linux if you are sure you will not want
to back out later. It is not possible to back out from Sun Java
Enterprise System 5.2 2005Q4 on Linux.
------------------------------------------------------------------------
To Upgrade Directory Proxy Server on Linux
1. Obtain the RPMs for your platform and installed server
component products.
* Shared components:
ICU: sun-icu-2.1-6.i386.rpm (or greater)
NSPR: sun-nspr-4.5.1-2.i386.rpm (or greater)
NSS: sun-nss-3.9.4-1.i386.rpm (or greater)
JSS: sun-jss-4.0-5.i386.rpm (or greater)
SASL: sun-sasl-2.02-2.i386.rpm (or greater)
LDAP-C-SDK: sun-ldapcsdk-5.12-3.i386.rpm (or greater)
LDAP-JDK: sun-ljdk-4.17-3.i386.rpm (or greater)
* Directory Server: 118080-10:
Product: sun-directory-server-5.2-24.i386.rpm
Man pages: sun-directory-server-man-5.2-8.i386.rpm
* Administration Server: 118079-10:
Product: sun-admin-server-5.2-18.i386.rpm
Console: sun-server-console-5.2-18.i386.rpm
Man pages: sun-admin-server-man-5.2-8.i386.rpm
* Calendar Server: 117851-14, 117852-14 (or greater)
* Directory Proxy Server: 118096-08:
Product: sun-directory-proxy-server-5.2-13.i386.rpm
* Messaging Server: 118209-01, 117786-03 (or greater)
You can download RPMs from
http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
2. Stop the console if it is running.
3. Stop all servers in this order:
1. Calendar Server
2. Messaging Server
3. Directory Proxy Server
4. Administration Server
5. Directory Server
4. Apply each RPM for the shared components.
See the shared component patch readme for the procedure.
5. Apply each RPM for the Administration Server component.
See the Administration Server component patch readme for
the procedure.
6. Apply each RPM for the the Directory Server component.
See the Directory Server component patch readme for the procedure.
7. Apply the RPM for the Directory Proxy Server component.
1. Ensure that the configuration directory server is running.
2. Apply the RPM:
# rpm -Fvh sun-directory-proxy-server-5.2-13.i386.rpm
The upgraded settings are automatically synchronized with the
configuration directory server.
3. If the configuration directory server is local, stop
the configuration directory server.
8. Apply the Messaging Server component RPM.
See the Messaging Server component patch readme for
the procedure.
9. Apply the Calendar Server component RPM.
See the Calendar Server component patch readme for the procedure.
10. Restart the servers in this order:
1. Directory Server
2. Administration Server
3. Directory Proxy Server
4. Messaging Server
5. Calendar Server
11. If you wish to upgrade from Linux RH AS 2.1 to Linux RH AS 3,
do so now. For information, see the Linux documentation.
------------------------------------------------------------------------
Troubleshooting
* If after applying the patches, you still see a Sun ONE-branded
console rather than a Sun Java System-branded console, verify
that you effectively synchronized with the configuration
directory server.
------------------------------------------------------------------------Special Install Instructions:
------------------------------
None.
README -- Last modified date: Monday, October 3, 2005
Sun Contracted Content
Sun Contracted Feature
