Sun and OracleChannel SunHow to BuyLog InEnglish

Sun Java System Application Server 9.1 Update 1-9.1 Update 2 Release Notes
  Search only this book
Search Help
View this book in:
Contained Within
Find More Documentation
Featured Support Resources
 Download this book in PDF (815 KB)

Hardware and Software Requirements

This section lists the requirements that must be met before installing the Sun Java System Application Server 9.1 product.

Supported Platforms

The following table lists the operating systems with which the Sun Java System Application Server 9.1 is compatible.

Table 2–2 Supported Operating Systems

Operating System 

Minimum Memory 

Recommended Memory 

Minimum Disk Space 

Recommended Disk Space 

JVM 

Sun Solaris 9, 10 (SPARC) 

Solaris 9, 10 (x86) 

512 MB 

512 MB 

250 MB free 

500 MB free 

J2SE 5.0 

Java SE 6 

64–bit Sun Solaris 10 (SPARC, x86) 

512 MB 

512 MB 

250 MB free 

500 MB free 

J2SE 5.0 

Java SE 6 

RedHat Enterprise Linux 3.0 U1, 4.0 

512 MB 

1 GB 

250 MB free 

500 MB free 

J2SE 5.0 

Java SE 6 

SuSE Linux Enterprise Server 10 SP1 

512 MB 

1 GB 

250 MB free 

500 MB free 

J2SE 5.0 

Java SE 6 

64–bit SuSE Linux Enterprise Server 10 SP1 

512 MB 

1 GB 

250 MB free 

500 MB free 

J2SE 5.0 

Java SE 6 

Ubuntu Linux, Hardy Release 

512 MB 

1 GB 

250 MB free 

500 MB free 

J2SE 5.0 

Java SE 6 

AIX 5.2, 5.3 

512 MB 

1 GB 

250 MB free 

500 MB free 

J2SE 5.0 

Windows Server 2000 SP4+ 

Windows 2000 Advanced Server SP4+ 

Windows Server 2003 

Windows XP Pro SP1+ 

Windows Vista 

1 GB 

2 GB 

500 MB free 

1 GB free 

J2SE 5.0 

Java SE 6 

Macintosh (Intel, Power) 

Supported only for development. 

512 M 

512 MB 

250 MB free 

500 MB free 

Java SE 5 

Note –

Its recommended that you use the NTFS file system rather than FAT or FAT32 when running the Application Server on any Microsoft Windows platform.

On UNIXTM, you can check your operating system version using the uname command. Disk space can be checked using the df command.

Note –

Although MacOS is not supported for production deployments, it is supported for development purposes. You can get information on downloading the Macintosh operating system from the GlassFish downloads page https://glassfish.dev.java.net/downloads/v2ur2-b04.html, or through the SDK page where Mac is listed. For example, on the JavaEE 5 SDK Update 5 download page https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=java_ee_sdk-5_05-nojdk-oth-JPR@CDS-CDS_Developer.

System Virtualization Support

System virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems. For information about Sun support for Sun Java System products in virtualized environments, see System Virtualization Support in Sun Java System Products.

Important Patch Information

Solaris Patch Requirements

It is recommended that Solaris 9, 10 (x86, SPARC) users have the “Sun recommended patch cluster” installed. This patch cluster is available under “Recommended and Security Patches” on the SunSolve Web site.

JDK Version

The minimum (and certified) version of JDK required for Application Server 9.1 is 1.5.0_12.

ProcedureTo Switch to the Supported J2SE Version

You can switch to a supported J2SE version by editing the asenv file as described here.

  1. If you have not already done so, install the new J2SE version on your system.

    The J2SE SDK can be downloaded from http://java.sun.com/j2se/

  2. Stop the Application Server.

    • From the command line:

      install_dir/bin/asadmin stop-domain

    • From the Administration Console:

      1. Click the Application Server node.

      2. Click Stop Instance.

  3. Edit the install_dir/config/asenv.conf file (asenv.bat on Windows), changing the value for AS_JAVA to point to the new Java home directory:

  4. Edit the as-install/samples/common.properties file, changing the line beginning com.sun.aas.javaRoot... to reference the new Java home directory.

  5. Restart the Application Server.

    • From the command line:

      as-install/bin/asadmin start-domain

    • From the Administration Console:

      1. Click the Application Server node.

      2. Click Start Instance.

Apache Ant Version

