5.1 RELEASE NOTES

December 2003

Welcome to the Novell exteNd Application Server Version 5.1. These release notes include the following sections:

Installation notes	Updated information about how to install and configure the Novell exteNd Application Server
J2EE compatibility	Information on the J2EE compatibility of the Novell exteNd Application Server
Novell product compatibility	Information on compatibility between the Novell exteNd Application Server and other Novell products
Software and hardware requirements	Software and hardware needed to run the Novell exteNd Application Server products
Supported databases	The database types and versions supported by the Novell exteNd Application Server
What's new	New features in this release
Upgrade notes	Server changes that may affect you when upgrading to the latest version
Known issues	Known issues with this release
Problems fixed in Version 5.1	Problems that have been fixed, including problem numbers

Release note updates   To check for updates to these release notes, click here.

Installation notes

This section provides updated information about installing and configuring the Novell exteNd Application Server. For more information, see Installing Novell exteNd.

• Current platform support
• NetWare notes
• Solaris notes
• HP-UX notes
• AIX notes
• Database-specific information

Current platform support

The Novell exteNd Application Server documentation describes the application server's use on a variety of platforms. The application server is not available on HP or AIX in this release. These release notes mention support for HP and AIX; that information represents the anticipated support in a future maintenance release. To check on the current availability of this version for a specific platform, click here.

NetWare notes

On Novell NetWare^®, you install the Novell exteNd Application Server as part of the NetWare install. You can choose to install the application server during the initial NetWare install, or you can do it later after NetWare is set up.

For updated notes on installing NetWare and the application server, see the NetWare Readme.

Solaris notes

Before you run the JRE on Solaris, you must install the required patches. The patch files are shipped on the Novell exteNd product CD in the required subdirectory. You may copy the patches from the CD or you may download these patches and any newer required patches from the Sun Web site.

See sunsolve.sun.com/pub-cgi/show.pl?target=patches/J2SE for Solaris patch requirements.

HP-UX notes

Before you run the JRE on HP-UX, you must install the required patches.

See the Hewlett-Packard Web site (www.hp.com) for up-to-date information on patches (www.hp.com/products1/unix/java/patches/index.html) and HP-UX Java software.

AIX notes

Before you run the JRE on AIX, you must install any required patches.

See the Release Note Updates for more information.

Database-specific information

The Novell exteNd Application Server Database Configuration Guide provides information about configuring various types of databases to work with the application server. Use the following table to find the chapter for your database type:

To use this database type	See
Cloudscape	Configuring Cloudscape Databases
DB2	Configuring DB2 Databases (also, see updates below)
Informix	Configuring Informix Databases (also, see updates below)
Microsoft SQL Server	Configuring Microsoft SQL Server Databases
MySQL	Configuring MySQL Databases
Oracle	Configuring Oracle Databases (also, see updates below)
Sybase Adaptive Server Anywhere and SQL Anywhere	Configuring Sybase Adaptive Server Anywhere Databases
Sybase Adaptive Server Enterprise	Configuring Sybase Adaptive Server Enterprise Databases

J2EE compatibility

This version of the Novell exteNd Application Server is compatible with Java 2 Platform, Enterprise Edition 1.3 (J2EE 1.3).

To learn the details about J2EE compatibility, see the J2EE Compatibility Web site hosted by Sun at java.sun.com/j2ee/compatibility.html. It lists products that are certified to be J2EE compatible, explains how they are tested, and describes the benefits of ensuring J2EE compatibility.

Novell product compatibility

To learn about compatibility between the Novell exteNd Application Server and other Novell products:

1. Go to the Novell support Web site: support.novell.com

2. See the following document:

   Document title	Solution ID
   exteNd Application Server on NetWare	NOVL87857

Software and hardware requirements

This section describes the software and hardware needed to run these products:

• Novell exteNd Application Server
• Web Server Integration Modules
• Server Management Console
• SilverJ2EEClient
• UDDI Services

Novell exteNd Application Server

To run the Novell exteNd Application Server, you must have the following hardware and software installed:

Component	Description
Operating system	One of the following: Windows 2000 Professional (for development) or Windows 2000 Server, with Service Pack 1 or higher (see the note below) Windows XP Professional (for development) or Windows 2003 Server Novell NetWare 6.5 SP1 Solaris (Sparc) 8 or 9 HP-UX 11.0, 11i IBM AIX 5.1 (32-bit only) SuSE Linux 8.2 Enterprise (32-bit x86) Red Hat Linux AS 2.1 (32-bit x86) Red Hat Linux 9.0 (32-bit x86) To check on the current availability of the Novell exteNd Application Server for a particular platform, click here.
Minimum RAM (memory)	128 MB and up for the application server, depending on the configuration (in addition to memory required for the OS and any other applications)
Disk space requirements	250 MB for the core server product; 45 MB for the JRE
Display mode	High-color, 16-bit or higher when running the Server Management Console (SMC) with resolution 1024x768 or better
Java 2 JRE (Java Runtime Environment)	One of the following (the JRE is provided and automatically installed with Novell exteNd): Windows 2000/2003: JRE 1.4.2_01 NetWare: Novell JVM 1.4.2_02 for NetWare Solaris: JRE 1.4.2_01 HP-UX: JRE 1.4.1.03 AIX: JRE 1.4.1 Linux: JRE 1.4.2_01
CORBA ORB JMS server JTS server	Novell exteNd Messaging Platform 5.0 (provided and automatically installed with the server) For details on running the JMS server in the Novell exteNd Application Server environment, see the chapter on running the server in the Administrator's Guide.
Database connection	See Supported databases (below) On Windows and Linux, MySQL 4.1 is installed with appropriate configurations of Novell exteNd. On NetWare, MySQL 4.0 is installed when you install the Novell exteNd Application Server. In addition, MySQL 4.1 is also installed if you install the other exteNd products on NetWare. For more information on MySQL installs for Novell exteNd, see Configuring MySQL Databases.

