
Conguration Files Removed in Sun Java System Web Server 6.1
The following conguration les are no longer supported and are removed during migration:
■
rules.properties
■
context.properties
■
servlet.properties
■
start-jvm
■
jvm12.conf
■
web-apps.xml
■
web-apps.xml.clfilter
■
webpub.conf
■
webpub.conf.clfilter
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 specied 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 le names are changed in Sun Java System Web Server 6.1. The Web Server 6.0 le
ns-cron.conf, is called schedulerd.conf in Sun Java System Web Server 6.1, and the version
6.0 le 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 les.
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 congure Java for every instance of the
server. Unlike in the previous 6.0 release which supported an installation-wide conguration of
the JDK.
Overview of Changes in Sun Java System Web Server 6.1
Sun Java System Web Server 6.1 SP9 Installation and Migration Guide • February 200858
Commentaires sur ces manuels