Sun Java System Application Server Platform Edition 8.2 Release Notes

Chapter 2 About Application Server Platform Edition 8.2

The Sun JavaTM System Application Server Platform Edition 8.2 is a J2EE 1.4 platform-compatible server for the development and deployment of J2EE applications and Java technology-based web services.

This chapter includes:

What’s New in the 8.2 Release

The Sun Java System Application Server Platform Edition 8.2 implements many new features:

The Sun Java System Application Server Platform Edition is free for development, deployment and redistribution. Customers interested in redistribution should contact Sun OEM sales for a redistribution license. Sun provides support at additional cost. If you would like to be contacted about licensing the Java 2 Platform, Enterprise Edition, fill out this form.

Hardware and Software Requirements

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

Platform Requirements

The following table lists the operating systems that are supported for Sun Java System Application Server Platform Edition 8.2 product.

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 1.4.2_10, J2SE 5_06 

Sun Java Desktop System 

512 MB 

1 GB 

250 MB free 

500 MB free 

J2SE 1.4.2_10, J2SE 5_06 

Redhat Enterprise Linux 3.0 U1, 4.0 

512 MB 

1 GB 

250 MB free 

500 MB free 

J2SE 1.4.2_10, J2SE 5_06 

Windows Server 2000 SP4+ 

Windows 2000 Advanced Server SP4+ 

Windows Server 2003 

Windows XP Pro SP1+ 

1 GB 

2 GB 

500 MB free 

1 GB free 

J2SE 1.4.2_10, J2SE 5_06 

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

Note –

You must 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

For the current list of required patches for Sun Java System Application Server Platform Edition 8.2 go to and select either “Patches” or “Patch Portal.” Follow the Sun Java System Application Server Platform Edition 8.2 links. As operating system patch requirements change and patches to Java Enterprise System components become available, updates will be made available on SunSolve, initially in the form of recommended patch clusters.

Solaris Patch Requirements

It is recommended that Solaris 8, 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.

RedHat Enterprise Linux 3.0 Additional Package Requirements

To run native components of this product, including installer, the following package, which is not part of the standard RedHat Enterprise Linux 3.0 distribution, should be installed: compat-libstdc++-7.3-2.96.118.i386.rpm. This package can be downloaded from

JDBC Drivers and Databases

The Sun Java System Application Server Platform Edition is designed to support connectivity to any DBMS with a corresponding JDBC driver. For a list of components that Sun has tested and found to be acceptable for constructing J2EE-compatible database configurations, please refer to the following table.

Table 2–2 J2EE-Compatible JDBC Drivers

JDBC Vendor 

JDBC Driver Type 

Supported Database Server 

i-net Software 

Type 4 

Oracle (R) 8.1.7, 9i,, 10.1.x, 10.2.x

Sybase ASE 12.5. 

Microsoft SQL Server 2000 4.0 Service Pack 1 


Type 2 

IBM DB2 8.1 Service Pack 3+ 


Type 4 

Apache Derby 


Type 4 

PointBase Network Server 5.2 


Type 4 



Type 4 

Oracle (R) 8.1.7, 9i,, 10.1.x, 10.2.x

Sybase ASE 12.5.2 

Microsoft SQL Server 

IBM DB2 8.1 Service Pack 3+ 


Type 4, Type 2 

Oracle (R), 10.1.x, 10.2.x

Using the Bundled Derby Database

This section provides instructions for using the Derby database implementation bundled with Application Server 8.2.

Starting and Stopping the Derby Database

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

Derby Utility Scripts

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

ProcedureTo Configure Your Environment to Run the Derby Utility Scripts

  1. Set the DERBY_INSTALL environment variable to point to the <appserver_install_dir>/derby 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 Derby

This example shows how to capture the DDL for a table in Pointbase and create the same table in Derby 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 Derby requires some changes to the Java code as well as to the CREATE PROCEDURE statements. Information on creating Derby Java procedures can be found in the Derby Reference manual. Support for the Boolean datatype should be in the next release of Derby.


This section lists the browsers that are supported with the Sun Java System Application Server Platform Edition 8.2 administration console and Quick Start Guide. The browsers supported when running applications on the Application Server depend on the applications being run.

Table 2–3 Browsers Supported




1.4, 1.5, 1.6, 1.7.x

Netscape Navigator 

6.2, 7.0 

Internet Explorer 

5.5 Service Pack 2, 6.0 



Upgrading the Sun Java System Application Server

Refer to the Sun Java System Application Server Platform Edition 8.2 Installation Guide for complete instructions for upgrading from a previous version of the Application Server to the Sun Java System Application Server Platform Edition 8.2.

Other Requirements

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

Bugs Fixed in the 8.2 Release


An EJBQL query may not contain all matching results if the where clause contains an OR operator and a single-valued cmr navigation.


Broken panels in the New Web Service Wizard.


The - asadmin create-domain --help command produces incorrect usage and an invalid option is documented (--admin.jmxport).