Version 1.6.5 of Apache Ant is bundled with Application Server 9.1 on all operating systems except Ubuntu Linux. Version 1.7.0 of Apache Ant is bundled with Ubuntu Linux and used with Application Server 9.1.

JDBC Drivers and Databases

Table 2–3 lists databases and drivers that meet the Java EE compatibility requirements. All supported configurations of the Sun Java System Application Server must contain at least one database/driver combination from this table, such as the bundled Java DB database and driver. In addition, the Application Server is designed to support JDBC connectivity to any additional DBMS with a corresponding JDBC driver.

Table 2–3 Java EE-Compatible JDBC Drivers

JDBC Driver Vendor 

JDBC Driver Type 

Supported Database Server 

Derby Network Client 

Type 4 

Derby 10.2 

DataDirect 3.6.x, 3.7.x

Type 4 

Oracle 10g 

Oracle 9i 

Sybase ASE 15 

MS SQL 2005 

DB2 9.1 

DB2 8.2 

MySQL Connector/J Driver 5.1.6 

Type 4 

MySQL 5.0 

Oracle 10G 

Type 4 

Oracle 10g 

-RAC 

PostGres 

Type 4 

8.2.x

Table 2–4 lists all the additional databases and drivers scheduled to be supported in the Application Server FCS release.

Table 2–4 Supported JDBC Drivers and Databases (Application Server FCS)

JDBC Driver Vendor 

JDBC Driver Type 

Supported Database Server 

Oracle OCI 

Type 2 

Oracle 9i 

IBM DB2 

Type 2 

DB2 9.1 

In general, the Application Server 9.1 supports all JDBC drivers that meet the Java EE specification.

Using the Bundled Java DB Database

This section provides instructions for using the Java DB database implementation bundled with Application Server 9.1. Java DB is based on the Apache Derby database.

Starting and Stopping the Java DB Database

Sun Java System Application Server 9.1 introduces two new asadmin commands for starting and stopping the Java DB Network Server.

  • Use the asadmin start-database command to start an instance of the Java DB network server:


    asadmin start-database [--dbhost 0.0.0.0] [--dbport 1527] [--dbhome path]

    The default value for the host is 0.0.0.0, which enables Java DB to listen on localhost as well as the IP/hostname interfaces. The value for the dbhome property is the location of where the Java DB databases reside. The default path is as-install/javadb.

  • Use the asadmin stop-database command to shut down a running instance of the Java DB network server:


    asadmin stop-database [--dbhost 0.0.0.0] [--dbport 1527]

Java DB Utility Scripts

The Java DB configuration that is supplied with Application Server 9.1 includes scripts that can help you use Java DB. The following scripts are available for use in the as-install/javadb/bin directory:

  • startNetworkServer, startNetworkServer.bat— Script to start the network server

  • stopNetworkServer, stopNetworkServer.bat— Script to stop the network server

  • ij, ij.bat— Interactive JDBC scripting tool

  • dblook, dblook.bat — Script to view all or part of the DDL for a database

  • sysinfo, sysinfo.bat — Script to display versioning information about the Java DB environment

  • NetworkServerControl, NetworkServerControl.bat — Script which provides a means of executing commands on the NetworkServerControl API

ProcedureTo Configure Your Environment to Run the Java DB Utility Scripts

  1. Ensure that the JAVA_HOME environment variable specifies the directory where the JDK is installed.

  2. Set the DERBY_HOME environment variable to point to the as-install/javadb directory.

See Also

For more information about these utilities, see the following Derby documentation:

Message Queue Versions

The embedded Sun Java System Message Queue code that is supplied as part of Application Server is only tested and certified (typically) against the equivalent version of the Message Queue broker. This means that using the supplied embedded Message Queue code to connect to a remote (not managed by Application Server) Message Queue broker running a different version of the Message Queue code is not supported.

Web Servers

This section lists the web servers that are supported for the Sun Java System Application Server 9.1.

Table 2–5 Supported Web Servers

Web Server 

Version 

Operating System 

Sun Java System Web Server 

6.1, 7.0 

Solaris SPARC 8, 9, 10 

Solaris x86 9, 10

Red Hat Enterprise Linux 2.1 Update 2, 3.0 Update 1 

Apache Web Server 

1.3+, 1.4, 2.0 

Solaris SPARC 9, 10 

Solaris x86 10

Red Hat Enterprise Linux 2.1 Update 2, 3.0 Update 1 

Microsoft IISTM

5.0+ 

