These release notes contain the following sections:
The Developers 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. To assist you in quickly getting started using the iPlanet Integration Module with Forte for Java, use the Tutorial available http://docs.iplanet.com/docs/manuals/ide/index.html
Transactions support for Third Party JDBC drivers.
The following enhancements have been made to the connection pooling infrastructure:
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>.
Support for freezing and unfreezing transactions.
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 Jaxp1.1 compliant Xerces parser, because iPlanet Application Server bundles the JAXP 1.0.1 compliant parser.
The following changes have been made to iPlanet Application Server installation procedure:
In cases where a patch is listed as missing and you have a later version installed, you can ignore the warning message and continue with installation. That is, the list of missing patches contains a patch whose higher version is already installed, for example you have 108435-05 on your system and the list of missing patches shows 108435-04. For more information, see iPlanet Application Server Installation Guide.
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:
The following samples have been added in iPlanet Application Server, Enterprise Edition 6.5 release:
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. You might also have to 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.
The default JVM arguments on iPlanet Application Server, Enterprise Edition, 6.5 are as follows:
-server -Xss512k -Xms128m -Xmx1024m -XX:NewSize=42m -XX:MaxNewSize=342m -XX:+DisableExplicitGC -Xconcurrentio
Refer to http://java.sun.com/docs/hotspot/VMOptions.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 64MB. Due to the change in default values, the memory startup footprint will be higher. A thumb of rule for NewSize & MaxNewSize are 1/3*
| Note |
If your system does not have 1GB memory, then reduce the maximum heap size to fit your system's resources.
|
When -XX:+DisableExplicitGC is set, VM disables explicit calls to GC. The HotSpot technology discourages use of explicit GC due to performance reasons. You may need to take care of this if your application invokes GC explicitly.
| Caution |
If GX.cleaner.enabled=yes in JAVA_ARGS setting, then remove -XX:+DisableExplicitGC. |
| Note |
You must restart your Solaris system after applying these patches. |
|
Patch |
Patch Description |
|---|---|
| 108652-37 | X11 6.4.1 patch |
| 108921-13 | CDE 1.4 patch |
| 108940-32 | Motif patch |
Other required patches:
|
Patch |
Patch Description |
|---|---|
| 108528-12 | kernel update patch |
| 108434-04(32-bit) / 108435-04 (64-bit) | libC patch |
| 108827-12 | SunOS 5.8: /usr/lib/libthread.so.1 patch |
| Note | On a FAT file system, the installer may not calculate the required space correctly and may run out of disk space without warning. |
| Note | If you are performing a `Webless' installation, the web server and browser need not be present on the same machine on which you are installing the application server. For more information on Webless installation, see iPlanet Application Server Installation Guide . |
For detailed instructions on installing the iPlanet Directory Server 5,0 SP1 patch, see iPlanet Application Server Installation Guide .
The following directory servers are certified to work with iPlanet Application Server 6.5.
| Directory Server | Version |
|---|---|
| iPlanet Directory Server |
5.1 5.0 SP1 (bundled with iPlanet Application Server 6.5) 4.13 |
|
Platform |
Version |
JVM |
|---|---|---|
| Windows 2000 | Professional, Server, Advanced Server | JDK 1.3.1_002 |
| Windows NT | 4.0 SP6a | JDK 1.3.1_002 |
| Solaris | 2.6, 8 | JDK 1.3.1_02 |
iPlanet Application Server 6.5 continues to support the database clients and servers for the iPlanet Application Server Type 2 JDBC Database Drivers listed here.
The following manuals and online help tools were updated for iPlanet Application Server, Enterprise Edition 6.5.
The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Installation Guide:
The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Administrator's Guide:
The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Migration Guide:
The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Developer's Guide:
The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Deployment Tool Online Help:
The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Performance and Tuning Guide:
The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Registry Guide:
This section describes known problems and associated workarounds with iPlanet Application
Server, Enterprise Edition 6.5. This information is organized into the following sections:
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
Workaround
Workaround
Workaround
Workaround
To
disable dynamic reloading:
Workaround
For example,
org.omg.CORBA.ORBClass=com.netscape.ejb.client.ClientORB.
Workaround
Workaround
Workaround
On Solaris, the JAVA_GX_ARGS=-DGX.cleaner.enabled
entry is by default set
to no .
On Windows, the cleaner is
enabled by default.
Delete the following
flags to the JavaArgs entry in the registry under, SOFTWARE\iPlanet\Application
Server\6.0\Java\ .
-DGX.cleaner.doGC=yes
where N denotes the time in
milliseconds.
Workaround
For
example, if a war file contains 970 files, set the File Descriptor limit
to 1000:
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
Workaround
Workaround
Workaround
If
the
DISPLAY
variable
is set incorrectly, iPlanet Application Server
post installation commands fail.
Workaround
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
Workaround
The Bank Application does not correctly update tables in the database,
and therefore you cannot create a new customer with same SSN. Workaround
Workaround
Workaround
Workaround
Workaround
Workaround
Workaround
Workaround
You can manually delete these files.
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.
Known
Problems
and Limitations
Installation
Issues
This
section
describes the known iPlanet Application Server, Enterprise Edition 6.5
installation issues, and the associated workarounds.
<
<
Core
Server Issues
This
section
describes the known iPlanet Application Server, Enterprise Edition 6.5
core server issues, and the associated workarounds.
ID
Summary
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.
When
configuring a cluster, ensure that
Maxbackups is 1 or more, not 0.
4639210
Problem
Transaction
propagation does not work consistently.
If two KJS' are pariticpating in a transaction and only one of them is made
recoverable,
then this configuration cannot lead to proper recovery.
Ensure
that in a recoverable scenario, all participant KJS' should be recoverable.
Either all should be recoverable or none should be recoverable.
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.
If
your iPlanet Application Server installation is using DB2 as the database,
then
ensure that both iPlanet Application Server and DB2 are installed on the same
server.
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.
Disable
recovery in iPlanet registry to bring up KJS again.
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.
Do
not enable dynamic reloading. Ensure that the
Versioning
key
is
set to 1 in the registry.
557991
Problem
On
Windows, the security principal class is not invoked automatically when
security is enabled for RMI/IIOP based applications.
Before
running RMI/IIOP based applications, the
org.omg.CORBA.ORBClass
property
value
should be changed to
com.netscape.ejb.client.ClientORB
in
the
orb.properties
file
under
iASInstDir
/ias/usr/java/jre/lib.
-
Problem
For
distributed sessions, a negative value for
setMaxInactiveInterval() will make
the session timeout immediately.
Pass a very high value as an argument to
setMaxInactiveInterval().
4539468
Problem
In certain cases, IMQ as the JMS will not work on Solaris.
Go to iASInstallDir/ias/env directory and open iasenv.ksh file. Check whether jmq.jar and jmqadmin.jar are in the CLASSPATH. If not, add them to the end of the CLASSPATH settings.
Stop and restart iPlanet Application Server. The iMQ classes will now be in the server environment.
4640812, 4640854, 4643711
Problem
Memory growth when using iPM and BillerXpert with iPlanet Application Server 6.5.
Disable the explicit Garbage Cleaner by uncommenting
-DGX.cleaner.interval=N
Deployment
Tool Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.5
Deployment Tool issues, and the associated workarounds.
ID
Summary
537872
Problem
Libthread
panic error while opening large application files on Solaris.
Change
the File Descriptor setting in the UNIX environment file using the
ulimit
command.
Set
the File Descriptor limit to a number greater than the number of files contained
in the ear/war/jar file.
ulimit
-n 1000
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/
.
To
perform a clean redeployment, first perform a remove followed by a
deploy.
537084
Problem
If
iPlanet Application Server is installed as root on a machine using the
custom installation, the deploytool (DT) is not accessible by other uses
to create applications on Solaris platforms.
If
a user "A" has installed app server and ALL its components, then any
other user "B" needs following permissions in order to run the Deploy Tool
properly (note that iasdir refers to the installation location of iPlanet
Application Server):
Database
Support Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.5
database support issues, and the associated workarounds.
ID
Summary
4639241
Problem
Vendor
specific parameters, such as global connection,
servername,
databasename,
ifxinformixhost, etc., are
not saved when datasource is registered using XML file.
The
vendor-specific property cannot be specified using iPlanet Application Server
6.0 SPx XML files. You cannot mix parameters between the old and new XML files.
Register the datasource using the new XML file.
PointBase
Database Installation (Solaris 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.
When
you attempt to install the Pointbase Database, you must have access to
an X Windowing System Server, and in particular, have the
DISPLAY
environment
variable
set to point to that accessable server.
4625632
Problem
Unable
to use Oracle 9i client libraries through iPlanet Type 2 Native Driver.
Workaround
Rename libclntsh.so.9.0
under,$ORACLE_HOME/lib to libclntsh.so.8.0.
4643903
Problem
On
Solaris 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.
Sample
Application Issues
This
section describes the
known iPlanet Application Server, Enterprise Edition 6.5 sample application
issues,
and the associated workarounds.
ID
Summary
4640249
Problem
Session
distribution of soap web application does not work as per sample application
documentation.
In
the
soap-install.html file, under "Deploy the Apache SOAP
Web Application" the third point should read:
Select
the WAR file from the list of Web Applications. Right-click and select Edit
Descriptor
from the pop-up menu. In the iAS tab, click the
Distributed Session
button so
that it is unselected and click the
Local Data Synchronization radio button so that it is
selected.
Since
the Apache SOAP implementation stores non-serializable objects in user session,
this step is required to disable session synchronization for the SOAP web
application.
Close the deployment descriptor window and be sure to save its contents.
549549
Problem
Samples fail after recreating tables in PointBase.
For those samples that require recreation of database tables before
running the samples a second time, restart iPlanet Application Server after
recreating the tables.
548418
Problem
"Inserted value too large for column" errors when using Bank application.
Avoid using special characters or `
-
'
for SSN or Phone
number
fields. Do not enter more than two letters for the State
field
and not more than four letters for the Prefix
field.
558611
Problem
Cannot create new customer in Bank Application with the same SSN of
a deleted customer.
548861
Problem
iPlanet Type 2 Native Drivers for Sybase gives errors with JPS 1.1.2.
Use a Sybase Type 4 driver to exercise JPS 1.1.2 with Sybase. The sample
has been tested with the Sybase jConnect type 4 driver.
549374
Problem
The setup_syb.bat and setup_syb.sh scripts for the Transactions sample
will not execute.
The path to isql
in
the script is wrong. Open the script with a text editor. Search and replace
SYBASE/bin/isql
with
SYBASE/OCS-12_0/bin/isql
.
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
.
Replace j2eeguide-confirmer
with
j2eeguide-converter
-
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.
When assembling the Bank sample application from scratch, the two lines
for BankUser
and
BankAdmin
have
to placed together on one line.
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.0 SP4 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.
1) Disable dynamic reloading, or
2) Avoid making changes to the application when dynamic reloading is
enabled.
-
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.
Change the port number from 80 to the port number being used by IIS
in the path-property for that shortcut.
Uninstallation
Issues
This
section describes
the known iPlanet Application Server, Enterprise Edition 6.5 uninstallation
issues, and the associated workarounds.
ID
Summary
Documentation
Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.5 documentation
issues, and the associated workarounds.
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.
Changes to the load balancing scenario requires that the application server
and WebConnector
Plugin (Web Server) be restarted.
4639475
Problem
Documentation on uninstallation does not list all the directories left after uninstall.
Some of the directories and files created by the installer, and those created by the user are not removed during uninstallation. Typically, the following directories are left after uninstallation:
-
Problem
Documentation on dynamic reloading incorrectly states that, "whenever a
reload is done, the sessions at that transit time become invalid".
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 March 25, 2002