Hardware and Software Requirements For OpenSSO Enterprise 8.0

Solaris 10 OS on SPARC, x86, and x64 based systems 

Solaris 9 OS on SPARC, x86, and x64 based systems 

All Web Containers Supported For OpenSSO Enterprise 8.0 except for Geronimo Application Server 2.1.1 with Tomcat only

OpenSolaris 

GlassFish Application Server V2 UR1 and UR2 

Apache Tomcat 6.0.18 

Red Hat Enterprise Linux 5 Base and Advanced Platform on Intel 32–bit (x86) servers and AMD 64–bit (x86_64) servers 

Red Hat Enterprise Linux 4 server Base and Advanced Platform on Intel 32–bit (x86) servers and AMD 64–bit (x86_64) servers 

All Web Containers Supported For OpenSSO Enterprise 8.0 except Geronimo

Ubuntu 8.0.4 

GlassFish Application Server V2 UR1 and UR2 

Apache Tomcat 6.0.18 

Windows Server 2003 Standard Edition 

Windows Server 2003 Enterprise Edition 

Windows Server 2003 Datacenter Edition 

All Web Containers Supported For OpenSSO Enterprise 8.0 except Geronimo

Windows Server 2003 R2 on 64–bit servers 

All Web Containers Supported For OpenSSO Enterprise 8.0

Windows XP 

Windows Vista 

All Web Containers Supported For OpenSSO Enterprise 8.0 except Oracle Server, JBoss Application Server, and Geronimo

Windows 2008 Server 

GlassFish Application Server V2 UR1 and UR2 

Apache Tomcat 6.0.18 

IBM AIX 5.3 

IBM WebSphere Application Server 6.1 

Notes:

• OpenSSO Enterprise supports patches and updates to these base releases? For example, subsequent patches and updates to Red Hat Linux 4.7 or Red Hat Linux 5.2 are supported.

• If not specifically documented for a platform, OpenSSO Enterprise supports 32–bit and 64–bit versions of an operating system if the supported OpenSSO Enterprise web container is also supported in the 32–bit and 64–bit mode on the same system.

Sun Java System Application Server 9.1 Update 1 and Update 2 

Download: http://www.oracle.com/technetwork/indexes/downloads/index.html

GlassFish Application Server V2 UR1 and UR2 

GlassFish site: https://glassfish.dev.java.net/

GlassFish download locations: 

GlassFish V2 UR1: https://glassfish.dev.java.net/downloads/v2ur1-b09d.html

GlassFish V2 UR2: https://glassfish.dev.java.net/downloads/v2ur2-b04.html

Sun Java System Web Server 7.0 Update 3 (32–bit and 64–bit) 

Download: http://www.oracle.com/technetwork/indexes/downloads/index.html

Update 3 only. Updates 1 and 2 are not supported.

Apache Tomcat 5.5.27 and 6.0.18 and later 

See http://tomcat.apache.org/

Oracle WebLogic Server 9.2 MP2 

See http://www.oracle.com/us/products/middleware/application-server/index.htm

Oracle WebLogic Server 10 

See http://www.oracle.com/us/products/middleware/application-server/index.htm

For the supported operating systems, see the following site: 

http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/index.html#1122259

Oracle Application Server 10g 

See http://www.oracle.com/technetwork/indexes/products/index.html

Version 10.1.3.1 is supported. 

IBM WebSphere Application Server 6.1 

See http://www-01.ibm.com/software/webservers/appserv/was/

Apache Geronimo Application Server 2.1.1 

See http://geronimo.apache.org/

Supported only with Tomcat on Solaris systems.

JBoss Application Server 4.x 

See http://www.jboss.com/

Server 

JDK 1.5.x or 1.6.x 

64-bit JVM on supported web containers 

Solaris virtual memory requirements. For Solaris systems, configure at least twice as much virtual memory as the JVM heap size, especially when the JVM is configured in 64–bit mode with over 4 GB for the heap size. Therefore, you might need to increase the operating system swap space.

Client (OpenSSO SDK) 

JDK 1.4.x, 1.5.x. or JDK 1.6.x 

Configuration data store 

(also referred to as the Service Management data store) 