Windows Server 2003 

Windows 2000 Advanced Server Service Pack 4+ 

Support for additional platforms, including Windows and HP-UX, will be available at a later date.

Browsers

This section lists the browsers that are supported with the Sun Java System Application Server 9.1.

Table 2–6 Supported Web Browsers

Browser 

Version 

Mozilla 

1.7.12 

Internet Explorer 

6.0 Service Pack 2, 7.0 

Firefox 

1.5.x, 2.x

Safari 

2 

Netscape 

8.0.4, 8.1, 9.0, 9.0.x

HADB Requirements and Supported Platforms

In addition to the requirements listed in Hardware and Software Requirements, verify that your system meets the requirements listed below for running HADB.

Note –

HADB is only bundled with the Application Server 9.1 Enterprise profile. Also note that the Java components of the system have been built with JDK 5 and has been tested on JDK 1.5.

Supported Platforms

  • Solaris (SPARC) – Solaris 8 MU7, Solaris 9 MU7, Solaris 10 RR.

  • Solaris (x86) – Solaris 9 MU7, Solaris 10 RR.

  • RedHat Enterprise Linux - 2.1 U5 (only ext2 file system is supported, not ext3), 3.0 U4 (both ext2 and ext3 are supported. Updates before U4 are not recommended due to excessive swapping). Note that HADB is tested on these operating system versions in 32–bit mode only. Also, note that HADB does not support RedHat Enterprise Linux 3.0 running in 64–bit mode due to a bug in the operating system (see known bug 6249685 in the High Availability section for details about impact on HADB).

  • Microsoft Windows – Microsoft Windows 2000 Advanced Server Service Pack 4 and Microsoft Windows 2003 Enterprise Edition. Note that HADB does not support any of the forthcoming Microsoft Windows operating system versions in 64–bit mode.

HADB Server Host Requirements

  • Minimum memory - 320 MB per node.

  • Minimum free disk space - 70 MB for HADB binaries per host. In addition, disk space is needed for the data devices, 512 MB for a test installation per node.

  • Recommended memory - 512 MB per node.

  • Recommended free disk space - 70 MB for HADB binaries per host. In addition, disk space is needed for the data devices, 1200 MB for a test installation per node.

Note –

Make sure write caching is disabled on devices storing HADB data and log files. Write caching is enabled by default on some Solaris platforms; for example, Solaris x86.

HADB Management Host Requirements

  • Minimum memory - 128 MB

  • Minimum free disk space - 70 MB for HADB binaries per node

HADB Client Host Requirements

  • Minimum memory - 120 MB

  • Minimum free disk space - 20 MB

Upgrading the Sun Java System Application Server

Refer to the Sun Java System Application Server 9.1 Update 1 Upgrade and Migration Guide for complete instructions for upgrading from a previous version of the Application Server to the current version.

Other Requirements

The following additional requirements should be met before installing the Sun Java System Application Server software.

  • Free space: your temporary directory must have a minimum of 35MB free for Sun Java System Application Server installation, and 250 MB of free space for the SDK installation.

  • Using the uninstall program: If you need to remove the Application Server from your system, it is important to use the uninstall program that is included with the software. If you attempt to use another method, problems will arise when you try to reinstall the same version, or when you install a new version.

  • Free ports: You must have seven unused ports available. The installation program automatically detects ports in use and suggests currently unused ports for the default domain. By default, the initial default ports are:

    • 8080 for HTTP, 8181 for HTTPS

    • 3700 for IIOP, 3820 for IIOP/SSL and 3920 for IIOP/SSL with Mutual Authentication

    • 4848 (HTTP) for the Administration Server

    • 8686 (RMI) port for pure JMX Clients

    Starting previously-installed servers (UNIX) — unless you are replacing the previously installed server, you should start it before you begin the Sun Java System Application Server 9.1 installation process. This allows the installation program to detect ports that are in use and avoid assigning them for other uses.

  • Replacing previously-installed servers (UNIX) — Refer to the Sun Java System Application Server 9.1 Update 1 Upgrade and Migration Guide for complete instructions for upgrading from a previous version of the Application Server.

  • Shutting down firewall (Microsoft Windows) — You must stop any firewall software before installing the Sun Java System Application Server software, because some of this software disables all ports by default. The installation program must be able to accurately determine which ports are available.

    For further compatibility information, see theSun Java System Application Server 9.1 Update 1 Upgrade and Migration Guide.