On all platforms, you will need for core directory server component:

• Disk: 400 MB for binaries, 2 GB of disk space for evaluation purposes and 4 GB for a production system with 250,000 entries with no binary attributes
• Memory: 1-2G for evaluation purposes, 4 GB for production systems.

For Directory Proxy server component:

• Memory: 1-2 GB for evaluation purposes, 4 GB for production
• Disk Space: 300 MB minimum for binaries + 2GB for server logs for evaluation

Please check documentation and Release Notes for details. http://docs.sun.com/app/docs/doc/820-4805

For core Directory Server, Proxy Server and Directory Server Resource Kit components the supported architectures are:

• SPARC
• x86
• AMD x64
• HP-UX (PA-RISC)

For Identity Synchronisation for Windows component:

• SPARC
• x86

Please check documentation and Release Notes for details. http://docs.sun.com/app/docs/doc/820-4805

For core directory server, proxy server and DSRK components:

• Sun Solaris 10 U5 Operating System for SPARC 64-bit and x64
• Sun Solaris 9 Operating System for SPARC 64-bit and x86
• Sun Solaris 10 U5 with Trusted Extensions for SPARC 64-bit and x64
• OpenSolaris 2009.06 Operating System for SPARC 64-bit and x64
• Linux Red Hat Enterprise Linux 5 U3 Operating System for x64
• Linux Red Hat Enterprise Linux 4 U8 Operating System for x64 and x86
• Linux SuSE Linux Enterprise Server 10 U2 Operating System for x64 and x86
• Microsoft Windows 2003 Standard and Advanced Server Standard Edition SP 2 for x86 and x64
• Microsoft Windows 2008 Standard and Advanced Server Standard Edition SP 1 for x86 and x64
• HP-UX 11iV2 (11.23) on PA-RISC

For Identity Synchronisation for Windows:

• Sun Solaris 10 Operating System
• Sun Solaris 9 Operating System
• Linux Red Hat Advanced Server 3.0
• Linux Red Hat Advanced Server 4.0
• Microsoft Windows 2003 Server Standard and Enterprise Edition
• Synchronisation with AD 2008 is supported but core Identity Synchronisation has to run either on Windows 2000 or 2003

Please check documentation and Release Notes for details and execution mode (32/64 bits). http://docs.sun.com/app/docs/doc/820-4805

The Sun Directory Server Enterprise Edition is licensed on a per-entry basis. An entry is defined as a single unique Distinguished Name ("DN") and its contained attributes.

As defined by Software Licence Agreement and Entitlement.

• DSML v2 - Directory Services Markup Language v2
• FIPS 180-1 - Secure Hash Standard (SHA-1)
• RFC 1777 - Lightweight Directory Access Protocol LDAP (v2)
• RFC 1778 - The String Representation of Standard Attribute Syntaxes
• RFC 1779 - A String Representation of Distinguished Names
• RFC 2079 - Attribute Type and Object Class to Hold URIs
• RFC 2246 - The TLS Protocol Version 1.0
• RFC 2247 - Using Domains in LDAP/X.500 Distinguished Names
• RFC 2307 - An Approach for Using LDAP as a Network Information Service
• RFC 2377 - Naming Plan for Internet Directory-Enabled Applications *
• RFC 2605 - Directory Server Monitoring MIB *
• RFC 2713 - LDAP Schema for Java Objects
• RFC 2739 - Calendar Attributes for vCard and LDAP *
• RFC 2788 - Network Services Monitoring MIB
• RFC 2798 - Definition of the inetOrgPerson LDAP Object Class
• RFC 2831 - Using Digest Authentication as a SASL Mechanism *
• RFC 2849 - LDAP Data Interchange Format (LDIF)
• RFC 2891 - LDAP Server-Side Sort Control
• RFC 2926 - Conversion of LDAP Schemas to and from SLP Templates *
• RFC 3045 - Storing Vendor Information in the LDAP Root DSE
• RFC 3062 - LDAP Password Modify Extended Operation
• RFC 3296 - LDAP Named Subordinate References
• RFC 3671 - Collective Attributes in LDAP *
• RFC 3698 - LDAP Additional Matching Rules *
• RFC 3829 - LDAP Authorisation Identity Controls
• RFC 3866 - Language Tags and Ranges in LDAP *
• RFC 4370 - LDAP Proxied Authorisation Control (v2)
• RFC 4422 - Simple Authentication and Security Layer (SASL)
• RFC 4505 - Anonymous Simple Authentication and Security Layer (SASL) Mechanism

