iPlanet Application Server 6.0 Service Pack 1 Release Notes

iPlanet Application Server

Release 6.0 Service Pack 1 Revision B

Release Notes

Updated October 9, 2000

Contents

What's New
System Requirements
Getting Started
Issues and Limitations
Documentation Errata
Reporting Problems
For More Information

What's New

Deployment Tool
Third Party JDBC Driver Support
Unregistering Applications
Control Command Script Enhancements
Installer Enhancements
Enhanced Sample Applications
Installation of Multiple Instances
Third Party CMP Integration

Deployment Tool
In Service Pack 1, a completely new Deployment Tool has been developed. It provides:

An easy to use graphical interface
Independent one-step installation separate from the iPlanet Application Server
Ease of deployment of complex J2EE applications
An easier process for assembling, packaging, and deploying applications
A deployment verification feature to ensure deployment of complete applications
Full-featured and robust online help
Screen-level context sensitive help

Launching Deployment Tool
The old deployGUI.bat (NT) deployGUI.sh (Solaris) has been replaced with the command deploytool.bat for NT and deploytool.sh for Solaris.

Using the Command Line Interface
You can launch the Deployment through a deploycmd command line interface. The script for the interface is located in: <ias install dir>\ias\bin\deploycmd.
The command line usage syntax is as follows:
deploycmd -<option> [args...]
Where the options include:

deploy Deploys a J2EE module/application.
createstubs Creates stubs and skeletons.
resreg Registers a data source.
getAllGroups Gets all the groups.
getAllUsers Gets all the users for a specified group.
getMembersOfRole Gets all the users/groups for a role.
mapRoles Maps a role to the users/groups.
help Gets help on a particular option.

