Web Server Compatibility Issues

The new administrative interfaces introduced in Release 5 Web Server are not backwardly compatible with earlier administrative interfaces. This impacts the upgrade and redeployment of web applications (including, for example, Java ES components).

---

Caution –

Web Server 7.0 Update 1 has compatibility issues with Portal Server. On a Java ES 5 setup that has Portal Server on Web Server, upgrading Web Server to Java ES 5 Update 1 level renders Portal Server as unusable. Release 5U1 Web Server uses JSF 1.2. But JSF-Portlet bridge in Release 5 Portal Server does not support JSF 1.2. So Portal Server will not work. Do not upgrade Web Server to Release 5U1 in case you want to continue using Release 5 Portal Server.

If you have deployed Web Server 7.0 and Portal Server on Windows, contact Sun Support for more information on how to upgrade to Web Server 7.0 Update 1.

http://www.sun.com/support

---

In particular, Release 5 and Release 5U1 Web Server use defaults for instance directories and virtual server names different from earlier releases, as shown in the following table.

Table 5–3 Web Server Instance Directories and Virtual Server Names

Item	Java ES 4 Web Server 6.x Default	Java ES 5 Web Server 7.0 Default
Configuration name		hostName.domainName
Instance directory path	WebServer6-base\https-hostName.domainName	WebServer7-base\https-hostName.domainName
Virtual server name	https-hostName.domainName	hostName.domainName