See below for continued list:

For core directory server, proxy server and DSRK components: Part 1

• DSML v2 - Directory Services Markup Language v2
• FIPS 180-1 - Secure Hash Standard (SHA-1)
• RFC 1777 - Lightweight Directory Access Protocol LDAP (v2)
• RFC 1778 - The String Representation of Standard Attribute Syntaxes
• RFC 1779 - A String Representation of Distinguished Names
• RFC 2079 - Attribute Type and Object Class to Hold URIs
• RFC 2246 - The TLS Protocol Version 1.0
• RFC 2247 - Using Domains in LDAP/X.500 Distinguished Names
• RFC 2307 - An Approach for Using LDAP as a Network Information Service
• RFC 2377 - Naming Plan for Internet Directory-Enabled Applications *
• RFC 2605 - Directory Server Monitoring MIB *
• RFC 2713 - LDAP Schema for Java Objects
• RFC 2739 - Calendar Attributes for vCard and LDAP *
• RFC 2788 - Network Services Monitoring MIB
• RFC 2798 - Definition of the inetOrgPerson LDAP Object Class
• RFC 2831 - Using Digest Authentication as a SASL Mechanism *
• RFC 2849 - LDAP Data Interchange Format (LDIF)
• RFC 2891 - LDAP Server-Side Sort Control
• RFC 2926 - Conversion of LDAP Schemas to and from SLP Templates *
• RFC 3045 - Storing Vendor Information in the LDAP Root DSE
• RFC 3062 - LDAP Password Modify Extended Operation
• RFC 3296 - LDAP Named Subordinate References
• RFC 3671 - Collective Attributes in LDAP *

For core directory server, proxy server and DSRK components: Part 2

• RFC 3698 - LDAP Additional Matching Rules *
• RFC 3829 - LDAP Authorisation Identity Controls
• RFC 3866 - Language Tags and Ranges in LDAP *
• RFC 4370 - LDAP Proxied Authorisation Control (v2)
• RFC 4422 - Simple Authentication and Security Layer (SASL)
• RFC 4505 - Anonymous Simple Authentication and Security Layer (SASL) Mechanism
• RFC 4511 - Lightweight Directory Access Protocol (v3)
• RFC 4512 - Lightweight Directory Access Protocol (LDAP): Directory Information Models
• RFC 4513 - Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms
• RFC 4514 - Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names
• RFC 4515 - Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters
• RFC 4516 - Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator
• RFC 4517 - Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules
• RFC 4519 - Lightweight Directory Access Protocol (LDAP): Schema for User Applications
• RFC 4522 - Lightweight Directory Access Protocol (LDAP): The Binary Encoding Option
• RFC 4523 - Lightweight Directory Access Protocol (LDAP) Schema Definitions for X.509 Certificates *
• RFC 4524 - COSINE LDAP/ X.500 Schema
• RFC 4532 - Lightweight Directory Access Protocol (LDAP) "Who am I?" Operation

RFCs 2251 through 2256 as well as several others have been made obsolete by a new set of RFCs, RFCs 4510 through 4520.

* = Directory Server supports part of this RFC, please refer to product documentation. http://docs.sun.com/app/docs/doc/820-4805

Any LDAP v3 compliant application with appropriate scheme.

For core directory server, proxy server and DSRK components:

• iPlanet Directory Server 5.1, Sun Java System Directory Server 5.2 (formerly Sun ONE Directory Server 5.2), Sun Java System Directory Server Enterprise Edition 6.x customers can upgrade to Directory Server Enterprise Edition 7.0 for free if they purchased original product and if they have a valid maintenance contract.
• Customers who purchased the product but do not have maintenance contract can benefit from upgrade, see upgrade price.
• Solaris customers using Directory Server 200,000 entries licence provided with Solaris 8, 9 and 10 (up to Update 4) and under maintenance should upgrade to full Directory Server Enterprise Edition, see upgrade price for pricing.

Please check Trade-Up Licence Only section.