Support for Windows 2000

This version of the Novell exteNd Application Server does not support these features that are new in Windows 2000:

• Active Directory (except as a straight LDAP provider)
• Kerberos
• The Windows 2000 load balancing and clustering features

Web Server Integration Modules

The Web Server Integration (WSI) modules are available for download at developer.novell.com/ndk/wsi.htm. These are the supported Web servers and platforms:

Web server	Platform
Apache HTTP Server 2.0 or higher	AIX, HP-UX, Linux, NetWare, Solaris, Windows NT/2000
Microsoft IIS 4.x	Windows 2000/2003
Sun iPlanet 4.x, 6.x	HP-UX, Solaris, Windows 2000/2003
Sun iPlanet 3.6	AIX

Server Management Console

The Server Management Console (SMC) of the Novell exteNd Application Server is a standalone J2EE application. It is supported on all the same platforms as the application server. It is normally installed with the server (if installed alone, it requires about 75 MB of space including the JRE, SilverCMD tools, and supporting files).

SilverJ2EEClient

SilverJ2EEClient is the J2EE application client container for the Novell exteNd Application Server. The SilverJ2EEClient installers are available for download at developer.novell.com/ndk/j2eeclient.htm. After downloading, copy the installers to the Novell exteNd AppServer\Resources\SilverJ2EEClientInstall directory on your application server host machine.

This version of the application server does not support access by earlier versions of SilverJ2EEClient; you must use the current version of SilverJ2EEClient. The current version of SilverJ2EEClient cannot access earlier versions of the application server.

Novell has a two-tier approach to platform support for SilverJ2EEClient:

Tier	Description
1	The platforms for which Novell tests and supports SilverJ2EEClient, and provides installers: Windows Solaris Linux
2	The platforms for which SilverJ2EEClient should work but that Novell will not test. They include: HP-UX AIX NetWare If you encounter a problem trying to use SilverJ2EEClient on these platforms, Novell will attempt to fix it; but the problem is likely VM-related and beyond the control of Novell. SilverJ2EEClient installers for these platforms are not provided.

To run SilverJ2EEClient, you must have the following hardware and software installed:

Component	Description
Java 2 JRE	Installed with SilverJ2EEClient
Minimum RAM (memory)	40 MB and up for SilverJ2EEClient (in addition to memory required for OS and other applications)
Minimum disk space (if installed alone)	50 MB, including the JRE

UDDI Services

You can add UDDI (Universal Description, Discovery, and Integration) capabilities to the application server by using UDDI Services. This facility is a lightweight edition of the Novell Nsure UDDI Server that comes with its own lightweight LDAP server. It supports Web Service development by providing a UDDI 2.0 test registry where you can publish and find components (using Novell exteNd Director™ or Novell exteNd Composer™) before production (when you can publish to the Novell Nsure UDDI Server).

UDDI Services is implemented as a J2EE Web application that you deploy to the application server. Everything you need to deploy UDDI Services is provided in the application server's UDDI subdirectory, along with deployment instructions and other UDDI Services documentation. The UDDI subdirectory and its files are copied to your file system during the Novell exteNd Application Server install.

Note that the exteNd Suite also contains a separate copy of the same lightweight LDAP server for test and tutorial purposes. If you run both at the same time you may have conflicts.

Supported databases

This section presents the database types and versions supported by the Novell exteNd Application Server. It's organized according to the various database uses possible in an application:

• SilverMaster and deployment support
• Connection pool support
• XA support
• EJB 2.0 container support

At the end of the section, you'll find some database vendor notes to be aware of.

General policy on database support   The tables in this section list the most recent versions of databases and drivers Novell has tested. Newer database/driver versions not listed will usually work fine for the Application Server—especially minor point releases. Older versions Novell has previously supported should still work for the Application Server as well.

If Novell knows of a specific database or driver version that is problematic, these notes will mention it. As long as you're using a database type and driver generally supported on a recent version of the Novell exteNd Application Server and are using a driver version that the vendor says is compatible with your database version, issues specific to newer databases or drivers can be submitted to Technical Support and Novell will investigate. Some issues are driver problems that Novell cannot address and that will simply require using an earlier or later version of the driver.

SilverMaster and deployment support

The following table lists databases/drivers that have been successfully tested for use as the application server's SilverMaster or as deployment databases.

