Sun Java System Web Server 6.1 SP10 Installation and Migration Guide

Overview of Changes in Sun Java System Web Server 6.1

When you migrate information from web server 6.0 to 6.1, changes are made in the following areas, listed alphabetically:

Cgistub Directory

The migration process does not migrate the CGIstub directory. If you configured CGI settings for an instance on your previous server, you need to manually copy the CGIstub directory to the appropriate location after migrating to Sun Java System Web Server 6.1.

Command Line Scripts

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

The following table lists the command line scripts that are available in Sun Java System Web Server 6.1, and also, points you to further documentation sources for more information:

Command Line Script  

Description  

For more information, see:  

start, startsvr.bat

  • Starts a server instance.

  • Each server instance has its own start script

Sun Java System Web Server 6.1 Administrator’s Guide

stop, stopsvr.bat

  • Stops a server instance.

  • Each server instance has its own stop script

Sun Java System Web Server 6.1 Administrator’s Guide

restart

Restarts a server instance 

Sun Java System Web Server 6.1 Administrator’s Guide

reconfig

Dynamically reconfigures the server without restarting it. 

Sun Java System Web Server 6.1 Administrator’s Guide

rotate

Rotates logs. 

Sun Java System Web Server 6.1 Administrator’s Guide

HttpServerAdmin

Provides command line utilities for virtual server administration 

Sun Java System Web Server 6.1 Administrator’s Guide

Configuration Files

The following table provides a summary listing of the configuration files in Sun Java System Web Server 6.1. It describes the changes introduced in the current release, and points you to further documentation sources:

Configuration File  

Description  

For more information, see:  

ACL files:

  • generated-https-server-id.acl

  • genwork-https-server-id.acl

  • Location: install-dir/httpacl/

  • These provide access control lists to protect server resources

  • May reference databases defined in Configuration Files

  • File names are specified in Configuration Files

  • During migration, ACL files from the old server-root/httpacl directory are copied to the new server-root/httpacl directory with the new instance name.

  • Non-default ACL files listed in the <ACLFILE> element of the server.xml file and that are present in the old server-root/httpacl directory are copied to the new server-root/httpacl directory.

Access Control Programmer’s Guide

certmap.conf

  • Location: server_root/userdb/

  • Configures how a client certificate is mapped to an LDAP entry

  • Not migrated. 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.

Sun Java System Web Server 6.1 Administrator’s Configuration File Reference

dbswitch.conf

  • Location: server_root/userdb/

  • Provides a list of authentication databases, and is used to check group membership for access control

  • Unchanged from Web Server 6.0

Sun Java System Web Server 6.1 Administrator’s Configuration File Reference

magnus.conf

  • Location: server-id/config

  • Defines server plug-ins library initialization and server parameters

  • Copied into the new server root director, during migration.

  • During migration, Sun Java System Web Server 6.1 loads built-in load module functions from the new installation directory while custom modules continue to be loaded from the old installation directory.

  • Some magnus.conf directives that were supported in Web Server 6.0 are deprecated in 6.1.

Sun Java System Web Server 6.1 Administrator’s Configuration File Reference, for a description of supported and deprecated directives.

Sun Java System Web Server 6.1 NSAPI Programmer’s Guide, for a description of the Init directives.

mime.types

  • Location: install-dir/config/

  • Contains mappings between MIME (Multipurpose Internet Mail Extensions) types and file extensions

  • During migration, the mime.types file of the old instance in the /config directory is migrated into the new server-root/server-instance/config directory.

  • Non-default mime.types (mime1.types, mime2.types, and so on) present in old server- instance/config directory which are listed in the MIME element of server.xml are migrated into the new server-instance/config directory.

Sun Java System Web Server 6.1 Administrator’s Configuration File Reference

nsfc.conf

  • Location: server_root/https-admserv/config/

  • Sets file cache parameters.

  • Unchanged from Web Server 6.0

Sun Java System Web Server 6.1 Administrator’s Configuration File Reference

obj.conf

  • Location: install-dir/config/

  • Contains instructions for the server on how to handle HTTP requests from clients and service web server content such as native server plugins and CGI programs.

  • Configured per virtual server class and named in the format <vs-name>.obj.conf

  • New directives and functions added in Web Server 6.1 to configure filters and WebDAV.

  • Search, JSP092, and Webpub objects are not migrated.

Sun Java System Web Server 6.1 NSAPI Programmer’s Guide

server.xml

  • Location: instance-dir/config/

  • Contains most of the server configuration.

  • During migration, the server.xml file created in the new Web Server 6.1 instance contains information from the following files:- old server.xml file- web-apps.xml- start-jvm- jvm12.conf

Sun Java System Web Server 6.1 Administrator’s Configuration File Reference

*.clfilter

  • obj.conf.clfilter

  • magnus.conf.clfilter

  • server.xml.clfilter

  • Location: instance-dir/config/

  • Legacy .clfilter files, for example, web-apps.xml.clfilter are not migrated.

Sun Java System Web Server 6.1 Administrator’s Guide

secmod.db 

  • Imported certificates and keys for external hardware accelerators are stored in the secmod.db file, which is generated when the PKCs#11module is installed.

  • Overwritten during migration

Sun Java System Web Server 6.1 Administrator’s Guide

  • access log

  • error log

  • Server log files records activity of the Server.

  • During migration, new access logs are created.

  • Error logs in 6.0 server-instance/logs directory are copied to the server-instance/logs in 6.1.

Sun Java System Web Server 6.1 Administrator’s Guide

