This chapter contains migration information, the changes that take place when you migrate the Web Server from version 6.0 to 6.1.
This chapter contains the following information:
To upgrade Sun Java System Web Server 6.1, which is a part of the Sun Java Enterprise System, use the patchadd command.
You can migrate the following iPlanet Web Server 6.0 information to work with Sun Java System Web Server 6.1.
Document roots
Configuration styles information
Virtual server settings
Access Control List (ACL) information
Secure Socket Layer (SSL) information
Certificates and keys
NSAPI information
JavaServer Pages (JSPs)
Server Side HTML (SHTML)
Simple Network Management Protocol (SNMP) settings (the snmp.conf file)
The file cache tuning configuration settings (the nsfc.conf file)
Shut down the server instances before migrating.
In the Administration Server page, click the Migrate Servers tab.
Click Migrate Server.
Enter the server root of the server from which you want to migrate and click Search. For example:
/usr/netscape/server4
C:\netscape\server4
Sun Java System Web Server detects whether there are server instances installed in the directory you specified and displays the servers you can migrate in a section of the page called “Installed Servers.” You cannot migrate the Administration Server.
Choose a server from the drop-down list and click Migrate.
In the new Migration parameters window that is launched, specify the migration parameters.
The sections on the form that you see depend upon which features your 6.0 Web Server is using and which components you installed. The following sections of parameters are possible:
Click Migrate.
The Migrate server_name page appears. It shows the results of the migration, including the parameters successfully migrated and the parameters that you need to migrate manually. It also shows any features of your 6.0 server that are not supported in 6.1.
If you get fatal errors during migration, migrating continues. The results page shows what errors occurred and you can use this information to troubleshoot.
Click Configure Migrated Server to configure your migrated server instance in the Server Manager, or click Close to close the migration window.
The migration process does not migrate the following:
See Legacy Servlets for more information.
Search collections and indexes
See Search Migration for more information.
See Command Line Scripts for more information.
See Cron Control for more information.
See Configuration Files for more information.
Some configuration files
See the sections Configuration Files and Configuration Files Removed in Sun Java System Web Server 6.1.
Simple Session Manager and JDBC Session Manager
See Session Managers for more information.
Connection Group settings in server.xml
See Connection Groups Settings for more information.
See Cgistub Directory for more information.
When you migrate information from web server 6.0 to 6.1, changes are made in the following areas, listed alphabetically:
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.
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:
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: |
---|---|---|
|
|
Access Control Programmer’s Guide |
|
Sun Java System Web Server 6.1 Administrator’s Configuration File Reference |
|
|
Sun Java System Web Server 6.1 Administrator’s Configuration File Reference |
|
|
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. |
|
|
Sun Java System Web Server 6.1 Administrator’s Configuration File Reference |
|
|
Sun Java System Web Server 6.1 Administrator’s Configuration File Reference |
|
|
Sun Java System Web Server 6.1 NSAPI Programmer’s Guide |
|
|
Sun Java System Web Server 6.1 Administrator’s Configuration File Reference |
|
|
|
Sun Java System Web Server 6.1 Administrator’s Guide |
secmod.db |
|
Sun Java System Web Server 6.1 Administrator’s Guide |
|
|
Sun Java System Web Server 6.1 Administrator’s Guide |
The following configuration files are no longer supported and are removed during migration:
webpub.conf
webpub.conf.clfilter
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 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.
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.
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/.
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 SP8 Programmer’s Guide to Web Applications.
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 SP8 Administrator’s Guide.
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 SP8 Administrator’s Guide and the Sun Java System Web Server 6.1 SP8 Programmer’s Guide.
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:
PersistentManager, a provided session manager that uses a persistent data store
IWSSessionManager, a provided session manager that allows backward compatibility with any custom session managers you may have created using Sun Java System Web Server 6.0.
MMapSessionManager (UNIX Only), a provided persistent memory map (mmap) file based session manager that works in both single process and multi-process mode
The following API functions of the Sun Java System Web Server 6.1 session manager API are not implemented in Sun Java System Web Server 6.1:
SimpleSessionManager and JdbcSessionManager. Web Server 6.0 provided deprecated support to the SimpleSessionManager and JdbcSessionManager options, and implemented the same functionality through iWSSessionManager and JdbcStore, respectively. The SimpleSessionManager and JdbcSessionManager options are not supported in Sun Java System Web Server 6.1.
For more information about Session Managers, see the Sun Java System Web Server 6.1 SP8 Programmer’s Guide to Web Applications.
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.
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:
server.xml
web.xml
sun-web.xml
obj.conf
The VS (virtual server) element in the server.xml file in Sun Java System Web Server 6.1 now contains a WEBAPP (web application) element for every web application it hosts. The attributes of the WEBAPP element are consistent with the mechanism used in Web Server 6.0 to configure web applications and are dynamically reconfigurable, that is, they do not require a server restart in order for changes to be applied to the server instance.
For every web application, the deployment descriptor file, sun-web.xml, is created in the <web-application>/WEB-INF directory. The deployment descriptor file is based on the schema file, sun-web-app_2_3-1.dtd, which is compliant with the Servlet 2.3 specification. This schema file is also located in the <web-application>/WEB-INF directory.
If you have used the web-apps.xml file to tune certain server parameters in the 6.0 version of the Web Server, you would perform an identical function using the sun-web.xml deployment descriptor in Sun Java System Web Server 6.1. Following is an example reap interval which specifies the number of seconds between checks for expired sessions.
In Web Server 6.0:
<init-param> <param-name>reapInterval</param-name> <param-value>180</param-value> </init-param>
In Web Server 6.1:
<sun-web-app> ... <session-config> <session-manager> <manager-properties> <property name=”reapIntervalSeconds” value=”180”> </manager-properties> </session-manager> ... </session-config> ... </sun-web-app>
For more information on the deployment descriptor files supported in Sun Java System Web Server 6.1, see the Sun Java System Web Server 6.1 SP8 Programmer’s Guide to Web Applications.
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 SP8 Administrator’s Guide. For more information on WebDAV functions in the obj.conf file, see the Sun Java System Web Server 6.1 SP8 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 SP8 Administrator’s Configuration File Reference.