These release notes contain information about new features, known problems, and other information about iPlanet Web Server, FastTrack Edition 4.1.
These release notes contain the following sections:
iPlanet Web Server, FastTrack Edition 4.1 runs on these platforms:
For each patch, use the listed revision or a higher revision. For example,
if you need patch 111111-01, the later revision 111111-03 will also work.
To get Sun patches, see your Sun service provider. Public patches are
available from http://sunsolve.sun.com/pubpatch.
If you are using a JDK, you may need additional patches.
Solaris 2.6
The following patches are the recommended patches for users running
iPlanet Web Server, FastTrack Edition 4.1, on Solaris 2.6:
| Solaris | SPARC | SPARC/V9 |
|---|---|---|
| 2.6 | 105591-05 | n/a |
| 7 | 106327-04 | 106300-05 |
This section includes additional information for installing your iPlanet Web Server, FastTrack Edition 4.1.
For example, if you install the JRE Database component, the next time you run the installer the Java and Servlets subcomponents are shown as not installed.
General Java and Java Servlets NSAPI Security
Workaround: The iPlanet web servers on Windows NT don't directly support handling document directories on remote-mounted volumes, but this generally seems to work, as long as you are aware of some known issues with it.
UNC ("universal naming convention", such as \\servername\path\) paths are not supported. You must map a drive letter to the remote volume you want to use before your iPlanet web server can serve files from it. Here is how to set up a drive mapping for your iPlanet web server:
(1) Change the user that your iPlanet web server runs as from the system
account (the default) to some other NT user on your system who
has access to the network volume you want to use. Do this by
opening the "Services" control panel in Windows NT, selecting
the proper service for your web server (such as, "https-servername"
for Web Server), clicking the "Startup..." button, then selecting
the radio button by "This Account" and entering the username and
password. Then close the dialog and the "Services" control panel.
(2) Log out of Windows NT, then log in as the user you specified in
step 1. From a DOS window, run the following command:
net use X: \\servername\path\directoryname /persistent:yes
where X: is the drive letter you want to use (anything that's
not currently in use), and "\\servername\path\directoryname"
is the complete UNC path to the directory you want to mount as
that drive letter.
You can also set up this mapping from File Manager or Windows
Explorer as long as you check the "reconnect on login" checkbox
in the drive mapping dialog.
You can log out from that user's account after you set this up.
Now, if you set up a drive mapping for X:, you should be able to tell your iPlanet web server to use its primary document directory on X:\, for example.
This may not work in all situations. If it doesn't, try upgrading to the latest copy of the client networking software for your computer. In particular, we have seen this fail if you're using the Microsoft networking software to connect to a Novell Netware file server; installing Novell Netware client software instead seems to fix the problem. Using drives mounted by Windows Networking and PC-NFS seems to work fine.
As noted above, using network volumes isn't directly supported by the iPlanet web server, and this may not work reliably.
Add addCgiInitVars="yes" to your obj.conf file to get these variables subsequently passed to shtml-init. For example, if you add the following code to your obj.conf file:
Init fn="init-cgi" LateInit="yes" var1="xy" var2="ab"
Init fn="shtml_init" addCgiInitVars="yes"
Then any cmd executed from shtml thru use of the cmd directive will see var1="xy" and var2="ab" in its environment.
So, for example, if you start the web server from a terminal window, you should see the output there. Use standard Unix file redirection to pipe the standard output into a file (that is, modify your server-root/https-instance/start file.
Workaround: In the contexts.properties file, set the following property:
contexts.global.isModifiedCheckAggressive=true
Workaround: Replace nsj with the wrapper java script in the sdk_test.sh script as follows:
# ${NS_HTTPS_HOME}/bin/nsj \
# com.netscape.server.http.examples.tools.HttpGetTest \
# -H ${HOST} -p ${HTTP_PORT} -f /servlet/${servlet}.class
/usr/java_dev2/jre/sh/java -classpath tools/SDKTools.jar \
com.netscape.server.http.examples.tools.HttpGetTest \
-H ${HOST} -p ${HTTP_PORT} -f /servlet/${servlet}.class
REQ_NOACTION is returned if none of the URIs listed in the from parameter match the current URI. REQ_ABORTED is returned if the file specified by the virtual-index parameter is missing or if the current URI cannot be found. REQ_RESTART is returned if the current URI matches any one of the URIs mentioned in the from parameter or if there is no from parameter.
Parameters:
| Parameter | Description |
| virtual-index | The URI of the content generator that acts as an index for the URI the user enters. |
| from | An optional comma-separated list of URIs for which this virtual-index is applicable. If from is not specified, the virtual-index always applies. |
Workaround: Do not activate LDAP during installation or in the administration server interface. Instead, edit the server_root/userdb/dbswitch.conf file as follows for anonymous binding over SSL:
directory default ldaps://directory.netscape.com:636:/dc%3Dcom
Or edit the server_root/userdb/dbswitch.conf file as follows for anonymous binding not over SSL:
directory default ldap://directory.netscape.com:389:/dc%3Dcom
Workaround: Click "Save" and then click "Apply" buttons at the right top of the Administration Server.
Workaround: See the workaround description under General Known Problems.
Workaround: Click "Save" and then click "Apply" buttons at the right top of the Administration Server.
Workaround: Replace nsj with the wrapper java script in the sdk_test.sh script as follows:
# ${NS_HTTPS_HOME}/bin/nsj \
# com.netscape.server.http.examples.tools.HttpGetTest \
# -H ${HOST} -p ${HTTP_PORT} -f /servlet/${servlet}.class
/usr/java_dev2/jre/sh/java -classpath tools/SDKTools.jar \
com.netscape.server.http.examples.tools.HttpGetTest \
-H ${HOST} -p ${HTTP_PORT} -f /servlet/${servlet}.class
Workaround: The context.global.parameterEncoding property in the contexts.properties file allows you to avoid these problems. It has the following options:
| Option | Description |
| utf8 | Dumps the entire parameter into Unicode. |
| none | Dumps the 8-bit characters of the parameter into Unicode. |
| auto | Tries to figure out the proper encoding from the charset if it is available, otherwise it is the same as none (default, current behavior). |
To correct this problem, set context.global.parameterEncoding in contexts.properties to auto or none.
However, it should read as follows, all on one line:
Init fn=flex-rotate-init rotate-start=2400 rotate-intervals=60Every line in the obj.conf file begins with one of the following keywords:
If any line of any example begins with a different word in the manual, the line is wrapping in a way that it does not in the actual file. In some cases this is due to line length limitations imposed by the PDF and HTML formats of the manuals.
For iPlanet Web Server, FastTrack Edition 4.1 administrator documentation, see the online help that 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 in the documentation, please refer to the FastTrack technical resources listed on the: iPlanet Web Server download site.