User`s guide

Migrating from Enterprise Server 3.6
74 Installation and Migration Guide
Migrating Server-Side JavaScript Applications
iPlanet Web Server 4.1 supports JavaScript 1.4. For information about the
changes between JavaScript 1.2 and 1.4, see the “New Features” section in the
document Core JavaScript Reference v1.4 at:
http://developer.iplanet.com/docs/manuals/javascript.html
You must recompile and reregister server-side JavaScript applications before
running them in 4.1. The migration will not pick up the entries from your old
jsa.conf automatically. Remember also that Server-Side JavaScript is turned
off by default. You must turn it on again in your migrated server.
Migrating NSAPI Applications
Most NSAPI programs you used with Enterprise Server 3.6 will work in iPlanet
Web Server 4.1 without being recompiled.Some undocumented data structures
have been moved out of nsapi.h and are no longer public. Going forward, if
your plugins use any of these data structures, you should re-write them to use
accessor functions. The data structures that are now private are defined in
nsapi_pvt.h, which is shipped with the build for informational purposes
only.
For more information on these data structures and the new accessor functions,
see the Programmer’s Guide to iPlanet Web Server 4.1.
Migrating Java Servlets
After you’ve migrated your server, Java servlets that ran in Enterprise Server 3.6
should run in 4.1 without being recompiled. The migration leaves 3.6 servlets in
their original directory. The migrated servlets run in compatibility mode, which
may make them a little slower than other 4.1 servlets.
Also, if your 3.6 servlet referenced any additional files, you need to add the
path to these files to your JVM classpath. To update the classpath, use the
Configure JVM Attributes page, which you can find in the Server Manager on
the Servlets tab.
Note When you install the Java subcomponent, the configuration files that are
installed include a set of files that end in .default (for example,
rules.properties.default). These files contain the default values for the
Java configuration files. During migration, the Java configuration files are not