Access and Error Logs

The access and error server log files records the activity of the Server. During migration, new access logs are created. Error logs from the 4.1server-instance/logs directory is copied to the server-instance/logs in Sun Java System Web Server 6.1.

Configuration Files

Certain directives found in the iPlanet Web Server 4.1 magnus.conf file are now located in the Sun Java System Web Server 6.1 server.xml file. During the migration process, these directives are automatically removed from the 6.1 server’s magnus.conf file and added to the server.xml file.

In addition, Init functions located in the iPlanet Web Server 4.1 obj.conf file are moved to the Sun Java System Web Server 6.1 magnus.conf file.

For a list of deprecated directives, see the Sun Java System Web Server 6.1 SP12 Administrator’s Configuration File Reference.

During migration, multi-line Init directives are compressed to single-line directives in the Sun Java System Web Server 6.1 magnus.conf file.

Java Server Pages

iPlanet Web Server 4.0 Java Server Pages (JSPs) were written in JSP 0.92. The iPlanet Web Server 4.1 and 6.0 JSPs are written in JSP 1.2. Version 0.92 is no longer supported in Sun Java System Web Server 6.1. JSPs must be rewritten according to the version 1.2 standard. In addition, Sun recommends that developers create JSPs as part of web applications. Style examples can be found in server_root/plugins/servlets/examples/web-apps.

JSPs written in JSP 1.2 that are part of a web application can reside in any directory that the server can serve from.

JSP 1.2 samples are in server_root/plugins/samples/servlets/jsp.10.

Java Servlets

Netscape Enterprise Server / iPlanet Web Server 4.0 and 4.1 supported the Java Servlet 2.1 specification. This specification did not include web applications. A deployment scheme was developed to make servlet deployment simpler. With the advent of Java Web Applications (.war files) and their deployment descriptors, it is no longer necessary to maintain a proprietary deployment system.

iPlanet Web Server 6.0 supported both types of deployment schemes, but the 4.x implementation referred to as legacy servlets was marked as deprecated. See Chapter 8: “Legacy Servlet and JSP Configuration” of the iPlanet Web Server, Enterprise Edition Programmer's Guide to Servlets.

Sun Java System Web Server 6.1 does not support Legacy Servlets. The legacy-style properties files for the server you want to migrate - servlet.properties, context.properties, and rules.properties - are removed during migration.

Because there is no one-to-one mapping for all of the features, legacy servlets cannot be migrated automatically.

For documentation and samples to help you migrate your 4.1 legacy-style servlets to the web applications structure, see the Sun Java System Web Server 6.1 SP12 Programmer’s Guide to Web Applications.

Cron Control

Cron file names have been changed in Sun Java System Web Server 6.1. The file ns-cron.conf is called schedulerd.conf in Sun Java System Web Server 6.1, and the file cron.conf is now called scheduler.conf. These are located in the https-admserv/config directory.

Cron settings from the previous version of your Web server are however not migrated to Sun Java System Web Server 6.1during migration. Copy the cron settings for the migrated instance to the cron files.

The certmap.conf File

The certificate mapping file, certmap.conf, is not migrated during the migration process. During migration you receive a message that you need to manually migrate existing entries in the certmap.conf of the server instance you want to migrate.

Simple Session Manager

Simple Session Manager and JDBC Session Manager are not supported by Sun Java System Web Server 6.1. For more details about session managers, see the Sun Java System Web Server 6.1 SP12 Programmer’s Guide to Web Applications.

If your iPlanet Web Server 4.1 web applications specified SimpleSessionManager, you should change the name of the class to IWSSessionManager. You then have the option of adding persistence. Persistence-type must be set to s1ws60. Other Init attributes such as timeOut and reapInterval are unchanged.

If your iPlanet Web Server 4.1 web application specified JDBCSessionManager, you should change the name of the class to IWSSessionManager and add the following attribute to the init-param element of the session manager: session-data-store=com.netscape.server.http.session.JdbcStore. Persistence-type must be set to s1ws60.

Other attributes such as provider and url remain unchanged.

The package name of the MMapSessionManager has been changed from com.netscape.server.http.session in the 4.1 version of the Web Server to com.iplanet.server.http.session in the 6.0 and 6.1versions.

Virtual Servers

In iPlanet Web Server 4.1, you could create multiple server instances using hardware and software virtual servers, but these instances were required to share the same configuration information. With Sun Java System Web Server 6.1, you can set up multiple classes of virtual servers. Each class has separate configuration information.

The settings for virtual servers are stored in the server.xml file, found in the server_root/server_ID/config directory. See the Sun Java System Web Server 6.1 SP12 Administrator’s Guide for more information on virtual servers.

Web Publishing

Sun Java System Web Server 6.1 does not support the iPlanet Web Server 4.1 Web Publishing feature. It provides a new feature called WebDAV that enables collaborative file sharing and authoring on the Web. See the Sun Java System Web Server 6.1 SP12 Administrator’s Guide for more information.

Search

Because the search engine used in iPlanet Web Server 4.1 has been replaced by a new search engine in Sun Java System Web Server 6.1, existing search collections and indexes are not migrated during the migration process. To use the Search functionality in Sun Java System Web Server 6.1, create and configure new search collections and indexes. For more information, see the Sun Java System Web Server 6.1 SP12 Administrator’s Guide.

Start and Stop Scripts

If you have made modifications to your start or stop scripts in your 4.1 server, those changes will not be carried forward by the migration program. This applies to the reconfig, restart, and rotate scripts as well.

Symbolic Links in Configuration Files (UNIX and Linux)

Symbolic or relative links in server configuration files might cause problems when upgrading. Ensure that server configuration files that contain absolute references to files under the server root always reference the path to the server root in the same way. These links should not transverse any symbolic links.

Server Side JavaScript (SSJS)/LiveWire

Data and settings are not migrated applications that use SSJS/Livewire.

See the Sun Java System Web Server 6.1 SP12 Programmer’s Guide to Web Applications for an appendix explaining how to convert SSJS applications to JSPs. In addition, you can find an example of a converted application in server_root/plugins/samples/servlets/jsp.10/hangman.