Sun Java System Application Server Enterprise Edition 8.1 2005Q1 Upgrade and Migration Guide |
Chapter 1
Application Server Compatibility IssuesThe Sun Java System Application Server 8.1 2005Q1 (Application Server 8.1) is upward binary-compatible with Sun Java System Application Server 8 2004Q2 (Application Server 8) and with Sun Java System Application Server 7 2004Q2 (Application Server 7) except for the incompatibilities noted below. J2EE applications that run on versions 7 and 8 also work on version 8.1 except for the incompatibilities noted below.
The topics discussed in this chapter include incompatibilities in the following areas:
Web Server FeaturesApplication Server 8.1 replaces the Web server shipped with Application Server 7 with a faster native web server component. As a result, the following web server-specific features are no longer supported in version 8.1:
Security RealmsThe package names of the security realm implementations have been renamed from com.iplanet.ias.security.auth.realm in Application Server 7 to com.sun.enterprise.security.auth.realm in Application Server 8.1. Custom realms written using the com.iplanet.* classes must be modified.
The com.sun.enterprise.security.AuthenticationStatus class has been removed.
The com.sun.enterprise.security.auth.login.PasswordLoginModule authenticate method implementation has changed as follows.
/**
* Perform authentication decision.
* <P> Note: AuthenticationStatus and AuthenticationStatusImpl
* classes have been removed.
* Method returns silently on success and returns a LoginException
* on failure.
*
* @return void authenticate returns silently on successful authentication.
* @throws LoginException on authentication failure.
*
*/
abstract protected void authenticate()
throws LoginException;For more information, see:
http://developers.sun.com/prodtech/appserver/reference/techart/as8_authentication/index.html
Sun Deployment Descriptor: sun-web.xmlIn Application Server 7, the default value for the optional attribute delegate was false. In Application Server 8.1, this attribute defaults to true. This change means that by default the Web application classloader first delegates to the parent classloader before attempting to load a class by itself. For details, see Application Server 8.1 Options Contrary to J2EE 1.4 Specification Recommendations.
encodeCookies PropertyThe encodeCookies property of the sun-web-app element in the sun-web.xml file performs URL encoding of cookies if set to true. If set to false, no encoding of cookies is performed. In Application Server 7, the default value of the encodeCookies property was true. This property was not present in Application Server 8. In Application Server 8.1, the default value is false.
In general, URL encoding of cookies is unnecessary. Setting this property to true is strongly discouraged. This property is provided only for those rare applications that depended on this behavior in Application Server 7. This property might be removed in a future release.
CORBA Performance OptionIn Application Server 7, users were able to specify the following system property to optionally turn on some ORB performance optimization:
-Djavax.rmi.CORBA.UtilClass=com.iplanet.ias.util.orbutil.IasUtilDelegate
The ORB performance optimization is turned on by default in Application Server 8.1. If you are using the system property reference above, you must remove it to avoid interfering with the default optimization.
File FormatsIn Application Server 8.1, domain.xml is the main server configuration file. In Application Server 7, the main server configuration file was server.xml. The DTD file of domain.xml is found in lib/dtds/sun-domain_1_1.dtd. The upgrade tool included in Application Server 8.1 can be used to migrate the server.xml from Application Server 7 to domain.xml for Application Server 8.1.
The lib/dtds/sun-domain_1_1.dtd. file for Application Server 8.1 is fully backward compatible with the corresponding file for Application Server 8, sun-domain_1_0.dtd.
In general, the configuration file formats are NOT backward compatible. The following configuration files are NOT supported:
Tools InteroperabilityAs a general rule, tools are not interoperable between Application Server 7 and 8.1. Users must upgrade their Application Server 7 tools to work with Application Server 8.1.
Cluster ScriptsThe clsetup and cladmin scripts in Application Server 7 are not supported in Application Server 8.1. In Application Server 8.1, the asadmin configure-ha-cluster command replaces the clsetup script, and asadmin commands that operate on clusters replace the commands supported by the cladmin script. For more information about the asadmin commands, see the Sun Java System Application Server Reference Manual.
Primary Key Attribute ValuesIn Application Server 7, it was possible to change any field (in the Administration Console) or attribute (in the command line interface). In Application Server 8.1, a field or attribute that is the primary key of an item cannot be changed. However, an item can be deleted and then recreated with a new primary key value. In most cases, the primary key is a name, ID, reference, or JNDI name. The following table lists the primary keys that cannot be changed.
Command Line Interface: hadbmThe following table lists options for the command line interface hadbm that are no longer supported. For more information about the hadbm commands, see the Sun Java System Application Server Reference Manual.
Command Line Interface: start-appserv and stop-appservThe start-appserv and stop-appserv commands are deprecated. Use of these commands results in a warning. Use asadmin start-domain and asadmin stop-domain instead.
In Application Server 8.1, the "Log Messages to Standard Error" field has been removed from the Administration Console. The log-to-console attribute in the domain.xml file is deprecated and ignored. The asadmin set command has no effect on the log-to-console attribute. Use the --verbose option of the asadmin start-domain command to print messages to the window in which you executed start-domain. This only works if you execute start-domain on the machine on which the domain you are starting is installed.
Command Line Interface: asadminThe following sections describe changes to the command line interface asadmin:
For more information about the asadmin commands, see the Sun Java System Application Server Reference Manual.
Subcommands
Subcommands are backward compatible except as noted below.
The following sub command is deprecated and ignored:
The following subcommands are not supported in Application Server 8.1:
The following subcommands are no longer supported in Application Server 8.1, because the software license key and web core were removed, and because controlled functions from web server features are no longer supported:
Error Codes for Start and Stop Subcommands
For Application Server 7, the exit codes returned by the start and stop subcommands of the asadmin command were based on the desired end state. For example, for asadmin start-domain, if the domain was already running, the exit code was 0 (success). If domain startup failed, the exit code was 1 (error).
For Application Server 8.1, the exit codes are based on whether the commands execute as expected. For example, the asadmin start-domain command returns exit code 1 if the domain is already running or if domain startup fails. Similarly, asadmin stop-domain returns exit code 1 if the domain is already not running or cannot be stopped.
Options
Options in the following table are deprecated or no longer supported.
Dotted Names
The following use of dotted names in asadmin get and set subcommands are not backward compatible:
- Default server name is server instead of server1
- server_instance.resource becomes domain.resources.resource
- server_instance.app-module becomes domain.applications.app-module
- Attributes names format is different, for example, poolResizeQuantity is now pool-resize-quantity
- Some aliases supported in Application Server 7 are not supported in Application Server 8.1
In Application Server 8.1, the --passwordfile option of the asadmin command does not read the password.conf file, and the upgrade tool does not upgrade this file. For information about creating a password file in Application Server 8.1, see the Sun Java System Application Server Administration Guide.
The table below displays a one-to-one mapping of the incompatibilities in dotted names between Application Server 7 and 8.1. The compatible dotted names are not listed in this table.
Note
Rows with note in previous table describe attribute names. In these instances, there is not a one-to-one relationship with the dotted names between Application Server 7 and 8.1.
Tokens in Attribute Values
The asadmin get command shows raw values in Application Server 8.1 instead of resolved values as in Application Server 8. These raw values may be tokens. For example, executing the following command:
asadmin get domain.log-root
displays the following value:
${com.sun.aas.instanceRoot}/logs
Nulls in Attribute Values
In Application Server 8, attributes with no values contained nulls. This caused problems in attributes that specified paths. In Application Server 8.1, attributes with no values contain empty strings, as they did in Application Server 7.