To get help on a particular option enter at the command line: deploycmd -help [-
For example: deploycmd -help -deploy provides a complete command description for the deploy option (command lists and usage).
For more information about using and deploying your applications, consult the Deployment Tool online help.
Third Party JDBC Driver Support
Support has been added for using third party JDBC drivers in conjunction with standard J2EE JNDI-based datasource access, iPlanet Application Server connection pooling, and transaction management features.
Refer to the System Requirements section of this Release Note for detailed Type 2 JDBC Driver Support.
Also, refer to the iPlanet Application Server Installation Guide V6.0 SP1 for more information on installing third party JDBC drivers.
Unregistering Applications
To unregister your applications and provide verbose output if required, type:
j2eeappreg -remove [-verbose] ear-file
To unregister a J2EE Application EAR file(s), you must supply the EAR file that was deployed to the ias/JAR/ directory when running J2eeappreg -remove. This EAR file should be representative of what was last deployed to the server instance.
Currently, the -remove option only deregisters the application from the iPlanet Application Server Registry. The feature does not remove application files (for example, JSPs, classes, etc.) from the deployment area (by default, <ias install>/ias/APPS/) of the file system. To fully undeploy an application, you would want to remove the application files as well.
Control Command Script Enhancements (Solaris Only)
The iascontrol script now supports starting, stopping, and killing iPlanet Application Server instances via a command-line interface.
A superset of the now-deprecated KIVAes.sh script is now available. Use iascontrol instead of KIVAes.sh.

Before using iascontrol on a local server:

Use the Admininstration Tool (ksvradmin) to register the local server.
If you do not register the local server, you will need to specify the host/port/name/password every time you run iascontrol.

iascontrol can start from scratch, stop, or force-kill local iPlanet Application Server instances.
For a registered server on the local machine type: iascontrol start | stop | kill
Where:
start: starts up KAS and all engines.
stop: gracefully brings down all engines, but leaves KAS running.
kill: kills all server processes immediately (localhost only). The Kill is equivalent to the old KIVAes.sh stop command.
To use iascontrol to start and stop remote iPlanet Application Server instances:

The remote KAS process must be running.
The KAS process cannot be started from a remote machine.
A remote iPlanet Application Server instance cannot be killed.
You must always specify name/password/host.
For example: iascontrol -user <username> -password <password> [-host <host>-port <port>] start | stop

If a host is not specified, a localhost is assumed.
If port is not specified, the default port 10817 is assumed.
The stop command is a graceful shutdown of all processes except KAS. It is equivalent to using Stop Server in the Administration Tool.

iascontrol Commands:

Desired Affect Command

Graceful Shutdown of Engines (excluding the Admin Server) iascontrol stop

Graceful Shut Down of All Engines and Stopping the Admin Server (kas) iascontrol stop
iascontrol kill

Stopping all iAS Processes via Forced Kill iascontrol kill

Starting Engines and Admin Server (kas) iascontrol start

Installer Enhancements
The installation process has been enhanced by adding the following features:

EZSetup: On NT and Solaris, installation is made quicker with the EZSetup option. This option is intended for quick installations for evaluation purposes. Do NOT use EZSetup for upgrading your release.
Installation Enhancements: The typical, express, and custom installation setup have been enhanced for easier installation.

See the iPlanet Application Server Installation Guide V6.0 SP1 for more information.
Enhanced Sample Applications
The sample applications distributed after release of iAS 6.0 have been further enhanced and packaged in this Service Pack 1 release. For details on the enhancements, refer to the README section of the Sample Applications Launchpad at http://<webserver host>/ias-samples/index.html or <iAS install path>/ias/ias-samples/index.html.
Multiple Instances of iPlanet Application Server
With this Service Pack 1 release, installation of multiple instances on a single Solaris machine is now supported. See the iPlanet Application Server Installation Guide V6.0 SP1 for more information.

Third Party CMP Integration
As described in the iPlanet Application Server 6.0 Programmer's Guide, as part of the iPlanet Application Server 6.0 release, iPlanet provides a simple single table mapping persistence manager reference implementation. The reference implementation uses mapping information generated by the Deployment Tool. Users may also hand modify the mapping information file produced by the Deployment Tool to access additional features. For example, custom finder methods are not supported by Deployment Tool but may be added to the mapping information file by hand. See the Known Issues section regarding steps on manually modifying the mapping information file generated by the Deployment Tool.
Since the release of iPlanet Application Server 6.0, THOUGHT, Inc. has integrated their existing CocoBase O/R mapping offering with iPlanet Application Server's pluggable CMP framework. CocoBase provides sophisticated generation tools, customizable implementations, a performant O/R runtime engine, and a wide assortment of supported database platforms. See the THOUGHT, Inc. web site for more details. http://www.thoughtinc.com/

System Requirements

Hardware and Software Requirements
Database Requirements
New Third Party JDBC Support
Patch Requirements
Application Compatibility

Hardware and Software Requirements

Device Requirement

Computer/Operating system Sun UltraSPARC running Solaris 2.6 or Solaris 8
Windows NT 4.0 SP 5

Memory Per CPU: 256 MB minimum; 512 MB recommended

Available disk space Total disk space:

200 MB NT
400 MB Solaris
800 MB Solaris if installing both NetDynamics and iPlanet Application Server 6.0

CD-ROM drive

Other software Support the following web servers:

iPlanet Web Server 4.1 Enterprise Edition
Microsoft Internet Information Server 4.0 (NT only)

One of the following web browsers:

Netscape Communicator 4.5 or later
Microsoft Internet Explorer 4.0 (NT only) or later

Database connectivity software (see the following tables)

Database Requirements
Pre-existing iPlanet Application Server Type 2 JDBC Driver Support (DAE2 and Native Client Libraries).

Database Client Database Server

Oracle 8.1.6 Oracle 8.0.5, 8i (8.1.5 and 8.1.6)¹, 7.3.4

Sybase 11.1.1 Sybase 11.9.2, 12

DB2 5.2 DB2 5.2, 6.1

ODBC 3.51 Microsoft SQL Server 7

Informix 2.4 Informix Server 9.x

¹ Support is for 8.1.5 functionality in an 8.1.6 server environment.

New Third Party JDBC Driver Support¹

Driver Platform

Oracle8i 8.1.6.0.1: Type 4 Solaris and NT

Oracle8i 8.1.6.0.1: Type 2 Solaris and NT

Merant (Intersolv) SequeLink Java Edition All OS platforms supported above
RDBMS platforms supported by SequeLink

Sybase jConnect for JDBC v5.0 Type 4 (with Oracle only) Solaris and NT

DB2 v6.1 NT only

Access to MSFT SQL Server Available from Merant

¹ Other drivers that support JDBC Driver Manager will work, but have not been tested. Only local transactions are supported with these drivers.
For more information on installing, configuring, and switching between native and third party JDBC drivers, see the iPlanet Application Server Installation Guide V6.0 SP1.
Refer to vendor documentation before installing these drivers.

Patch Requirements
The iPlanet Application Server 6.0 bundles Solaris Production JDK 1.2.2_05a for SPARC. For proper operation of the Application Server, the following Solaris patches need to be applied to the system:

Patch ID Patch Description

105490-07 Linker Patch

105568-14 Libthread Patch

105210-25 LibC Patch

106040-13 X Input & Output Method Patch

105633-30 OpenWindows 3.6: Xsun Patch

106409-01 Fixes the Chinese TrueType fonts

108091-01 SunOS 5.6: ssJDK1.2.1_03 fails with fatal error in ISO8859-01 Locales

105181-17 Kernel Update (socket close/hang)

105669-09 CDE 1.2: libDTSvc Patch (dtmail)

105284-31 Motif 1.2.7: Runtime library patch

These patches are NOT bundled with iPlanet Application Server 6.0 Service Pack 1 distribution. They can be downloaded from: http://www.sun.com/software/solaris/java/download.html.
Select the Solaris SPARC Platform Edition link, under J2SE: Java 2 Standard Edition (1.2.2_05a). Registration or login is needed to access the download page.
Although Solaris 8 does not need any patches, to work around a Solaris libthread bug (4326537), use libthread.so from /usr/lib/lwp. This has the effect of using Bound Solaris threads instead of user level threads; enhancing stability without impacting performance.
Arguments can be supplied to the Solaris JDK can be set via the JAVA_ARGS shell variable in kjs shell script.
Settings with JVM flags, particularly -Xms and -Xmx flags, specify the starting and maximum heap size used by each kjs engine. This decision is based on how much memory is available on the system, and how much can be set aside for Java Object heaps. Set these as large as possible without starving other applications running on the same server. The default starting heap size is 8MB. This setting grows automatically if the dataset is large. Starting with a large heap size avoids frequent garbage collection during growth.
To cap the heap growth size, use the -Xmx flag. The JDK documentation provides more information on these and other flags.
No patches are needed to run JDK 1.2 on the Solaris 2.8 platform.

Application Compatibility
All J2EE applications previously registered will work with this Service Pack 1 release without any modifications. Please consider the following:

In Entity beans, if the bean persistence is managed by the EJB Container (CMP model), getting the primary key using EJBContext would result in an exception from the ejbActivate method. The primary key field is filled in at a later point and should be available for all business or bean methods.
It is recommended that different datasource names be used for third party JDBC and Native drivers. By doing this, these drivers could be used at the same time if need be.
For running Netscape Application Server 2.1 applications, you will need to add a registry entry under the \\SOFTWARE\\iPlanet\\6.0\\CCS0\\DAE with key ksample and value set to the driver name e.g. ksample = ORACLE_OCI

Getting Started
The iPlanet Application Server 6.0 Service Pack 1 is distributed on two CDs:

Disk1: iPlanet Application Server 6.0 Service Pack 1
Disk2: NetDynamics 5.0.2
Insert the CD in your CD-ROM drive and run the setup program to initiate the upgrade.

Upgrading the iPlanet Application Server 6.0
Using the Silent Installation Feature
Modifying the iPlanet Application Server Java Runtime Environment Settings
Running the Java Message Service (JMS)
Java Message Service Sample Application
Assembling and Registering J2EE Modules and Applications
Underlying Registration Command Line Interfaces
Sample Application Build Facility

Upgrading the iPlanet Application Server 6.0
Before installing the iPlanet Application Server, you must either install or upgrade the web server, and note the web server instance (required for Solaris installs).

To Upgrade from Release 6.0 to Service Pack 1 (Solaris):

untar the upgradeldap.tar file located in Upgrade/Solaris/ldap directory on the CD to your <install dir>/lib directory. (For example, /iplanet/ias6/lib).
Run the setup command.
Select the Upgrade option.
You will be prompted to identify the Netscape configuration directory server admininstration ID and password.

When the "Shutting down server slapd-<your_hostname>" message appears on the terminal window, navigate to <install dir>/slapd-<your_hostname> directory and start the LDAP server again.

run the setup command from Upgrade/Solaris/Adminconsole and choose the iasconsole option.
This will upgrade the Admin Console from Version 4.0 to 4.2.

Edit the GX_ROOTDIR, ldap host, and password for "cn=Directory Manager" variables in the file update_gds.sh.
Also, edit the sp1.ldif to reflect your cluster and instance name; e.g. "iASCluster" and configuration name; e.g. "iasconfig" from Upgrade/Solaris/ and run the script to update the registry with some registry entries.

For more information on upgrading your Application Server installation, see the iPlanet Application Server Installation Guide V6.0 SP1.

Using the Silent Installation Feature

Silent installation allows you to install the Application Server on multiple Solaris machines without running the installation program more than once.

To use silent installation to install on multiple Solaris machines:

Run the setup -k command on the first machine.
Proceed with the installation program.
An install.inf file is generated in the <install directory>/setup directory. In addition, a log file,userinput.log, is generated in the <install directory>/ias directory. This file contains all input entered during the installation procedure.

Once you have completed the installation process, copy install.inf and userinput.log and add them to the /tmp directory of a second system.
Modify the copies of install.inf and userinput.log, making the following changes:

install.inf: change the values for the following keys by entering the machine name and IP address of the machine where you are silently installing the Application Server:

FullMachineName
ConfigDirectoryLdapURL
UserDirectoryLdapURL
ServerIdentifier
ServerIpAddres s

userinput.log: change the following keys by entering the machine name and IP address of the machine where you are silently installing the Application Server:

LDAP_Hostname
LDAP_ServerIdentifier
LocalHostName
NSRootDir
CLUSTERNAME
nsinst
LocalIPAddress

Enter the value of the LDAP_RootDNPwd by typing the password for the directory manager.
Run the following command on the second system to begin silent installation: setup -s -f <full path>/install.inf
This will perform an installation with exactly the same setup as the first system.

Modifying the iPlanet Application Server Java Runtime Environment Settings
The iPlanet Application Server 6.0 Service Pack 1 supports the integrated Java 2 runtime environment which is installed automatically during the installation process.
Setting the Java Runtime's CLASSPATH
Before deploying Java applications to the iPlanet Application Server that require third party helper classes and/or frameworks that is not assembled as part of the J2EE deployment modules, you must ensure that the classes are made available via the CLASSPATH used by the application server.

On Solaris:
Prior to starting the server, set the CLASSPATH ENVIRONMENT VARIABLE as required by your application.

On Window NT:
Java runtime related properties specific to the Application Server operation are under: My Computer \HKEY_LOCAL_MACHINE\SOFTWARE\iPlanet\Application Server\6.0\Java in the Windows NT registry.
Apply arguments to the Java runtime by setting the flags in the Registry variable JavaArgs. The CLASSPATH is preset to include all necessary classes and .jar files, including deployed applications.
Setting the Java Runtime's Native Library Path
Before using JNI and native libraries from your Java applications deployed to the application server, you must include the native libraries in the Java runtime environment of the server.
On Solaris:
set LD_LIBRARY_PATH
On Windows NT:
LibPath is set to point to all native dlls needed by the application server. J2EE applications that use native code dlls, can append to it, if necessary.
Disabling the Just in Time (JIT) Compiler

On Solaris:
-Djava.compiler=NONE
On Windows NT:
To turn off the Just In Time Compiler, (for example to get line numbers in Exception Stack traces during debugging), add -Xint to JavaArgs variable in registry.
-DJAVA.COMPILER=NONE
Running the Java Message Service (JMS)
For more information about using JMS with iPlanet Application Server, see Appendix A of the iPlanet Application Server Java Programmer's Guide.
Enabling JMS on Solaris:

Go to <ias install dir>/jms/bin
Run jmssetup by typing the command in a shelltool.
Run jmsreg
The JMS service should now be available.

Enabling JMS on Windows NT:

From the iPlanet console, shutdown the iPlanet Application Server.
Go to the jms/setup directory.
Execute the command jmssetup to enable connection pooling.
Set up the iAS CLASSPATH for the selected JMS provider.
You must provide the installation location of that provider.

IBM MQ JMS: setjmscp mq c:\mqseries. (Replace mqseries with name of the top directory in the MQ series installation.)
Sun JMQ: setjmscp jmq c:\jmq1.1\lib. (Replace c:\jmq1.1\lib with the location of the JMQ lib directory.)

Note: Do not include spaces in the setjmscp.bat pathnames.
The iPlanet Application Server CLASSPATH must be set up for the selected JMS provider. The values for the CLASSPATH and LibPath are copied to the file jmscp.txt in the setup directory.
To add these values to the settings in the iPlanet Application Server registry:

Use Notepad to view the file jmscp.txt.
Select the value for the CLASSPATH and copy it to the Windows clipboard by typing CTRL+C.>
Launch the regedit program.
Navigate to the key \Software\iPlanet\Application Server\6.0\Java\.
Select the value CLASSPATH and pull down the "Modify Value" entry in the Edit menu.
Use the End key to move the insertion point to the end of the entry.
Press CTRL+V to paste the jms classpath from the clipboard to the modify value dialog.
Select OK.
If a LibPath entry is given in jmscp.txt, select it and copy it to the clipboard.
In regedit, select the value LibPath and pull down the "Modify Value" entry in the Edit menu.
Use the End key to move the insertion point to the end of the entry.
Press CTRL+V to paste the jms LibPath entry to the dialog
Select OK.
Restart the iPlanet Application Server.

Java Message Service Sample Application
A new JMS sample application is available at <iASinstallpath>/ias/ias-samples/index.html. If you installed the web server plugin the location is http://<webserverhost>ias-samples/index.html.
This sample replaces the JMS samples delivered in the iPlanet Application Server 6.0 release. It includes instruction for both JMQ and MQSeries on NT.
Assembling and Registering J2EE Modules and Applications
Deployment of applications to iPlanet Application Server can be acheived using several different tools. The tool that is appropriate depends on whether you are deploying an application to a production operational environment or a development runtime envrironment.

Use EAR Level Tools for Production Operational Deployments
Due to classloading and security considerations of deploying J2EE modules in a standalone manner (i.e. independent of an EAR file), for operational deployments you are strongly encouraged to assemble J2EE applications into Enterprise Archive (EAR) files using the Deployment Tool GUI, and then deploy the applications in the form of EAR files. Either the Deployment Tool GUI or the deploycmd command line interface (CLI) can be used to deploy an EAR file.

User Either EAR Level or Module Level Tools for Development Deployments
For development deployments of application modules, when quick cycle time in support module development is of the utmost importance, use either J2EE module-level (WAR and EJB JAR) or EAR-level registration. In a development environment, deploying a standalone WAR module will enable you to gain the benefits of dynamic servlet class reloading without having to restart the application server's JVM (KJS) processes.
For module-level registration you may use either the Deployment Tool GUI or the deploycmd CLI. (For example, the IDE plug-ins for iPlanet the module-based registration tools).

Do Not Mix Use of EAR and Module Level Deployments
Mixing the use of EAR and module level deployments is not supported. You are likely to encounter class loading issues with your applications when mixing the use of EAR and module level registration.

Underlying Registration Command Line Interfaces
Although deploycmd is mainstream deployment command line interface, there are several commands that effectively perform the registration portion of deployment against a local application server instance. The commands j2eeappreg, webappreg, and ejbreg register (they do not transfer) EAR, WAR, and EJB JAR modules, respectively. Although j2eeappreg is supported for both operational and development deployments, webappreg and ejbreg are supported for development deployments only. In all cases, you are strongly encouraged to use deploycmd to register EAR, WAR, and EJB JAR files to iPlanet Application Server.
The new j2eeappreg unregistration feature (-remove) is available only via deploycmd. In a subsequent release, the unregistration, or "undeployment" feature, will be added to the Deployment Tool.
Sample Application Build Facility
The sample applications include instructions and build scripts demonstrating command line tools to:

Compile application sources
Build EJB stubs and skeletons
Reassemble EAR, WAR, and EJB JAR files
Register EARs to a local application server

These scripts demonstrate the raw structure of J2EE deployment descriptors and how command line tools can be used to rebuild J2EE applications. Feel free to leverage these command line build tools in your developer environments. However, although the command line build tool is a convenient way to rebuild J2EE applications, you will find the Deployment Tool is better suited for J2EE assembly, modification, and development tasks.

Known Issues and Limitations

Resolved Issues
Known Issues

Resolved Issues
The following issues have been resolved in the iPlanet Application Server 6.0 Service Pack 1 release.

Core Server

ID Summary

384401 Authentication mechanism no longer fails for multiple servlets.

386862 KIVAes.sh script now shuts down gracefully.

387913 NAS4.0 SP2, NAS Plugin no longer has problems with Custom Headers.

389033 No longer need to add default-pool-size to XML descriptor for servlets.

390701 Default value for stickiness of the servlet is no longer sticky.

392006 Context and security role reference descriptions are written to XML.

398585 Web server restart is no longer required.

398590 application.xml context root is now working.

399764 JSP include of non-JSP files no longer fails when I18N enabled.

400544 Authorization Servlet Stickiness: applications now work.

401078 Distributed servlet session updates are not lost (dsync-backed).

402264 iASAT now works properly if the locale of iAS and iASAT is different.

408701 Information missing in iAS migration docs.

419571 iAS can now host J2EE applications that are packaged as com.netscape or com.kivasoft.

430070 Cluster: Kill Primary, Backup kxs no longer crashes.

453650 com.netscape.server.nas.BaseLogic.setTemplate() now displays DataSet data in browser.

512409 JMS and Cluster Samples: HTML files are now accessible via web server docroot.

NONE The iWS CD includes NT, Solaris, and HP-UX. However iAS supports only NT and Solaris platforms.

iPlanet Lightweight CMP Deployment Tool

ID Summary

392549 Deployment Tool: able to define roles for manual deployment.

509101 When using registering EAR files, web content (JSPs, HTML, images, etc.) is no longer being extracted under a directory name based on the J2EE application name rather than based on the web application name. This issue was making it difficult to include multiple WAR modules in an EAR file and to address the web content under each WAR module in the appropriate manner.

512495 Verifier in Deployment Tool no longer fails when ejb-link is not in web.xml.

513815 Database column names now appear in iPlanet Lightweight CMP tab of Deployment Tool after opening the descriptor of an EJB. The column names exist in the CMP XML file, but they do not appear in the GUI.

Sample Applications

ID Summary

397618 Now you can add a new user to the Pet Store sample.

397620 The sign-in/sign-out status is now more reliable.

512533 Pet Store does not support IIS server.

512802 Bank Sample: Added Quotes Around Dynamically Generated URLS in HREFs.

515694 Container managed transactions are not fully supported when global transactions are not enabled.

NONE Pet Store: non-oracle RDBMS issues encountered when placing an order with PetStore. A "Server 500" error message appears.
Workaround: The OrderDAOclass relies on some database-specific classes for implementing the OrderEJB. In order to use the correct OrderDAO implementation class, the OrderDAO class checks for the name of the database in use by calling dbConnection.getMetaData().getDatabaseProductName(). Using jConnect 5.2, the string "Sybase SQL Server" is returned, but the OrderDAO code checks only for startsWith("Oracle"), equals("SQL Server"), and equals("DBMS:cloudscape"). So, to fix this problem add another check for startsWith("Sybase") and instantiate the existing implementation class OrderDAOSybase when startsWith("Sybase") is true.

Known Issues
The following issues have been addressed in this release and a workaround is provided.
Administration Tool

ID Summary

495501 Admintool: limitation configuring third party JDBC drivers.
Workaround: use kregedit to configure all third party JDBC drivers.

Core Server

ID Summary

445289 Three drivers is the maximum number of third party drivers that can be configured with the Application Server.
Workaround: If you wish to configure more than three (3) third party drivers, you can configure them by using the post-install configuration tools.

468309 Installer fails if server identifier is not set to the default.
Workaround: When installing the iPlanet Directory Server with the iPlanet Application Server, the Directory Server instance name should be left to the default setting "hostname."

481221 Unable to connect when using Rowset for 3rd party drivers.
Workaround: Looking up RowSet from JNDI lookup is not implemented. Construct a RowSet object directly and by setting the URL to make the underlying connection.

500941 Applications deployed with data models do not work on a remote host.
Workaround: Add ORACLE_HOME and TNS_ADMIN to the system variables and reboot the machine.

506541 Issues associated with using IIOP to access EJBs.
Workaround: To avoid these issues, use HTTP and XML to communicate between clients and EJBs. HTTP is used to interact with servlets and/or JSPs which in turn interface to EJBs.

509761, 512803 Web container: JSPs that dynamically generate HREFs and don't place quotes around the URLs result in URLs that are not rewritten.
Workaround: always use quotation marks around URLs.

510802 Text fields are too small.
Workaround: On Solaris 2.6 and NT, the text fields are of normal size. On Solaris 7 and 8 the text fields are too small, but when you resize the Admin Tool window, the fields become bigger and the data can be entered. This will be resolved in the next release.

511896 Packaging of nab25.jar with iPlanet Application Server 6.0 SP1.
Workaround: If you are migrating from NAS 2.1 and the iPlanet Application Builder to create your application, you will need to add the file nab25.jar located in the ias/lib/java/nab25.jar to the classpath of the iPlanet Applicaiton Server. If you do not perform this operation you will see NoClassDefFoundError exceptions indicating com/netscape/server/nas/BaseLogic class not found.

512452 Must set command line setting of host and port for RMI/IIOP clients.
Workaround: The following properties need to be passed to Java when running the Client:
-Dorg.omg.CORBA.ORBInitialHost=<CXS Host> -Dorg.omg.CORBA.ORBInitialPort=<CXS IIOP Port>
For example: java -Dorg.omg.CORBA.ORBInitialHost=pico -Dorg.omg.CORBA.ORBInitialPort=9010 com.netscape.tests.RC.unit.metadata.RemoteClient pico

516590 Namespace collisions in EJBs.
Workaround: Assemblers should use Java-oriented package names for the EJB name field of EJBs in order to avoid namespace collisions. For example, rather than using "BankService" use "com.iplanet.ias.bank.ejbs.BankService" or a similar name. Then, the entry for this bean in the Application Server Registry will be a qualified name and it is not likely to conflict with beans from other vendors or applications.

516628 Problems using the same filename for WAR and EJB JAR modules.
Workaround: The 6.0 SP1 release of the Application Server does not support using the same filename for WAR and EJB JAR modules.

516631 Naming collisions with EJB JAR and WAR module names.
Workaround: EJB JAR and WAR module names identified by the first portion of their filenames (without the .war and .jar) extensions must be unique when deploying to the Application Server. Use a Java package-like naming scheme for: module filenames, EAR filenames, and EJB names as found in the <ejb-name> portion of the ejb-jar.xml files. The use of this package-like naming scheme ensures that name collisions do not occur. The benefits of this naming practice apply not only to the iPlanet Application Server, but to other J2EE application servers as well.

516639 Uninstall on NT systems works best if performed as a two-step process.
Workaround: perform the uninstallation using the following steps:

Uninstall the Application Server 6.0 and the Administration services by making sure these are the only checked boxes in the uninstall Components window.
Note: a clean uninstall of the Application Server requires the Directory to be up and running. If it is not running, there is a timeout delay while the uninstall program tries to access the directory.

Run the uninstall program again (it won't be available from the Windows Program group, but will still exist on your drive) to remove the Directory Suite and Netscape Server Family Core Components.
Reboot your system and delete the Application Server install directory structure.

NONE Resource loading for Solaris UK.
Workaround: Avoid by setting all locales to LC_* vars=C.

NONE Uninstall takes approximately 40 minutes or more to uninstall.
Workaround: For NT systems, follow the uninstall steps provided in the above workaround. Solaris uninstallation has not been as problematic.

Database Support

ID Summary

369014 escapeSyntax is supported for Oracle database only in this release.

384721 Unable to get LONG type from Oracle stored procedure size on Solaris and NT.

387419 Duplicate row insertion throws exception on third party JDBC driver.
Workaround: On NT, using Sybase JConnect 5.2, do not insert duplicate rows.

402289
413008 JDBC getMetaData() is not supported.

412428 preparedStatement.setByte fails for Informix on Solaris.

412888 Text datatypes in prepared statements are not supported for Informix and Sybase.

421259 DB2 jdbcMultipleSP problem on Solaris.
Workaround: The stored procedure CaluInt2 returned '0' instead of '1' when called to INSERT using executeUpdate().

427569 On Informix getMetaData() may cause KJS to crash.

428609 DB2 jdbcSimpleCallStmt2.
Workaround: On Solaris, the stored procedure SPDate with getDate(2) returns an incorrect date value when using the native JDBC driver. This problem will be corrected in Service Pack 2.

428729 DB2 jdbcSimpleCallStmt3 problem.
Workaround: On Solaris, the stored procedure SPTimestamp with getTimestamp(2) returns an incorrect timestamp value when using the native JDBC driver. This problem will be corrected in Service Pack 2.

432809 RIGHT OUTER JOIN does not work for Informix.
Workaround: On Solaris, ther is no code to support this. This problem will be addressed in a later release.

441410 Oracle 8.1.6 database connection failure.
Workaround: On NT, when starting the iPlanet Application Server from services, the error "failed to create a data connection with any of specified drivers" is received. Check if a previous version of Oracle client was installed, and workaround by renaming that home directory.

463691 DB2 jdbcPrepLong.
Workaround: On both Solaris and NT setLong() calling executeQuery() returns an invalid value. This will be corrected in Service Pack 2.

487562 Data values not inserted in tables on Solaris.
Workaround: Inserting int/double/date values to a string column does not throw an error, and does not insert the values in the database. This feature will be resolved in a future release.

NONE Unregistration of a J2EE application EAR files does not seem to work.
Workaround: To unregister a J2EE Application EAR file(s), the user must supply the EAR file that was deployed to the ias/JAR/ directory when running J2eeappreg -remove. This EAR file should be representative of what was last deployed to the server instance.

NONE Using the callable statement getString() returns the correct string, but the wrong string length is displayed when using native driver.

Deployment Tool

ID Summary

457769 java.rmi.RemoteException:CORBA OBJ_ADAPTER changed during rich client functionality test on Solaris.
Workaround: To avoid this problem, do not write methods starting with an underscore.

486741 Stateful session bean failover implementation.
Workaround: The timer thread does NOT async state saves.

511901 Deployment tool: Need to document the third party datasource registration feature

512690 Deployment tool: If you do not want to insert the independent classes into a module, you can edit the classpath field in the Edit Preferences dialog to include jars/folders on which insertion elements have dependencies. Be aware that you must take full responsibility to ensure that during iAS runtime all classes required by the application are available.

512808 When deploying to multiple application server instances in the same cluster where a common directory server is shared to house the iPlanet Application Server Registry, you are likely to encounter registration errors due to concurrent deletes and additions occurring against the same areas of the Registry.
Workaround: Deploy the application to the application server instances in a sequential manner. A new feature will be added in the next version of the Deployment Tool to enable sequential deployment to application servers in the same cluster.

513266 The home directory set through Preference Dialog is lost.
Workaround: This happens when the user chooses a different directory while creating a new archive. This will be fixed in next release.

513618 Unable to edit context root when modifying an EAR file.
Workaround: Save and close the newly generated EAR file. Now reopen the EAR file and modify the context root(s).

513979 XXX-RmiCorba.jar is not created while deploying an EjbJar to Rich Clients.
Workaround: Create an EAR file and add the EjbJar to the EAR for generating the XXX-RmiCorba.jar required for Rich Client deployment. At least one primary key must be specified for the CMP Bean.

NONE Drag-n-drop is not implemented in the Component view.
Workaround: Use the File view to drag-n-drop.

NONE Context root appears in the WAR descriptor editor instead of EAR descriptor editor.
This will be moved to the EAR descriptor editor in the next release.

NONE Encountering a "class not found" exception.
Workaround: add the class in the user preferences. Also, you haven't set the dependency classes.

NONE When editing an EAR file, the context root for a WAR module appears in the WebApp descriptor.
Workaround: Modify the context root at the WAR level and save the EAR file.

J2EE

ID Summary

461449 convert2jsp11 utility puts duplicate information into an already converted JSP file on Solaris.
Workaround: To avoid this problem, search if the + init( ) function already exists in the JSP file.

404585 JSP result caching: positiveCachingWithOR.jsp does not work properly on Solaris.
Workaround: JSP caching with OR caching criteria is not working properly. Caching only happens when ?y=10 is specified at the URL. However, with ?x=24(checker), caching is not happening. This problem will be addressed in SP2.

iPlanet Lightweight CMP Deployment Tool

ID Summary

513914 Deployment Tool does not support specification of custom finders via the GUI. You must add custom finder information for CMP Entity Bean manually outside the Deployment Tool GUI.
Workaround: See J2EE Developer's Guide Product EJB example for details (ias/ias-samples/j2eeguide/docs/index.html). Workaround is based on expanding the EJB JAR file after assembling in Deployment Tool. Once the JAR is expanded, manually modify the CMP XML file by adding the custom finder information.

513918 Deployment Tool does not support reordering of CMP Entity Bean variables and database columns. The resulting CMP XML causes the CMP engine to insert incorrect data into the wrong database columns.
Workaround: See J2EE Developer's Guide Product EJB example for details (ias/ias-samples/j2eeguide/docs/index.html). After expanding EJB JAR file, modify the allFiles section in the CMP XML file to order the fields based on the order of the columns in the database.

Documentation Errata
In the Migration Guide, the section titled "C++ Applications and Extensions" suggests that legacy system extensions like Tuxedo and/or CICS will retain support for the NAS2.1 Universal Call Interface (UCI) programming model. This is incorrect, NAS2.1 UCI programing is NOT supported in iAS6.0 and will not be supported in future releases.
In the Migration Guide various sections on session sharing, the appName in NAS and the Scope value in the iAS Deployment tool are equivalent values. To get the session shared, the scope value needs to be set to the same value as appName in NAS.
The Java Programmer's Guide incorrectly identifies the commands jms_setup and jms_reg these should read jmssetup and jmsreg. They are located in the jms/bin directory of the iPlanet Application Server installation.
In Chapter 5 of the Java Programmer's Guide, the section on session bean failover, it incorrectly specifies that the timer thread does async state saves. The timer thread does NOT async state saves.

Reporting Problems
Online and telephone Technical support can be found at: http://iplanet.com/support/online/

For More Information
For all iPlanet Application Server documentation, including the Installation Guide, and updated release notes, refer to: http://docs.iplanet.com/docs/manuals/ias.html
Copyright � 2000 Sun Microsystems, Inc. Some preexisting portions copyright � 2000 Netscape Communications Corp. All rights reserved.

Desired Affect	Command
Graceful Shutdown of Engines (excluding the Admin Server)	`iascontrol stop`
Graceful Shut Down of All Engines and Stopping the Admin Server (kas)	`iascontrol stop` `iascontrol kill`
Stopping all iAS Processes via Forced Kill	`iascontrol kill`
Starting Engines and Admin Server (kas)	`iascontrol start`

Device	Requirement
Computer/Operating system	Sun UltraSPARC running Solaris 2.6 or Solaris 8 Windows NT 4.0 SP 5
Memory	Per CPU: 256 MB minimum; 512 MB recommended
Available disk space	Total disk space: 200 MB NT 400 MB Solaris 800 MB Solaris if installing both NetDynamics and iPlanet Application Server 6.0 CD-ROM drive
Other software	Support the following web servers: iPlanet Web Server 4.1 Enterprise Edition Microsoft Internet Information Server 4.0 (NT only) One of the following web browsers: Netscape Communicator 4.5 or later Microsoft Internet Explorer 4.0 (NT only) or later Database connectivity software (see the following tables)

Database Client	Database Server
Oracle 8.1.6	Oracle 8.0.5, 8i (8.1.5 and 8.1.6)¹, 7.3.4
Sybase 11.1.1	Sybase 11.9.2, 12
DB2 5.2	DB2 5.2, 6.1
ODBC 3.51	Microsoft SQL Server 7
Informix 2.4	Informix Server 9.x

Driver	Platform
Oracle8i 8.1.6.0.1: Type 4	Solaris and NT
Oracle8i 8.1.6.0.1: Type 2	Solaris and NT
Merant (Intersolv) SequeLink Java Edition	All OS platforms supported above RDBMS platforms supported by SequeLink
Sybase jConnect for JDBC v5.0 Type 4 (with Oracle only)	Solaris and NT
DB2 v6.1	NT only
Access to MSFT SQL Server	Available from Merant

Patch ID	Patch Description
105490-07	Linker Patch
105568-14	Libthread Patch
105210-25	LibC Patch
106040-13	X Input & Output Method Patch
105633-30	OpenWindows 3.6: Xsun Patch
106409-01	Fixes the Chinese TrueType fonts
108091-01	SunOS 5.6: ssJDK1.2.1_03 fails with fatal error in ISO8859-01 Locales
105181-17	Kernel Update (socket close/hang)
105669-09	CDE 1.2: libDTSvc Patch (dtmail)
105284-31	Motif 1.2.7: Runtime library patch

ID	Summary
384401	Authentication mechanism no longer fails for multiple servlets.
386862	KIVAes.sh script now shuts down gracefully.
387913	NAS4.0 SP2, NAS Plugin no longer has problems with Custom Headers.
389033	No longer need to add default-pool-size to XML descriptor for servlets.
390701	Default value for stickiness of the servlet is no longer sticky.
392006	Context and security role reference descriptions are written to XML.
398585	Web server restart is no longer required.
398590	application.xml context root is now working.
399764	JSP include of non-JSP files no longer fails when I18N enabled.
400544	Authorization Servlet Stickiness: applications now work.
401078	Distributed servlet session updates are not lost (dsync-backed).
402264	iASAT now works properly if the locale of iAS and iASAT is different.
408701	Information missing in iAS migration docs.
419571	iAS can now host J2EE applications that are packaged as com.netscape or com.kivasoft.
430070	Cluster: Kill Primary, Backup kxs no longer crashes.
453650	com.netscape.server.nas.BaseLogic.setTemplate() now displays DataSet data in browser.
512409	JMS and Cluster Samples: HTML files are now accessible via web server docroot.
NONE	The iWS CD includes NT, Solaris, and HP-UX. However iAS supports only NT and Solaris platforms.

ID	Summary
392549	Deployment Tool: able to define roles for manual deployment.
509101	When using registering EAR files, web content (JSPs, HTML, images, etc.) is no longer being extracted under a directory name based on the J2EE application name rather than based on the web application name. This issue was making it difficult to include multiple WAR modules in an EAR file and to address the web content under each WAR module in the appropriate manner.
512495	Verifier in Deployment Tool no longer fails when ejb-link is not in web.xml.
513815	Database column names now appear in iPlanet Lightweight CMP tab of Deployment Tool after opening the descriptor of an EJB. The column names exist in the CMP XML file, but they do not appear in the GUI.

ID	Summary
397618	Now you can add a new user to the Pet Store sample.
397620	The sign-in/sign-out status is now more reliable.
512533	Pet Store does not support IIS server.
512802	Bank Sample: Added Quotes Around Dynamically Generated URLS in HREFs.
515694	Container managed transactions are not fully supported when global transactions are not enabled.
NONE	Pet Store: non-oracle RDBMS issues encountered when placing an order with PetStore. A "Server 500" error message appears. Workaround: The `OrderDAO`class relies on some database-specific classes for implementing the `OrderEJB`. In order to use the correct `OrderDAO` implementation class, the `OrderDAO` class checks for the name of the database in use by calling `dbConnection.getMetaData().getDatabaseProductName()`. Using jConnect 5.2, the string "Sybase SQL Server" is returned, but the `OrderDAO` code checks only for startsWith("Oracle"), equals("SQL Server"), and equals("DBMS:cloudscape"). So, to fix this problem add another check for startsWith("Sybase") and instantiate the existing implementation class `OrderDAOSybase` when startsWith("Sybase") is true.

ID	Summary
445289	Three drivers is the maximum number of third party drivers that can be configured with the Application Server. Workaround: If you wish to configure more than three (3) third party drivers, you can configure them by using the post-install configuration tools.
468309	Installer fails if server identifier is not set to the default. Workaround: When installing the iPlanet Directory Server with the iPlanet Application Server, the Directory Server instance name should be left to the default setting "hostname."
481221	Unable to connect when using `Rowset` for 3rd party drivers. Workaround: Looking up `RowSet` from JNDI lookup is not implemented. Construct a `RowSet` object directly and by setting the URL to make the underlying connection.
500941	Applications deployed with data models do not work on a remote host. Workaround: Add ORACLE_HOME and TNS_ADMIN to the system variables and reboot the machine.
506541	Issues associated with using IIOP to access EJBs. Workaround: To avoid these issues, use HTTP and XML to communicate between clients and EJBs. HTTP is used to interact with servlets and/or JSPs which in turn interface to EJBs.
509761, 512803	Web container: JSPs that dynamically generate HREFs and don't place quotes around the URLs result in URLs that are not rewritten. Workaround: always use quotation marks around URLs.
510802	Text fields are too small. Workaround: On Solaris 2.6 and NT, the text fields are of normal size. On Solaris 7 and 8 the text fields are too small, but when you resize the Admin Tool window, the fields become bigger and the data can be entered. This will be resolved in the next release.
511896	Packaging of nab25.jar with iPlanet Application Server 6.0 SP1. Workaround: If you are migrating from NAS 2.1 and the iPlanet Application Builder to create your application, you will need to add the file `nab25.jar` located in the `ias/lib/java/nab25.jar` to the classpath of the iPlanet Applicaiton Server. If you do not perform this operation you will see `NoClassDefFoundError` exceptions indicating `com/netscape/server/nas/BaseLogic` class not found.
512452	Must set command line setting of host and port for RMI/IIOP clients. Workaround: The following properties need to be passed to Java when running the Client: `-Dorg.omg.CORBA.ORBInitialHost=<CXS Host> -Dorg.omg.CORBA.ORBInitialPort=<CXS IIOP Port>` For example: `java -Dorg.omg.CORBA.ORBInitialHost=pico -Dorg.omg.CORBA.ORBInitialPort=9010 com.netscape.tests.RC.unit.metadata.RemoteClient pico`
516590	Namespace collisions in EJBs. Workaround: Assemblers should use Java-oriented package names for the EJB name field of EJBs in order to avoid namespace collisions. For example, rather than using "BankService" use "com.iplanet.ias.bank.ejbs.BankService" or a similar name. Then, the entry for this bean in the Application Server Registry will be a qualified name and it is not likely to conflict with beans from other vendors or applications.
516628	Problems using the same filename for WAR and EJB JAR modules. Workaround: The 6.0 SP1 release of the Application Server does not support using the same filename for WAR and EJB JAR modules.
516631	Naming collisions with EJB JAR and WAR module names. Workaround: EJB JAR and WAR module names identified by the first portion of their filenames (without the .war and .jar) extensions must be unique when deploying to the Application Server. Use a Java package-like naming scheme for: module filenames, EAR filenames, and EJB names as found in the <ejb-name> portion of the `ejb-jar.xml` files. The use of this package-like naming scheme ensures that name collisions do not occur. The benefits of this naming practice apply not only to the iPlanet Application Server, but to other J2EE application servers as well.
516639	Uninstall on NT systems works best if performed as a two-step process. Workaround: perform the uninstallation using the following steps: Uninstall the Application Server 6.0 and the Administration services by making sure these are the only checked boxes in the uninstall Components window. Note: a clean uninstall of the Application Server requires the Directory to be up and running. If it is not running, there is a timeout delay while the uninstall program tries to access the directory. Run the uninstall program again (it won't be available from the Windows Program group, but will still exist on your drive) to remove the Directory Suite and Netscape Server Family Core Components. Reboot your system and delete the Application Server install directory structure.
NONE	Resource loading for Solaris UK. Workaround: Avoid by setting all locales to `LC_* vars=C`.
NONE	Uninstall takes approximately 40 minutes or more to uninstall. Workaround: For NT systems, follow the uninstall steps provided in the above workaround. Solaris uninstallation has not been as problematic.

ID	Summary
369014	`escapeSyntax` is supported for Oracle database only in this release.
384721	Unable to get LONG type from Oracle stored procedure size on Solaris and NT.
387419	Duplicate row insertion throws exception on third party JDBC driver. Workaround: On NT, using Sybase JConnect 5.2, do not insert duplicate rows.
402289 413008	JDBC `getMetaData()` is not supported.
412428	`preparedStatement.setByte` fails for Informix on Solaris.
412888	Text datatypes in prepared statements are not supported for Informix and Sybase.
421259	DB2 `jdbcMultipleSP` problem on Solaris. Workaround: The stored procedure `CaluInt2` returned '0' instead of '1' when called to INSERT using `executeUpdate().`
427569	On Informix `getMetaData()` may cause KJS to crash.
428609	DB2 `jdbcSimpleCallStmt2`. Workaround: On Solaris, the stored procedure `SPDate` with `getDate(2)` returns an incorrect date value when using the native JDBC driver. This problem will be corrected in Service Pack 2.
428729	DB2 `jdbcSimpleCallStmt3` problem. Workaround: On Solaris, the stored procedure `SPTimestamp` with `getTimestamp(2)` returns an incorrect timestamp value when using the native JDBC driver. This problem will be corrected in Service Pack 2.
432809	RIGHT OUTER JOIN does not work for Informix. Workaround: On Solaris, ther is no code to support this. This problem will be addressed in a later release.
441410	Oracle 8.1.6 database connection failure. Workaround: On NT, when starting the iPlanet Application Server from services, the error "failed to create a data connection with any of specified drivers" is received. Check if a previous version of Oracle client was installed, and workaround by renaming that home directory.
463691	DB2 `jdbcPrepLong`. Workaround: On both Solaris and NT `setLong()` calling `executeQuery()` returns an invalid value. This will be corrected in Service Pack 2.
487562	Data values not inserted in tables on Solaris. Workaround: Inserting `int/double/date` values to a string column does not throw an error, and does not insert the values in the database. This feature will be resolved in a future release.
NONE	Unregistration of a J2EE application EAR files does not seem to work. Workaround: To unregister a J2EE Application EAR file(s), the user must supply the EAR file that was deployed to the `ias/JAR/` directory when running `J2eeappreg -remove`. This EAR file should be representative of what was last deployed to the server instance.
NONE	Using the callable statement `getString()` returns the correct string, but the wrong string length is displayed when using native driver.

ID	Summary
457769	`java.rmi.RemoteException:CORBA OBJ_ADAPTER` changed during rich client functionality test on Solaris. Workaround: To avoid this problem, do not write methods starting with an underscore.
486741	Stateful session bean failover implementation. Workaround: The timer thread does NOT async state saves.
511901	Deployment tool: Need to document the third party datasource registration feature
512690	Deployment tool: If you do not want to insert the independent classes into a module, you can edit the classpath field in the Edit Preferences dialog to include jars/folders on which insertion elements have dependencies. Be aware that you must take full responsibility to ensure that during iAS runtime all classes required by the application are available.
512808	When deploying to multiple application server instances in the same cluster where a common directory server is shared to house the iPlanet Application Server Registry, you are likely to encounter registration errors due to concurrent deletes and additions occurring against the same areas of the Registry. Workaround: Deploy the application to the application server instances in a sequential manner. A new feature will be added in the next version of the Deployment Tool to enable sequential deployment to application servers in the same cluster.
513266	The home directory set through Preference Dialog is lost. Workaround: This happens when the user chooses a different directory while creating a new archive. This will be fixed in next release.
513618	Unable to edit context root when modifying an EAR file. Workaround: Save and close the newly generated EAR file. Now reopen the EAR file and modify the context root(s).
513979	`XXX-RmiCorba.jar` is not created while deploying an EjbJar to Rich Clients. Workaround: Create an EAR file and add the EjbJar to the EAR for generating the `XXX-RmiCorba.jar` required for Rich Client deployment. At least one primary key must be specified for the CMP Bean.
NONE	Drag-n-drop is not implemented in the Component view. Workaround: Use the File view to drag-n-drop.
NONE	Context root appears in the WAR descriptor editor instead of EAR descriptor editor. This will be moved to the EAR descriptor editor in the next release.
NONE	Encountering a "class not found" exception. Workaround: add the class in the user preferences. Also, you haven't set the dependency classes.
NONE	When editing an EAR file, the context root for a WAR module appears in the WebApp descriptor. Workaround: Modify the context root at the WAR level and save the EAR file.

ID	Summary
461449	`convert2jsp11` utility puts duplicate information into an already converted JSP file on Solaris. Workaround: To avoid this problem, search if the `+ init( )` function already exists in the JSP file.
404585	JSP result caching: `positiveCachingWithOR.jsp` does not work properly on Solaris. Workaround: JSP caching with OR caching criteria is not working properly. Caching only happens when ?y=10 is specified at the URL. However, with ?x=24(checker), caching is not happening. This problem will be addressed in SP2.

iPlanet Application Server

Release 6.0 Service Pack 1 Revision B

Release Notes

Updated October 9, 2000

Contents

What's New

Deployment Tool

Launching Deployment Tool

Using the Command Line Interface

Third Party JDBC Driver Support

Unregistering Applications

Control Command Script Enhancements (Solaris Only)

iascontrol Commands:

Installer Enhancements

Enhanced Sample Applications

Multiple Instances of iPlanet Application Server

Third Party CMP Integration

System Requirements

Hardware and Software Requirements

Database Requirements

New Third Party JDBC Driver Support1

Patch Requirements

Application Compatibility

Getting Started

Upgrading the iPlanet Application Server 6.0

Using the Silent Installation Feature

Modifying the iPlanet Application Server Java Runtime Environment Settings

Setting the Java Runtime's CLASSPATH

On Solaris:

On Window NT:

Setting the Java Runtime's Native Library Path

On Solaris:

On Windows NT:

Disabling the Just in Time (JIT) Compiler

On Solaris:

On Windows NT:

Running the Java Message Service (JMS)

Enabling JMS on Solaris:

Enabling JMS on Windows NT:

Java Message Service Sample Application

Assembling and Registering J2EE Modules and Applications

Use EAR Level Tools for Production Operational Deployments

User Either EAR Level or Module Level Tools for Development Deployments

Do Not Mix Use of EAR and Module Level Deployments

Underlying Registration Command Line Interfaces

Sample Application Build Facility

Known Issues and Limitations

Resolved Issues

Core Server

iPlanet Lightweight CMP Deployment Tool

Sample Applications

Known Issues

Administration Tool

Core Server

Database Support

Deployment Tool

J2EE

iPlanet Lightweight CMP Deployment Tool

Documentation Errata

Reporting Problems

For More Information

`iascontrol` Commands:

New Third Party JDBC Driver Support¹