Release Notes for iPlanet™ Application Server, Enterprise Edition
Version 6.0 SP4
Updated December 04
These release notes contain important information available at the time of the Version 6.0 SP4 release of iPlanet Application Server, Enterprise Edition. New features and enhancements, installation notes, known problems, and other late-breaking issues are addressed here. Read this document before you begin using iPlanet Application Server, Enterprise Edition.
These release notes contain the following sections:
- What's New in iPlanet Application Server, Enterprise Edition 6.0, SP4
- Compatibility with Previous Releases
- Documentation Updates
- Software and Hardware Requirements
- Installation Notes
- Upgrading to SP4
- Resolved Issues
- Known Problems and Limitations
- How to Report Problems
What's New in iPlanet Application Server, Enterprise Edition 6.0 SP4iPlanet Application Server, Enterprise Edition 6.0 SP4 includes enhancements described in the following sections:
- iPlanet Directory Server 5.0, SP1 Support
- iPlanet Web Server, Enterprise Edition 6.0, SP1 Support
- JDK 1.2.2_10 Support
- Orbix 2000 Support
- Core Server Enhancements
- Dynamic LDAP Groups Support.
- Installation, Administration, and Deployment Enhancements
- Performance and Scalability Enhancements
- Developer Resources
- Product Packaging
iPlanet Directory Server 5.0, SP1 Support
iPlanet Directory Server 5.0, SP1 is supported for both configuration and user directory. Note that the directory server is not upgraded when you upgrade to iPlanet Application Server, Enterprise Edition 6.0, SP4.
iPlanet Web Server, Enterprise Edition 6.0, SP1 Support
iPlanet Application Server Enterprise Edition, 6.0 SP4 supports iPlanet Web Server, Enterprise Edition 6.0, SP1.
JDK 1.2.2_10 Support
JDK 1.2.2_10 is bundled with iPlanet Application Server Enterprise Edition, 6.0 SP4. This version of the JDK provides enhanced stability and includes several bug fixes.Orbix 2000 Support
iPlanet Application Server Enterprise Edition, 6.0 SP4 supports Iona's Orbix 2000 1.2.1 ORB, providing client-side CORBA functionality. The Orbix ORB enables portable interceptor based client side authentication, and more load balancing options.
RMI/IIOP applications are now highly scalable; upto 3000 concurrent rich client users have been tested with the ORBIX ORB.
Core Server Enhancements
iPlanet Application Server, Enterprise Edition 6.0, SP4 includes enhancements in the following areas:
- Struts Framework Support
- URL Encoding
- Webconnector Plugin
- EJB Container
- Web Container
- Global Transactions
- JDBC
- Dsync
Struts Framework Support
All applications developed using the struts framework are fully supported by iPlanet Application Server Enterprise Edition, 6.0 SP4. Additional enhancements include:
- All files packaged in J2EE application archives (JAR/WAR) are extracted.
- Alt-dd xml files are extracted to their respective directories.
URL Encoding Enhancements
iPlanet Application Server, Enterprise Edition 6.0, SP4 provides the user the choice of either using implicit URL rewriting (the default method), or explicit URL rewriting.
Implicit URL rewriting is enabled by default in iPlanet Application Server, Enterprise Edition 6.0, SP4. To enable explicit URL rewriting, use kregedit to modify the default=implicit key in the iPlanet Application Server registry path:
Software/iPlanet/Application Server/6.0/CCS0/HTTPAPI/URLRewrite
To use explicit URL rewriting change the value, default=implicit to default=explicit .
Implicit URL rewriting is performed by the WebConnector Plugin and does not require any changes to the code by the developer. To enable Explicit URL Rewriting, which is performed by the Web container, developers have to modify the Servlet or JSP code to make explicit calls to encodeURL and encodeRedirectURL .
For more information on URL Rewriting, see iPlanet Application Server Developer's Guide .
WebConnector Plugin
- All static content types are supported in iPlanet Application Server Enterprise Edition, 6.0 SP4. Mime types can now be specified in the mime-type tags within the web.xml file.
EJB Container
- EJB Container supports primary key sizes greater than 512.
Web Container
- Support for Unavailable Exceptions (both permanent and temporary) in Servlets.
- Request Parameter is validated at run time.
- Enhancements to Form Based Authentication has made it more robust.
Global Transactions
A new registry flag has been added that allows the application server to automatically use a local database connection, if no transaction context is used and when global transactions are enabled.
The registry flag, RETURNLOCALIFNOGLBL, is automatically created under SOFTWARE\iPlanet\Application Server\6.0\CCS0\DAE2\, the first time a database operation is performed.
This flag comes into picture when global transactions are enabled (i.e resource manager is specified for a data source), and the transaction attribute of a Container Managed transaction Bean is "Supports".
In this case, if the client calls with a transaction context, global connection is used. If the client calls without a transaction contect, a local connection is used if the above flag is set to 1. If the above flag is set to 0, then an error is generated if the client calls without transaction context.
JDBC
- Connection pooling enhancements for Third Party drivers.
Dsync
- Clean up of timed out session nodes has been optimized for better performance.
Installation, Administration, and Deployment Enhancements
- After installation, iPlanet Application Server is automatically registered with the Administration Server.
The CXS engine is also automatically registered alongwith KJS, KCS and KXS engines.
- You can configure different directory servers to host the configuration directory and user directory.
- A new option, -ENG , has been added to the iascontrol command, allowing a specified engine to be gracefully shutdown.
For more information on its usage, see iPlanet Application Server Administration Guide .
- Deploy Tool's resolver mechanism has been modified to support EJB inheritance. This enhancement will also allow for smoother integration with Cocobase.
Performance and Scalability Enhancements
iPlanet Application Server Enterprise Edition, 6.0 SP4 contains several enhancements and bug fixes that provide better performance over the previous releases.
- Overall performance improvement over iPlanet Application Server, Enterprise Edition, 6.0 SP3 with the Trade 2 Benchmark tests.
- Scalabilty improvements for applications using RMI/IIOP with major bug fixes to the JavaSoft ORB.
- Memory Management
Two new options to control memory management have been introduced in iPlanet Application Server Enterprise Edition, 6.0 SP4. The following two switches can help to fine tune memory allocation in cases where unexpectedly high memory growth is seen.
Explicit Garbage Collector
Memory utilization by the application server can now be controlled by modifiying the behaviour of the explicit Garbage Collector. You can enable or disable the cleaner by modifying the JAVA_GX_ARGS=-DGX.cleaner.enabled key in iasenv.ksh file on Solaris, and in the registry settings on Windows.On Solaris, the JAVA_GX_ARGS=-DGX.cleaner.enabled entry is by default set to no , to improve respone time for requests. If you notice an inordinately high usage of memory by iPlanet Application Server, enable the cleaner by changing the value to yes , or or by commenting out the JAVA_GX_ARGS line.
JAVA_GX_ARGS=-DGX.cleaner.enabled=yes
Once enabled, the cleaner is invoked every 10 seconds. The cleaner interval can be controlled by adding the following line to iasenv.ksh file:
JAVA_GX_ARGS=-DGX.cleaner.interval=N
where N denotes the time in milliseconds.On Windows, the cleaner is enabled by default. To improve performance you can disable the cleaner or set a longer time interval.
If you want to modify or change the default behaviour of the cleaner, it can be done by adding the following flags to the JavaArgs entry in the registry under, SOFTWARE\iPlanet\Application Server\6.0\Java\ .
-DGX.cleaner.doGC=yes
-DGX.cleaner.interval=Nwhere N denotes the time in milliseconds.
Deferred Garbage Collection
A new switch has been introduced to enable deferred GC for Applogic based applications that see memory growth. This can be turned on by setting the java system property useDeferredGC . On Solaris you can enable this by appending the following JAVA_ARGS in iasenv.ksh file:-DuseDeferredGC=true
On Windows, append the following to the JavaArgs entry which can be found in the registry under, SOFTWARE\iPlanet\Application Server\6.0\Java\ :
-DuseDeferredGC=true
The default value of this property is set as false , since high memory growth has been reported with a few Applogic based applications. In deferred garbage collection, the references of the newly created objects are stored temporarily till the end of execution of the request, to prevent its garbage collection. Therefore at the end of the request, all the memory is freed at once but it can also lead to transient (until end of request) memory growth.
Dynamic LDAP Groups Support
iPlanet Application Server, Enterprise Edition 6.0, SP4 supports authentication to dynamic LDAP groups.Developer Resources
The iPlanet Application Server, Enterprise Edition 6.0, SP4 now includes a Developer Resources component to assist developers developing applications using the Forte for Java™ IDE and seamlessly deploying those applications to the iPlanet Application Server and Web Server.The Developers Resources for iPlanet Application Server 6.0 Service Pack 4 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.
- A Trial Version of Forte for Java Enterprise Edition Version 3.0.
- iPlanet Application Server Integration Tool for Forte for Java Enterprise Edition Version 3.0.
- iPlanet Web Server Integration Tool for Forte for Java Version 3.0.
An unsupported developer's copy of the iPlanet Presentation Framework (formerly known as JATO) Version 1.2.
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.
Product Packaging
The following products are packaged with iPlanet Application Server, Enterprise Edition 6.0 SP4:
- iPlanet Directory Server 5.0. SP1
- iPlanet Web Server, Enterprise Edition 6.0, SP1
- JDK 1.2.2_010 on Windows and JDK 1.2.2_10 on Solaris
Compatibility with Previous ReleasesThis section describes changes made in SP4 that affect applications developed or deployed on earlier versions of iPlanet Application Server, Enterprise Edition.
- EJB
- Servlet Request URI
- Web Server Access
- Domain Suffix
- LDAP Authentication
- Default Locale Encoding
- Sample Applications
EJB
For an unauthenticated user, getCallerPrincipal() will return an Empty String (""), as a default caller of the Enterprise Bean .
Note We recommend that the call to getCallerPrincipal() should always be made when a client security context is present as per EJB specifications.
Servlet Request URI
PlatformHttpServletRequest. getRequestURI() by default will return the context path and the URL path, in SP4. However, if you change the PREPENDNASAPP switch in iasenv.ksh or kjs ( JavaArgs in Windows) to false, getRequestURI() will behave in the same way as in SP3, returning the application name and URL path.
Web Server Access
Existing Appplications which use getRemoteHost method of Request Object for getting the Web server's Name & Port will have to use the methods, getServerName( ) and getServerPort( ) of Request Object.
Domain Suffix
The default directory suffix format in SP4 has been changed to dc=sales,dc=sun,dc=com format from o=sales.sun.com , followed in SP3 and earlier releases. If your applications use LDIF files to populate user directory data, you must change the directory suffix format to that specified during the installation of iPlanet Application Server, Enterprise Edition 6.0, SP4 .This change is required only if you perform a fresh installation of iPlanet Application Server, Enterprise Edition 6.0, SP4 and want to deploy your existing applications on SP4. This will not impact an upgrade to SP4, as after an upgrade, iPlanet Application Server will continue to use the older directory server.
LDAP Authentication
Support for authentication of users in arbitrarily deep trees under the UserRoot (for example, ou=People,o=Sun.COM ) has been added.
SP3 and earlier versions used single-level authentication to look for a user in the top level of the LDAP tree. If you search for a user (who is actually not present at the top level) with the same name down in the hierarchical structure in LDAP (even though it was not supported by pre-SP4 versions of the iPlanet Application Server), we might end up trying to authenticate this user down in the hierarchy, where we would have thrown an Authentication Exception in SP3.
Default Locale Encoding
The default character set encoding has been changed from 8859_1to ISO-8859-1. Existing applications, which use 8859_1 encoding will have to be changed to ISO-8859-1.
Included JSPs, which use different encoding than including JSPs, may have some problems for non-international characters.
Sample Applications
The HelloDB and Java Pet Store 1.2.2 sample applications bundled in SP3 will not work with SP4, as the default character set encoding has been changed from 8859_1to ISO-8859-1.
Documentation UpdatesThe following manuals and online help tools were updated for iPlanet Application Server, Enterprise Edition 6.0 SP4.
Installation Guide
The iPlanet Application Server, Enterprise Edition 6.0 SP4 release includes the following changes for the Installation Guide:
- Upgrade to SP4 procedures documented.
- Includes changes pertaining to iPlanet Directory Server 5.0 information.
- Bug fixes
Getting Started Guide
A new guide, aimed at first time users of iPlanet Application Server Enterprise Edition, 6.0 SP4 has been included with iPlanet Application Server documentation set. This guide describes basic commands and functions for administering and deploying applications to iPlanet Application Server 6.0. An overview of iPlanet Application Server architecture is also provided.
Developer's Guide
The iPlanet Application Server, Enterprise Edition 6.0 SP4 release includes the following changes for the Developer's Guide:
- "Using the ejbc Compiler" section added in Chapter 4, Enterprise Java Beans.
- "C++ IIOP Client Applications" section, and ORBIX configuration information added in Chapter 9, Developing and Deploying CORBA-based Clients.
- "Sessions and URL Rewriting" section added in Chapter 11, Creating and Managing User Sessions.
- Enhanced introduction to Chapter 10, Packaging for Deployment.
- Classloader information added to Appendix B, Runtime Considerations.
- "Modularizing Applications" section added to Chapter 1, Developing Applications.
Deployment Tool Online Help
The iPlanet Application Server, Enterprise Edition 6.0 SP4 release includes the following changes for the Deployment Tool Online Help :
- Added the EAR descriptor to the documentation for the context root tab.
- The online help now uses internationalization safe fonts.
Software and Hardware RequirementsYour system must meet the following requirements before you can install iPlanet Application Server.
Solaris
Your Solaris™ system must meet the following requirements before you can install iPlanet Application Server:
- Sun® UltraSPARC™ running Solaris 2.6 or Solaris 8
- 750 MB free hard disk space
- 512 MB RAM
- One of the following Web Servers:
- iPlanet Web Server, Enterprise Edition 6.0, SP1
- iPlanet Web Server, Enterprise Edition 4.1 SP7
- Apache Web Server 1.3.19
- The following Web browser:
Solaris Patch Requirements
iPlanet Application Server 6.0, SP4 bundles Solaris Production JDK 1.2.2_10 for SPARC. The following patches for JDK 1.2.2_10 must be applied on Solaris 2.6. These patches can be downloaded from the http://sunsolve.sun.com/ Web site.
Table 1 Required JDK 1.2.2_10 patches
Patch
Patch Description
For Solaris 8, apply the recommended JDK 1.2.2_10 patches listed on the http://java.sun.com/ Web site.
Windows
Your Microsoft Windows system must meet the following requirements before you can install iPlanet Application Server:
- Microsoft Windows NT 4.0 with SP6a, or Windows 2000 Professional SP2, or Windows 2000 Server SP2, or Windows 2000 Advanced Server
- 300 MB free hard disk space (NTFS)
Note On a FAT file system, the installer may not calculate the required space correctly and may run out of disk space without warning.
- 512 MB RAM
- One of the following Web Servers:
- iPlanet Web Server, Enterprise Edition 6.0, SP1
- iPlanet Web Server, Enterprise Edition 4.1 SP7
- Microsoft Internet Information Server 5.0
- Microsoft Internet Information Server 4.0
- Apache Web Server 1.3.19
- One of the following Web browsers:
- Netscape Communicator 4.5 or later
- Internet Explorer 4.0 or later
Installation Notes
This section includes information for installing your iPlanet Application Server. For detailed information about installation procedures, see the Installation Guide.
Prerequisites for Installation
Before you begin installing iPlanet Application Server, verify that the following prerequisite conditions are met:
Meet the Minimum System Requirements for the platform on which you are installing iPlanet Application Server. If you are planning to use a fresh installation of iPlanet Application Server, Enterprise Edition 6.0, SP4 with a remote user directory, you must install the iPlanet Directory Server 5.0 SP1 patch before installing iPlanet Application Server. This patch must be installed even if you are using iPlanet Directory Server 4.13 or later versions, as your user directory. For more information on how to install the patch, see Installing iPlanet Directory Server 5.0 SP1 Patch .
Have administrative privileges on the Windows or Solaris system. On Solaris platforms, establish a UNIX user and group for iPlanet Application Server. Use this account to install and manage iPlanet Application Server. Make sure you have your product key nearby; it's in the Welcome letter. Ensure that a static IP address is assigned to the machine (contact your system administrator to get one).
The default directory suffix format in SP4 has been changed to dc=sales, dc=sun,dc=com format from o=sales.sun.com , followed in SP3 and earlier releases. If your applications use LDIF files to populate user directory data, you must change the directory suffix format to that specified during the installation of iPlanet Application Server, Enterprise Edition 6.0, SP4 . If you choose not to install the Directory Server Suite on a fresh installation of iPlanet Application Server, Enterprise Edition 6.0, SP4 on Windows, then you must copy the libnspr3.dll file from the product CD to the Winnt\system32 directory. This is to ensure that your LDAP applications work properly when the configuration directory is on a remote machine. The libnspr3.dll file can be found on the product CD in the /Windows/iAS directory.
Make sure that no other service is running on port 9010 before installing iPlanet Application Server, as the CXS engine uses port 9010 for IIOP, and it gets registered automatically during installation.
Make sure that no other service is running on port 9092 before installing iPlanet Application Server as the bundled PointBase database application uses port 9092 by default. If you are running Windows 2000, ensure that the Primary DNS suffix has been correctly set on the machine on which you are installing iPlanet Application Server.
To set the Primary DNS suffix, go to Start menu> Settings>Control Panel>System>Network Identification>Properties>More .
On Solaris platforms, ensure that the machine has its fully qualified domain name mentioned in the /etc/hosts file, as shown in this example:
#
# Internet host table
#
127.0.0.1 localhost
192.168.0.255 myhost.company22.com myhost loghost
- On Solaris platforms, ensure that the Directory Server is installed on the local file system. Multiple physical drives can be used, but they need to be mounted locally.
Configure the Web Server
Make sure that one of the recommended Web Server and Web Browser is installed and configured before you install iPlanet Application Server. The iPlanet Web Server, Enterprise Edition 6.0, SP1 is available for download at: http://www.iplanet.com/downloads/download/ . On the Solaris platform, iPlanet Application Server user and the Web Server user must either be the same or from the same group. If the Web Server is installed as a regular user, and the iPlanet Application Server user is installed as the root user, a file permission problem will exist. The Web Server will not start because it doesn't have access to the registry file, reg.dat . Webless Installation
If your web server runs on a different machine from the machine on which iPlanet Application Server is installed, you perform what is referred to as a "webless" installation. After performing a webless installation, you must install the Web Connector plug-in on the web server in your configuration.
For more information, see Appendix A, "Configuring iPlanet Application Server", in iPlanet Application Server Installation Guide .
Create a Raw Partition (Optional)
Create a raw partition on a separate disk prior to running the installation program. This is where the transaction manager log file gets stored for each Java TM Server.
Create a Mirror Directory for Transaction Manager (Optional)
Create a directory on a separate drive from the iPlanet Application Server installation directory and specify a path to it - prior to installing the application server.
Install and Configure Database Servers (Optional)
Before installing iPlanet Application Server, install the database servers and clients to use with this iPlanet Application Server installation.
During application server Custom installation, you can choose to configure iPlanet Type 2, third party JDBC, or no JDBC drivers. Although you can only configure either the Type 2 driver or third party JDBC driver during installation, you can choose to configure both after installation.
You can configure third party JDBC drivers after installation by executing db_setup.sh script on Solaris and jdbcsetup.exe on Windows. When configuring the database drivers after installation, you must restart the application server to apply the changes. For more information, see the iPlanet Application Server Administrator's Guide.
Installing iPlanet Directory Server 5.0 SP1 Patch
This patch should be installed if you are planning to use a fresh installation of iPlanet Application Server, Enterprise Edition 6.0, SP4 with a remote user directory. This patch must be installed even if you are using iPlanet Directory Server 4.13 or later versions, as your user directory.
You don't need to install the iPlanet Directory Server 5.0 SP1 patch if you are upgrading from an earlier version of iPlanet Application Server, Enterprise Edition, 6.0. While upgrading, make sure you do not select the iPlanet Directory Suite component. For detailed instructions on upgrading iPlanet Application Server, see iPlanet Application Server Installation Guide .
Follow these instructions to install iPlanet Directory Server 5.0 SP1 Patch. This patch must be copied to the appropriate directory before installing iPlanet Application Server, Enterprise Edition, 6.0 SP4.
To Install the Patch on Solaris
To Install the Patch on Windows
To Install the Patch on Solaris
- Copy the contents of the product CD under the Solaris/iAS directory to a local directory on your machine.
- From the product CD, copy the nsslapd.zip file from the iDS50SP1patch/Solaris directory to the slapd directory under the iPlanet Application Server installables on your local machine.
- Run the iPlanet Application Server, Enterprise Edition, 6.0 SP4 installation from this local directory.
For detailed installation instructions, see iPlanet Application Server Installation Guide .
To Install the Patch on Windows
- Copy the contents of the product CD under the Windows\iAS directory to a local directory on your machine.
- From the product CD, copy the slapd.z file from the iDS50SP1patch\Windows directory to the slapd directory under the iPlanet Application Server installables on your local machine.
- Run the iPlanet Application Server, Enterprise Edition, 6.0 SP4 installation from this local directory.
For detailed installation instructions, see iPlanet Application Server Installation Guide .
Certified Directory Servers The following directory servers are certified to work with iPlanet Application Server 6.0, SP4.
Table 2 Certified Directory Servers
Directory Server
Version
5.0 SP1 (bundled with iPlanet Application Server 6.0, SP4) 4.13
The following Web servers are certified to work with iPlanet Application Server, Enterprise Edition 6.0, SP4.
Table 3 Certified Web Servers
Web Server
Interface
The following JVMs are certified to work with iPlanet Application Server 6.0, SP4.
Table 4 Certified JVMs
Platform
Version
JVM
Certified Third Party JDBC Database Drivers The following Third Party JDBC drivers are certified to work with iPlanet Application Server 6.0, SP4.
Table 5 Third party JDBC database drivers certified in SP4 on Windows and Solaris
Database Vendor
JDBC Driver
Certified Native Type 2 Database Servers and Clients
iPlanet Application Server 6.0 continues to support the database clients and servers for the iPlanet Application Server Type 2 JDBC Database Drivers listed here.
Table 6 Certified Native Type 2 database servers and clients for SP4
Database Server
Database Client
Platform
Note For proper functioning of the Sybase global transactions on Solaris, the following Sybase patches for client version 12.0 should be installed:
These patches are available from the Sybase website at: http:// http://docs.iplanet.com/docs/manuals/ias/60/sp4/www.sybase.com .
Upgrading to SP4
This section describes procedures to upgrade from iPlanet Application Server 6.0, SP1 RevB, SP2 and SP3, to iPlanet Application Server Enterprise Edition (EE) 6.0, SP4 release.
Due to changes made to provide enhanced security and to the Class Loader in SP3 and SP4, you must redeploy applications running on SP1 using the redeploy utility. For more information on upgrading from SP1 RevB to SP4, see Upgrading from SP1 RevB to SP4 .
Upgrading from SP2 and SP3 to SP4 is fairly straightforward. Your applications are automatically migrated to SP4 when you run the SP4 installation program. For more information on upgrading from SP2 and SP3 to SP4, see Upgrading from SP3 to SP4 .
The following topics are covered in this section:
Before You Start
Make sure to follow these guidelines before upgrading to SP4:
If you are running a release earlier than iPlanet Application Server 6.0, SP1 RevB, then you must do a complete reinstall. Stop iPlanet Application Server before starting the upgrade process. If the current iPlanet Application Server installation is part of a cluster, then you must stop all application servers running in that cluster before upgrading. Make sure that the Directory Server is running. If you want to make any changes to the existing configuration, first complete the upgrade procedure, and then use iPlanet Application Server Administration Tool (IASAT) to make those changes. iPlanet Application Server installation or upgrade will cause the Directory Server installed locally on the same machine on which the application server is being installed, to restart. Other application server instances configured to the same Directory Server will display error messages, until the Directory Server is up again.
Upgrading from SP3 to SP4
Use the following procedure to upgrade to iPlanet Application Server Enterprise Edition 6.0, SP4.
This section includes upgrade procedures for the following platforms:
Upgrading on Windows Platforms Upgrading on Solaris Platforms
Upgrading on Windows Platforms
To upgrade to iPlanet Application Server 6.0 SP4 on Windows, perform the following steps:
Ensure you have met all the conditions listed in Minimum System Requirements , and Prerequisites for Installation . Run the setup program. Click Next after the Welcome screen appears. Click Yes to accept the license agreement.
Click Next to install the iPlanet Server and core components. Select Typical or Custom as the type of installation. The Setup program will automatically select the same location as your current installation. Click Next to continue.
Select iPlanet Application Server 6.0 component only.
Make sure this is the only selected component. Do not select the other five components .
Enter the configuration directory administrator ID and password. Click OK when you are asked whether you want to upgrade. Confirm the configuration directory information displayed and enter the password of the user directory administrator (typically cn=Directory Manager). Enter the Product Key. The product key is in the welcome letter you received with the product CD. Click Install to complete the upgrade.
Upgrading on Solaris Platforms
To upgrade to iPlanet Application Server 6.0, SP4 on Solaris, perform the following steps:
Note Choose the same configuration options that you chose for the existing installation. You can make modifications to your configuration after upgrading.
Ensure you have met all the conditions listed in Minimum System Requirements , and Prerequisites for Installation . Run the setup program. Enter y and press Enter at the Welcome Screen. Enter y and press Enter to accept the license agreement. Select 1 to install iPlanet Servers. Select Typical or Custom as the type of installation. Change the location of install to point to the same location as your existing installation. Press Enter.
Enter 4 and press Enter to install only the iPlanet Application Server component. Make sure this is the only selected component. Do not select the other three components .
Select the sub-components shown in subsequent screens. Enter the fully qualified domain name ( hostname.domain.com ) of the machine on which you are installing iPlanet Application Server. Enter the system user and system group names. Enter the Administrator ID and password for the Configuration Directory Server.
When you are asked whether you want to upgrade, type y at the prompt and press Enter. Enter the password of the user directory administrator (typically cn=Directory Manager). Enter the Product Key. The product key is in the welcome letter you received with the product CD.
The installation program extracts the required files and completes the upgrade process.
Upgrading from SP2 to SP4
Use the following procedure to upgrade to iPlanet Application Server Enterprise Edition 6.0, SP4.
This section includes upgrade procedures for the following platforms:
On Windows Platforms On Solaris Platforms
On Windows Platforms
To upgrade to iPlanet Application Server 6.0, SP4 on Windows, perform the following steps:
Note Stop iPlanet Application Server before starting the upgrade process.
Ensure you have met all the conditions listed in "Software and Hardware Requirements, and "Prerequisites for Installation" . Run the setup program. Click Next after the Welcome screen appears. Click Yes to accept the license agreement.
Click Next to install the iPlanet Server and core components. Select Custom as the type of installation. The Setup program will automatically select the same location as your current installation. Click Next to continue.
Select iPlanet Application Server 6.0.
Follow directions in the installer as you would for a normal installation. You will require the License Key that you received along with the product CD. Enter configuration details, such as configuration directory administrator ID, password and port numbers, exactly as used for your current installation.
The installer will display the port numbers as used by the existing installation. Do not modify any of the values.
Click Next through the rest of the screens to complete the install.
On Solaris Platforms
To upgrade to iPlanet Application Server 6.0, SP4 on Solaris, perform the following steps:
Ensure you have met all the conditions listed in Minimum System Requirements , and Prerequisites for Installation . Run the setup program.
For detailed information on the installation procedure, see Chapter 4, "Advanced Installations for Solaris", in iPlanet Application Server Installation Guide .
Select Custom as the type of installation. Choose to install the software in the same location as your current installation. Press Enter.
Enter 4 and press Enter to install only the iPlanet Application Server component. Make sure this is the only selected component. Do not select the other components .
Enter the Directory Server administrator ID and password. When you are asked whether you want to upgrade, type y at the prompt and press Enter. Follow directions in the installer as you would for a normal installation.
Enter configuration details, such as, configuration directory administrator ID, password and the port numbers, exactly as used for your current installation.
Follow directions in the installer as you would for a normal custom installation. You will require the License Key that you received along with the product CD.
Upgrading from SP1 RevB to SP4
The following changes made to iPlanet Applications Server EE 6.0, SP3 and SP4 make it necessary to redeploy applications running on SP1 RevB:
iPlanet Application Server Enterprise Edition 6.0, SP4 extracts class files in a .war file under the directory, iASInstallDir /ias/APPS/<app-name>/<module-name>/classes , compared to iASInstallDir /ias/APPS in SP1.
The Jasper compiler integrated with iPlanet Application Server 6.0, SP4 specifically expects this directory structure.
The new Class Loader implemented in SP4 might not be able to load class files from previously deployed .war components of .ear files, which are placed in the wrong path.
For more information, see the iPlanet Application Server Migration Guide .
To upgrade from SP1 RevB to SP4
To upgrade from SP1 RevB to SP4, on both the Windows and Solaris platforms:
Install SP4 in the same location where SP1 is currently installed.
Follow instructions given in Upgrading from SP2 to SP4 .
After completing the SP4 installation, run the redeploy utility to migrate applications to SP4.
The redeploy utility is shipped along with iPlanet Application Server 6.0 EE SP4 and can be found at the following location:
On the Windows platform, run:
iASInstallDir /ias/bin/redeploy.exe
On the Solaris platform, run the redeploy shell script from
iASInstallDir /ias/bin/redeploy
The redeploy utility finds all applications and the corresponding ear files deployed on SP1, and re-deploys each application on SP4. All class files from the .war components of applications deployed on SP1 are moved to the following location:
iASInstallDir /ias/trash/sp1
A directory structure corresponding to the package structure of that class is recreated in this location.
Resolved Issues
The following table lists the critical issues resolved in iPlanet Application Server, Enterprise Edition 6.0, SP4 release.
Known Problems and Limitations
This section describes known problems and associated workarounds with iPlanet Application Server, Enterprise Edition 6.0 SP4. This information is organized into the following sections:
- Installation Issues
- Core Server Issues
- Administration Tool Issues
- Deployment Tool Issues
- Database Support Issues
- Sample Application Issues
- Uninstallation Issues
- Documentation Issues
Installation Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0, SP4 installation issues, and the associated workarounds.
Core Server Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP4 core server issues, and the associated workarounds.
ID Summary 546093
Problem
Automatic restart of iPlanet Application Server on the Windows platform may not occur on slower machines.
This is due to a problem with iPlanet Directory Service startup.
Workaround
Add the environment variable, IAS_KASWAITTIME , and set it to between 5-15 (seconds) for automatic startup to work in such cases. This variable need not be set for manual startup.
543455
Problem
A ClassNotFound exception occurs during session timeout.
Workaround
If KJS logs show a ClassNotFound exception when the Http Session Binding Listener times out, then copy those classes to the iASInstallDir \ias\APPS directory.
548555
Problem
Servlet caching fails in kxs if delimiters are used in the application name.
Workaround
Do not use delimiters, such as `|', `-', `,' in the application name (EAR), web application name (WAR) or Context Root.
543455
Problem
Although iPlanet Application Server supports distributed sessions, the implementation imposes the condition that the objects being put into the session be Serializable.
Workaround
If the requirement is to have a non serializable value in the session, then have a lite session with the tag session-impl=lite .
541173
Problem
The "500 SC_INTERNAL_SERVER_ERROR" message is shown if the JSP based Welcome file is not found in the specified directory.
The browser will display this message if the JSP file cannot be found.
Workaround
If your Welcome file is a JSP file, for example index.jsp , ensure that the file is placed in the specified directory.
542273
Problem
The CORBA Executive Server crashes when exceptions are thrown.
544533
Problem
To enable custom HTTP headers on Windows NT, you must restart the web server.
541566
Problem
Session not retained during a kjs failover when dsync-type=dsync-local.
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
Do not enable dynamic reloading. Ensure that the Versioning key is set to 1 in the registry.To disable dynamic reloading:
- Start iPlanet Registry Editor, kregedit, and modify the Disable value under the Versioning key : SOFTWARE/iPlanet/Application Server/6.0/CCS0/SYSTEM_JAVA/Versioning
- Set the Disable value to 1
- Restart iPlanet Application Server to enable the change.
557991
Problem
On Windows, the security principal class is not invoked automatically when security is enabled for RMI/IIOP based applications.Workaround
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 .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
Pass a very high value as an argument to setMaxInactiveInterval() .
Administration Tool Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP4 Administration Tool issues, and the associated workarounds.
ID Summary 544526
Problem
Deleting Datasource from Administration Tool does not work.
Workaround
Deleting an external or iPlanet Type 2 Datasource cannot be done from the Administration Tool. Delete the datasource entry from the registry using kregedit . For more information, see Chapter 8, `Administering Database Connectivity' in iPlanet Application Server Administrator's Guide .
540597
Problem
Shutdown method in the StartupClass is not invoked when KIVAes.sh stop command is used.
Workaround
Use the command iascontrol stop . We recommend that you do not use KIVAes.sh as it has been deprecated.
For more information, see Chapter 1, `Performing Basic Administrative Tasks' in iPlanet Application Server Administrator's Guide .Note : To use the iascontrol command, you must have registered the server with the Administration Tool.
561521
Problem
When a cxs process is launched, a UTIL-loadcomponent_init_module error is printed to the cxs logs .
Workaround
This is a harmless error message. Fuctionality of the cxs server is not impacted and J2EE applications can be run without any problems.
562567
Problem
Administration Tool may hang during ACL definition on Japanese locales.
Deployment Tool Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP4 Deployment Tool issues, and the associated workarounds.
ID Summary 537872
Problem
Libthread panic error while opening large application files on Solaris.
Workaround
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.For example, if a war file contains 970 files, set the File Descriptor limit to 1000:
ulimit -n 1000
548426
Problem
Redeployment of an updated version of an application does not remove the content of the a previous deployment from the file system area of the application area. The default location of deployed files isinstall_dir/ias/APPS/modules/module_name/
orAPPS/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
To perform a clean redeployment, first perform a remove followed by a deploy.
528161
Problem
While migrating NAS 4.0 applications to iPlanet Application Server 6.0 SP4, descriptors in the XML file of deployed applications is overwritten by the default values set by Deployment Tool.
This problem arises because the Deployment Tool does not recognize XML as a descriptor XML file, unless the Deployment Tool itself creates it, or it's inserted inside an application/module in the appropriate directory with the appropriate name.
Workaround
Perform the following steps to migrate NAS 4.0 XML applications to iPlanet Application Server 6.0 SP4:
- Convert Property files to XML with convertProps2Xml .
- Rename the generated files to ias-ejb-jar.xml and ejb-jar.xml .
- Create a new EJB JAR module with Deployment Tool and insert EJB classes into it.
- Go to File > Save to save the EJB JAR file.
The Deployment Tool will now create the ejb module (jar file) with xml files containing default descriptor values.
- Extract the jar file.
- Replace the XML files in META-INF directories with XML files generated earlier ( ias-ejb-jar.xml and ejb-jar.xml ).
- Recreate the EJB.JAR file with the following command:
541066
Problem
Disable Reload option doesn't work for Servlet deployment descriptor.
Workaround
The Disable Reload button in the `IAS' tab of Servlet Deployment Descriptor is currently not supported. In the same window, under Server Information, the following options are not supported: IP Address, Port and StickyLoadB.
-
Problem
The Pass-by-value option in the EJB Descriptor's General panel (its values are stored in ias-ejb-jar.xml) is currently not supported.
It's value will not be considered if you enable the option.
-
Problem
Deployments in iPlanet Application Server uses non validating XML parser.
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.
Workaround
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):
- DT reads/writes in iasdir/registry/reg.dat. Make sure that directory "iasdir/ias/registry " has ALL permissions for user "B".
- Deploy Tool writes its temporary xml files from descriptors, ejb skels and stubs into "iasdir/ias/tmp". Make sure that user "B" has WRITE permissions to this directory.
- Deploy Tool writes its preferences into "iasdir/ias/dt". If user "B" needs to save the preferences, this directory needs to be WRITABLE by user "B". This permission is not critical for normal functioning of Deploy Tool.
- User "B" needs to have READ and EXECUTE permissions to many other directories/files as Deploy Tool loads/runs scripts/executables/executable jars/libs/dlls, and so on from "iasdir/ias/bin", "iasdir/ias/lib", "iasdir/ias/java/classes (on Unix platforms)" and others.
- As an additional precaution, user "B" needs to have WRITE permission to the directory where the app/module being opened resides on file system. For example, bank.ear resides in "iasdir/ias/ias-samples/bank". Consequently, that directory should be WRITABLE.
543277
Problem
<ejb-name>
and EJB JAR file name cannot be same.
561520
Problem
A module cannot be added to an EAR by the drag and drop method, when Component View is selected in the Deploy Tool.The drag and drop feature for EAR file assembly is presently only supported in File View mode.
561520
Problem
New J2EE applications cannot be deployed in iPlanet Application Server through the command line utility, iasdeploy .Workaround First time deployments should be made from the Deploy Tool as iasdeploy cannot create the stubs and skeletons. Subsequent deployments can be made using the iasdeploy command line utility.
Database Support Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP4 database support issues, and the associated workarounds.
ID Summary 542911
Problem
Native driver connection problem for Sybase client on Windows NT.
Workaround
Perform the following steps:
481221
Problem
RowSet lookups from JNDI is not implemented for Third Party drivers.
Workaround
To use RowSet, construct the RowSet object directly and set the URL to make the underlying connection.
427149
Problem
Text/blob datatypes in prepared statements is not supported for Informix and Sybase native drivers.
Workaround
Use Third Party JDBC drivers.
550207
Problem
While trying to configure more than one resource managers for multiple databases, db_setup on Solaris creates incomplete open string.Workaround There are two possible solutions for this issue:
- Use the Administration Tool to create resource managers, or to modify the open string.
- Configure all resource managers for each database, one at a time.
-
Problem
On Windows NT, the installer, by default sets global transactions to enabled.
Workaround
Disable it when using Third Party drivers.
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 population of the database with sample entries fails.Workaround
When you attempt to install the Pointbase Database, you must have access to an X Windowing System Server, and in particular, have theDISPLAY
environment variable set to point to that accessable server. Otherwise the installation will not complete the database integration properly.If the
DISPLAY
variable is set incorrectly, iPlanet Application Server post installation commands fail.
541425
Problem
Before using applications which access the PointBase driver, make sure that the value ofSOFTWARE\\iPlanet\\Application Server\\6.0\\CCS0\\DAE2\\IS3PJDBC
is set to 1. If not, set it to 1 using kregedit.
-
Problem
You cannot simultaneously configure and use iPlanet Application Server Native drivers and Third Party, Type 2 or Type 4, drivers with the same application server instance.Using Native drivers and Third party drivers simultaneously may cause iPlanet Application Server to hang.
Workaround
If you have configured Native drivers and now would like to use Third Party drivers, ensure that the IS3PJDBC key is set to 1 using kregedit. The IS3PJDBC key is under the registry entry, iPlanet\Application Server\6.0\CCSO\DAE2 .On Windows systems, the ODBC DLL is in the system path and therefore Native drivers are enabled by default.
534541
Problem
iPlanet Application Server is not detecting and purging bad connections for Third Party JDBC Type 2 drivers.Workaround
A patch for this issue, Third Party JDBC Type 2 drivers, is available on request.
Sample Application Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP4 sample application issues, and the associated workarounds.
Note The Bank sample application has been deprecated and is targeted for removal in the next major release of iPlanet Application Server. Therefore, existing bugs in this sample will not be resolved.
ID Summary 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
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.
Workaround
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.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
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.Workaround
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 .
Workaround
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.
Workaround
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.
Workaround
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.
Workaround
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.0 SP4 uninstallation issues, and the associated workarounds.
ID Summary 549853
Problem
Unable to delete iPlanet Application Server entries from the directory server during uninstallation, on the Solaris platform.
You might get this error message even if you have correctly specified the directory entries.
Workaround
Press s to skip this step and continue with the uninstallation process.
-
Problem
Uninstallation of iPlanet Application Server will delete all files under the Planet Application Server installation directory. Therefore, back up important files before uninstalling.
Documentation Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP4 documentation issues, and the associated workarounds.
ID Summary
Deployment Tool Online Help
ID Summary
Problem
The shell scripts and batch files to compile sample applications mentioned in the Deployment Tool help are no longer available.
Workaround
To recompile the core server samples available under iASInstallDir /ias/ias-samples/ ,
- Go to the iASInstallDir /ias/ias-samples/<sample name>/src/ directory
- Execute build compile to recompile, or build core to recompile and reassemble the whole application.
- On Solaris, make sure to set the iASInstallDir /ias/bin/ directory in your PATH environment variable before executing the build command.
How to Report Problems
If you have problems with iPlanet Application Server, Enterprise Edition 6.0 SP4, contact iPlanet customer support using one of the following reporting mechanisms:
- iPlanet online support web site at http://www.iplanet.com/support/online/
From this location, the CaseTracker and CaseView tools are available for logging problems.
The telephone dispatch number associated with your maintenance contract
To assist you in the best possible way to resolve your problems, please have the following information available when you contact support:
- Description of the problem, including the situation where the problem occurs and its impact on your operation
- Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
- Detailed steps on the methods you have used to reproduce the problem
- Any error logs or core dumps
You may also find it useful to subscribe to the following interest groups, where iPlanet Application Server, Enterprise Edition topics are discussed:
- General: snews://secnews.netscape.com/iplanet.ias.general
- Installation: snews://secnews.netscape.com/iplanet.ias.install
- Performance: snews://secnews.netscape.com/iplanet.ias.perf
- Clustering: snews://secnews.netscape.com/iplanet.ias.cluster
For More InformationUseful iPlanet information can be found at the following Internet locations:
- iPlanet release notes and other documentation — http://docs.iplanet.com/docs/manuals/
- iPlanet product status — http://www.iplanet.com/support/technical_resources/
- iPlanet Professional Services information — http://www.iplanet.com/services/professional_services_3_3.html
- iPlanet developer information — http://developer.iplanet.com/
- iPlanet learning solutions — http://www.iplanet.com/learning/index.html
- iPlanet product data sheets — http://www.iplanet.com/products/product_map/product_name_2_0a.html
Use of iPlanet Application Server, Enterprise Edition is subject to the terms described in the license agreement accompanying it.
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.
Last Updated November 13, 2001