Specifying target message by java-method does not work in client-side message-security-binding elements.


Using the AMX API, removing a J2EE application reference from a server removes the application, but the application is still accessible.


AS 8.2 PE/EE: Use the PlatformMBeanServer if available.


DOCS:java.sql.statement.getConnection() does not meet javadoc specification for pooling connections.


Port 8080 is not released by domain even after stopping and deleting.


Cannot save transaction support value when JMS connection factory was created for the first time.


For Application Server 8.1 UR2 PE, asant cannot be run on Windows 2000 at all; command too long error is returned.


Rich client RMI-IIOP failover testing fails.


Bundle Grizzly ARA supports in 8.2.


Application Server 8.1 Virtual Server access log location not updating.


Generic RA for JMS need to be integrated with AS 8.2.


Disk I/O for XA transaction logs too high.


Make Application Server 8.x native launcher Bourne shell-friendly by disassociating from controlling TTY.


S1AS 7.0/SJAS7.1 : EJBC/RMIC generates STUB/Skel with NOT fully Qualified Package Name.


Server has to reject requests with double Content-Length header


asadmin create-domain --help produces some CVS merge characters and is garbled.


setAutoCommit to false gets propagated when the same connection is used by the next user.


Undeploy: Error unregistering mbean.


Servlet container UTF-8 URI mapping issue.


Deploytool does not work with spaces in the install path


Deploy command fails on file based non-root installation.


Deployment hangs in Windows.


Deployed applications cannot be accessed after upgrade.


Deployment performance improvement needed.


Redeploy sometimes fails with Error while running ejbc -- Fatal Error from EJB Compiler.


Undeployment does not release all files.


Redeployment of WAR file (remote deployment for Creator) fails.


AS8102 memory leaks on deploy/undeploy scenario (SubCR from 6324399 EJBClassLoader.

J2EE Support

The Sun Java System Application Server 8.2 supports the J2EE 1.4 and Java EE 5 platforms. The following table describes the enhanced APIs available on the J2EE 1.4 platform.

Table 2–4 Major API changes on the J2EE 1.4 Platform




Application and Application Client 

Implementation of standard deployment descriptors by means of XML schemas 

Enterprise JavaBeans (EJB) 2.1 

Timer service and EJB Web-service endpoint 

Java Servlet 2.4 

Web-service endpoint filter 

JavaServer Pages (JSP) 2.0 architecture 

Expression language and tag library 

J2EE Connector Architecture 1.5 

Inbound resource adaptor and Java Message Service (JMS) pluggability 

Web Services

Java Web Services Developer Pack 1.5 

Integrated toolkit for building, testing and deploying XML applications, Web services, and Web applications 

Java API for XML-based Remote Procedure Calls (JAX-RPC) 1.1 

Mapping for WSDL and Java technology and support for development of Web-service clients and endpoints 

WS-I Basic Profile 1.0 

The enabling element for interoperability using WSDL and SOAP 

SOAP with attachment API for Java (SAAJ) 1.2 

An API for SOAP-based messaging; fosters the creation of SOAP messages with attachments 

Java APIs for XML Registries (JAXR) 1.0 

A uniform and standard API for accessing XML registries, such as those for Universal Description Discovery and Integration (UDDI and ebXML) 


J2EE Deployment 1.1 

Standard APIs that enable deployments of J2EE components and applications 

J2EE Management 1.0 

Definitions for the information model for managing the J2EE platform 

Java Management Extensions (JMX) 1.2 

Standard management API 

Java Authorization Contract for Containers (JACC) 1.0 

Definitions of security contracts between a J2EE Application Server and the authorization policy provider 

Java API for XML Processing (JAXP) 1.2 

An API with which applications can parse and transform XML documents; also adds support for processing of XML schemas 

JMS 1.1 

A messaging standard that enables J2EE application components to create, send, receive, and read messages; also adds support for uniform APIs for queues and topics 

JavaMail 1.3 

A set of abstract classes that model a mail system; also includes minor updates to the APIs 

Switching to Another Supported J2SE Version

Sun Java System Application Server 8.2 supports both J2SE 1.4.2 and J2SE 5.0 as the underlying JVM. If you want to switch from one J2SE version to another, perform the following general steps. (Windows and Unix)

ProcedureTo switch to another supported J2SE version

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

    The J2SE SDK can be downloaded from

  2. Completely stop the Application Server.

    You can use the following command line:

    as-install/bin/asadmin stop-domain

    Alternatively, you can use the Administration Console GUI:

    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 J2SE home directory.

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

  5. Restart the Application Server.

    as-install/bin/asadmin start-domain
Next Steps

If you are upgrading from a JDK version earlier than the bundled version (JDK 1.4.2_06), then you cannot upgrade to J2SE 5.0 or later using just the steps above. Specifically, in addition to the above steps, you must delete any existing domains and recreate them.