Sun Java System Application Server 9.1 Release Notes

Chapter 2 About Application Server 9.1

The Sun Java System Application Server 9.1 is a Java EE 5 platform-compatible server for the development and deployment of Java EE applications and Java technology-based web services in large-scale production environments.

This chapter includes:

What’s New in the 9.1 Release

The Application Server 9.1 includes the following enhancements:

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

All supported operating systems are 32-bit unless indicated otherwise. The 64-bit JDK is supported only on 64-bit supported operating systems.

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

Table 2–1 Supported Operating Systems

Operating System 

Minimum Memory 

Recommended Memory 

Minimum Disk Space 

Recommended Disk Space 


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 

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 

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

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.

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 if JDK required for Application Server 9.1 is 1.5.0_13. JDK 1.5.0_13 can be downloaded from

JDBC Drivers and Databases

Table 2–2 lists databases and drivers that meet the Java EE compatibility requirements. All supported configurations of the Sun Java System Application Server Enterprise Edition 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–2 Java EE-Compatible JDBC Drivers

JDBC Driver Vendor 

JDBC Driver Type 

Supported Database Server 

Derby Network Client 

Type 4 

Derby 10.2 

DataDirect 3.60.29 

Type 4 

Oracle 10g 

DataDirect 3.6 

Type 4 

DB2 9.1 

DB2 8.2 

Oracle Thin 

Type 4 

Oracle 10g 


Type 4 


MySQL Connector/J Driver 3.1 

Type 4 

MySQL 5 

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

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

JDBC Driver Vendor 

JDBC Driver Type 

Supported Database Server 

Oracle OCI 

Type 2 

Oracle 9i 


Type 2 

DB2 9.1 

Oracle 10G 

Type 4 


DataDirect 3.60.29 

Type 4 

Sybase ASE 15 

MS SQL 2005 

MySQL Connector/J Driver 3.1 

Type 4 

MySQL 5 

In general, the Application Server Enterprise Edition 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.

Java DB Utility Scripts

Note –

These scripts are deprecated in Application Server 9.1.

The Java DB configuration that ships with Application Server 9.1 also includes several useful scripts which can help you use Java DB. The following scripts are available for use in the <appserver_install_dir>/javadb/frameworks/NetworkServer/bin directory:

ProcedureTo Configure Your Environment to Run the Java DB Utility Scripts

  1. Set the DERBY_INSTALL environment variable to point to the <appserver_install_dir>/javadb directory.

  2. Unset your CLASSPATH environment variable.

  3. You can also optionally set the following properties:

    1. DERBY_SERVER_HOST to the host on which the network server will listen.

      Can also be set to to enable all listeners.

    2. DERBY_SERVER_PORT to the port number on which the network server will listen.

See Also

For more information about these utilities, see the Derby Tools and Admin guides.

Exporting Tables from Pointbase to Java DB

This example shows how to capture the DDL for a Pointbase table in commander and create the same table in Java DB using NetBeans 5.0. Another option for doing this is by using the commander tool and the unload database command:

Do you wish to create a new Database. (Yes (Y) or No (N))? [default: N]: 
Enter product to connect with: (Embedded (E) or Server (S))? [default: E]: e
Enter driver to use? [default: [com.pointbase.jdbc.jdbcUniversalDriver]: 
Enter database URL? [default: [jdbc:pointbase:embedded:sample]: 
Enter Username? [default: PBPUBLIC]: 
Enter Password? [default: PBPUBLIC]: 

PointBase Commander 5.2 ECF build 294 size restricted version EMBEDDED

Interactive SQL command language. SunOS/5.9

(C) Copyright 2004 DataMirror Mobile Solutions, Inc. All rights reserved.

Licensed to: Sun_customer_demo_use
For commercial version contact PointBase at:
PHONE: 1-877-238-8798 (US & CANADA)
       1-408-961-1100 (International)

SQL>unload database sampledb.sql;
SQL> unload database sampledb.sql;
SQL> 13 Row(s) Unloaded. (PBPUBLIC.CUSTOMER_TBL)
SQL> 9 Row(s) Unloaded. (PBPUBLIC.OFFICE_TBL)
SQL> 15 Row(s) Unloaded. (PBPUBLIC.ORDER_TBL)
SQL> 30 Row(s) Unloaded. (PBPUBLIC.PRODUCT_TBL)
SQL> 10 Row(s) Unloaded. (PBPUBLIC.SALES_REP_TBL)
SQL> 12 Table(s) Unloaded.
SQL> quit;

The results from executing the unload database command is written in the above example to the file sampledb.sql. The sampledb.sql file contains all of the DDL required to create the necessary tables and indexes. It also contains the DML to insert the data back into the database. The commander command RUN is intended to be used import the data into another Pointbase database using the script that was generated. Here is an example of what the INSERT statements and associated data look like in the generated file:

VALUES( ?, ?, ?, ?, ? );
'ISLAND              ','en_US','Island Adventures','Experience an island /
paradise in a way fit for your needs.','Island_Adventures.gif'
'JUNGLE              ','en_US','Jungle Adventures','Experience a jungle /
paradise in a way fit for your needs.','Jungle_Adventures.gif'
'MOUNTAIN            ','en_US','Mountain Adventures','Experience an /
elevated paradise with a view.','Mountain_Adventures.gif'
'ORBITAL             ','en_US','Orbital Adventures','Experience a vacuum /
paradise with a beautiful view and where no one can hear you scream.', /
'WESTERN             ','en_US','Western Adventures','Enjoy the Wild West. /
'SOUTH_POLE          ','en_US','South Pole Adventures','Experience a /
frozen paradise in a way fit for your needs.','SouthPole_Adventures.gif'

You could easily edit the file generated from the commander unload database command so that it only consisted of the DDL (for example, it would not be hard to write a program which would process the insert statements). As a simple test, we use the unload database command against the Pointbase sample database, and then edit the generated script, making the following changes:

Next, a simple Ant script is used to execute the DDL using the sql target. Finally, the same experiment is repeated for the sun-appserv-samples database requiring the following additional changes to the generated SQL file:

Converting Pointbase Java procedures to work with Java DB requires some changes to the Java code as well as to the CREATE PROCEDURE statements. Information on creating Java DB Java procedures can be found in the Derby Reference manual. Support for the Boolean datatype should be in the next release of Java DB.

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–4 Supported Web Servers

Web Server 


Operating System 

Sun Java System Web Server 

6.1, 7.0 

Solaris SPARC 9, 10 

Solaris x86 9, 10

Red Hat Enterprise Linux , 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


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.


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

Table 2–5 Supported Web Browsers





Internet Explorer 

6.0 Service Pack 2 






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. You can download HADB at ***. 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

HADB Server Host Requirements

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

HADB Client Host Requirements

Upgrading the Sun Java System Application Server

Refer to the Sun Java System Application Server 9.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.

Java EE 5 Platform APIs

The Sun Java System Application Server Enterprise Edition 9.1 supports the Java EE 5 platform. The following table lists the enhanced APIs available on the Java EE 5 platform.

Table 2–6 Major API changes on the Java EE 5 Platform



Java EE 5

Java Platform, Enterprise Edition 5

JSR 244

Web Services Technologies

Implementing Enterprise Web Services 

JSR 109

Java API for XML-Based Web Services (JAX-WS) 2.0

JSR 224

Java API for XML-Based RPC (JAX-RPC) 1.1

JSR 101

Java Architecture for XML Binding (JAXB) 2.0

JSR 222

SOAP with Attachments API for Java (SAAJ)

JSR 67

Streaming API for XML

JSR 173

Web Service Metadata for the Java Platform 

JSR 181

Component Model Technologies

Enterprise JavaBeans 3.0

JSR 220

J2EE Connector Architecture 1.5

JSR 112

Java Servlet 2.5

JSR 154

JavaServer Faces 1.2

JSR 252

JavaServer Pages 2.1

JSR 245

JavaServer Pages Standard Tag Library 1.2

JSR 52

Management Technologies

J2EE Management

JSR 77

J2EE Application Deployment

JSR 88

Java Authorization Contract for Containers

JSR 115

Other Java EE Technologies

Common Annotations for the Java Platform 

JSR 250

Java Transaction API (JTA)

JSR 907

JavaBeans Activation Framework (JAF) 1.1

JSR 925


JSR 919

Java Message Service API

JSR 914

Java Persistence API

JSR 220

Java EE 5 SDK

Sun Java System Application Server 9.1 is available as part of the Java EE 5 SDK.

There are two Java EE 5 SDK versions:

In addition, you can download these SDK distributions with the JDK or with the NetBeans 5.5.1 tools. For more information, access the download page at

Note –

GlassFish V2 and Application Server 9.1 does not work with NetBeans 5.5 for developing Java EE applications. You must use NetBeans 5.5.1.

Switching to Another Supported Java Version

Sun Java System Application Server 9.1 requires J2SE 5.0 or greater as the underlying JVM. If you want to switch from one Java version to another, perform the following general steps. (Windows and Unix)

Note –

Downgrading to an earlier Java version is not recommended after a domain has been created with a newer Java VM. If you must downgrade your JVM, it is recommended that you do it on a per-domain basis. The followiong procedure describes how to do this.

ProcedureTo switch to another supported Java version

  1. Download the desired Java SDK (not the JRE) and install it on your system, if you have not already done so.

    The Java SDK can be downloaded from

  2. Start the domain for which you want to change the JDK:

    as_install/bin/asadmin start-domain domain_name
  3. Log in to the Admin console and change the JVM attributes for the domain.

    In particular, you may want to change the JAVA_HOME variable on the JVM Settings page for the domain.

    Alternatively, you can use the asadmin command:

    as_install/bin/asadmin set ""

Known Java ES 5 Compatibility Issues

There are two known compatibility issues between Application Server 9.1 and Java ES 5 (JES5).

  1. The JES5 Service Registry is not compatible with Application Server 9.1 because of the JSF 1.2 version provided by Application Server 9.1. The Service Registry needs to be upgraded to JES5u1 prior the Application Server upgrade to 9.1. This limitation is also documented in the Service Registry documentation.

  2. The JES5 Portal Server is not compatible with Application Server 9.1 because of the JSF 1.2 version provided by Application Server 9.1. Portal Server needs to be upgraded to JES5u1 prior the 9.1 upgrade to 9.1.

    On a Java ES 5 setup that has Portal Server on Application Server 8.2, upgrading Application Server 8.2 to 9.1 makes the Portal Server unusable. Application Server 9.1 uses JSF 1.2, but the JSF-Portlet bridge in Release 5 Portal Server does not support JSF 1.2. On Solaris/Linux the Portal Server needs to be upgraded to JavaES5 Update 1. On Windows do not upgrade Application Server to 9.1 if you want to continue using the Release 5 Portal Server, as Portal Server is not supported in Java ES 5 Update 1 on Windows.

Using the Application Server Update Center

The Application Server 9.1 Update Center provides automated Application Server updates and easy access to additional components.

When the Update Center is enabled, it performs an automated software update. During this automated update process, the Update Center collects and transmits the following data to Sun Microsystems (or its service provider):

No personally identifiable information is tracked. No personally identifiable information is associated with any other data or used for reporting purposes.

ProcedureTo Use the Update Center

To ensure explicit agreement of the automated update, the Update Center is disabled by default. To enable the Update Center to perform periodic checks and automated updates:

  1. Start the Update Center.

    • On Unix: <installdir>/updatecenter/bin/updatetool

    • On Windows: <installdir>\updatecenter\bin\updatetool.bat

  2. Select the Preferences tab.

  3. In the Update Scheduling window, change the Check for Updates drop-down box value from Never (Manual) to a desired value. For example, daily or weekly.

  4. Specify the desired day of the week and time of the day for the update.

  5. Select the Save button to save your changes.

    The Update Center will now automatically check for Glassfish or Application Server component updates according to the schedule specified. When an update is available, the Update Center will launch and notify you of the component available to update.

More About WSIT Integration

For detailed information about WSIT status, refer to the WSIT Status Notes page. Also refer to the The WSIT Tutorial for information about using WSIT with Application Server.