Migrating Nsapi Applications; Migrating Java Servlets - Netscape ENTREPRISE SERVER 6.1 - INSTALLATION AND MIGRATION GUIDE Installation And Migration Manual

Migrating NSAPI Applications

Most NSAPI programs you used with iPlanet Web Server 4.x will work in
Enterprise Server 6.1 without being recompiled. Some undocumented data
structures have been moved out of
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
, which is shipped with the build for informational purposes only.
nsapi_pvt.h
Custom NSAPI plug-ins are not automatically copied to the new server directory.
If you have custom plug-ins, make sure you copy your plug-ins to the upgraded
path as shown in the magnus.conf of the new server.
For more information on these data structures and the new accessor functions, see
the Netscape Enterprise Server NSAPI Programmer's Guide.

Migrating Java Servlets

After you've migrated your server, Java servlets that ran in iPlanet Web Server 4.x
should run in Enterprise Server 6.1 without being recompiled. The migration
leaves iPlanet Web Server 4.x servlets in their original directory. The migrated
servlets run in compatibility mode, which may make them a little slower than other
Enterprise Server 6.1 servlets.
Also, if your iPlanet Web Server 4.x 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.
Although iPlanet Web Server 4.x servlets and JavaServer Pages™ run properly
without modification on Enterprise Server 6.1, application developers should
rewrite these as web applications to take advantage of new features.
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 changed from the previous version. If you want to update the old
files to the new settings, refer to the .default files. You can also refer to
the .default files in the future if you want to revert to the Enterprise
6.1
Server
nsapi.h
default settings.
and are no longer public. Going
Chapter 4 Migrating Your Enterprise Server 61