• OpenSSO configuration data store

  Note: If you specify the OpenSSO configuration data store, you must deploy OpenSSO Enterprise on a local file system, because the OpenSSO configuration data store is not supported on an NFS-mounted file system.

• Sun Java System Directory Server 5.2, 6.0, 6.3, and 6.3.1

User data store  

• Sun Java System Directory Server 5.2, 6.0, 6.3, and 6.3.1

• Microsoft Active Directory 2003 on Windows Server 2003 R2

• IBM Tivoli Directory Server 6.1

• OpenSSO user data store

  Note: The OpenSSO user data store is not supported for production deployments. It is recommended only for prototype, proof of concept (POC), or developer deployments that have a small number of users.

Caution: Sun Java System Directory Server 6.2 is not recommended. For more information, see http://sunsolve.sun.com/search/document.do?assetkey=1-66-235361-1.

OpenSSO Enterprise 8.0 

Two or more OpenSSO Enterprise instances must be running on different host servers and configured as a site behind a load balancer. 

The load balancer does not have any specific requirements. However, a load balancer that supports cookie-based sticky configuration usually provides better performance. 

Sun Java System Message Queue 4.1 

Message Queue brokers must be running in cluster mode on different servers. 

Oracle Berkeley DB 4.6.18 

The Berkeley DB client and database must be deployed on the same servers as the Message Queue brokers. 

You can deploy the Message Queue brokers and Berkeley DB on the same servers that are running the OpenSSO Enterprise instances. However, for improved performance, consider installing the brokers on different servers. 

Version 3.0 policy agents 

OpenSSO Enterprise supports new version 3.0 J2EE and web policy agents, including new version 3.0 features. 

For more information, including the available version 3.0 agents, see http://docs.sun.com/coll/1767.1.

Version 2.2 policy agents 

OpenSSO Enterprise supports version 2.2 J2EE and web policy agents. 

However, when deployed with OpenSSO Enterprise, a version 2.2 policy agent must continue to use version 2.2 features. For example, the agent must store its configuration data locally in its AMAgent.properties file, and OpenSSO Enterprise centralized agent configuration is not supported.

For more information, including the available version 2.2 agents, see http://docs.sun.com/coll/1322.1.

Version 2.1 policy agents 

OpenSSO Enterprise does not support version 2.1 policy agents.

MySQL 

MySQL version 4.1.1 or later, because the OpenSSO Enterprise logger uses the MySQL STR_TO_DATE function.

Note: The Solaris 10 OS includes MySQL Server 4.0.37, so you must upgrade this MySQL version to use OpenSSO Enterprise database logging.

Oracle 

Oracle Database 10g or later 

RAM 

Prototype or developer deployment: 1 GB 

Production deployment: 4 GB recommended 

Disk space 

For OpenSSO Enterprise server with console, server only, or console only deployment: 

• Server: 512 MB for OpenSSO Enterprise binary files and configuration data

• Log files: 7 GB for log files, including container log files

For client SDK deployment: 

• Client SDK: 100 MB minimum

• Log files: 5 GB recommended for debug logs, if debug level (com.iplanet.services.debug.level) is set to message

Considerations for log files: The log file requirements depend on the actual production load and can be adjusted accordingly. The disk space requirements are based on the default 100 MB log file size, with one history file per log file type. Several considerations are:

• Delete the debug log files periodically, especially if the debug level is set to message.

• Check the .access and .error logs periodically in the logs directory for their size and contents.

• Consider configuring the log rotation to delete the oldest log files.

Firefox 2.0.0.x and 3.0.x 

Windows Vista, Windows XP, and Windows Server 2003 

Solaris OS, versions 9 and 10 

Red Hat Linux 4 and 5 

Mac OS X 10.4 and later 

Firefox 1.0.7 and 1.5 

Windows XP 

Windows 2000 

Solaris OS, versions 9 and 10 

Red Hat Linux 4 and 5 

Microsoft Internet Explorer 7 

Windows Vista, Windows XP, and Windows Server 2003 

Microsoft Internet Explorer 6.0 SP1  

Windows XP 

Microsoft Internet Explorer 6.0 SP1 

Windows 2000 

Mozilla 1.7.12 

Solaris OS, versions 9 and 10 

Windows XP 

Windows 2000 

Red Hat Linux 4 and 5