Configuration Files Removed in Sun Java System Web Server 6.1

The following configuration files are no longer supported and are removed during migration:

Connection Groups Settings

Every listen socket in the Sun Java System Web Server 6.0 has at least one connection group associated with it. When you created a listen socket, a connection group was also created, which contained the default virtual server you specified for the listen socket.

In Sun Java System Web Server 6.1, the connection group functionality is dropped. The virtual server is now directly bound to a listen socket. During migration, each connection group is migrated to an LS (listen socket) element. Each LS element contains attributes derived from both the connection group’s and the listen socket’s attributes.

Cron Control

Cron file names are changed in Sun Java System Web Server 6.1. The Web Server 6.0 file ns-cron.conf, is called schedulerd.conf in Sun Java System Web Server 6.1, and the version 6.0 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 not migrated to Sun Java System Web Server 6.1during migration. If you need to preserve these, copy the cron settings for the migrated instance to the cron files.

Java Migration

Unlike in the 6.0 release, Java is enabled by default in the Sun Java System Web Server 6.1. In the Sun Java System Web Server 6.1, you can enable and configure Java for every instance of the server. Unlike in the previous 6.0 release which supported an installation-wide configuration of the JDK.

During migration you can choose to install either the JDK that is bundled with Sun Java System Web Server 6.1 (JDK 1.4.2_13) or install a custom JDK. If you install the server with a custom JDK, the javahome setting of the migrated instance refers to the custom JDK path (taken from the javahome setting of the Administration Server). Otherwise the javahome setting points to /bin/https/jdk.

Sun Java System Web Server 6.1 supports the Java Development Kit (JDK) version 1.4 and above. It does not support a standalone Java Runtime Environment (JRE).

In the Sun Java System Web Server 6.1 this data is stored in the server.xml file.

The JAVA element in the new server.xml file contains the JDK configuration information copied from the start-jvm file of the migrated instance.

The JVMOPTIONS element in the new server.xml file contains the JVM options information from the jvm12.conf file of the migrated instance.

If the previous version of your server was configured to use JDK 1.4.1 or above, the NSES_JDK path from the server’s start-jvm file is copied into the Sun Java System Web Server 6.1 server.xml file, otherwise, the JDK path points to server-root/bin/https/jdk, which is the default JDK path in Sun Java System Web Server 6.1.

For information about the mapping of the start-jvm and jvm12.conf files with the server.xml file in Sun Java System Web Server 6.1, refer to the Sun Java System Web Server 6.1 Administrator’s Configuration File Reference.

Java Server Pages

Sun Java System Web Server 6.1 supports Java Server Pages (JSP) 1.2 specification. The JSP092 object representing JSP version 0.92 is no longer supported in Sun Java System Web Server 6.1 and is deleted during migration.

Style examples using JSP 1.2 can be found in the following directory: server_root/plugins/servlets/examples/web-apps/.

Legacy Servlets

Sun Java System Web Server 6.1 supports the Servlet 2.3 specification.

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.x legacy-style servlets to the web applications structure in Sun Java System Web Server 6.1, see the Sun Java System Web Server 6.1 SP10 Programmer’s Guide to Web Applications.

Search Migration

Because the search engine used in Sun Java System Web Server 6.0 is 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, you create and configure new search collections and indexes. For more information, see the Sun Java System Web Server 6.1 SP10 Administrator’s Guide.

Security

Sun Java System Web Server provides new flat file authentication and closer integration of native access control with web application security constraints. However, core authentication and authorization support is the same as in the version 6.0 release.

Sun Java System Web Server 6.1, apart from providing ACL-based authentication, also leverages the security model defined in the J2SE Specification to provide several features that help you develop and deploy secure Java Web applications. The J2SE/Servlet-based access control infrastructure relies on the use of security realms.

In Sun Java System Web Server 6.1, authentication is performed by Java security realms which are configured through AUTHREALM entries in the server.xml file. In case any such rules have been set, authorization is performed by access control rules in the deployment descriptor file web.xml, .

For more information about security-related features in Sun Java System Web Server 6.1, see the Sun Java System Web Server 6.1 SP10 Administrator’s Guide and the Sun Java System Web Server 6.1 SP10 Programmer’s Guide.

Session Managers

The Simple Session Manager and JDBC Session Manager that were deprecated in the version 6.0 release of Sun Java System Web Server are not supported in the 6.1 release.

Sun Java System Web Server 6.1 provides the following session management options:

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. Sun recommends these links should not transverse any symbolic links.

Web Applications

In the 6.0 version of the Web Server, information pertaining to web applications was stored in the server.xml file and the web-apps.xml file. The web-apps.xml file is not supported in Sun Java System Web Server 6.1, and web application data is now stored in the following files:

Web Publishing Using WebDAV

Sun Java System Web Server 6.1 introduces a new feature, web publishing through WebDAV (Web Distributed Authoring and Versioning), a protocol that enables in-place collaborative web publishing.

WebDAV functionality is configured by extending the VS element in the server.xml file to include two new elements, DAV and DAVCOLLECTION.

New functions have been added to the obj.conf file to support WebDAV functionality as an NSAPI plug-in.

For more information on the WebDAV feature, see the Sun Java System Web Server 6.1 SP10 Administrator’s Guide. For more information on WebDAV functions in the obj.conf file, see the Sun Java System Web Server 6.1 SP10 NSAPI Programmer’s Guide. For more information on WebDAV-related elements in the server.xml file, see the Sun Java System Web Server 6.1 SP10 Administrator’s Configuration File Reference.