Database	Driver type	Novell exteNd Application Server platforms
IBM Cloudscape 4.014	Cloudscape JDBC/Type 4 included with database	Windows, Linux, Netware, Solaris, HP-UX, AIX
IBM DB2 7.2	IBM DB2 JDBC/Type 2 Version 2.0	Windows, Linux, Solaris, HP-UX, AIX
IBM DB2 8.1	IBM DB2 JDBC/Type 2 Version 2.0	Windows, Linux, Solaris, HP-UX, AIX
IBM Informix Online Dynamic Server 2000 (9.2)	Informix Type 4 JDBC 2 driver Version 2.11.JC1	Windows, Linux, Solaris, HP-UX, AIX
Microsoft SQL Server 7.0 with Service Pack 2 or later	Microsoft ODBC driver for SQL Server version 3.70.09.61 with Novell exteNd JDBC-ODBC bridge (see the Note on deprecation)	Windows
Microsoft SQL Server 2000	Microsoft ODBC driver for SQL Server version 2000.80.194.00 with Novell exteNd JDBC-ODBC bridge (see the Note on deprecation)	Windows
Microsoft SQL Server 2000	Microsoft JDBC driver for SQL Server version 2.2.0022	Windows, Linux, Netware, Solaris, HP-UX, AIX
MySQL 4.0.16	Connector/J 3.0.6	NetWare
MySQL 4.1	Connector/J 3.0.6	Windows, Linux, NetWare
Oracle 8i (8.1.7)	Novell exteNd Oracle 8 driver with Oracle 8i client (see the Note on deprecation)	Windows, Linux, Solaris, HP-UX, AIX
Oracle 8i (8.1.7)	Oracle Thin JDBC 8.1.7 Driver	Windows, Linux, Netware, Solaris, HP-UX, AIX
Oracle 9i (9.0.1.1.1)	Oracle Thin JDBC 9.0.1.1.0 Driver	Windows, Linux, Netware, Solaris, HP-UX, AIX
Oracle 9i (9.0.1.1.1)	Oracle OCI Driver	Windows, Linux, Solaris, HP-UX, AIX
Oracle 9i (9.2.0.1)	Oracle Thin JDBC 9.2.0.1 Driver	Windows, Linux, Netware, Solaris, HP-UX, AIX
Oracle 9i (9.2.0.1)	Oracle OCI Driver	Windows, Linux, Solaris, HP-UX, AIX
Sybase Adaptive Server Enterprise 11.9.2	jConnect 4.x, jConnect 5.2	Windows, Linux, Netware, Solaris, HP-UX, AIX
Sybase Adaptive Server Enterprise 12.5	jConnect 5.5	Windows, Linux, Netware, Solaris, HP-UX, AIX
Sybase Adaptive Server Anywhere 8.0	jConnect 5.5	Windows, Linux, Netware, Solaris, HP-UX, AIX

Note on deprecation   The Novell exteNd JDBC-ODBC bridge and the Novell exteNd Oracle drivers are deprecated. Novell recommends that you use the vendors' JDBC drivers to connect to your databases.

Connection pool support

The application server supports JDBC access to databases via connection pools. JDBC connection pools can be established for databases that provide either a JDBC 1.0 or JDBC 2.0 driver.

For more information on connection pool support, see the chapter on data source configuration in the Administrator's Guide.

XA support

The following table lists databases/drivers that have been successfully tested with the application server's XA (global transaction) support in connection pools.

Database	Driver type	Novell exteNd Application Server platforms
IBM Cloudscape 4.014	Cloudscape JDBC/Type 4 included with database	Windows, Solaris, HP-UX, AIX, Linux, NetWare
IBM DB2 7.2	IBM DB2 JDBC/Type 2 version 2.0	Windows, Solaris, Linux
Oracle 8i (8.1.7)	Oracle Thin JDBC 8.1.7 Driver	Windows, Solaris, HP-UX, AIX
Oracle 9i (9.0.1.1.1)	Oracle Thin JDBC 9.0.1.1.0 Driver	Windows, Solaris, HP-UX, AIX
Oracle 9i (9.2.0.1)	Oracle Thin JDBC 9.2.0.1 Driver	Windows, Solaris, HP-UX, AIX, Linux, Netware

EJB 2.0 container support

The following table lists databases/drivers that have been successfully tested with the application server's EJB 2.0 container.

Database	Driver type	Novell exteNd Application Server platforms
IBM Cloudscape 4.014	Cloudscape JDBC/Type 4 included with database	Windows, Linux, Netware, Solaris, HP-UX, AIX
IBM DB2 7.2, 8.1	IBM DB2 JDBC/Type 2 version 2.0	Windows, Linux, Solaris, HP-UX, AIX
IBM Informix Online Dynamic Server 2000 (9.3)	Informix Type 4 JDBC 2 driver Version 2.11.JC1	Windows, Linux, Solaris, HP-UX, AIX
Microsoft SQL Server 2000	Microsoft JDBC driver for SQL Server version 2.2 patch 1	Windows, Linux, Netware, Solaris, HP-UX, AIX
MySQL 4.0.16	Connector/J 3.0.6	NetWare
MySQL 4.1	Connector/J 3.0.6	Windows, Linux, Netware
Oracle 8i (8.1.7)	Oracle Thin JDBC 8.1.7 Driver	Windows, Netware, Solaris, HP-UX, AIX
Oracle 9i (9.0.1.1.1)	Oracle Thin JDBC 9.0.1.1.0 Driver	Windows, Linux, NetWare, Solaris, HP-UX, AIX
Oracle 9i (9.0.1.1.1)	Oracle OCI Driver	Windows, Solaris, HP-UX, AIX
Oracle 9i (9.2.0.1)	Oracle Thin JDBC 9.0.1.1.0 Driver	Windows, Linux, NetWare, Solaris, HP-UX, AIX
Oracle 9i (9.2.0.1)	Oracle OCI Driver	Windows, Solaris, HP-UX, AIX
Sybase Adaptive Server Enterprise 12.5	jConnect 5.5	Windows, Linux, NetWare, Solaris, HP-UX, AIX
Sybase Adaptive Server Anywhere 8.0	jConnect 5.5	Windows, Netware, Solaris, HP-UX, AIX

Database vendor notes

This section provides details you should know about Novell exteNd Application Server support for particular databases. Topics include:

• Support for DB2
• Support for Informix
• Support for Oracle

Support for DB2

