Release Notes for iPlanet Application
Server, Enterprise Edition
Version 6.0 SP3
Updated August 17, 2001
These release notes contain important information available at the time of the Version 6.0 SP3 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 SP3
iPlanet Application Server, Enterprise Edition 6.0 SP3 includes enhancements described in the following sections:
Windows 2000 Support
Windows 2000 Professional and Windows 2000 Server SP2 platforms are now supported in production and development
environments.
Note that only iPlanet Application Server is supported on Windows 2000 platforms. The bundled
Directory and Web Server are not supported by iPlanet Support on Windows 2000 platforms.
iPlanet Web Server, Enterprise Edition 6.0 Support
iPlanet Web Server, Enterprise Edition 6.0 is now supported.
iPlanet Directory Server 5.0 Support
iPlanet Directory Server 5.0 is only supported for user authentication.
Apache Web Server Support
Apache Web Server 1.3.19 is supported
Product Packaging
The following products are packaged with iPlanet Application Server, Enterprise Edition 6.0 SP3:
-
iPlanet Web Server, Enterprise Edition 4.1, SP7
-
iPlanet Directory Server 4.13
-
PointBase Network 3.5
-
PointBase Network 3.5, an ORDBMS package, is bundled with this release of iPlanet Application Server, Enterprise Edition 6.0 SP3. PointBase is installed by default when you select iPlanet Application Server 6.0 in the Components to Install panel during installation.
-
The PointBase database server enables you to test your applications on your development machine.
-
Note that PointBase Network 3.5 is an evaluation version of the product. You must buy a full license
from PointBase to use it in production environments.
For more information, see iPlanet Application Server Installation Guide.
-
Web Connector Plug-in for the Apache Web Server
-
Apache Web Server 1.3.19 is supported in iPlanet Application Server, Enterprise Edition 6.0 SP3. For more information on installing and configuring Apache on Solaris and Windows, see iPlanet Application Server Installation Guide.
-
Common Configuration Script for Solaris
-
On the Solaris platform, the common environment variable settings are recorded in a single script file. The iasenv.ksh script records the common environment variable settings of all other scripts, such as kjs, kas, and kxs. These scripts get the required common environment settings from the iasenv.ksh script.
-
The script is located in the <iASInstallDir>/ias/env directory.
Note
|
-
If any of your current applications are reading environment information from these scripts (kjs, kxs, kas, etc.), they need to be modified to read from iasenv.ksh instead.
-
If you face backward compatibility issues, you can define the required
variables within iasenv.ksh instead of modifying the individual
scripts, such as kxs and kjs.
If the same values are present in both iasenv.ksh script and other
scripts which refer to iasenv.ksh (such as kjs), then depending on the
location of the definition of that variable within these scripts, either
iasenv.ksh script setting would be considered (for example, when the variable is
defined before the invocation of iasenv.ksh script within, say kjs) or
the setting that is defined within the other script would be taken into
account (for example, when the variable is defined after the invocation of
iasenv.ksh script within kjs).
|
Core Server Enhancements
iPlanet Application Server, Enterprise Edition 6.0 SP3 includes the following core server enhancements:
Support for multiple LDAP domains
Multiple domains are now supported by iPlanet Application Server. With this, iPlanet Application Server will be able to perform authentication against any directory server that is compliant with Nortel LDAP Schema. For more information on how to use iPlanet Registry Editor (kregedit) to configure multiple domains, see Chapter 1, `Performing Basic Administrative Tasks' in iPlanet Application Server Administrator's Guide.
Jasper Integration
iPlanet Application Server, Enterprise Edition 6.0 SP3 has migrated from its native JSP compiler to Apache's Jasper JSP compiler. This compiler, which is based on Tomcat 3.2.1, is compliant with JSP 1.1 spec.
Note
|
iPlanet Application Server 6.0 SP3 release supports the bundled JSP parser only.
|
For more details, see iPlanet Application Server Developer's Guide (Java).
Programmatic Login Support
New APIs allow a developer to programmatically login to, and logout from, a secured web resource. Developers can use this feature to programmatically authenticate inside a Servlet/EJB method, such that, the principal name for a J2EE application can be controlled through programmatic means.
For more information, see iPlanet Application Server Developer's Guide (Java).
Startup Class Support
This feature allows a user-defined class to be automatically loaded when the Application Server starts up. This class can perform initialization tasks within the Application Server environment.
Note
|
If a Startup class is not deployed, a message is generated in the kjs log file.
|
For more information on how to build and deploy a Startup Class, see iPlanet Application Server Developer's Guide (Java).
Dynamic Class Reloading
iPlanet Application Server, Enterprise Edition 6.0 SP3 supports new hot deployment features through dynamic
class reloading of EJBs. Modification of an EJB occurs immediately when the EJB Container refreshes the pool
for that Bean. State information is maintained for other active beans.
Note that this is not recommended in production systems.
By default, dynamic servlet, EJB and registered JSP reloading is disabled in iPlanet Application Server.
To enable dynamic reloading of servlets, EJBs and registered JSPs, perform the following steps:
-
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 0 (By default, the Disable value is set to 1)
-
Restart iPlanet Application Server to enable the change
Note
|
Unregistered JSPs are dynamically reloaded by iPlanet Application Server even when dynamic reloading is disabled.
|
To hot deploy your application, simply compile and replace the file in the appropriate directory or, use iasdeploy to redeploy applications. Application components are typically stored in the following paths:
-
Applications (ear files) are extracted under:
-
<iASInstallDir>/ias/APPS/<application_name>
-
Servlets are extracted under:
-
<iASInstallDir>/ias/APPS/<application_name>/<module1>/WEB-INF/CLASSES
-
EJBs are extracted under:
-
<iASInstallDir>/ias/APPS/<application_name>/<module1>/
-
JSPs are extracted under:
-
<iASInstallDir>/ias/APPS/<application_name>/<module1>/
-
Individual modules (war and jar files) of applications are extracted under:
-
<iASInstallDir>/ias/APPS/modules/<module1>
-
<iASInstallDir>/ias/APPS/modules/<module2>
Note
|
If you are upgrading from iPlanet Application Server, Enterprise Edition 6.0 SP2 or earlier, you must repackage your EJBs to take advantage of the dynamic reloading feature.
|
RMI/IIOP
When deploying your own RMI/IIOP-based applications, you need not add the module expansion directory to the application server's CLASSPATH. This also helps in leveraging dynamic EJB reloading.
Note
|
If you are upgrading from iPlanet Application Server, Enterprise Edition 6.0 SP2 or earlier you must repackage your EJBs to take advantage of this, and the dynamic reloading feature.
|
Kregedit
The following enhancements have been made to kregedit.
-
Changes the IP address in the entire registry.
-
Find/Replace option added.
-
To enable users to easily find and replace entries in iPlanet Application Server registry, a Find/Replace option has been added. To access the Find/Replace option, start kregedit and select Edit > Find Replace.
For more information, see Chapter 1, `Performing Basic Administrative Tasks' in the iPlanet Application Server Administrator's Guide.
Enhanced KAS Audit Logs
Administration Server (KAS) audit logs, along with the time stamp, now log all configuration parameter changes, except some engine configuration parameters. These engine parameters are logged with a generic message `Config Parameter of Engine ID changed'. The actual parameter can be identified by logging GDS updates.
Log messages of KAS can be viewed in a file by setting the environment variable IAS_KASLOGFILE to 1.
The following New Log messages have been added to KAS, each of them preceded by the time stamp:
Table 1    KAS Log messages with time stamp
S no.
|
Message
|
Description
|
Legend
|
1 |
kas-log> Dispatched Config Parameter change to {0} |
Logged when Config Parameter of Engine Changes |
{0} = Engine Description |
2 |
kas-log> Events for failure of the following : {0} to {1} used script {2} |
Logged when event parameters are modified |
{0} = Failure conditions {1} = mail IDs where message is sent {2} = Script run if any |
3 |
kas-log> Set JAR Path {0} |
Logged when application paths are changed in iASAT |
{0} = JAR path |
4 |
kas-log> Dispatched Re-Init Engine to {0} |
Logged When Engine is re-initialised |
{0} = Engine Description |
5 |
Set LDAP backends, {0} entries, {1} errors while setting |
Logged when LDAP parameters are modified/added |
{0} = No. of entries modified {1} = No. of errors while setting LDAP entries |
6 |
Added KJS Engine Port No. {0} |
Logged when KJS Engine is added |
{0} = Port No. of the Engine |
7 |
Added KCS Engine Port No. {0} |
Logged when KCS Engine is added |
{0} = Port No. of the Engine |
8 |
Added KXS Engine Port No. {0} |
Logged when KXS Engine is added |
{0} = Port No. of the Engine |
9 |
Added CXS Engine Port No. {0} running on IIOP port {1} |
Logged when CXS Engine is added |
{0} = Port No. of the Engine {1} = IIOP port |
10 |
Changed KJS Config Parameter {0} to New Value {1} |
Logged when KJS Engine Config Parameter is changed, Currently used for only "StopTimeout" |
{0} = Config Parameter name (1} = New Value of Config Parameter |
11 |
Changed KCS Config Parameter {0} to New Value {1} |
Same as above |
Same as above |
12 |
Changed KXS Config Parameter {0} to New Value {1} |
Same as above |
Same as above |
13 |
Changed CXS Config Parameter {0} to New Value {1} |
Same as above |
Same as above |
14 |
Config Parameter {0} updated, new value {1} |
Logged when Main KAS Config Parameters are changed |
{0} = Config Parameter name (1} = New Value of Config Parameter |
Deployment Tool Enhancements
The following enhancements have been made to the Deployment Tool:
General Enhancements
-
Save Descriptor feature added
-
The Save Descriptor option is accessible from the Edit menu. The option is also available when you right click a node.
-
Edit Descriptor added at the EJB.JAR level.
-
You can now edit descriptors at the EJB.JAR level. Options available at this level are General and Roles.
-
To edit the description of an EJB.jar file, select the EJB.jar file on the left pane and, either click Edit > Edit Descriptor, or right-click > Edit Descriptor.
-
The View XML option is now accessible from under the newly added View menu item. To see the source of an XML file, select the file and either, click View > View XML, or right-click > View XML.
-
The Extract Module option has been moved from under the Tools menu to the File menu.
-
Update option added
-
The Update option updates changes to the class files. Now, instead of removing and re-inserting the file to enable changes, use Edit > Update.
iasdeploy Enhancements
The following changes and enhancements have been made to the iasdeploy command line utility:
-
The iasdeploy -help command lists the new commands and their usage.
-
verify option added to iasdeploy.
-
The verify option, which is already available in the GUI based Deployment Tool, is now available as a command line utility in iasdeploy.
-
Usage: iasdeploy verify [-verbose] EAR_file|module_ file, where EAR_ file|module_ file is the file name of the J2EE application's EAR file/J2EE module web application WAR file, or ejb jar file.
-
The new redeployapp command speeds up application redeployment. The command usage is same as the deployapp command, and is equivalent to the -reregapp command in j2eeappreg.
-
Example: iasdeploy redeployapp fortune.ear
Note
|
Using redeployapp for undeployed applications will make the deployment slower.
|
-
removeweb command added to remove web applications. This command is equivalent to the -remove web command available in j2eeappreg. You only have to provide the web application's name; the name of war file is not necessary.
-
Usage: removeweb webapp_name
-
removeejb command added to remove EJBs. This command is equivalent to the -remove ejb command available in j2eeappreg.
-
Usage: removeejb ejbjar_name
-
The removeapp command now supports the use of the J2EE application name as the argument.
-
Usage: iasdeploy removeapp j2ee_app_name.
-
To maintain backward compatibility, iasdeploy removeapp ear_file_name, continues to work.
-
The DTDs of all XML files have now been moved to a new location, <iASInstallDir>/ias/dtd. In earlier releases they were placed in the APPS directory.
-
Changes in the Registry
-
In the SP3 release, the versioning of deployed Beans has been removed. The SOFTWARE/iPlanet/Application Server/ClassDef/GUID/version key will always be 1.0 for newly deployed Beans. Version numbers for Beans deployed in iPlanet Application Server 6.0 SP2 release will not be incremented.
Sample Application Enhancements
The following samples have been added in iPlanet Application Server, Enterprise Edition 6.0 SP3 release:
-
EJB to Backend CORBA Demonstrates access to backend CORBA services from EJB and web components on iPlanet Application Server.
-
Apache SOAP Samples Installation of Apache SOAP and Apache SOAP samples.
-
SOAP Helloworld A simple sample that demonstrates calling an iPlanet Application Server EJB using SOAP as the transport protocol.
-
SOAP Shoppingcart A complex sample that shows how to access stateful session beans.
-
HelloDB A simple interface to a database.
-
BLOB Demonstrates access to BLOB data types using JDBC.
-
SQLRunner Demonstrates a web based SQL interface to a relational database.
-
Servlet Caching Demonstrates Servlet Caching.
-
Transactions This sample demonstrates iPlanet Application Server support for local and global transactions (both Container Managed and Bean Managed using JTA).
Documentation for the sample applications is available at: <iASInstallDir>/ias/ias-samples/index.html, or through the web server of your iPlanet Application Server installation at: http://host:port/ias-samples/index.html
Web Connector Log Messages
The Web Connector's log messages can now be redirected to a file of your choice. By default, the Plug-in sends its messages to the Web Server's log.
To send the messages generated by the plug-in to a file, for example /space/user/logs/iasplugin.log, set the shell variable on Solaris, and the System Environment Variable on Windows, IAS_PLUGIN_LOG_FILE to /space/user/logs/iasplugin.log.
Note
|
The shell variable on Solaris, and the System Environment Variable on Windows, IAS_PLUGIN_LOG_FILE should contain the absolute pathname of your log file.
The user-defined log file should have the same owner:group as the web server with the appropriate permissions.
|
Compatibility with Previous Releases
This section describes upgrading and SP2 JSP Parser compatibility issues.
Upgrading
This iPlanet Application Server, Enterprise Edition 6.0 SP3 release enables you to upgrade from SP1/SP1 RevB and SP2 to SP3. For more information on upgrading to SP3, see Upgrading to SP3.
Note
|
SP1 and SP1 RevB have been used interchangeably in this document.
|
Backward Compatibility with the SP2 JSP Parser
iPlanet Application Server, Enterprise Edition 6.0 SP3 adheres more strictly to the J2EE specifications than earlier releases. To allow existing applications that depend on the case-insensitiveness of the JSP Parser included in SP2, kjs has been modified to accept a parameter, which makes Jasper case-insensitive.
To make Jasper case-insensitive, make the following changes on your Solaris or Windows platform:
-
On Solaris, the 'kjs' script needs to be modified to include the argument
-
-DIAS_JSP_IGNORECASE=true
-
The last line of the kjs script should read:
-
$GX_ROOTDIR/bin/$KJS -DIAS_JSP_IGNORECASE=true -DPATH=$PATH $opts
-
On Windows, use kregedit to add the value -DIAS_JSP_IGNORECASE=true to the JAVAARGS key at the following location in the registry:
-
\\(SOFTWARE\iPlanet)\Application Server\6.0\JAVA\JavaArgs
The native JSP Compiler included with iPlanet Application Server, Enterprise Edition 6.0 SP2 release can be used instead of Jasper by setting the following parameter:
-
On Solaris, the 'kjs' script needs to be modified to include the argument
-
-DIAS_JSPSTRICT=false
-
The last line of the kjs script should read:
-
$GX_ROOTDIR/bin/$KJS -DIAS_JSPSTRICT=false -DPATH=$PATH $opts
-
On Windows, use kregedit to add the value -DIAS_JSPSTRICT=false to the JAVAARGS key at the following location in the registry:
-
\\(SOFTWARE\iPlanet)\Application Server\6.0\JAVA\JavaArgs
To adhere to the J2EE specifications, we recommend that you do not use these modifications.
Documentation Updates
The following manuals and online help tools were updated for iPlanet Application Server, Enterprise Edition 6.0 SP3.
Installation Guide
The iPlanet Application Server, Enterprise Edition 6.0 SP3 release includes the following changes for the Installation Guide:
-
Created a new chapter "Preparing to Install" to consolidate information and introduce the various types of installation procedures.
-
Created a new chapter for uninstallation procedures.
-
Improved the overall flow of the task-oriented procedures.
-
Added information on the various types of upgrade and migration scenarios.
Administrator's Guide
The iPlanet Application Server, Enterprise Edition 6.0 SP3 release includes the following changes for the Administrator's Guide:
-
Explained how to manage entries in iPlanet Registry
-
Described the process for changing the IP Address in iPlanet Registry.
-
Explained how to use start and stop iPlanet Application Server using command-line tools
-
Explained how to enable support for Multiple LDAP Domains
-
Described the process for setting up iPlanet Application Server for development
-
Explained how to set up and configure 3rd party JDBC drivers, resource managers and data sources on both Windows and Solaris.
-
Described how to encrypt communication between web server and iPlanet Application Server.
-
Described the process to set up and manage firewalls for iPlanet Application Server, along with examples and illustrations.
-
Explained how to process to monitor log files on both Solaris and Windows.
-
Described the process through which a backup Directory Server can be configured for failover.
-
Explained how to manually configure the web-connector plug-in.
-
Described how to use command-line tools to manage distributed transactions.
-
Explained cluster configuration and how to set up and manage clusters using iPlanet
-
Application Server Administration Tool and iPlanet Registry Editor. A detailed example detailing the coordination within a seven-server cluster has also been provided.
Migration Guide
The iPlanet Application Server, Enterprise Edition 6.0 SP3 release includes the following changes for the Migration Guide:
-
Described how to use the new redeploy command utility to redeploy your iPlanet Application Server, Enterprise Edition 6.0 SP1 applications to the 6.0 SP3 release.
Developer's Guide (Java) (renamed from "Programmer's Guide (Java)")
The iPlanet Application Server, Enterprise Edition 6.0 SP3 release includes the following changes for the Developer's Guide (Java):
-
Documented all iPlanet Application Server 6.0 SP3 features.
-
Rewrote the RMI/IIOP chapter.
-
Rewrote the CMP section.
-
Added new information for servlet parameter verification.
-
Rewrote the JSP load balancing information.
Deployment Tool Online Help
The iPlanet Application Server, Enterprise Edition 6.0 SP3 release includes the following changes for the Deployment Tool Online Help:
-
Added the verify option documentation (iasdeploy command).
-
Added the Update option to the Edit menu help page.
-
Added a new help page for the View menu.
-
Added a new section on extracting modules (option now available from the File menu).
-
Added a new page for the Context tab in the web deployment descriptors.
-
Added a new section on how to modify EJB components globally.
-
Added a new section on saving and editing descriptors.
Software and Hardware Requirements
Your 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
-
400 MB free hard disk space
-
256 MB RAM (512 MB recommended)
-
One of the following Web Servers:
-
iPlanet Web Server, Enterprise Edition 6.0,
-
iPlanet Web Server, Enterprise Edition 4.1 SP7
-
Apache Web Server 1.3.19
-
The following Web browser:
-
Netscape Communicator 4.5 or later
-
Solaris Patch Requirements
-
On Solaris 2.6, iPlanet Application Server, Enterprise Edition 6.0 bundles Solaris Production JDK 1.2.2_07 for SPARC. The following patches for JDK 1.2.2_07 must be applied on Solaris 2.6. These patches can be downloaded from the http://sunsolve.sun.com site.
Table 2    Required JDK 1.2.2_07 patches for Solaris 2.6
Patch
|
Patch Description
|
105181-23 |
Kernel update patch |
105210-32 |
libaio, libc & watchmalloc patch |
105284-37 |
Motif 1.2.7: Runtime library patch |
105568-18 |
Libthread patch |
105633-48 |
OpenWindows 3.6: Xsun patch |
105669-10 |
libDtSvc Patch |
106040-14 |
X Input & Output Method patch |
106409-01 |
Fixes the Traditional Chinese TrueType fonts |
107733-08 |
Linker patch |
108091-03 |
ssJDK1.2.1_03 fails with fatal error in ISO8859-01 Locales |
-
For Solaris 8, apply the recommended JDK 1.2.2_07 patches listed on the http://sunsolve.sun.com site.
Table 3    Recommended Solaris 8 OS patches
Patch
|
Patch Description
|
108991-12 |
libc and watchmalloc patch |
Windows
Your Microsoft Windows system must meet the following requirements before you can install iPlanet Application Server:
Installation Notes
This section includes information for installing and upgrading your iPlanet Application Server. For additional information about system requirements and installing the product, see the Installation Guide.
Prerequisites for Installation
Before you start, consider the following guidelines:
-
Check the Software and Hardware Requirements
-
Login to the system as a user who has administrative privileges
-
Have the product key nearby; it's in the Welcome letter
-
Ensure that a static IP address is assigned to the installation machine (contact your system administrator to get one)
-
If your user directory is on a remote machine, ensure that you specify the same admin domain name for the configuration directory and the user directory.
-
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.
-
If you are planning to use iPlanet Application Server, Enterprise Edition 6.0 SP3 with iPlanet Directory Server (IDS) 5.0 on a different machine, ensure that during the installation of IDS 5.0, the domain suffix is specified as o=xxx.yyy.zzz, and not in the default format: dc=xyz, dc=yyy, dc=zzz.
-
iPlanet Application Server will not work with IDS 5.0 if the suffix is given as dc=xxx, dc=yyy, dc=zzz.
-
Have a Web Server and Web Browser installed
Note
|
The Apache Web Server 1.3.19 is supported in this release of iPlanet Application Server, Enterprise Edition 6.0 SP3. However, to use the Apache web server, you must first install iPlanet Application Server with either iPlanet Web Server or IIS.
After installation is complete, follow procedures listed under "Configuring Apache Web Server" in the Installation Guide to set up Apache with iPlanet Application Server, Enterprise Edition 6.0 SP3.
|
On both the Windows and Solaris platform, there are several installation options, including:
-
ezSetup
-
Express
-
Typical
-
Custom
-
Silent
Use the Custom installation options for more complex installations. In addition, the Silent type of installation allows you to simultaneously install the product on multiple machines. For more information, see iPlanet Application Server Installation Guide.
Upgrading to SP3
This section describes procedures to upgrade from iPlanet Application Server, Enterprise Edition 6.0 SP1 RevB and SP2, to iPlanet Application Server, Enterprise Edition 6.0 SP3.
Due to changes in SP3 to provide enhanced security, and the class loader, you must redeploy applications running on SP1 using the redeploy utility. For more information on upgrading from SP1 RevB to SP3, see Upgrading from SP1 RevB to SP3.
Upgrading from SP2 is fairly straightforward. Your applications are automatically migrated when you install SP3. For more information on upgrading from SP2 to SP3, see Upgrading from SP2 to SP3.
Before You Start
Make sure to follow these guidelines before you start upgrading to SP3:
-
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) and other utilities to make those changes.
-
During the upgrade process on Solaris, existing kas, kxs, kjs and kcs scripts are backed up in the <iASInstallDir>/ias/backup directory. If you had previously made changes to these scripts, then you must enter them in the iasenv.ksh file, after upgrading.
-
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.
-
After the Directory Server has restarted, all iPlanet Application Server instances will function normally.
-
If you are running a release earlier than iPlanet Application Server, Enterprise Edition 6.0 SP1 RevB, then you must perform a complete reinstall.
Upgrading from SP2 to SP3
Use the following procedure to upgrade to iPlanet Application Server, Enterprise Edition 6.0 SP3.
This section includes upgrade procedures for the following platforms:
Upgrading on Windows Platforms
To upgrade to iPlanet Application Server, Enterprise Edition 6.0 SP3 on Windows platforms, perform the following steps:
-
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.
-
You must accept the License agreement to continue.
-
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.
-
The Components to Install screen appears.
-
Deselect Directory Server Suite.
-
Select iPlanet Application Server 6.0.
-
Make sure this is the only selected component.
-
Follow directions in the installer as you would for a normal installation. You will require the License Key that you received in the Welcome letter.
-
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.
-
For detailed information on the installation procedure, see iPlanet Application Server Installation Guide.
Upgrading on Solaris Platforms
To upgrade to iPlanet Application Server, Enterprise Edition 6.0 SP3 on Solaris, perform the following steps:
-
Ensure you have met all the conditions listed in Software and Hardware Requirements, and Prerequisites for Installation.
-
Run the setup program.
-
For detailed information on the installation procedure, see 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.
-
The iPlanet Server Products Components screen appears.
-
Type-in 4 and press Enter to install only iPlanet Application Server Suite component.
-
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.
Note
|
Choose the same configuration options that you chose for the existing installation. You can make modifications to your configuration after upgrading.
The installer will not display the existing port numbers and configuration details. You must enter the same values as used by the existing installation.
|
-
Follow directions in the installer as you would for a normal custom installation. You will require the License Key that you received in the Welcome letter.
-
For detailed information on the installation procedure, see iPlanet Application Server Installation Guide.
Upgrading from SP1 RevB to SP3
The following changes made to iPlanet Applications Server, Enterprise Edition 6.0 SP3 make it necessary to redeploy applications running on SP1 RevB:
-
Applications that contain code that tries to read the username and password from an HTTP request string will not work on SP3, even after redeploying the application on SP3. You will have to modify the application's source code to use Form Based Authentication.
-
iPlanet Application Server, Enterprise Edition 6.0 SP3 extracts class files in a .war file under the directory, <iASInstallDir>/ias/APPS/<application-name>/<module1>/classes, compared to <iASInstallDir>/ias/APPS in SP1.
-
The Jasper compiler integrated with iPlanet Application Server 6.0 SP3 specifically expects this directory structure.
Note
|
The Jasper source files have been modified to work better with iPlanet Application Server 6.0 SP3. Only use the archives that are bundled with the application server installation.
|
-
The new Class Loader implemented in SP3 might not be able to load class files from previously deployed .war components of .ear files placed in the wrong path.
-
For more information, see the iPlanet Application Server Migration Guide.
To upgrade from SP1 RevB to SP3
To upgrade from SP1 RevB to SP3, on both the Windows and Solaris platforms, perform the following procedure:
-
Install SP3 in the same location where SP1 is currently installed.
-
Follow instructions given in Upgrading from SP2 to SP3.
-
After completing the SP3 installation, run the redeploy utility to migrate applications to SP3.
-
The redeploy utility is shipped along with iPlanet Application Server 6.0, Enterprise Edition 6.0 SP3 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 SP3. 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.
Note
|
Applications that consist of only .war files (not packaged within an .ear file), will have to be redeployed manually after upgrading.
If you have applications deployed on SP1 that uses database clients not supported by SP3, then you must register a database client compatible with iPlanet Application Server EE 6.0 SP3 and register the data sources for these applications.
To register the database drivers, run dbsetup.exe (for native drivers) and jdbcsetup.exe (for third party drivers) on Windows, and db_setup.sh on Solaris after completing the upgrade.
Use the iasdeploy utility to register datasources.
|
Resolved Issues
The following table lists the critical issues resolved in iPlanet Application Server, Enterprise Edition 6.0 SP3 release.
Table 4    List of resolved issues
Bug ID
|
Area
|
Description
|
513368 |
Core server |
Java memory leak problem |
529628 |
Core server |
Not recovering from two primaries(Split Brain) |
513371 |
Core server |
Keeping CNX opened between WS and NAS |
537059 |
Core server |
RFE:Binding of user to multiple DNs |
536588 |
Core server |
href link in a jsp the session id does not get attached |
526420 |
Dsync |
JSP response time grows with time on load in cluster mode |
530400 |
Dsync |
Cyclic Degradation of Performance |
401078 |
Dsync |
Distributed Servlet session update sometimes lost |
531705 |
JDBC |
KJS dumps core for illegal SQL statement |
527017 |
JDBC |
Exception thrown in forming prepared statement with esc character |
525211 |
JDBC |
KJS crashes when >500 db connections are simultaneously initiated |
529229 |
JDBC |
Return code is modified forcefully |
534541 |
JDBC |
iPlanet Application Server not detecting and purging bad connections |
545635 |
JDBC |
Create statement throws exception if global transaction is enabled for the database on Windows NT. |
521075 |
EJB |
Stateful Session Bean with failover: leaks memory |
535611 |
EJB |
Multipart/Compound CMP Custom Finder without parameter does not work |
517600 |
EJB |
[REG] Multipart key for CMP does not work |
528572 |
JSP |
JSP session data not spilled over |
527403 |
JSP |
JSP size too large to be loaded by servlet engine |
533381 |
JSP |
User defined error pages not working correctly |
531180 |
JSP/Session |
Objects with session scope are lost in nested JSP's |
531962 |
JSP/Session |
session.remove attribute does not work in nested JSP's |
533962 |
JSP/Session |
saveSession()call fix to PlatformHttpServletResponse.class |
532749 |
Session |
iPlanet Application Server does not pass session info between web applications |
534638 |
Session |
ias-webparam does not work |
535354 |
Plug-in |
Web server crashes while streaming serialized objects having float value 0.0312 |
529187 |
Plug-in |
Strange error messages appear in the error log files of iWS |
529999 |
Plug-in |
Web connector logging files than their errors |
527408 |
Plug-in |
Sticky Load balancing doesn't work when cookies are disabled |
546012 |
Plug-in |
Unable to open kregedit from the machine on which the Web Connector is installed. |
526502 |
Deploy Tool |
Long file names for EJB causes deployment tool fail while creating stubs and skeletons. |
533358 |
Deploy Tool |
Form is written as Form; FORM expected |
541239 |
Deploy Tool |
In a multi-server setup, application deployment doesn't work if multiple servers are selected. |
537340 |
Servlet |
Calling httpresponse sendRedirect returns invalid location with cookie-less browser |
533961 |
Servlet |
NASAPP is not case sensitive |
528155 |
Security |
Certificate authentication |
532387 |
Cluster |
Unable to remove a NAS server from cluster |
529581 |
Java Script |
Discrepancy when executing Javascript code from a JSP for the first time |
517945 |
Directory Server |
No easy way to change LDAP Directory Location. |
Known Problems and Limitations
This section describes known problems and associated workarounds with iPlanet Application Server, Enterprise Edition 6.0 SP3. This information is organized into the following sections:
Installation Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP3 installation issues, and
the associated workarounds.
ID |
Summary |
549653 |
Problem
Installation/upgradation fails on Windows if iPlanet Application Server installables are placed in a
directory containing spaces or special characters.
Workaround
The iPlanet Application Server installables should be placed in a directory, which has no spaces or special
characters.
|
549837 |
Problem While upgrading to SP3, the installation might pause for a long time. The delay
occurs if you have large number of applications deployed in the existing installation.
Workaround
This is normal behavior, when the existing installation has a large deployment base. Wait for the installation to
complete.
|
546941 |
Problem iPlanet Application Server fails to install Directory Server on Windows
2000, after IDS 5.0 has been uninstalled from the machine.
This problem occurs if you had previously uninstalled iPlanet Directory Server 5.0 from the Windows 2000 machine on which you are installing iPlanet Application Server, along with the default directory server.
Workaround
Delete ns-dshttpd40.dll from the
Winnt\System32 directory before installing iPlanet
Application Server.
|
524125 |
Problem In custom installation mode, at the point where the user is asked if he wants
to populate the Directory Server with entries, if he chooses None then no entry is created.
After
installation, connecting to the server fails since the user is not in the LDAP information.
Workaround Instead of choosing None, the user should select the option Suggest.
|
- |
Problem Creation of administrator user entry in the remote user directory fails if that directory is read-only.
The administrator user entry must exist in the configuration LDAP directory for registering the server through iPlanet Application Server Administration Tool (iASAT).
Workaround
To enable iPlanet Application Server to authenticate against a remote configuration directory server, complete the
installation and then perform the following steps:
-
Create an adminuser.ldif file with the following entries:
|
dn: uid=iasadmin., ou=People, o=iplanet.com
|
changetype: add
|
cn: Nas Administrator
|
sn: Nas Administrator
|
givenname: iAS admin
|
objectclass: top
|
objectclass: person
|
objectclass: inetorgperson
|
ou: People
|
uid: iasadmin
|
userpassword: password
|
|
-
Run the ladapmodify command:
<iASInstallDir>/shared/bin> -D "cn=Directory Manager" -p <ldap_PortNo.> -w
<password> -a -f adminuser.ldif.
|
- |
Problem Having the configuration directory and user directory in two different machines is not supported.
|
547124 |
Problem
The installation of iPlanet Application Server on a Unix System fails with the message "Unable to contact Driectory Server".
Workaround
Ensure that the machine is reachable by doing "ping .". If not, add the fully qualified
domainname in /etc/hosts.
|
550753 |
Problem
If you install iDS 5.0 and iPlanet Application Server, EE 6.0 SP3 separately, iPlanet Application Server returns an error
message on Solaris platforms.
Workaround
While installing iDS 5.0, there is a suffix screen which has by default an entry as dc=india, dc=sun, dc=com. Change
this value from dc=red dc=iplanet dc=com to o=red.iplanet.com, and the installation is successful.
|
Core Server Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP3 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.
|
541702 |
Problem Using HttpServletRequest.getRequestDispatcher with a relative path does not work.
|
542650 |
Problem
HTTP Authentication fails due to LDAP library libldap30.so Incompatibility.
iPlanet Application Server installation modifies the LDAP lib (libldap30.so ) path in
obj.conf . After installation, the web server attempts to use libldap30.so from the
Application Server installation which fails due to version incompatibility.
Workaround
Rename libldap30.so in ias/gxlib .
Alternatively, modify the post installer not to extract libldap30.so in ias/gxlib since
iPlamet Application Server doesn't use it.
|
Administration Tool Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP3 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.
|
Deployment Tool Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP3 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 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
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 SP3, 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 SP3:
-
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.
-
This will create a META-INF directory, and directories with the package name.
-
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:
-
jar cvMf ejb.jar META-INF package_name
|
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 deploytool
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".
- DT 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.
- DT 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 DT.
- User "B" needs to have READ and EXECUTE permissions to many other directories/files as DT 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.
|
Database Support Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP3 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:
-
Add the line locale = C, us_english, iso_1 in the <Sybase_home>\SYBASE\locale\locales.dat file.
-
In the Environment variable settings, add the key DSQUERY and assign it the name of the Sybase server.
-
Reboot your system.
|
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 the DISPLAY 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.
|
- |
Problem
Before using applications which access the Pointbase driver, make sure that the value of
SOFTWARE\\iPlanet\\Application Server\\6.0\\CCS0\\DAE2\\IS3PJDBC is set to 1.
If not, set it to 1 using kregedit.
|
384721 |
Problem
Unable to get the size of LONG type from Oracle Stored procedure on Solaris and NT platforms using the native driver.
Using the getString() method of callableStatement displays the wrong string length, although the
correct string is returned.
|
Sample Application Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP3 sample application issues, and the associated workarounds.
ID |
Summary |
549549 |
Problem Samples fail after recreating tables in PointBase.
Several of the J2EE Developer's Guide samples require 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 Oracle Type 4 driver with Bank application.
Workaround
Avoid using special characters or `-'
for SSN
or Phone number fields.
|
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
|
549990 |
Problem Documentation error in the Transactions sample.
In the "Local JDBC Transaction Application" chapter, under "Running the Application" heading, the URL given for starting the application is wrong.
Workaround
The correct URL is /NASApp/transactions-localjdbc/index.html.
|
550427 |
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 SP3 does not
support subqueries.
|
Uninstallation Issues
This section describes the known iPlanet Application Server, Enterprise Edition 6.0 SP3 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 SP3 documentation issues, and the associated workarounds.
Installation Guide
ID |
Summary |
- |
Problem Missing space in Code Example A-3, under "Configuring Apache Web Server" in the Chapter "Configuring iPlanet Application Server".
Workaround
An extra space should be present between nas_module<iASInstallDir> in the line LoadModule nas_module<iASInstallDir>/ias/bin/iASApachePlugin.dll.
|
Deployment Tool Online Help
ID |
Summary |
532751 |
Problem The documentation for the Context Root tab of EAR descriptor is currently documented under WAR Deployment Descriptor.
Workaround
Read the information for the Context Root tab of EAR descriptor from, Deployment Descriptor tabs > Web Application > Context Root.
|
546464 |
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 SP3, contact iPlanet customer support using one of the following reporting mechanisms:
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:
For More Information
Useful iPlanet information can be found at the following Internet locations: