NSAPI and WAI

Configuring the Web Server to Run Non-threadsafe NSAPI Applications: 
iPlanet Web Server 4.0 can be run in Multiprocess Mode, but also has the advantage of being multi-threaded. However, multi-threading is not an advantage for NSAPI applications that are not threadsafe. So, it is important to only make 1 thread at a time available to an NSAPI application that is not threadsafe. To do this, the web server includes configuration parameters that allow users to set aside a pool of threads for a particular application. If this pool of threads is set to 1, only 1 thread at a time will be made available to the application and it should not encounter any stability issues as a result. To achieve some level of performance for this application, however, the server must be running in multiprocess mode. Multiprocess mode enables concurrency of processing for the application, and will enable the server to attain a higher level of performance.

iPlanet Web Server, Enterprise Edition 4.0 no longer contains Visibroker (an object request broker (ORB)).  This means that you have to buy and install an ORB before you can use WAI. Also, if you want to write your own object implementations using Common Object Request Broker Architecture(CORBA)/Internet Inter-ORB Protocol (IIOP) you must buy and install an appropriate ORB.

Compiling WAI applications:   You need to compile or recompile WAI applications from previous releases of iPlanet Web Server, Enterprise Edition 4.0 with Version 6.0 of Visual C++ for Windows NT 4.0, SparcWorks 4.2 for Solaris, and aCC on HP-UX.

Plugin development compiler versions [HP-UX]:   The proper compiler versions to use for plugin development are:

/opt/aCC/bin/aCC:

HP aC++ B3910B A.03.13
HP aC++ B3910B X.03.11.10 Language Support Library

/usr/bin/cc:

LINT A.11.01.00 CXREF A.11.01.00
HP92453-01 A.11.01.00 HP C Compiler
$ PATCH/11.00:PHCO_95167  Oct  1 1998 13:46:32 $

344157.   Addressing WAI Backward Compatibility: WAI applications built using older server versions will require some command line options to run under the new ORB (C++ and JDK1.1). Under Java 2, some code has to be changed and the application must be rebuilt.

355991.   Note that net_isalive() has been deprecated for iPlanet Web Server, Enterprise Edition 4.0. Now net_isalive() always returns 1 (TRUE), which indicates that the socket is alive. Developers should not call this function.

357561.   For most platforms (Solaris, Windows NT, and Compaq) iPlanet Web Server, Enterprise Edition 4.0 requires using JDK 1.2. However, the WAI ORB doesn't support this version, and instead requires an older version (1.1). So, you have to install the older version of the JDK, and when you start your WAI application from the command line, you need to reference that version of the JDK, using syntax like: old_jdk/bin/java WAIApp.java. The syntax is unchanged from Enterprise Server 3.6; the important thing to know is that you need a separate JDK to run these applications on some platforms.

364274 (AIX only).   iPlanet Web Server, Enterprise Edition 4.0 is built on AIX 4.2 which natively supports runtime-linking. Consequently, NSAPI plugins (which reference symbols in the ns-httpd main executable) must be built with the "-G" option which specifies that symbols must be resolved at runtime.

Previous versions of Netscape Enterprise Server, however, were built on AIX 4.1 which did not support native runtime-linking. Plugins were enabled to work by building iPlanet Web Server, Enterprise Edition 4.0 with specific additional software provided by IBM AIX development to Netscape. No special runtime-linking directives were required to build plugins. Because of this, plugins which have been built for previous versions of Enterprise on AIX will not work with iPlanet Web Server, Enterprise Edition 4.0 as they are. However, they can easily be relinked to work with iWS 4.0. We've provided a script to relink existing plugins. Only the existing plugin itself is required for the script; original source and .o files are not needed. More specific comments are in the script itself. Since all AIX versions from 4.2 onward do and will natively support runtime-linking, we do not anticipate this issue being a problem again for future iPlanet Web Server, Enterprise Edition 4.0 releases built on AIX.

Relink Script

Note that the relink script relink_36plugin to modify a plugin built for NES 3.X to work with iWS 4.X has also been added into directory server_root/plugins/nsapi/examples/. (See relink_36plugin script for usage.)

#!/bin/ksh
#
# script to modify a plugin built for NES3.X to work with iWS4.X
#
# usage: relink_plugin <plugin.so>
#
# Script will create <plugin.so>.new that will work with iWS4.X.
#
# If your <plugin.so> was built with a specific default LIBPATH, then
# you must modify the DEF_LIBPATH variable below. Run the command
# "dump -H <plugin.so>" and your existing default LIBPATH will be listed
# as the PATH information by INDEX 0 under the ***Import File Strings***
# section.


DEF_LIBPATH=/usr/lib/threads:/usr/ibmcxx/lib:/usr/lib:/lib


# If your <plugin.so> has dependencies on other shared objects, then you
# must modify the LIB variable below to include those dependencies
# (e.g.
# if you need symbols from shared objects libusra.so, libusrb.so, & libusrc.so;
# you would specify LIBS="-lusra -lusrb -lusrc")
# Run the command "dump -H <plugin.so>" to see if your <plugin.so> has
# any dependencies; they will be listed under the ***Import File Strings***
# section (Note: you don't have to specify system library dependencies
# such as libc.a, libc_r.a, etc.)


LIBS=


# Note: the following warnings may appear, but you can ignore them:
# ld: 0711-415 WARNING: Symbol __priority0x80000000 is already exported.
# ld: 0711-224 WARNING: Duplicate symbol: __priority0x80000000
# ld: 0711-224 WARNING: Duplicate symbol: .__priority0x80000000
# ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information.


# Note: If you are running with the AIX CSet++ 3.1.4 compiler instead of
# the CSet++ 3.6.4 compiler, then replace all references in this script
# to "ibmcxx" with "lpp/xlC".


/usr/bin/ld -bnso -r -o /tmp/obj.o $1
/usr/ibmcxx/bin/makeC++SharedLib_r -p 0 -G -blibpath:$DEF_LIBPATH $LIBS \
/tmp/obj.o -o $1.new


364553 (AIX-only).   Cannot start WAI on 4.0 instance on AIX platforms.
If WAI is enabled on a 4.0 server instance, the instance will not start and an error message is displayed.

When WAI is installed make sure that the you specify the path to the place where the orb is installed only and not orb/lib or orb/bin.

Online Help Documentation

• 361418.   No online documentation for "Manage Certificates" page.
  Clicking on the "Help" button under Manage Certificates results in the "Error - Help information for this topic was not found" error message. To view the online documentation for this topic, perform the following procedure:
  1. Display the online documentation.
  2. Go to "Appendix E Enterprise Server User Interface"
  3. Click "Server Manager" link.
  4. Click "The Manage Server Certificates Page" link.

• 363876.   The Search Confirmation Page Online Help:  The "Check Access Permissions on Collection Root before Doing a Search" section of the online help for the Search Confirmation Page should read as follows:

  "Checks access permission of a server user before performing a search on the collection chosen. If proper authorization is not entered, the requested search is not performed."

• 363879.   The Edit Access Page Online Help:   The "Programs" section of the "Edit Access Page" online help that is displayed when you select the Enterprise Administration Server "Restrict Access" option from the "Global Settings" tab, should display the following information:

  All Programs. Allows users or groups access to all the tabs in Enterprise Administration Server.

  Only the Following. Allows users or groups access to either specific tabs or specific pages. You can choose multiple tabs by pressing the Control key and then clicking the tabs.

  Update. Saves your entries.

  Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

  Help. Displays the online help.

Security

• Cross Web Site Scripting Vulnerability:
  It has been determined that the default response for HTTP error 404, "File not found" can be used as a mechanism for exploitation as described in the CERT© advisory CA-2000-02. iPlanet recommends that the configuration for any of the following webservers be modified to prevent such an attack:
  • Netscape Enterprise Server 2.x
  • Netscape Enterprise Server 3.x
  • Netscape Enterprise Server 4.0 (iPlanet Web Server Enterprise Edition 4.0)

  The server configuration should be modified to override the default response provided by the server with one you supply. The main difference is that the default response would include the value of the HTTP referrer header in its response to the client. This is not necessary and is the source of the vulnerability. Future versions of the web server will contain safeguards in the default response.

  To modify your server, you can use the Administration Server or modify the configuration directly. Each approach is outlined below:

  Using the Administration Server user interface
  Perform the following steps:

  1. Select a server instance to manage.
  2. Select Error Responses from the left panel
  3. Select Editing: The entire server
  4. For Error Code: Not Found, set "File:" to point at a static html file containing the proper response.

  Manually modifying the configuration
  Add the following line to the default object, substituting the absolute path to your error response file:

  Error fn="send-error" reason="Not Found" path="c:/netscape/server4/docs/errors/notfound.html"

  For additional information regarding this issue, see the:   CA-2000-02   CERT© Advisory.

• 380430.   SSL running on multiProcessor systems takes a performance hit without MaxProcs=#CPU.
  For optimal performance when running SSL on HP-UX, set MaxProcs to equal the number of processors on the server. MaxProcs may be set by manually editing the magnus.conf file.
• 383657.   The Administration screen function to allow additional cryptographic modules to work with the iPlanet Web Server does not function correctly. You can use the modutil program from the command line to perform this function. The modutil//bin/https/admin/bin/modutil. Typing modutil without arguments will display a help menu.

Simple Network Management Protocol (SNMP)

• 367391 (Compaq only).   SNMP outputs reversed IPAddress of system on Compaq platforms.
  If an SNMP client asks for the IPAddress of the server on Compaq, using the Netscape mib, instead of n1.n2.n3.n4, the user gets n4.n3.n2.n1. To obtain the correct information, ask for the IPAddress using the system mib.

Server-Side JavaScript (SSJS) / LiveWire

• Error return on registerCFunction:  The registerCFunction() function returns true if the C shared library is registered correctly. It can return false in two cases. One is if the application is just added and server has not been restarted, and user tries to invoke application which causes registerCFunction() to be called. This behavior occurs because the shared library has not been loaded. Shared libraries are loaded during server start. The second case where registerCFunction() can return false is if the shared library specified in the registerCFunction() call does not match the "external library" specified when adding that application in the appmgr.

  If the function name registered does not exist in the shared object, registerCFunction() returns true since it does not check to see if the function name exists in the shared object or not. However, if that function is invoked, an "undefined" is returned.

• Configuring the Maximum Number of Database Connections (Sybase only):  A new environment variable MAX_LW_SYBS_CONN has been added to let you configure this limit. By default, the limit is 100 and if you set the limit to be higher than 100, the web server will use the higher number instead. This "higher" number should fall between 100 and 50000 to be a valid number. This will provide the extension that users require.

  To configure the maximum number of database connections, perform the following steps:

  1. Modify the start script to set the environment variable (for example, MAX_LW_SYBS_CONN=1000; export MAX_LW_SYBS_CONN ).
  2. Restart you web server.
• Default Version of JavaScript:   The default version of JavaScript supported in this release is JavaScript 1.4.  Netscape recommends porting your applications to 1.4.  However, JavaScript 1.2 is supported for backward compatibility only, and is deprecated. In order to use JavaScript 1.2, you must compile your application using jsac -a 1.2.
• SSJS Database Object is Deprecated:   The SSJS database object is deprecated and you should use the DbPool object instead.

• Recompiling Pre-4.0 SSJS Applications:   SSJS applications from previous versions of iPlanet Web Server, Enterprise Edition 4.0, need to be recompiled with the new JSAC (edition 24.13 or higher) in order to be run on iPlanet Web Server, Enterprise Edition 4.0.
• Behavior of SSJS functions write() and flush() has changed in 4.0:  In Enterprise Server 3.6, if the user clicks the "Stop" button in the browser while the application is executing the write() or flush() function, or prior to the application executing the write() or flush() function, execution of that request is aborted. In iPlanet Web Server, Enterprise Edition 4.0 SP2, if the user clicks the "Stop" button in the browser while the application is executing the write() or flush() function, or prior to the application executing the write() or flush() function, execution of that request is not aborted. In addition, write() and flush() now returns TRUE if the function succeeded in sending data to the browser and FALSE if it failed.
• Using DB2 on HP-UX 11.0:   If you use  DB2 on HP-UX 11.0 you need to install additional OS patches and to modify certain HP-UX system parameters. This information can be obtained on the IBM web site in the release notes and in Chapter 22 of the manual Quick Beginnings for UNIX.
• Regular Expression Qualifier Operator:   If you use the qualifier operator to specify a single value, as in:

  /a{2}/

  which should match two "a" characters; for example: /a{2}/("baaab") should return "aa". However, this expression actually returns "aaa".
  The work-around is to specify this value as:

  /aa/

  In addition, note that /\11/ should match the tab character, but does not. The work-around is to use /\011/ instead.

• Informix transactions and cursors cannot span multiple pages:  If an application contains transactions and/or cursors that span several pages, you may see the error message, "1802 - Connection name in use." The transaction may be in an unknown state, and the server may have to be restarted to clear the error.
• Using DB2 Data types  To use DB2 data types BLOB, CLOB, or DBLOB, you need the following statement in the db2cli.ini file, which is located in your db2 client installation directory:

  [<database name>]
  longdatacompat=1

• Close cursors, result sets, and stored procedure objects:   In this release of iPlanet Web Server, Enterprise Edition 4.0 (unlike pre 3.x versions), you must explicitly close cursors, result sets, and stored procedure objects. You should also explicitly release connections and disconnect from databases when done.
• 42484.   You cannot connect to any databases right after a web server installation. Stop the server, set all necessary environment variables, and restart the server from the command line.
• 43695.   Connecting to an Informix MODE_ANSI database, using insertRow() or updateRow() via a cursor that has varchar or char columns gives you Informix error -766, "String must be null terminated." (This is Informix bug #68872.) You can avoid this problem by using the execute() method instead.
• 43714.   SQL statements that use the execute() method to modify a table do not work properly after opening a non-updatable cursor in MS SQL Server. To work around this problem, open an updatable cursor instead.
• 45155.   When connected to Sybase, using updateRow() in a cursor to update an image bigger than 26K may not work.
• 48546.   If the IN parameter for a DB2 stored procedure is expecting an integer type, the DB2 stored procedure should define the incoming variable as double, so as to ensure accurate processing of the integer value. When a user updates a data type column with a JavaScript object, DB2 takes only the date portion of the JavaScript object and issues a warning stating that the data is truncated.
• 48886.   If you stop an application while it is trying to get a connection from DbPool() (that is, when it is in the timeout period), the web server may crash. You can avoid this problem by letting the connection timeout normally.
• 51326.   When connecting to Informix, the Informix Server may crash when using updateRow() or deleteRow() via a cursor to modify a column that has a BLOB. (This is Informix bug #59162.) To work around this problem, surround the cursor with beginTransaction() and commitTransaction().
• 64327.   For MS SQLServer and DB2, you cannot display large BLOBS. (The limit for .gif files is 70 - 75 K; the limit for .jpg files is 60 K.)
• 65668.   You need to use the "/Null/" directive to insert a null into a MS SQL Server stored procedure. If you pass null, a blank is inserted.
• 68834.   Server-side JavaScript does not support passing BLOB datatypes to DB2 stored procedures.
• 69391.   Updating a char or varchar column greater than 256 characters through a cursor could crash the Informix server, and you may see Informix error, "-22582" and "-1803" in majorErrorCode().
• 74813.   If you are installing iPlanet Web Server, Enterprise Edition on the same machine as the Informix server (a local installation), you must install both the Informix client and the Informix server. Furthermore, you must install the I-Connect client first, and then install the Informix server. If you are installing iPlanet Web Server, Enterprise Edition and the Informix server on separate machines (a remote installation), install only the Informix client on the machine where you installed iPlanet Web Server, Enterprise Edition.
• 82538.   When using the write() or debug() methods with cursors, identify the cursor with the cursor column name (cursor.colName) instead of the index. For example, use cursor.fld1 instead of cursor[0].

• 87084, 94314.   When you are using an Oracle database, you may encounter a problem with the SQLTable() method with large integers. This is because Oracle stores integers internally as floats, so you can't pass large integers whose capacity exceeds 32 bits. To avoid this truncation (or overflow) or error messages, use float datatypes for large numbers, instead of integers.
• 98272.   To use DB2 under several clients at a time, you must add the following statement to the db2cli.ini file, which is located in your DB2 client installation directory:

  [common]
  disablemultithread=0

• 113281.   DbPool.connection() returns a valid object even if it does not get a connection from the DbPool before it times out.
• 315321.   When you attempt to grab a cursor for update in Sybase, the cursor does not grab an update lock on the page. The only locks obtained are a shared intent lock for the select and an exclusive page lock for the update. Because there is no update lock granted, it is possible for another connection to obtain an exclusive lock on the same page and cause a deadlock situation.
• 344652.   Usage of the JSAC compiler has changed in iWS 4.0:
• On Windows NT platforms, if you move the jsac compiler from the <server-root>/bin/https/bin directory, then in order for jsac to find its dependent dlls, you will have to add <server_root>/bin/https/bin to your PATH.
• On Unix platforms, you will have to add <server_root>/bin/https/lib to your LD_LIBRARY_PATH or SHLIB_PATH or LIBPATH (depending on platform) in order for the dependent shared objects be found. You can accomplish this by running the start script of the server with the -shell option, that is, start -shell. This creates a shell with the appropriate environment from which you can then run jsac.
• 344698 (Solaris only).   To establish LiveWire database connectivity on Solaris to an Informix database, you need to additionally set your LD_LIBRARY_PATH environment variable to $INFORMIXDIR/lib:$INFORMIXDIR/lib/esql.
• 346158.   You need to recompile any applications you compiled with a previous version of the Enterprise Server (3.x or Web Server 4.0).  The new compiler version is 24.13.
• 346246. [HP-UX]   You need to  add the database library paths to the SHLIB_PATH environment variable. For example:

 
SHLIB_PATH=/export2/hpux/oracle8.0.5/lib:/opt/IBMdb2/V5.0/lib:/export2/hpux/informix-csdk2.1 /lib/esql:/export2/hpux/informix-csdk2.1/lib:/export2/hpux/sybase11.1.1/lib;export
SHLIB_PATH
• 348674.   The definition of the getYear() function of Date has changed in JavaScript 1.4. In older versions of JavaScript it used to return the year minus 1900 for years in the 20th century and the year otherwise. In JavaScript 1.4 it always returns the year minus 1900. In JavaScript 1.4, the getFullYear() method  always returns the year as a four-digit number.  Use getFullYear() to make sure a year is compliant with years after 2000.

Since the definition of getYear() was confusing and prone to errors, it is deprecated and using  getFullYear() is encouraged. For people requiring the old semantics of getYear(), you  have to compile your application in the JavaScript 1.2 compatibility mode, that is, jsac -a 1.2...., though this is deprecated.
• 349802.   08 and 09 are no longer valid decimal constants in JavaScript 1.4 (since numbers starting with 0 are considered octal).   As a convenience for backward compatibility, you can use these numbers in JavaScript 1.4.  They are considered to be decimal 8 and 9 respectively.  However, the compiler generates a warning when you use them.  These constants occur most often in Date constructors. The other two digit numbers used in dates (01, 02, etc.) were already working like these constants.
• 349828.   If LiveConnect applications use netscape.javascript.JSObject, then the server is unstable due to a bug in this class. Without using JSObject, the stability of LiveConnect is much improved. To improve the stability further and eliminate server crashes, turn the JIT off. In addition, refer to the following platform-specific information:
  • On Windows NT and Solaris, edit config/jvm12.conf and adding the line (or uncommenting this line if it is already there): java.compiler=NONE
  • On HP-UX, edit config/jvm.conf, changing jvm.hpuxJIT to 0, and removing the # comment character from the line. The default version of JavaScript supported in this release is JavaScript 1.4. Netscape recommends porting your applications to 1.4. However, note that JavaScript 1.2 is supported for backward compatibility only, and is deprecated. In order to use JavaScript 1.2, you must compile your application using jsac -a 1.2.
• 351407.   Oracle Stored Procedure ResultSet cannot return more than 98 columns. This problem is fixed in iPlanet Web Server, Enterprise Edition 4.0. Now, you can have a Oracle Stored Procedure returning a resultset of up to 510 columns. If you must use more than 510 columns, you can try the following workarounds:
1. Workaround #1: Execute the stored procedure and return the SQL string as an out parameter. Then create a cursor using the SQL string to execute query and fetch result.
2. Workaround #2: Use regular cursor to fetch the rows if you want to pass a table with so many columns (recommended method) OR break the table into smaller size (in terms of columns).
• 351433.   Servlets/LiveWire may stop working after you disable and then re-enable them via the user interface. The user interface may place the servlets/LiveWire NameTrans directives after the document-root NameTrans directive in obj.conf, which prevents them from being executed. The workaround is to manually edit the obj.conf file, and to reorder the servlet and/or LiveWire NameTrans directives to be the first in the list.
• 352074.   The JavaScript compiler no longer allows "=" as the comparison (equals) operator. You must use "==" as the equals operator, or you will receive an error message when you compile.
• 359738.   If you have SSJS and the Application Manager turned on and you setup a configuration style and ACL to protect your application, depending on the order of some lines in obj.conf, the ACL may or may not be executed. To prevent this behavior, define the ACLs for configuration styles prior to your SSJS definitions in the obj.conf file.
• 364066.   ORA8 can't execute SELECT FOR UPDATE. When you use cursors and try to connect to an Oracle 8 Server, iPlanet Web Server, Enterprise Edition 4.0 may display the error: "Can't execute 'SELECT FOR UPDATE' for Oracle 8 sever with ORA-01002 fetch out of sequence." If this error occurs, you need to add explicit transactions around the update code. For example: database.beginTransaction() and database.commitTransaction(). Note that iPlanet Web Server, Enterprise Edition 4.0 does not generate this error if you are connecting to an Oracle 7 database.
• 364224 (AIX-only).   libdtcp.a could not be loaded when connecting to DB2.
  Unable to connect to DB2 Database when having the environment variables set to connect to Informix. Therefore the user cannot connect to Informix, Oracle, and DB2 databases, or Informix and DB2 databases with the same server at the same time.

  Suggested work-around is as follows:

  For AIX, in order to have database connectivity make sure that your LIBPATH in the start script looks something like the following example:

  LIBPATH=${LD_LIBRARY_PATH}:${LIBPATH}:${ORACLE_HOME}/lib:${INFORMIXDIR}/lib:${IN
  FORMIXDIR}/lib/esql:${SYBASE}/lib:${DB2PATH}/lib:/usr/threads/lib:/usr/ibmcxx/li
  b:/usr/lib:/lib; export LIBPATH

  Note that it is important to include the Database client libraries prior to including the AIX libraries.

Web Publishing and Search

• 322138.   If you edit an html file in Netscape Composer, the result is a lock on the file (key symbol).
  Such files need to be published from the Composer in order to not appear as a locked file. Currently if the Composer plugin is installed and a file is opened in the Composer and no changes are made, the file will be locked. Publishing the file will clear the lock on the file.
• 349914.   There may be intermittent problems with Netscape Communicator starting and stopping the WebPub applet on UNIX platforms.
• 360457.   Property sheets in the Navigator/Communicator web publishing system (for specific platforms) no longer support the Created: field. In addition, iPlanet Web Server, Enterprise Edition 4.0 cannot guarantee the correctness of the CM_CDATE variable.
• 361905.   PDF collections cannot be created from the Enterprise Administration Server New Collection screen on HP 11.0. Though you won't see any error message, the document contents will not be indexed.

---

Platform-Specific Information

This section describes platform-specific known problems and work-arounds for the following platforms:

• Windows NT Platforms
• Compaq Platforms
• Unix Platforms
• HP Platforms
• AIX Platforms

Windows NT Platforms

• Using ns-httpd Process with Windows NT Network Shared Resources:   Since the ns-httpd process runs as a Windows NT process, there are no file permissions to access and it will fail. This is a Windows NT Service restriction.

  The work-around is to change the service owner to a different user who has access permissions to Windows NT network shared resources.

• 344652.   Usage of the jsac compiler has changed in iWS 4.0:
  On Windows NT platforms, if you move the jsac compiler from the <server-root>/bin/https/bin directory, then in order for jsac to find its dependent dlls, you will have to add <server_root>/bin/https/bin to your PATH.

  On Unix platforms, you will have to add <server_root>/bin/https/lib to your LD_LIBRARY_PATH or SHLIB_PATH or LIBPATH (depending on platform) in order that the dependent shared objects be found. You can accomplish this by running the start script of the server with the -shell option, that is, start -shell. This option creates a shell with the appropriate environment from which you can then run JSAC.

• 349828.   If LiveConnect applications use netscape.javascript.JSObject, then the server is unstable due to a bug in this class. Without using JSObject, the stability of LiveConnect is much improved. To improve the stability further and eliminate server crashes, turn the JIT off. In addition, refer to the following platform-specific information:
  • On Windows NT and Solaris, edit config/jvm12.conf and adding the line (or uncommenting this line if it is already there): java.compiler=NONE
  • On HP-UX, edit config/jvm.conf, changing jvm.hpuxJIT to 0, and removing the # comment character from the line. The default version of JavaScript supported in this release is JavaScript 1.4. Netscape recommends porting your applications to 1.4. However, note that JavaScript 1.2 is supported for backward compatibility only, and is deprecated. In order to use JavaScript 1.2, you must compile your application using jsac -a 1.2.
• 358429.   iPlanet Web Server, Enterprise Edition 4.0 will unpack onto the drive designated by the TEMP environment variable. Make sure there is enough space on the device pointed to by TEMP before starting the installation.)
• 360361.   Resize does not always work on Unix Netscape Navigator or Internet Explorer 4.0 on Windows NT platforms.
  When resizing the browser screen for the iPlanet Web Server, Enterprise Edition 4.0, the redraw does not always add the continuation arrow for the additional tabs. The placement of the Apply button may be off the screen as well. Note that this behavior occurs more frequently while using either Unix Netscape Navigator (4.51) or Internet Explorer 4.0 on Windows NT platforms.
• 362306. (Windows NT only)  Directory Server 4.1 and iPlanet Web Server, Enterprise Edition 4.0 can be installed on the same Windows NT host machine. If during installation you are asked which version of libraries to install, always select those which have the most recent release dates. If you need to uninstall either product, you must first make a copy of the uninstall program (uninst.exe) since it will be removed during the uninstall process. Also, you must uninstall iPlanet Web Server, Enterprise Edition 4.0 before you uninstall Directory Server 4.1.

  To uninstall iPlanet Web Server, Enterprise Edition 4.0 and Directory Server 4.0, perform the following steps:

  1. Copy uninst.exe to another file, for example, uninst_slapd.exe.
  2. Use uninst.exe to uninstall iPlanet Web Server, Enterprise Edition 4.0.
  3. Rename uninst_slapd.exe to uninst.exe.
  4. Use uninst.exe to uninstall Directory Server 4.1.
• 362248.   Creating .htaccess files on Windows NT.
  When creating .htaccess files on Windows NT, make sure that you press the Enter key at the end of the last line in the file. This "hard return" adds a line terminator to the end of the last line, and prevents an error message.

Compaq Platforms

• 363682 (Compaq and AIX only).   iPlanet Web Server, Enterprise Edition 4.0 requires additional variables in order to connect to DBs.
  In order to connect to the Databases on this 4.0 release it is necessary to point to the database client libraries on the LD_LIBRARY_PATH and LIBPATH environment variables.

  For Compaq platforms:

  LD_LIBRARY_PATH=$ORACLE_HOME/lib:$SYBASE/lib:$INFORMIXDIR/lib:
  $INFORMIXDIR/lib/e sql:$SERVER_ROOT/bin/https/lib

• 367391 (Compaq only).   SNMP outputs reversed IPAddress of system on Compaq platforms.
  If an SNMP client asks for the IPAddress of the server on Compaq, using the Netscape mib, instead of n1.n2.n3.n4, the user gets n4.n3.n2.n1. To obtain the correct information, ask for the IPAddress using the system mib.
• 367654 (Compaq only).   fsize not working for virtual or real files when sizefmt=bytes When sizefmt="bytes" in an shtml file, the fsize command returns a null response for either virtual or real files. Use sizefmt="abbrev" instead. It returns file size in K versus bytes.

Unix Platforms

• Do not use the Express Installation option if you have previously installed an AnswerBook Server (Solaris 8 only):  If you are running Solaris 8 and have installed an AnswerBook server, do not install the iPlanet Web Server 4.0 via the Express Install option. Select the Typical Install option, instead.

• File permissions during installation:
  During installation, unpacking of the .tar file causes the permissions of the destination directory to be modified so that applications can no longer write files into it. To avoid this problem, you should download to a directory where the permissions of the directory can be modified. If you wish to use the /tmp directory for installation, use a subdirectory under /tmp, for example, /tmp/nes40install.
• Bug in the Digital Unix 4.0d kernel which causes the kernel to crash:  There is a bug in the Digital Unix 4.0d kernel which causes the kernel to crash under some stressed conditions with file cache in the Web Server. A future OS patch kit will correct this problem. Meanwhile, to avoid this problem, add the following entry in the /etc/sysconfigtab file and reboot the system:
  

  vm:

  vm-map-index-enabled=0

• 330884 (Unix-only).   ACLs are attached to directories or files by name.
  When a file or directory can be accessed using more than one name, as when symbolic links are used on Unix, ACLs that were applied to the alternate path to the file or directory may not be applied properly, potentially allowing access to files you want to restrict. To avoid this problem, dissallow symbolic and hard links by choosing Server Preferences | Symbolic Links and dissallowing them.

• 344652.   Usage of the jsac compiler has changed in iWS 4.0:
  On Unix platforms, you will have to add <server_root>/bin/https/lib to your LD_LIBRARY_PATH or SHLIB_PATH or LIBPATH (depending on platform) in order for the dependent shared objects be found. You can accomplish this by running the start script of the server with the -shell option, that is, start -shell. This creates a shell with the appropriate environment from which you can then run jsac.
• 344698.   To establish LiveWire database connectivity on Solaris to an Informix database, you need to additionally set your LD_LIBRARY_PATH environment variable to $INFORMIXDIR/lib:$INFORMIXDIR/lib/esql.
• 346227.   The default setting for HPUX for jvm.disableThreadRecycling in jvm.conf should not be changed. Doing so has been shown to cause the JVM to crash when running simple servlets.
• 349457.   On error exit, X-term window fails to echo typed commands.
  During installation, an error exit will cause an X-term window to respond to typed commands, but it will not echo the commands to the display. A "reset" fixes the problem.
• 349914.   There may be intermittent problems with Netscape Communicator starting and stopping the WebPub applet on UNIX platforms.

HP-Only Platforms

• Using DB2 on HP-UX 11.0:   If you use  DB2 on HP-UX 11.0 you need to install additional OS patches and to modify certain HP-UX system parameters. This information can be obtained on the IBM web site in the release notes and in Chapter 22 of the manual Quick Beginnings for UNIX.
• Compiles using the Java Native Interface (HP-UX):  Any compiles using the  Java Native Interface (JNI) require the following options:
for aCC  -DNATIVE  -D_POSIX_C_SOURCE=199506L -D_HPUX +u4 +Z -ext
for cc   -DNATIVE  -D_POSIX_C_SOURCE=199506L -D_HPUX +u4 +Z -Ae

 Refer to the JVM/JNI documentation on HP for details.

In addition, any plugins for HP-UX must also use these options when compiled. Note that the +u4 option affects boundary alignment, which may impact 64-bit data access performance.

• Plugin development compiler versions (HP-UX):   The proper compiler versions to use for plugin development are as follows:

/opt/aCC/bin/aCC:

HP aC++ B3910B A.03.13
HP aC++ B3910B X.03.11.10 Language Support Library

/usr/bin/cc:

LINT A.11.01.00 CXREF A.11.01.00
HP92453-01 A.11.01.00 HP C Compiler
$ PATCH/11.00:PHCO_95167  Oct  1 1998 13:46:32 $

• 346246. (HP-UX)   You need to  add the database library paths to the SHLIB_PATH environment variable. For example:

 
SHLIB_PATH=/export2/hpux/oracle8.0.5/lib:/opt/IBMdb2/V5.0/lib:/export2/hpux/informix-csdk2.1 /lib/esql:/export2/hpux/informix-csdk2.1/lib:/export2/hpux/sybase11.1.1/lib;export
SHLIB_PATH
• 362462 (HP-UX).   During migration from Enterprise Server 3.6 to iPlanet Web Server, Enterprise Edition 4.0, choosing to export local users to an LDIF file fails on HP platforms. To successfully migrate local users to an LDIF file on iPlanet Web Server, Enterprise Edition 4.0, export the user database to an LDIF file through the Enterprise Server 3.6 admininstration server interface (using the Export option available via the "Users and Groups" tab).

  In addition, you can follow the same steps to add the base DN field to the user information by using the ldif2ldap script included with Directory Server.

• 380430 (HP-UX).   SSL running on multiProcessor systems takes a performance hit without MaxProcs=#CPU.
  For optimal performance when running SSL on HP-UX, set MaxProcs to equal the number of processors on the server. MaxProcs may be set by manually editing the magnus.conf file.

AIX-Only Platforms

• Recommended JDK Version.   We recommend that you use JDK 1.1.6_10 for iPlanet Web Server 4.0 SP4 for AIX.

• 363186.  If you have set up the environmental variable LIBPATH on AIX with /usr/lib/threads in front of it and then database libraries, the server will crash. The IBM-standard libraries should always appear last in the resulting LIBPATH. To prevent this problem, do not add any of the following paths to the LIBPATH environmental variable:

  /usr/lib/threads:/usr/ibmcxx/lib:/usr/lib:/lib

  iPlanet Web Server, Enterprise Edition 4.0 automatically adds them to the LIBPATH environmental variable.
• 363682 (AIX and Compaq only).   iPlanet Web Server, Enterprise Edition 4.0 requires additional variables in order to connect to DBs.
  In order to connect to the Databases on this 4.0 release it is necessary to point to the database client libraries on the LD_LIBRARY_PATH and LIBPATH environment variables.

  For AIX platforms:

  LIBPATH=$ORACLE_HOME/lib:$SYBASE/lib:$INFORMIXDIR/lib:$INFORMIXDIR/lib/esql:$DB2 PATH/lib:$SERVER_ROOT/bin/https/lib

• 364064 (AIX and IRIX).   AIX Unable to connect to Informix due to a trust issue.
  If you encounter difficulties connecting from an IRIX or AIX server to an INFORMIX database, follow these steps:
  1. Since this is a 'trust' issue, enlist each machine's name in other machines /etc/hosts.equiv file.
  2. On some O/S, the sqlhosts file must reside on local machine not on NFS-mounted directory.
  3. If still doesn't work, in the sqlhosts file, replace the hostname with the IP address and service name with port number. For example:

     ifmx_online onsoctcp 203.12.52.104 2055

• 364224.   libdtcp.a could not be loaded when connecting to DB2.
  Unable to connect to DB2 Database when having the environment variables set to connect to Informix. Therefore the user cannot connect to Informix, Oracle, and DB2 databases, or Informix and DB2 databases with the same server at the same time.

  Suggested work-around is as follows:

  For AIX, in order to have database connectivity make sure that your LIBPATH in the start script looks something like the following example:

  LIBPATH=${LD_LIBRARY_PATH}:${LIBPATH}:${ORACLE_HOME}/lib:${INFORMIXDIR}/lib:${IN
  FORMIXDIR}/lib/esql:${SYBASE}/lib:${DB2PATH}/lib:/usr/threads/lib:/usr/ibmcxx/li
  b:/usr/lib:/lib; export LIBPATH

  Note that it is important to include the Database client libraries prior to including the AIX libraries.

• 364274 (AIX only).   iPlanet Web Server, Enterprise Edition 4.0 is built on AIX 4.2 which natively supports runtime-linking. Consequently, NSAPI plugins (which reference symbols in the ns-httpd main executable) must be built with the "-G" option which specifies that symbols must be resolved at runtime.

  Previous versions of Netscape Enterprise Server, however, were built on AIX 4.1 which did not support native runtime-linking. Plugins were enabled to work by building iPlanet Web Server, Enterprise Edition 4.0 with specific additional software provided by IBM AIX development to Netscape. No special runtime-linking directives were required to build plugins. Because of this, plugins which have been built for previous versions of Enterprise on AIX will not work with iPlanet Web Server, Enterprise Edition 4.0 as they are. However, they can easily be relinked to work with iWS 4.0. We've provided a script to relink existing plugins. Only the existing plugin itself is required for the script; original source and .o files are not needed. More specific comments are in the script itself. Since all AIX versions from 4.2 onward do and will natively support runtime-linking, we do not anticipate this issue being a problem again for future iPlanet Web Server, Enterprise Edition 4.0 releases built on AIX.

  The relink script relink_36plugin to modify a plugin built for NES3.X to work with iWS4.X has also been added into directory server_root/plugins/nsapi/examples/. (See relink_36plugin script for usage.)

• 364933 (AIX 4.3.2 only).   When installing ES40 on AIX 4.3.2, messages stop appearing after the user answers the question "Do you want to use your own JDK?". This problem is fixed by applying IBM patch U463922 to AIX 4.3.2.
• 366982.   Uninstall needs admin uid and password.
  On AIX when you uninstall using the uninstall program, you get the error message: "ERROR: please specify admin user id and password." If you see this you can still uninstall using the following command: ./uninstall -u <userid> -p <password> . You will still have to remove any additional files as before.

---

Internationalization Information

This section includes information regarding internationalization issues.

• 359636.   Display problem regarding double-byte chars in Bind DN text field.
  During the installation process, the "Bind DN" text field (in the "Using LDAP for User and Group Administration" window) should enable users to input Japanese text; however, iPlanet Web Server, Enterprise Edition 4.0 displays the actual text in an unreadable form. Use the Enterprise Administration Server UI Global Settings -> Configure Directory Service to correct this problem after installation.
• 359683.   If a new user is created with "display preferred language" set and data in "Pronunciation" fields are provided, these pronunciation fields data will not appear in the "Pronunciation" fields in Netscape Console LDAP server user interface despite selecting the preferred language; however, note that the pronunciation data entered in Enterprise Administration Server 4.0 can be used in Netscape Console LDAP server "Users and Groups" search.

  To view the pronunciation data entered for the user created by the Enterprise Administration Server user interface, use the "Manage Users" option from the Enterprise Administration Server "Users and Groups" tab.

• 359714.   The user edit text fields for international information differs between Enterprise Administration Server and Netscape Console. In Netscape Console, in addition to the untagged cn fields, there is a preferred language cn field which doesn't exist in the Enterprise Administration Server.
• 381384.   I18N in parameters.
  The web server incorrectly parses non-English characters passed as parameters to a servlet.

---

ValiCert Web Server Validator 2.5 for iPlanet Web Server, Enterprise Edition

The ValiCert Web Server Validator is an NSAPI plug-in that adds automatic certificate validation, including CRL checking, to the iPlanet Web Server, Enterprise Edition. The product plugs into the iPlanet Web Server, Enterprise Edition, enabling you to check the revocation status of digital certificates issued by all major CAs. This added capability helps to protect you against exposure to liability and fraud that can occur if a user's certificate is lost or stolen. Specific benefits of the ValiCert Web Server Validator for Netscape Enterprise Server include the following:

• Increased trust and security for web-based enterprise, extranet, and online retailing applications.
• Support for multiple certificate validation protocols, including certificate revocation lists (CRLs), online certificate status protocol (OCSP), and certificate revocation tree (CRT) methods.
• Complete CA interoperability, including focused integration with Netscape CMS, Baltimore, Entegrity, Entrust, GTE, Microsoft, Thawte, and VeriSign.
• Complete LDAP directory server interoperability, including focused integration with Netscape Directory Server 3.x/4.0
• Support for both local directory/validation servers and public validation services such as the ValiCert Global VA Service.
• Easy installation and configuration.

The ValiCert Web Server Validator has been fully tested with both the Netscape Certificate Management System (CMS) 4.1 and iPlanet Web Server, Enterprise Edition 4.0. It is available for download from the Netscape Enterprise Server 4.0 CD-ROM, under the directory labelled /valicert. For additional information about the Web Server Validator, and to download the latest version, please link to http://www.valicert.net/netscape.

If you have any questions, please contact ValiCert technical support at support@valicert.com.

---

LiveWire Database Client Versions

The following table lists the database vendor client libraries supported on each platform by iPlanet Web Server, Enterprise Edition 4.0:
 

Database / Platform	Windows NT 4.0 w/SP4	SOLARIS 2.6 / 2.7	HP-UX 11.0	Compaq Tru64 UNIX	AIX
Oracle	8.0.5	8.0.5	8.0.5	8.0.5	8.0.5
Informix	SDK 2.10 TC1 (ESQL 9.16)	SDK 2.10 (ESQL 9.16)	SDK 2.10 (ESQL 9.16)	SDK 2.10 (ESQL 9.16)	SDK 2.10 (ESQL 9.16)
Sybase	11.1.1	11.1.1	11.1.1	11.1.1	11.1.1
DB2	V5.2	V5.2	V5.2	No Support	V5.2
ODBC Manager 3.51 MCAD 2.0 SP2	MS SQL Server 6.5 (3.60 driver) SQL Anywhere 5.5 (5.00 driver) MS Access 7.0 (3.51.171300 Driver)	No Support	No Support	No Support	No Support

---

Corrections to Documentation

Please note the following changes to the iPlanet Web Server, Enterprise Edition 4.0 documentation:

• database object is deprecated and will not be supported.
  Beginning with iPlanet Web Server, 4.0, the database object is deprecated and is no longer supported. Please ignore all references to the database object in the iPlanet Web Server documentation.

• Sun Solaris Patches
  the sun solaris patch information in the printed version of the iplanet web server Installation and Migration Guide has been updated. For the current information, see Sun Solaris Patch Information, in this document.

• Netscape Console Support
  Netscape Console is not supported in iPlanet Web Server, Enterprise Edition 4.0. The description for "Administrating and Managing Enterprise Servers" in Chapter 1, "Introduction to Enterprise Server" (on page 35-36), in the iPlanet Web Server Administrator's Guide should read as follows:

  "You can manage your Enterprise Server(s) via the following interfaces:
  

  • Enterprise Administration Server
  • Server Manager"

  Note that the final paragraph in this section should be deleted.

  In addition, delete the section titled "Netscape Console" (on page 50-51) of the Administrator's Guide.

• Error in "Cache-init" in Chapter 10, Configuring the Server for Performance", in the iPlanet Web Server Administrator's Guide:
  The section that describes the cache-init utility (on page 251-253) of the Administrator's Guide should read as follows (changes are highlighted in bold text style):

  Parameters:
  

  cache-size	(optional) Specifies the size of the cache in bytes. Valid values for the number of elements in the cache are 32 to 32768; the default is 512. The cache-size value should be greater than the size of all the documents on your server. You should include any static files such as HTML, text, images, sounds, or any other unchanging data in the count. URLs that are dynamic (such as CGI or NSAPI routines) return different data, depending on who calls them, and should not be counted.
  mmap-max	(optional) Specifies the maximum amount of memory set aside for memory-mapped (mmap) files the server will keep open at any point. Acceptable values range from 512K to (512*1024)KB; the default is 10000KB (10MB). To get maximum speed, the cache keeps many mmap files open. To estimate the optimal value for mmap-max on your system, approximately compute the total number of bytes of "static" data on your system. For example, if you have 200 files that are 10K in size, then 2MB should be sufficient for mmax-map.
  disable	(optional) Specifies whether the file cache is disabled or not. If set to anything but "false" the cache is disabled. By default, the cache is enabled.
  PollInterval	(optional) How often the files in the file cache are checked for changes. The default is 5 seconds. In Web Server 4.0, this parameter is ignored -- use the MaxAge parameter in the nsfc.conf file instead.
  MaxNumberOfCachedFiles	(optional) Maximum number of entries in the accelerator cache. The default is 4096, minimum is 32, maximum is 32K.
  MaxNumberOfOpenCachedFiles	(optional) Maximum number of accel_file_cache entries with file_cache entries. Default is 512, minimum is 32, maximum is 32K.
  MaxCachedFileSize	(optional) Maximum size of a file that can be cached. Files larger than this size are not cached. The default is 525K. In Web Server 4.0, this parameter is ignored. Use the MediumFileSizeLimit parameter in nsfc.conf instead.
  MaxTotalCachedFileSize	(optional) Total size of all files in the cache. Default is 10K, minimum is 1K, maximum is 16M. In Web Server 4.0, this parameter is ignored on Unix. Use the MediumFileSpace parameter in nsfc.conf instead. In Web Server 4.0, this parameter is ignored because it no longers applies to the platform.
  MaxNumberOfOpenCachedFiles	(optional) Maximum number of cached files that can be open simultaneously.
  CacheHashSize	(optional) size of hash table for the file cache accelerator. Default is 8192, minimum is 32, max is 32K.
  NoOverflow	(optional) IRIX only.
  IsGlobal	(optional) IRIX only.

• Error in "The perfdump Utility" in Chapter 10, Configuring the Server for Performance", in the iPlanet Web Server Administrator's Guide:
  The section that describes how to install the perfdump utility (on page 231) of the Administrator's Guide should read as follows:

  1.Add the following object to your obj.conf file (after the default object):

  <Object ppath="/usr/netscape/server4/docs/.perf">
  Service fn="service-dump"
  </Object>

• Error in "File Cache Dynamic Control and Monitoring" in Chapter 10, Configuring the Server for Performance", in the iPlanet Web Server Administrator's Guide:
  The section that describes how to add an object to the obj.conf file to enable the NSFC file cache to be dynamically monitored and controlled (on page 250) of the Administrator's Guide should read as follows:

  Then add a new object definition:

  <Object ppath="{SR}/docs/nsfc">
  Service fn="service-nsfc-dump"
  </Object>

• Error in "Guidelines for Installing a PKCS#11 Module" in the iPlanet Web Server Administrator's Guide:
  In the Chapter 5, "Working with Server Security", the section that describes how to install a PKCS#11 module (page 131) of the Administrator's Guide should read as follows:

  "To tell the server to start with that server certificate instead, you must edit magnus.conf and add the following line anywhere in the file:

  CERTDefaultNickname $TOKENNAME:Server-Cert

  
  

• Tuning the File Cache
  The file cache tuning documentation as described in Chapter 10, "Configuring the Server for Performance," of the iPlanet Web Server Administrator's Guide has been updated. In order to tune the file cache, you must create a file called nsfc.conf and add the parameter information to it. For current information see the iPlanet Web Server 4.0 Performance Tuning, Sizing, and Scaling Guide.

• FlushInterval
  The description for FlushInterval in section "File Cache in Enterprise Server 4.0" (on page 248), in the iPlanet Web Server Administrator's Guide should read as follows:

  "The interval (in seconds) at which a reaper thread looks for cache entries that are older than MaxAge and deletes them."

• Line length limit for .nsconfig files
  The description for .nsconfig in section "Writing .nsconfig Files," in Chapter 7, "Configuring Server Preferences," in the Administrator's Guide should read as follows:

  "Note that lines are limited to a maximum of 1024 characters."

• Configuring Remote Servlet Debugging
  In the Programmer's Guide for Servlets online documentation for how to configure remote servlet debugging, the instructions include the following required settings:
  

  jvm.enableDebug=1
  java.compiler=DISABLED

  The documentation should read as follows:
  

  jvm.enableDebug=1
  java.compiler=NONE

  In addition, for Java 1.2 on some platforms you may be required to specify the bootclasspath. For example, for Solaris platforms, you set it as:

  jvm.option=-Xbootclasspath/a:/usr/java/lib/tools.jar

  (Assuming that Java 1.2 is in /usr/java.)

• Error in "CGI to NSAPI Conversion" in the iPlanet Web Server NSAPI Programmer's Guide:
  In the Chapter 4, "Creating Custom SAFs", the section that describes how to convert a CGI into a SAF using NSAPI, of the NSAPI Programmer's Guide incorrectly lists the NSAPI version for CONTENT_LENGTH and CONTENT_TYPE. The correct NSAPI conversion is:

  CONTENT_LENGTH pblock_findval("content-length", rq->headers);
  CONTENT_TYPE pblock_findval("content-type", rq->headers);

• CGIWaitPid
  The description for CGIWaitPid in "Appendix B, Variables in magnus.conf," in the NSAPI Programmer's Guide for Enterprise Server 4.0 should read as follows:

  "For UNIX platforms, when CGIWaitPid is set to on, the action for SIGCHLD signal will be the system default action for the signal. If a NSAPI plugin fork/execs a child process, it should call waitpid with its child process pid when CGIWaitPid is enabled to avoid leaving "defunct" processes when its child process terminates. When CGIWaitPid is enabled, the SHTML engine will wait explicitly on its exec cmd child processes. Note that this directive has no effect on CGI."

• CGIExpirationTimeout
  In the NSAPI Programmer's Guide for Enterprise Server 4.0 online documentation for CGIExpirationTimeout, the description should read as follows:

  "This directive specifies the maximum time in seconds that CGI processes are allowed to run before being killed."

  Note that init-cgi timeout does not work on Windows NT platforms, only Unix, so you must use CGIExpirationTimeout.

• Thread Pools
  In the NSAPI Programmer's Guide for Enterprise Server 4.0, the description of "Init Stage" in Chapter 3, "Predefined SAFS for Each Stage in the Request Handling Process," should read as follows:

  "On Unix platforms, each Init directive has an optional LateInit parameter. If it is set to "yes" or is not provided, the function is executed by the child process after it is forked from the parent. If it is set to "no", the function is executed by the parent process before the fork. Any activities that must be performed as the user root (such as writing to a root-owned file) must be done before the fork. Any activities involving the creation of threads must be performed after the fork, with the exception of thread-pool-init, which requires the optional EarlyInit parameter to used and set to "yes.""

• Closing Database Cursors and Connections (see the Server-Side JavaScript Guide): 
  When doing a database transaction using cursors, stored procedures and result sets, you must close these object explicitly in your application. Also, database connections (represent by connection objects) must be released back to the database connection pool (represented by a DbPool object) so it is made available to other requests/users. The closing and releasing of these database related objects can be done within a request or in the clean up code. Having orphan database cursors, stored procedures, result sets and connections may result into unpredictable server behaviors such as hanging and crashing.

• Error in "Calling Stored Procedures" in Chapter 9, "Working with a Database", in the iPlanet Web Server Server-Side JavaScript Guide:
  The section "Working with Result Sets" includes incorrect code examples used to generate stored procedures in DB2 and Oracle databases. The correct code examples are provided here:

  The correct SQL code to create a DB2 stored procedure is as follows:

  create proc getcusts as
  begin
  select id, name, city from custinfo where id < 200
  end
  

  The correct SQL code to create an Oracle stored procedure is as follows:

  create or replace package orapack as
  type custcurtype is ref cursor return custinfo%rowtype;
  end orapack;
  

  create or replace procedure custresultset ( custcursor OUT orapack.custcurtype)
  AS
  begin
  open custcursor for select id, name, city from custinfo where id < 200;
  end;
  

• Server-parsed HTML tags: shtml_init and shtml-send
  The description for these server-parsed HTML tags in "Chapter 3. Server-Parsed HTML Tags," in the Programmer's Guide for Enterprise Server 4.0 should read as follows:

  "When you activate parsing, you need to be sure that the following directives are added to your obj.conf file (note that native threads are turned off):

    Init funcs="shtml_init,shtml_send" shlib="H:/es40tip/WINNT4.0_DBG.OBJ/bin/https/bin/Shtml.dll"
   NativeThread="no" fn="load-modules"

  Note that you must set NativeThread=no for Enterprise 4.0 servers. In addition, these functions now originate from Shtml.dll, (or libShtml.so on Unix) which is located in /bin/https/bin for Windows NT, and /bin/https/lib for Unix."

---

How to Report Problems

See the iPlanet Technical Support site at http://www.iplanet.com/support

---

Where to Go for More Information

For iPlanet Web Server, Enterprise Edition 4.0 installation instructions, see the Installation and Migration Guide.

For iPlanet Web Server, Enterprise Edition 4.0 administrator documentation, see the online helpthat accompanies the product. The Administrator's Guide and related documents are also posted at the location http://developer.iplanet.com/docs/manuals/enterprise.html.

If you can't find the information you need, please contact iPlanet technical support.

---

© Copyright 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © Netscape Communications Corp. All rights reserved.