• JDBC2 connection pools for XA transactions   To create JDBC2 connection pools for XA transactions with DB2, you can create your connection pools in one of two ways:
  • By specifying the XADatasource class and a properties list:

       SilverCmd AddCP yourASHostname yourPoolName J -U administrator -P admin
       -A user -W password -p "databaseName=MIKEDSM" -g COM.ibm.db2.jdbc.DB2XADataSource -m 4

  • By using the LDSKey from the platforms.dbl file (located in the application server's \Resources directory) and a properties list:

       SilverCmd AddCP yourASHostname yourPoolName -J -U administrator -P admin
       -A user -W password -l IBMDB2V6 -p "databaseName=YOURDB" -m 4

  Note that the LDSKey IBMDB2V6 is correct for DB2 version 7.x.

Support for Informix

• Unsupported driver versions   Versions 2.2 and 2.22 of the Informix Type 4 JDBC driver are not supported.

Support for Oracle

• Lib path requirement with Oracle 9i   On HP-UX and AIX, you must add $ORACLE_HOME/lib32 (not $ORACLE_HOME/lib) to the SHLIB_PATH (HP) and LIBPATH (AIX) environment variables when using Oracle 9i.

• Unsupported SQLNet client version   If the application server hangs during server startup, check to see if you are running SQLNet Client Version 2.3.3.0.0. The application server does not support this version of SQLNet and Novell recommends that you upgrade the SQLNet client to 2.3.4. You can obtain this upgrade from Oracle Corporation.

What's new

For information about new features, see What's New in the application server's help.

Upgrade notes

This section lists server changes that may affect you when upgrading to the latest version.

• Rebranding
• J2EE
• Database
• Configuration
• General
• Legacy

Rebranding

As of Version 5.0, this product is branded Novell exteNd Application Server. Earlier versions were branded SilverStream^® eXtend Application Server. If you are upgrading from one of those earlier versions, note that the following changes have been made for the product's rebranding:

• Default install directory   When the application server is installed on Windows, the default install directory is C:\Program Files\Novell\exteNdn\AppServer. (It used to be C:\Program Files\SilverStream\eXtendAppServer.)

  When the application server is installed on UNIX or Linux, the default install directory is /opt/Novell/exteNdn/AppServer. (It used to be /opt/silverstream.)

• Program group   When the application server is installed on Windows, the following program group is created: Novell exteNd n.n>AppServer. (It used to be SilverStream eXtend>AppServer n.n.)

• Environment variables   When the application server is installed on Windows, an environment variable is created (for use by sample applications) to point to the server product directory. This environment variable used to be named SILVERSTREAM_HOME. It is now NOVELL_EXTEND_APPSERVER_HOME. (SILVERSTREAM_HOME is still provided in this release, but it is deprecated.)

  When the application server is installed on UNIX or Linux, the environment file .agprofile is created to set environment variables that the server needs at runtime. The environment variable that points to the server's root location is named EXTENDAPPSERVERROOT. (It used to be SILVERSTREAMROOT.)

• Database drivers   The SilverStream JDBC-ODBC bridge driver is now the Novell exteNd JDBC-ODBC bridge driver. The SilverStream Oracle drivers are now the Novell exteNd Oracle drivers. (Note that these drivers are deprecated.)

• SMC   The SMC used to be the SilverStream Management Console but is now the Server Management Console.

• Command-line options   Some of the startup options you can specify on the command line for server executables (SMC, SilverCmd, SilverJ2EEClient) have been renamed. Specifically, all options that used to start with -ss_ now start with -as_. For example, -ss_password is now -as_password. (The -ss_ option names are still supported in this release, but they are deprecated.)

• Server startup options for EJB debugging   The SSSWEJBDebug server startup option is now EJBDebug. The SSSWEJBDebugName server startup option is now EJBDebugName.

• EJB deployment plan   In the DTD (XML document type definition) for the EJB deployment plan, the element nonSSSWPersistenceInfo has been renamed to externalPersistenceMgr.

• Deployment plan in archive   When you create a J2EE archive for deployment to the application server, you have the option of storing the deployment plan inside that archive. If you do, the deployment plan must be named appserver.xml. (It used to be silverstream.xml.)

• Directory for temporary files during deployment   If you have a HOME environment variable defined, the SilverCmd deployment commands (such as DeployEAR) store temporary files in the %HOME%\.appsrv directory. (This directory used to be named %HOME%\.silverstream.)

• Security realm string   The application server's security realm string now defaults to Silver Security. This string is displayed in the server login dialog. It is also passed on the WWW-Authenticate response header sent to the client.

  If you want to change the security realm string, you can now use the property com.sssw.srv.http.authHeaderRealm in the httpd.props file. (Previously, this string was set to SilverStream and you couldn't change it.)

• What's not changed   Several aspects of the application server are not affected by rebranding, even though they involve names containing Silver, Ag, or SSSW. This is primarily to ensure backward compatibility for J2EE applications developed under earlier versions of the server. Things that haven't changed include:
  • Names of executable files (such as SilverServer.exe) in the server's bin directory

  • Names of JAR files (such as SilverServerAll.jar) in the server's lib directory

  • Use of the name SilverMaster to refer to the server's system database

  • Use of the name Silver Security to refer to the server's native security (and the login realm name remains SSSW)

  • Package and class names (such as com.sssw.rts.adminapi.AgiAdmServer) in the server's API

  • Property names in the httpd.props file (such as http-server.com.sssw.srv.port_rt)

  • Use of the AGCLASSPATH environment variable to set the server's classpath

  • Server system table names (such as AgContents)

  • Server system URLs including the name SilverStream, such as:

       http://servername/SilverStream/Statistics/

J2EE

• Redeploy required when upgrading   If you have existing J2EE applications running on an earlier (pre-5.0) version of the server, you must redeploy them in order to run on the 5.x server. This requirement applies to both J2EE 1.2 and J2EE 1.3 applications.

• J2EE 1.3 deployment plans required   As of 5.0, the server no longer supports J2EE 1.2 deployment plans for any archives (EARs, WARs, EJBs, and so on). You must use J2EE 1.3 deployment plans, even if deploying J2EE 1.2 archives (which have J2EE 1.2 deployment descriptors). Novell exteNd Director includes facilities to help you upgrade deployment plans from 1.2 to 1.3 (see "How to Handle J2EE Versions" in the Utility Tools book of the exteNd Director help).

  For more information on the supported deployment plans, see the chapter on deployment plan DTDs in the Facilities Guide.

• Moving to the EJB 2.0 container   As of 5.0, the old EJB 1.1–only container has been removed from the server. As a result, you'll use the EJB 2.0 container for all EJB deployments, including 1.1 and 2.0 EJBs.

  Whether you're deploying 1.1 or 2.0 EJBs, you'll need to use an EJB 2.0 deployment plan. If you're starting with 1.1 EJBs and EJB 1.1 deployment plans, you must at least migrate those plans to 2.0. Migrating the beans themselves to 2.0 EJBs is recommended but not required.

  For more information on the EJB 2.0 container, see the server implementation notes chapter in the Facilities Guide.

• SilverJ2EEClient installation   As of 5.0, installation of SilverJ2EEClient is independent of SilverJRunner (which has been removed). As of 5.1, the SilverJ2EEClient installers:
  • SilverJ2EEClientInstall.exe
  • SilverJ2EEClientInstallSolaris.sh
  • SilverJ2EEClientInstallLinux.sh

  are no longer included on the product CD. You must download them from the Novell Web site and set them up on your server. Then users can access them from your server's SilverJ2EEClient install page:

     http://servername/SilverStream/Pages/SilverJ2EEClient.html

  or directly from this location:

     http://servername/SilverStream/SilverJ2EEClientInstall/

• Setting permissions for deployed archives   As of 5.0, the SMC's Security/Permissions panel lists deployed J2EE archives under the Deployed Objects directory. In earlier versions of the server, this directory was named EJB JARs & Media.

• ClassLoader hierarchy issues   See EJB java.lang.NoClassDefFoundErrors in the "Known issues" section of these release notes (below).

• JAR organization for deployed EJBs   As of 4.0, there are no more remote JARs for deployed EJBs. Instead, you need to add the client JAR (which contains the stubs, ties, and so on) into the client archive and deploy. This provides cross-vendor access of EJBs.

• Support removed for a JAR access technique   In 3.7.x you could add a JAR to the ObjectStore and reference it via a manifest classpath entry from a WAR, EJB, and so on. This is not supported as of 4.0.

• Path mapped URL patterns need leading slash   As of 4.0, you must have a leading slash in any path mapped URL patterns. In 3.7.x, this requirement was not enforced.

  This change may affect exteNd Director applications when you upgrade them to J2EE 1.3 to run on your post-3.7.x server. For example, you may discover that resources in a resource set cannot be found. The solution is to change $CONTEXT_URL$resource to $CONTEXT_URL$/resource and change the resource servlet mapping from:

     <url-pattern>resource/*</url-pattern>

  to:

     <url-pattern>/resource/*</url-pattern>

• JSP URLs need .jsp   As of 4.0, the .jsp extension is required when you reference a JSP page via an URL. In 3.7.x you could reference the JSP page as pagename instead of pagename.jsp:

     http://localhost/directory/mypage?parm=x

  Now you need to specify:

     http://localhost/directory/mypage.jsp?parm=x

• Tag library access for included JSP pages   In 3.7.x if you had a JSP page (aaa.jsp) that included other JSP pages (bbb.jsp and ccc.jsp), then ccc.jsp would get access to custom tag libraries declared in bbb.jsp. This was incorrect behavior. As of 4.0, you must do one of the following instead:
  • Reference the TLD in both bbb.jsp and ccc.jsp
  • Reference the TLD in aaa.jsp (which automatically gives bbb.jsp and ccc.jsp access to it)

Database

• ASA and Cloudscape DBMSs no longer installed   As of 5.1, the Sybase ASA (Adaptive Server Anywhere) and IBM Cloudscape DBMSs are no longer provided with the application server install. The DBMS provided with the application server is now MySQL.

  If you want to continue using ASA, you can keep running the ASA version that was installed with your old application server. Or you can obtain the latest ASA version from Sybase.

  If you want to continue using Cloudscape, obtain the Cloudscape software from IBM.

Configuration

• Converting an RSA certificate to be FIPS-compliant   If you have an RSA certificate installed on your application server, but want to configure that server to be FIPS-compliant once you install 5.1, you must convert the RSA certificate to be FIPS-compliant. You can use the SMC to perform this conversion. Before you upgrade to 5.1, use the SMC to:
  1. Export the certificate
  2. Re-import the certificate

  For more information, see the chapter on setting up security in the Administrator's Guide.

• Consolidation of the server's port types   As of 5.0, you can configure two separate port types for handling the application server's operations: administration and runtime. The design port type (supported in earlier versions) has been consolidated into the administration port type.

• Support removed for enCommerce getAccess   As of 5.0, support for enCommerce getAccess is removed from the Web Server Integration (WSI) modules.

• New guidelines for client connections   The guidelines for determining your application server's client connection settings have been updated as of 5.0. For more information, see the chapter on tuning the server in the Administrator's Guide.

• JAR-related changes on the server   As of 5.0, the following JARs have been removed from the application server's \lib and \userlib directories (because JRE 1.4 provides all classes contained in these JARs):
  • Removed from \lib:

       crimson.jar
       jaas.jar
       jndi.jar
       ldap.jar

  • Removed from \userlib:

       crimson-java_xml_pack_fall_2001.jar
       xalan-java_xml_pack_fall_2001.jar
       xerces-1_4_4.jar
       xercesImpl-2_0_1.jar
       xmlParserAPIs-2_0_1.jar

    Because the XML classes are now included with the JRE, the excludeJ2EEXMLJars subelement of the EAR, EJB, and WAR deployment plans is ignored. Make sure you test applications that relied on the classes in the XML JARs (in the \userlib directory). The XML classes included with JRE 1.4 do not provide backward compatibility.

• How upgrading affects the name service port   As of 4.0, the property that specifies the server's name service port has been moved from the httpd.props file to the SilverMaster database. When you upgrade your server from an earlier version, the name service port will be reinitialized to 54890. If any of your servers use a value other than 54890 for the name service port, you will have to update the name service port to the value you want to use. After you upgrade your servers, you can change the name service port using the SMC or SilverMasterInit with the -C option (the latter is the required way if you are running multiple instances of the server on the same machine).

  In the SMC, the name service port setting is in the ORB settings section of the Configuration/General panel. Make sure to click Update after setting the value.

  To use the SilverMasterInit -C option, you'll need to create a property file. The property file can have any name and can reside in any location that is accessible to SilverMasterInit. The property file has the same syntax as the httpd.props file, except that you do not specify http-server in front of the property; instead, you specify hostname.portnumber (note that the host name and port number are separated by a dot and not a colon). The port number is the administration port and is required only when it is some value other than 80. To set the nameServicePort, specify:

     hostname.portnumber.com.sssw.srv.nameServicePort=nnnn

  For example:

     tundra.8080.com.sssw.srv.nameServicePort=55597

  When you run SilverMasterInit you should also use the -r option, because it will update an existing SilverMaster. This example shows how to use SilverMasterInit with the property file called port.props:

     SilverMasterInit -C port.props -U smbb -P password -A administrator -W admin -r

General

• Localization   The list of languages for which the server provides runtime support has changed. The supported languages as of 5.0 are:
  • Simplified Chinese
  • Traditional Chinese
  • English
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Portuguese
  • Russian
  • Spanish

  For more on localization, see the server implementation notes chapter in the Facilities Guide.

• Status of Server Administration API   Though not deprecated in this release, the existing Server Administration API will likely be replaced in Version 6.0 of the application server by the J2EE Management API, which will result from JSR-77 and be part of J2EE 1.4. The J2EE Management API will provide a standard model for managing J2EE environments. For more information about the J2EE Management API, see jcp.org/jsr/detail/77.jsp.

  As of Version 5.0 of the application server, reference documentation (including javadoc) for the Server Administration API is no longer included in the application server's help. Instead, this documentation is available on request from Novell.

• Remote UserTransaction support   Support for remote UserTransaction objects is deprecated as of Version 4.0 of the application server. If you use this feature, it should only be to maintain backward compatibility with existing applications. When looking up the remote UserTransaction object, make sure you use the old-style lookup string RMI/SilverStream-UserTransaction. For example:

     utx = (UserTransaction)PortableRemoteObject.narrow( initialContext.lookup(
           "RMI/SilverStream-UserTransaction" ), UserTransaction.class);

Legacy

• Classic features removed   In Version 4.x of the application server, the legacy SilverStream tools and technologies are supported but deprecated. As of Version 5.0, the application server no longer includes these classic features. The 5.x server is strictly for standard J2EE development and deployment.

Known issues

Here are some noteworthy issues or problems that apply to this version of the Novell exteNd Application Server.

• Install issues
• Database issues
• Administration issues
• Deployment issues
• Runtime issues
• EJB issues
• Web Service issues

Install issues

• Path requirements for running new and old versions   Installing the application server on Windows will append the server's installation directory to your path. If you are keeping an earlier version of the application server on the same machine, you should change your path so that the version you are currently running comes first. Running both at the same time is not recommended and may result in some unexpected behavior—but if you try it, the more recent version should appear first on your path.

Database issues

• Troubleshooting for Microsoft JDBC driver   If you have trouble using the Microsoft JDBC driver, placing the required JAR files in a location without spaces in the path may help. (The default install location for this driver will contain a number of spaces.)

Administration issues

When updating name service port   If your server uses a fully qualified domain name (such as myserver.mydomain.com), you will not be able to use SilverMasterInit -C to update your name service port. You will instead need to start the server and use the SMC to modify the port number. Be sure to use the fully qualified name when adding the server in the SMC in order for the port modification to take effect properly.

Deployment issues

• Deploying to the SSL administration port   If you deploy to the SSL administration port using SilverCmd, make sure you specify the HTTPS protocol with your server name (for example, https://localhost:8080). Otherwise, SilverCmd will block until the connection times out or until you initiate a break (via Ctrl+C or equivalent). (PPR 34573)

• Supported compilers   The SJ compiler listed in Compileroptions.xml is not supported.

• isEnabled setting for WARs   WARs with isEnabled set to false in the deployment plan are nonetheless enabled after deployment. (PPR 24720)

• Avoiding Sybase ASE deadlock during deployment   If you deploy a large and/or complex application to Sybase Adaptive Server Enterprise, in rare cases the database may deadlock. You can reduce the possibility of deadlock by reducing the number of threads used by the deployer to one. If that does not resolve the problem, there is a workaround involving dropping and adding indexes on a server system table; contact Technical Support.

Runtime issues

• OutOfMemoryError on Linux   If you get the failure message java.lang.OutOfMemoryError when running the application server on Linux, the problem may be insufficient threads. In this case, you need to increase the value of the tasks.h parameter NR_TASKS. (PPR 22849)

EJB issues

• EJB java.lang.NoClassDefFoundErrors   If you encounter java.lang.NoClassDefFoundErrors when running entity or session beans, it may be a JAR packaging problem. The server's ClassLoader hierarchy is:
  • EAR ClassLoader (highest level)
  • EJB ClassLoader
  • WAR ClassLoader (lowest level)

  A WAR delegates to an EJB, and an EJB delegates to an EAR.

  Classes loaded by a ClassLoader at a lower level can access any class loaded by a ClassLoader at a higher level (a component can call up the hierarchy, but not down it). For example, any class loaded by the WAR ClassLoader can access any class loaded by the EJB ClassLoader or the EAR ClassLoader. But the reverse is not true: a class loaded by the EAR ClassLoader cannot access a class loaded by the EJB ClassLoader or the WAR ClassLoader.

• Support limitation for CA certificates   The application server does not support the following CA certificates with EJBs using SSL over IIOP:
  • Autoridad Certificadora de la Asociacion Nacional del Notariado Mexicano,A.C..der
  • Autoridad Certificadora del Colegio Nacional de Correduria Publica Mexicana,A.C..der
  • C&W HKT SecureNet CA Class A.der
  • C&W HKT SecureNet CA Class B.der
  • C&W HKT SecureNet CA Root.der
  • C&W HKT SecureNet CA SGC Root.der
  • Equifax Secure Certificate Authority.der
  • Equifax Secure eBusiness CA-2.der
  • EUnet International Root CA.der
  • Saunalahden Serveri CA.der
  • Saunalahden Serveri CA_2.der

• Setting establishTrustInClient for EJB 2.0 IOR security   SUPPORTED mode for EJB 2.0 IOR security establishTrustInClient (subelement of the deployment plan's transportConfig and iorSecurityConfig elements) doesn't provide predictable SSL behaviors. Use NONE or REQUIRED mode for applications. (PPRs 34450 and 34441)

Web Service issues

• Web Service access problems with 100 continues   You may find that a Web Service works fine from a standalone Java program but hangs or generates SocketExceptions when called from the Novell exteNd Application Server. The problem is probably that the server hosting the Web Service claims to be HTTP1 1.1 compliant but doesn't support 100 continues properly. When HTTP client code running in the application server makes a request of a server with this bug, there will be some problems. The first request to the server will work (regardless of whether it's a GET or a POST), but the next POST request will hang or throw a SocketException.

  The best thing to do is see if there is a later version of the server software and proxy software. Most webmasters will be happy to get their sites working well. Novell knows that the following servers and proxies have this problem:

  • GLUE versions before 3.1 (www.themindelectric.com/glue/index.html)

Problems fixed in Version 5.1

Number	Description
34889	DB-MySQL - No column information in DB Metadata for tables in MySQL
35100	EJB - Message Beans - Error when selecting a deployed MDB in 'Deployed Objects' screen
35508	Deployment - WARs - JSP tag attribute values that span lines generate invalid Java
36082	Server General - ConcurrentModificationException shutting down server
36100	Deployment - WARs - Must specify full paths to WAR and DP to SilverCmd on Linux
36258	Administer Server/SMC - NPE when clicking on ClusterName entry in list when server is down
36288	EJB - Entity Beans - Oracle 9.2 has problem handling Date (ConcurrencyViolation)
36365	Security (AppServer) - Change default for J2EE security checks on group membership
36433	SSL (AppServer) - Creating a cluster whose member servers use SSL hangs the SMC
36436	SilverJ2EEClient/CARs - SilverJ2EEClient exits silently if client cert info is incorrect.
36443	JSP-Java Server Pages - Illegal to flush within a custom tag at TSS
36456	Administer Server/SMC - AgoConnectionException using SMC against a cluster with a down member server
36468	JSP-Java Server Pages - Struts 1.1-rc1 tiles-documentation.war does not deploy - NPE
36533	Servlets - File at javax.servlet.context.tempdir does not exist sometimes
36561	Deployment - WARs - NPE when deploying from workbench if web.xml does not have taglib entry.
36566	SilverCmd - Invalid name with SetUserGroupInfo CreateUser corrupts SMC User display
36578	JSP-Java Server Pages - JSP include chain can lose request parameters
36596	UDDI Services - Server fails to shut down cleanly when running UDDI
36626	JNDI (AppServer) - Unexpected behavior when looking up java:comp/env
36627	EJB - Entity Beans - EJB Container pooling code bug caused unexpected exception
36694	WSI (Web Plugin) - WSIWatcherInterval directive not recognized
36723	Administer Server/SMC - AgiAdmDeployedObject.isActive() is returning true for a EJB jar that is shutdown
36769	Administer Server/SMC - Need way to set com.sssw.srv.http.authHeaderRealm from SMC
36800	Connectors J2EE (AppServer) - should give same error message as other silvercmd when dp is not specified
36803	Admin API - LDAP providers added to cluster members don't show up if added by SilverCmd
36806	WSI (Web Plugin) - WSI for Apache on Linux, connection pool does not work
36807	WSI (Web Plugin) - WSI for Apache on Linux, WSITraceDirectory causes segmentation fault
36833	jBroker TM - Transaction manager errors: java.lang.NullPointerException (out of disk space)
36859	Administer Security/SMC - Server Login Prompt - Inconsistent behavior after failed login.
36866	Administer Server/SMC - Log file fields not visible when logging set to "File"
36937	SilverCmd - Unable to add Database to a remote server via SilverCMD
36938	WSI (Web Plugin) - WSI for Apache creates trace files with trace level = 0
37249	EJB - Session Beans - Calls to remote ejbs have remote references coverted to hostname
37261	Connection Pooling (AppServer) - Unable to change connection properties if min set too high
37323	Admin API - SMC Restart button does not work when server running as a service
37505	EJB - Entity Beans - Concurrency violation on update and delete to MySQL
37553	SilverCmd - SilverCMD getConsole -p throws incorrect error message
37583	Administer Security/SMC - Editing LDAP Security Provider, Toggling SSL change not sticking
37679	EJB - Session Beans - ejbRemove() not called when a stateless SB is undeployed
37730	Administer Server/SMC - SMC does not refresh info in panel after making changes and changing panels
38158	Server General - Restarting AppServer via SMC doesn't restart the server on NetWare 6.5
38159	WSI (Web Plugin) - Apache Web Server abends while running Nessus - security scanner tool
38162	Server General - When starting SilverServer with wrong heap setting the NLM will not exit complet
38249	Server General - appserver does not pick up agclaspath larger than 520 characters
38748	Administer Server/SMC - Reword and rework New JDBC Connection Pool dialog
39047	Cluster Tools - Cluster build fails with unable to contact dispatcher error message
39093	Design Env General - failure on the part of AppServer 4.0 and 5.1 to call the init() method for each
39457	Administer Server/SMC - JTS Property updates do not work
39682	SilverCmd - SilverCMD changes AppServer\Resources\Preferences\user.prefs improperly
39731	JNDI (AppServer) - JNDI lookup failures when trying to execute a JMS Send from a Servlet on the app
39895	EJB QL - Remote finder methods fail with EOFException
40336	Admin API - Unable to update Servlet Background Thread Pool property in a cluster
40343	SilverCmd - SilverCmd errors are directed to wrong output in Linux platform
40379	Administer Server/SMC - The Cancel Login when selecting Undeploy causes the EAR  to undeploy
40420	Security (AppServer) - Unable to create security files from the SMC without privileges - no messages
40611	Security (AppServer) - Server won't permit login after twelve hours or so , dbping not working
40684	Administer Server/SMC - Unable to get back to Debug pane of Advanced tab of SMC if server in a cluster
40732	Connectors J2EE (AppServer) - trace connector loglevel should overwrite the <logLevel> value in dp<
40747	EJB - Entity Beans - Can not mark member variable as "protected" in primary key class
40786	SilverCmd - SilverCmd fails with unsecured silvermaster
40789	Servlets - failed to get Root Cause Throwable from ServletException
40816	Server General - Missing timestamps in error log when logging to file
40835	UDDI Services - com.sssw.shr.http.AgoServletException
40914	Security (AppServer) - AppServer on a workgroup only Win2K box does not return any users or groups
40921	WSI (Web Plugin) - Mod WSI abend- Apache2.nlm when loading the server. Memory problem with Mod WSI
40952	Security (AppServer) - Unnecessary Native mode calls made during NT login
41094	Deployment-EARs - NPE when deploying a TSS version of PetStore; trivial EAR deploys w/o error
41099	Administer Server/SMC - Problem with Global Transaction (XA) checkbox in Add Connection Pool dialog
41132	Administer Server/SMC - Unable to set transaction log location in smc
41177	HTTP (AppServer) - trace client 0 doesn't disable http session manager debug output
41230	API (Director Portal) - Portal Aggregator throws exceptions when running with multiple threads
41284	DB-MySQL - SQL exception - Duplicate entry to AGSESSBEANS table...
41299	JSP-Java Server Pages - foo is already defined in _jspService when compiling JSP
41427	Administer Server/SMC - AppServer commandshell should be able to read from a named pipe on Linux
41452	Server General - filecache directory location can't be configured
41513	Security (AppServer) - Can't login as newly added ldap user
41632	WSI (Web Plugin) - Apache Web Server still abends when running Nessus
41677	Administer Server/SMC - SMC of Appserver5.0 is not correct key mapping on Japanese environment.
41689	jBroker TM - OutOfMemoryError when starting TM with corrupt log
41723	DB-MySQL - MySQL generates the wrong datatype for LongVarChar
41811	Deploy (Director) - ExpressPortal deploy fails with ClassNotFoundException
41828	Admin API - Get Corba ciphersuites only return a portion of valid ciphersuites
41838	Security (AppServer) - Getting NT System information is very slow
41921	Server General - Appserver stops responding after several hours under load (on NetWare)
41941	Connection Pooling (AppServer) - com.sssw.srv.resourcepool.ResourcePoolSystemException: Illegal operation on pool
42008	Servlets - IOExceptions are not propagated back to the calling class from included servlets
42011	HTTP (AppServer) - GetRequestURI and getContextPath called on included requests includes DB name
42035	HTTP (AppServer) - HTTPSession is a different object across requests to the same deployed WAR
42071	HTTP (AppServer) - Invalidating session and then calling isRequestedSessionIDValid results in TRUE
42188	Servlets - getRequestedSessionID returning null when client provides jsessionid
42251	HTTP (AppServer) - Calling setMaxInactiveInterval method on session doesn't timeout session
42488	DB-DB2 - platforms.dbl needs support for DB2 JDBC Type 4 driver
42491	Security (AppServer) - CommuncationException using LDAP server with SSL
42502	Administer Server/SMC - Updates to server aren't sent if you change the port number and press Update
42509	Administer Server/SMC - Shouldn't need to restart a server in a cluster if you add an LDAP provider