These release notes contain the following sections:
Note | The following list is based on new features in iPlanet Application Server, Enterprise Edition, 6.5 release. For the complete list of changes from iPlanet Application Server 6.0, SP1, refer to the Release Notes for each intervening Support Pack releases at: http://docs.iplanet.com/docs/manuals/ias.html.
|
iPlanet Application
Server determines the transaction type for a particular component/application
by initially referring under the J2EE-module name, followed by the component
<classdef\<guid>, and finally for the instance wide value under <CCSO\TXNMGR>.
The message-driven bean functionality in this release is certified for developer use only.
For more
information, see chapter 7, "Using Message Driven Beans" in the Developers
Guide, and chapter 15, "Configuring JMS Providers", in the Administration
Guide.
The J2EE 1.3 RI ORB is Portable Object Adaptor (POA) compliant and makes upgrades easier in the future.
This ORB upgrade provides better performance and scalability in the rich client path. A few bugs in the J2EE 1.3 RI ORB have been fixed in the ORB version bundled with iPlanet Application Server.
A few classes, which were earlier part of J2EE 1.2 RI ORB, have been moved to JDK1.3. Consequently, the class definitions and packages of some of these classes have changed.
The orb.properties file has been modified by commenting out some of the properties, since default values for those properties must be used for J2EE 1.3 RI ORB.
- SOAP applications assume index.html as the default welcome file. However, there is no default welcome-file in iPlanet Application Server. You can modify either the web.xml of soap.war, or make index.html, or index.jsp as the default welcome files.
- SOAP uses the JAXP 1.1 compliant parser. You have to either upgrade to the current XML parser or use JAXP 1.1 compliant Xerces parser, because iPlanet Application Server bundles the JAXP 1.0.1 compliant parser.
Developer's Resources for iPlanet Application Server 6.5 includes:
For more information about installing and using the Developer Resources Integration modules for
developing applications for the iPlanet Application Server, consult the ReadMe located on
the product CD in devtools/readme.html
.
Additionally, the most up-to-date Developers Resources documentation can be found at: http://docs.iplanet.com. Select the Developer Pack link to locate the latest documentation for developers.
Use the Redeploy option in the Deploy dialog box to redeploy applications quickly. The Deploy Tool compares the old and the modified application/module and appends ias_hotdeploy_ to the new file. This file is then replaced in the appropriate directory and the necessary changes to the registry are made.
Deployment Tool offers an easy way to migrate your datasource descriptors, which are in the old format, to the new datasource XML formats.
The datasource registration screens have been changed to support the new datasource registration options.
Transaction Manager type (local/global) can be specified at application level, J2EE-module level, or at the component level, during deployment.
Deployment Tool modified with Message-driven bean specific options.
The following monitoring and tracing features are available in 6.5:
This sample demonstrates the following features:
This sample demonstrates how to access EJBs directly using Apache SOAP EJBPluggableProvider class.
This sample application demonstrates Java Message Service (JMS) support built into iPlanet Application Server. The Chat sample application is based on a servlet accessing a JMS queue and then displays the results through the same servlet. The servlet sends a simple message from a queue to another queue and then receives the same message from the queue and displays it through a servlet.
This sample location provides an introduction to the integration of CORBA components with iPlanet Application Server. These samples focus on the use of servlets and EJBs acting as clients to existing backend CORBA objects using Visibroker ORB. This document explains the configuration of a third party ORB to interoperate with iPlanet Application Server, and the deployment of small-scale samples applications to demonstrate the interoperability.
You will have to configure the datasource with a third party driver.
Note | Applogics based applications will not
be affected by this change.
|
For more information on configuring datasources, see Chapter 8, "Administering Database Connectivity" in iPlanet Application Server Administrator's Guide.
As a result, C++ Applogics based applications might have to be recompiled and change native code to follow ANSI/ISO C++ standard, and install additional OS/Compiler patches.
You will have to rename all occurrences of gx_session_id to GX_SESSIONID, if you are using this parameter in your applications.
In this method you only need to specify the contentType in the page that includes the other JSP.
See JSP specifications for more details about the differences between static and dynamic includes.
Use this method to display Japanese messages correctly in a message-driven bean Java Client.
Since the application uses com.kivasoft.util.GX, as it is an internal API, you have to set $LD_LIBRARY_PATH to /ias/gxlib to enable the JMS client to send messages.
JAVA_ARGS="-server -Xss512k -Xms128m -Xmx1024m"
Refer to http://www.hp.com/products1/unix/java/java2/sdkrte1_3/infolibrary/sdk_rnotes_1-3-1-02.html for details on VM parameters.
The heap values will need to be changed based on available system memory. In previous versions of iPlanet Application Server, the default values of minimum & maximum heap used to be 64 MB. Due to the change in default values, the memory startup footprint will be higher.
Note | If your system does not have 1GB memory, then reduce the maximum heap size to fit your system's resources. |
Note | On the product CD, the Readme lists iPlanet Web Server, Enterprise Edition, 6.0.1 as iPlanet Web Server, Enterprise Edition 6.0, SP2b. The correct version number is 6.0.1.
|
Note | You must restart your HP-UX system after
applying these patches.
|
HP-UX Patches
Open iAS_InstallDir/ias/env/iasenv.ksh file and replace PA_RISC2.0 with PA_RISC in the JRE path entry.
For detailed instructions on installing the iPlanet Directory Server 5.0 SP1 patch, follow the directions listed for Solaris in iPlanet Application Server Installation Guide.
Directory Server | Version |
---|---|
iPlanet Directory Server | 5.1
5.0 SP1 (bundled with iPlanet Application Server 6.5) 4.13 |
Platform |
Version |
JVM |
---|---|---|
HP-UX | HP9000 architecture with PA-RISC 1.1 or 2.0 CPU | JDK 1.3.1_002 |
Note | On Oracle, transactions are supported on Oracle 8.1.7 or later server versions. |
This section describes known problems and associated workarounds with iPlanet Application Server, Enterprise Edition 6.5. This information is organized into the following sections:
ID | Summary |
---|---|
4543771 |
Problem kcs process dies with bus error; fails inside internal gx library Workaround
|
- |
Problem iascontrol commands - start, stop and kill does not function correctly if the installable path exceeds 42 characters. On HP-UX 11.0 process descriptions are limited to 64 characters. |
4626356 |
Problem Administration Tool fails to connect to application server after the primary fails. This would happen if you have a cluster set-up configured with Maxbackups=0. If Maxbackups
is specified as 0 (none), then there is no backup application server and
the alternates change to the standalone state. However, when the primary
comes up again, it cannot connect to the alternate as it's in standalone
mode.
Workaround
|
4639210 |
Problem Transaction propagation does not work consistently. If two KJS' are participating in a transaction and only one of them is made recoverable, then this configuration cannot lead to proper recovery. Workaround
|
4633284 |
Problem When using DB2 as the database, transactions are not rolled back even though one of the application servers fails to recover from a crash. This problem occurs due to limitations in DB2. Workaround
|
4633274 |
Problem KJS crashes during transaction recovery, if DB2 is in an inconsistent sate. If recovery is done when DB2 is in an inconsistent state, the recovery call to DB2 dumps core and crashes KJS. Workaround
|
542273 |
Problem The CORBA Executive Server crashes when exceptions are thrown. |
536256 |
Problem A JSP of size larger than 185 KB cannot be executed on iPlanet Application Server. |
560053 |
Problem Struts applications fail when the Versioning key is enabled. Workaround
To disable dynamic reloading:
|
557991 |
Problem The security principal class is not invoked automatically when security is enabled for RMI/IIOP based applications. Workaround
For example, org.omg.CORBA.ORBClass=com.netscape.ejb.client.ClientORB. |
- |
Problem For distributed sessions, a negative value for setMaxInactiveInterval() will make the session timeout immediately. Workaround
|
4640812, 4640854, 4643711 |
Problem Memory growth when using iPM and BillerXpert with iPlanet Application Server 6.5. Workaround
On HP-UX, the JAVA_GX_ARGS=-DGX.cleaner.enabled entry is by default set to no .
|
ID | Summary |
---|---|
548426 |
Problem Redeployment of an updated version of an application does not remove the contents of the previous deployment from the file system area of the application area. The default location of deployed files is install_dir/ias/APPS/modules/module_name/ or APPS/ear_name/module_name/ . In addition to leftover file system content, some of the application server registry settings are also not overwritten and/or removed as an application is redeployed. This behavior can lead to older application settings remaining in effect after a redeploy. Workaround
|
537084 | Problem
If iPlanet Application Server is installed as root on a machine using the custom installation, the Deployment Tool (iASDT) is not accessible by other uses to create applications on Unix platforms. Workaround
|
ID | Summary |
---|---|
- |
Problem Personal Edition of Oracle is not supported on Unix platforms. |
4639241 |
Problem Vendor specific parameters, such as global connection, servername, databasename, ifxinformixhost, etc., are not saved when datasource is registered using XML file. Workaround
|
PointBase Database Installation (Unix Platforms) |
Problem The PointBase database installation requires access to the X Windowing System environment. If you are installing the PointBase database with the application server, the installation should have access to an X Windowing System. If there is no access to the X Windows environment, the PointBase database server will fail to start-up on that machine. Workaround
If the DISPLAY variable is set incorrectly, iPlanet Application Server post installation commands fail. |
4643903 |
Problem On Unix platforms, you will be unable to use the Oracle OCI driver if it has been registered under External JDBC Driver, through the Administration Tool. Workaround Ensure that $ORACLE_HOME is set in the iasenv.ksh script, under iASInstallDir /ias/env directory. |
ID | Summary |
---|---|
4668124 |
Problem Administration Tool resolves multibyte iPlanet Application Server instance. |
4668084, 4668105, 4668107, 4668128 | Problem
Kregedit does not correctly display registered multibyte applications and characters. |
4668133 |
Problem Invalid multibyte permissions are not validated while creating ACLs through Administration Tool. |
4668068 |
Problem 'Font specified in font.properties not found' error is displayed in the console. This error message is displayed even if the recommended font patches for HP-UX Asian True fonts are applied. |
4665761 |
Problem While installing, the following error is thrown during PointBase integration: Cannot convert string "-monotype-arial-medium-r-normal--*-140-75-75-p-*-iso8859-1" to type FontStruct. However, this message is harmless and PointBase integration is successfully completed. |
4663565 |
Problem When invoking Deployment Tool from the command line in Ja locale, an exception is thrown. |
4668770 |
Problem Multibyte cookies retrieved using get and set methods appears as garbage in a browser. |
ID | Summary |
---|---|
4640249 |
Problem Session distribution of soap web application does not work as per sample application documentation. Workaround
|
549549 |
Problem Samples fail after recreating tables in PointBase. Several of the J2EE Developer's Guide samples require that you to recreate the database tables before executing the samples a second time. If you use the SQL files provided to recreate the tables without restarting the application server, several of the J2EE Developer's Guide samples will fail. Workaround
|
548418 |
Problem "Inserted value too large for column" errors when using Bank application. Workaround
|
558611 |
Problem Cannot create new customer in Bank Application with the same SSN of a deleted customer. The Bank Application does not correctly update tables in the database, and therefore you cannot create a new customer with same SSN. |
548861 |
Problem iPlanet Type 2 Native Drivers for Sybase gives errors with JPS 1.1.2. Workaround
|
549374 |
Problem The setup_syb.bat and setup_syb.sh scripts for the Transactions sample will not execute. Workaround
|
550427 |
Problem Documentation error in the J2EEGuide sample. In the chapter "Currency Converter EJB", the third point under "Assemble EAR File", the value of the context root of the web application, is incorrectly mentioned as j2eeguide-confirmer . Workaround
|
- |
Problem Documentation error in the Bank sample. Under the "Create bank.war Module" > "Modify Web Application Descriptor" topic, the login information in the "Security Tab" point is incorrect. Workaround
|
545753 |
Problem Search functionality does not work when using JPS 1.1.2 with PointBase. Search functions do not work in JPS 1.1.2 when using the bundled PointBase database engine as the current version of PointBase bundled with iPlanet Application Server 6.5 does not support subqueries. |
560667 |
Problem Exception while running l10n application An exception is thrown when the user logs in as restaurant owner. |
562432 |
Problem Hot deployment of Petstore Application throws exception. Workaround
|
- |
Problem When iPlanet Application Server is installed with Microsoft IIS Webserver running on port number other than 80, the shortcut link for Sample Application will not work. Workaround
|
ID | Summary |
---|---|
4538866, 4675352 |
Problem iPlanet Application Server uninstaller does not stop the web server, resulting in numerous 'file busy' errors. Workaround
|
ID | Summary |
---|---|
4537538 |
Problem Task description about load balancing procedures is incomplete. In iPlanet Application Server Administrator's Guide, Chapter 14, "Balancing User-Request Loads ", the instructions do not specify to restart the Web server. Workaround
|
4639475 |
Problem Documentation on uninstallation does not list all the directories left after uninstall. Workaround
|
- |
Problem Documentation on dynamic reloading incorrectly states that, "whenever a reload is done, the sessions at that transit time become invalid". When reloading is enabled, there's no effect on HTTPSession established in the application. For example, consider an application that has three servlets- login servlet, processServlet, and logout servlet. If the processServlet is changed after accessing the login servlet, the user can still give a request to processServlet and get a new implementation of processServlet. |
Use of iPlanet Application Server, Enterprise Edition is subject to the terms described in the license agreement accompanying it.
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.
Last Updated May 10, 2002